◆ Asana

Ensure projects stay on schedule

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 taskFor the 'Q4 Marketing Campaign' project, move the 'Ad Creative Approval' task from 'In Review'…+
For the 'Q4 Marketing Campaign' project, move the 'Ad Creative Approval' task from 'In Review' to 'Completed' and notify Sarah that it's done.
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 acceptReview the 'System Migration' project schedule. Find any tasks that are at risk of slipping…+
Review the 'System Migration' project schedule. Find any tasks that are at risk of slipping past their due dates and flag them for my attention. Suggest ways to reallocate resources or adjust dependencies to get them back on track, so we don't miss the January 15th go-live.
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 lead developer just told me he needs another week for the 'API Integration' task, which…+
The lead developer just told me he needs another week for the 'API Integration' task, which pushes our UAT start date.
The lead developer just told me he needs another week for the 'API Integration' task, which pushes our UAT start date. The sales team is already counting on this feature for their Q3 targets, and I'm afraid of losing their trust if we delay. I'm not sure if I should push back on the developer or tell sales the bad news. What are the immediate ripple effects of this delay, and what's the best way to communicate this to stakeholders without causing panic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternDeadlines often get missed because team members don't update their task status regularly,…+
Deadlines often get missed because team members don't update their task status regularly, making it hard to see true progress.
Deadlines often get missed because team members don't update their task status regularly, making it hard to see true progress. I spend too much time chasing updates. I need a better habit for ensuring everyone keeps their tasks current, so I can accurately report project health to leadership and intervene before things go off track.
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.