◆ Asana

Present drafts for feedback

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGet feedback on the Q3 marketing campaign draft from Sarah, David, and the legal team. Set the…+
Get feedback on the Q3 marketing campaign draft from Sarah, David, and the legal team. Set the review deadline for next Tuesday, October 24th, and make sure their comments are consolidated for me.
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 I present the Q3 marketing campaign draft to the executive team, make it easy for Sarah,…+
Before I present the Q3 marketing campaign draft to the executive team, make it easy for Sarah, David, and legal to give clear feedback. Highlight the sections I'm most unsure about, and ask them to flag any potential compliance issues or messaging inconsistencies.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSarah just said the Q3 campaign draft is 'too risky' for our current market, but David thinks…+
Sarah just said the campaign draft is 'too risky' for Q3, but David thinks it's 'bold and necessary.'
Sarah just said the Q3 campaign draft is 'too risky' for our current market, but David thinks it's 'bold and necessary' for growth. Legal hasn't weighed in yet. I'm afraid if I push it, I'll alienate Sarah, but if I pull back, David will feel ignored. What's the best way to get actionable feedback without picking a side, especially before legal reviews it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWhen we present drafts for feedback, comments always come in scattered across emails and…+
Team feedback on drafts always comes in scattered, making revisions a nightmare.
When we present drafts for feedback, comments always come in scattered across emails and meetings, making consolidated revisions a nightmare and delaying launch. I lose hours trying to track everything down. What habit should I change to ensure feedback is always organized and actionable from the start, so I can make revisions efficiently?
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.