◆ Asana

Create a project transition plan

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 taskCreate a project transition plan for the 'Phoenix' project. Key phases are documentation…+
Create a project transition plan for the 'Phoenix' project. Key phases are documentation handover, team debrief, client communication, and final archiving. Assign documentation to Sarah, debrief to Mark, client comms to me, and archiving to David. Set a deadline of October 31st for all phases.
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 present this project transition plan to the client, make it more reassuring and…+
Before I present this project transition plan to the client, make it more reassuring and professional. Highlight the key benefits of a smooth handover, emphasize continuity, and ensure all potential client concerns about data access or ongoing support are clearly addressed.
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 for the 'Orion' project just announced they're leaving in two weeks, and we…+
The lead developer for the 'Orion' project just announced they're leaving in two weeks, and we have no clear transition plan.
The lead developer for the 'Orion' project just announced they're leaving in two weeks, and we have no clear transition plan. The project is critical and mid-flight. I'm afraid we'll lose vital institutional knowledge and the project will stall. I can't extend their notice period. What's the likely diagnosis for why this transition wasn't planned, and what's the best next move to minimize disruption and capture their knowledge before they go?
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 burned by key personnel leaving projects without adequate knowledge transfer or…+
I keep getting burned by key personnel leaving projects without adequate knowledge transfer or a clear handover strategy.
I keep getting burned by key personnel leaving projects without adequate knowledge transfer or a clear handover strategy, causing delays and rework. It feels like we're always scrambling when someone departs. What habit should I change to ensure project transitions, especially for key roles, are proactively planned and documented, rather than a last-minute crisis?
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.