◆ Asana

Move tasks

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 taskMove the 'Finalize Q1 Report' task from the 'In Progress' column to 'Ready for Review' so Sarah…+
Move the 'Finalize Q1 Report' task from the 'In Progress' column to 'Ready for Review' so Sarah knows it's her turn.
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 acceptThe 'Website Redesign' project is falling behind. Show me all tasks currently in the 'Design'…+
The 'Website Redesign' project is falling behind. Show me all tasks currently in the 'Design' phase that have a due date within the next two weeks, and then move them into the 'Urgent' section of the 'Design' project board, so the team can prioritize.
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 escalated a critical bug, and I need to pull a developer off their current task…+
The client just escalated a bug, and I need to pull a developer off their current task to address it immediately, but I'm worried about disrupting their existing workflow.
The client just escalated a critical bug, and I need to pull a developer off their current task to address it immediately, but I'm worried about disrupting their existing workflow and missing other deadlines. I can't tell them to just drop everything without a clear plan. What's the likely diagnosis for how to re-prioritize this developer's tasks without causing a domino effect, and what's the best next move to communicate this change effectively?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternTasks frequently get stuck in the wrong project or section, making it hard to find them later,…+
Tasks frequently get stuck in the wrong project or section, making it hard to find them later.
Tasks frequently get stuck in the wrong project or section, making it hard to find them later, especially when new team members are involved. This leads to missed deadlines and wasted time searching. What habit should I change to ensure tasks are consistently placed in the correct location from the start, so everyone knows where to look?
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.