◆ Asana

Export all 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 taskExport all projects, including all tasks and subtasks, into a CSV file for…+
Export all projects, including all tasks and subtasks, into a CSV file for archiving.
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 acceptI need to export all projects for our annual audit. Before I do, suggest how to include custom…+
I need to export all projects for our annual audit. Before I do, suggest how to include custom fields like 'Budget Owner' and 'Risk Level' in the export, and format it so it's easy for the auditors to sort and review by project status.
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 CEO just asked for a comprehensive overview of all active projects, including their current…+
The CEO just asked for a comprehensive overview of all active projects, including their current status and key milestones, for a board meeting in two hours.
The CEO just asked for a comprehensive overview of all active projects, including their current status and key milestones, for a board meeting in two hours. I'm afraid of missing a critical project or misrepresenting its status, which would be a huge hit to my credibility. I can't tell him I need more time. What's the likely diagnosis of what the board really wants to see, and what's the best next move to get this data quickly and accurately?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently need to provide high-level summaries of all projects, but generating them is…+
I frequently need to provide high-level summaries of all projects, but generating them is always a scramble.
I frequently need to provide high-level summaries of all projects, but generating them is always a scramble, pulling data from various views and manually aggregating. This makes me look unprepared and wastes valuable time before key meetings. What habit should I change to make exporting and summarizing project data faster and more consistent?
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.