◆ Asana

Collect stakeholder 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 taskCollect stakeholder feedback on the new onboarding flow from the product council meeting on…+
Collect stakeholder feedback on the new onboarding flow from the product council meeting on Friday. Create a single feedback task assigned to me, with subtasks for collecting notes from product council, support, sales, and legal. Set the feedback due date to next Wednesday, and request a decision from Priya in product on whether to accept each suggested change by Friday the week after.
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 send the feedback request, make it simple for reviewers to act: lead with the change…+
Before I send the feedback request, make it simple for reviewers to act: lead with the change summary and the expected impact, provide a checkbox list of proposed accept/reject items with a short reason field, and flag any comments that require a compliance review. Highlight which items need Priya's decision and which can be handled by the product owner.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSupport wants an extra confirmation step, sales says remove friction, and legal asks for copy…+
Stakeholders returned conflicting feedback on the same flow element.
Support wants an extra confirmation step, sales says remove friction, and legal asks for copy changes that increase friction. I have Priya, the support lead Jonah, and legal counsel Asha involved. I'm stuck deciding which feedback to prioritize and I cannot tell whether any choice will break adoption targets. How do I quickly weigh these conflicting inputs and recommend the next move that balances risk and conversion?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release we get a flood of stakeholder comments that turn into slow, incremental edits and…+
Feedback cycles create endless minor edits and no decisive outcomes.
Every release we get a flood of stakeholder comments that turn into slow, incremental edits and no clear decisions, which costs us time and blunts product momentum. What process habit should we introduce to keep feedback decisive, who needs to own it, and a short template for collecting and ruling on feedback so decisions happen on schedule?
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.