◆ Asana

Resolve personnel problems during production

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 new task 'Review Q3 Performance Report' to David, with a due date of next Tuesday.…+
Assign the new task 'Review Q3 Performance Report' to David, with a due date of next Tuesday. Make sure it's dependent on Sarah completing 'Compile Q3 Sales Data' by Monday.
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 acceptWhen I assign new tasks to team members, I need a quick way to see if they're already…+
When I assign new tasks to team members, I need a quick way to see if they're already overloaded. Before assigning 'Marketing Campaign Brainstorm' to Maria, show me her current workload for the next two weeks and suggest if someone else might be a better fit.
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's pulling two engineers off the 'Website Redesign' project…+
The lead developer just told me he's pulling two engineers off the 'Website Redesign' project for an urgent client fix, and he can't give me a firm return date. I'm afraid this will blow our launch date, and I can't tell the client yet. What's the most realistic impact on our timeline, and who should I notify first?
The lead developer just told me he's pulling two engineers off the 'Website Redesign' project for an urgent client fix, and he can't give me a firm return date. I'm afraid this will blow our launch date, and I can't tell the client yet. What's the most realistic impact on our timeline, and who should I notify first?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy team members often miss critical dependencies, causing delays and rework because they don't…+
Team members often miss critical dependencies, causing delays and rework.
My team members often miss critical dependencies, causing delays and rework because they don't see the full picture. What habit should I change in how I set up new projects to make sure everyone understands how their work impacts others down the line?
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.