◆ Asana

Restore Asana projects

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 taskRestore the 'Website Redesign Phase 2' project from the backup file…+
Restore the 'Website Redesign Phase 2' project from the backup file 'WebsiteRedesign_2024-09-28.zip' located in 'Project Backups/September 2024'. Make sure it's visible to the entire design team.
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 acceptWe need to restore the 'Client Onboarding Flow' project. Use the backup from last Tuesday, but…+
We need to restore the 'Client Onboarding Flow' project. Use the backup from last Tuesday, but only bring back the tasks assigned to Maria and David that were due in October. Don't overwrite anything currently marked 'Completed' if it's already there.
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 'Compliance Audit Prep' project was accidentally deleted by a new team member, and the…+
A critical project was accidentally deleted, and I have a backup, but I'm unsure of the best way to restore it without causing more problems.
The 'Compliance Audit Prep' project was accidentally deleted by a new team member, and the audit is next week. I have a backup from yesterday, but I'm worried about restoring it and creating duplicate tasks or overwriting recent progress on other linked projects. What's the safest way to get the project back online quickly, ensuring minimal disruption to other work and that the team sees the correct version?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWhen I need to restore a project, I often end up bringing back too much or not enough, creating…+
I often struggle to restore specific parts of a project without affecting the whole.
When I need to restore a project, I often end up bringing back too much or not enough, creating confusion for the team. I lose time sorting through duplicates or missing pieces. What habit can I change to make restoring specific tasks or sections of a project more precise and less disruptive for everyone involved?
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.