◆ Asana

Oversee project development

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 taskAssign the 'Website Redesign' project to Maria as the lead, set the due date for October 27th,…+
Assign the 'Website Redesign' project to Maria as the lead, set the due date for October 27th, and create these three subtasks: 'Content Review', 'Design Mockups', and 'Developer Handoff'.
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 we kick off the 'New Product Launch' project, set up the project plan so it's easy for…+
Before we kick off the 'New Product Launch' project, set up the project plan so it's easy for the marketing team to see their deadlines and for engineering to track their dependencies. Make sure the executive update view highlights progress against the overall timeline.
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 the 'Mobile App Update' project, saying they need it by December…+
The client just pushed back on the timeline for the 'Mobile App Update' project, saying they need it by December 1st, not December 15th.
The client just pushed back on the 'Mobile App Update' project, saying they need it by December 1st, not December 15th. My team is already stretched thin, and I'm worried about burnout if we try to accelerate. I can't tell the client we're understaffed. What's the likely impact on other projects if we try to hit this new date, and what's the best way to negotiate without revealing our internal constraints?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting blindsided by small tasks that weren't in the original project plan, causing…+
I keep getting blindsided by small tasks that weren't in the original project plan, causing delays and forcing weekend work.
I keep getting blindsided by small tasks that weren't in the original project plan, causing delays and forcing weekend work. This happens on almost every project. I need a better habit for capturing all the little details and potential blockers upfront, before they become urgent problems, so we don't scramble at the last minute.
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.