◆ Asana

Manage proofing and QA platforms

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Asana tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up a new proofing workflow for the 'Q3 Marketing Campaign' assets. Add Maria and John as…+
Set up a new proofing workflow for the 'Q3 Marketing Campaign' assets. Add Maria and John as reviewers for the banner ads, with a deadline of Wednesday. Ensure the copy review happens before the design review.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we launch the 'Website Redesign' QA, make it robust. Include distinct stages for…+
Before we launch the 'Website Redesign' QA, make it robust. Include distinct stages for functional testing, mobile responsiveness, and content accuracy. Assign specific sections to Emily for content and Carlos for functionality, so nothing slips through the cracks.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe client, Acme Corp, just returned the 'Annual Report' brochure proof with five last-minute,…+
The client just sent back the final brochure proof with five new, critical changes, but the printer needs final files by end of day.
The client, Acme Corp, just returned the 'Annual Report' brochure proof with five last-minute, non-negotiable text changes. It's 2 PM, and the printer needs the final, approved PDF by 5 PM today, Friday. Our usual QA process takes at least two hours with multiple eyes. I'm worried we'll either miss the print deadline or introduce new errors under pressure. What's the best way to get these changes implemented and approved quickly without risking a costly reprint?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOn nearly every project, small typos or formatting issues slip through our proofing and QA…+
We frequently find minor errors in live content that were missed in proofing, impacting our credibility.
On nearly every project, small typos or formatting issues slip through our proofing and QA platforms, only to be caught by users after content goes live. This makes us look unprofessional. What habit should I change in how we structure our proofing rounds or assign reviewers to catch these details before they become public-facing problems?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Asana's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.