◆ Asana

Avoid common mistakes in planning

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 taskDraft a project plan for the 'Q3 Marketing Campaign' project. Include phases for ideation,…+
Draft a project plan for the 'Q3 Marketing Campaign' project. Include phases for ideation, content creation, review, and launch. Assign initial tasks to Sarah for ideation and Mark for content creation, with a target launch date of September 15th.
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 finalize this project plan for the 'New Product Launch', help me identify potential…+
Before I finalize this project plan for the 'New Product Launch', help me identify potential bottlenecks or overlooked dependencies. I want to avoid the usual scramble we have at the end, especially with the engineering team's workload. Flag anything that typically derails a launch like this.
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 just pushed back on our proposed timeline for the 'Website Redesign', saying it's…+
The client just pushed back on our proposed timeline for the 'Website Redesign', saying it's too aggressive.
The client just pushed back on our proposed timeline for the 'Website Redesign', saying it's too aggressive. I'm afraid if we stretch it too much, we'll lose momentum and exceed the budget. I can't tell if they genuinely need more time or if they're just negotiating. What's the best way to respond to this without committing to an unfeasible extension or alienating them?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur project plans consistently underestimate the time needed for client feedback and internal…+
Our project plans consistently underestimate the time needed for client feedback and internal reviews.
Our project plans consistently underestimate the time needed for client feedback and internal reviews, pushing deadlines and stressing the team. I need to change how I estimate these phases. What habit can I adopt to build more realistic buffers into our schedules from the start, especially for the 'Website Redesign' project?
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.