◆ Asana

Create milestones for launches

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 taskI need milestones created for the July 21 product launch and the staggered beta release on…+
I need milestones created for the July 21 product launch and the staggered beta release on August 4. Make a milestone for feature freeze on June 30, QA complete on July 12, marketing content live on July 18, and launch on July 21. Add owners: Elena for engineering, Marco for QA, Priya for content, and Tess for launch ops. Put the milestones on the project timeline in that order and check no dates clash with existing sprints this quarter.
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 show this to the launch team, make the milestone list easy to scan: surface the launch…+
Before I show this to the launch team, make the milestone list easy to scan: surface the launch date and the single biggest risk next to each milestone, bold the owner, and add a one-line acceptance criterion for each (what counts as 'done'). Flag any milestone that depends on external vendors or on decisions not yet made.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentEngineering tells me a key API will likely slip past June 30. I have Elena, the release…+
I just learned engineering may miss feature-freeze.
Engineering tells me a key API will likely slip past June 30. I have Elena, the release engineer, and Priya, the product lead, on the thread. I am worried a slip forces QA into a weekend and breaks content timing; I cannot tell whether engineering already committed the delay to stakeholders. How should I assess whether to move the milestone now or keep the current date and plan contingency weekend QA? Recommend the quickest diagnosis and the best next step.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last six launches, we scramble because milestones shift in the final fortnight and we…+
Milestones routinely shift in the final two weeks before launch.
Over the last six launches, we scramble because milestones shift in the final fortnight and we lose control of QA and content timing. Which habit change would reduce last-minute shifts, who must own it, and a short checklist to enforce that habit across teams? Focus on practices that reduce surprise slips and preserve credibility with stakeholders.
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.