◆ Asana

Study data to draw conclusions

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 taskGet me the key takeaways from the Q3 customer churn report and the Q3 new lead generation…+
Get me the key takeaways from the Q3 customer churn report and the Q3 new lead generation report, focusing on any overlap or conflicting trends between them. I need to present this to the leadership team by end of day Friday.
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 these Q3 reports, help me find the 'so what' for our product team. Highlight…+
Before I present these Q3 reports, help me find the 'so what' for our product team. Highlight the data points that directly suggest a change to our product roadmap or feature prioritization, and flag any areas where the data is inconclusive for product decisions.
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 sales team is disputing the churn report's conclusions, saying our data doesn't match what…+
The sales team just pushed back hard on the Q3 churn analysis, saying it doesn't reflect their on-the-ground experience.
The sales team is disputing the churn report's conclusions, saying our data doesn't match what they're seeing in the field. I'm afraid if I push back too hard, they'll disengage, but if I don't, leadership will question the data's validity. I can't tell if their concerns are legitimate or just resistance to bad news. What's the likely diagnosis here, and what's the best next move to get to a shared understanding before the Friday meeting?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find myself spending too much time trying to translate data findings into…+
I always struggle to translate raw data into actionable insights for different departments.
I consistently find myself spending too much time trying to translate data findings into actionable insights that resonate with different departments, like sales versus product. My conclusions often feel generic, and I lose credibility when I can't speak directly to their specific needs. What habit should I change to more effectively tailor my data analysis for diverse audiences?
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.