◆ Asana

Schedule tasks with start and due dates

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 taskSchedule the 'Content Review' task for the blog post to start on October 25th and be due by…+
Schedule the 'Content Review' task for the blog post to start on October 25th and be due by October 27th, assigned to Liam.
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 schedule the 'User Acceptance Testing' phase for the new app, make sure the timeline…+
Before I schedule the 'User Acceptance Testing' phase for the new app, make sure the timeline is realistic. Factor in potential delays for bug fixes, allow for at least two rounds of feedback from the pilot users, and flag any dependencies that could bottleneck the process.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI need to schedule the 'Marketing Campaign Launch' tasks, but the creative team is behind, and…+
I need to schedule the 'Marketing Campaign Launch' tasks, but the dependencies are a mess.
I need to schedule the 'Marketing Campaign Launch' tasks, but the creative team is behind, and the ad platform needs three days to approve ads after submission. I'm afraid of committing to a launch date we can't hit, which will upset the buyer. I can't tell if I should push the launch or try to compress the creative phase. What's the best way to schedule these tasks to hit our target launch date without burning out the team or missing critical steps?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternDespite setting start and due dates, my scheduled tasks frequently slip, causing downstream…+
My scheduled tasks frequently slip, causing downstream delays and missed deadlines.
Despite setting start and due dates, my scheduled tasks frequently slip, causing downstream delays and missed deadlines for other teams. This makes our project timelines unreliable. What habit should I change when I schedule tasks so that they are more consistently completed on time, and I can better anticipate and communicate potential delays?
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.