◆ Asana

Export tasks

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 taskExport all tasks from the 'Product Launch' project that are assigned to Mark and due next week,…+
Export all tasks from the 'Product Launch' project that are assigned to Mark and due next week, into a CSV.
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 overdue tasks from the 'Client Implementations' project. Before I do,…+
I need to export all overdue tasks from the 'Client Implementations' project. Before I do, suggest how to include the project name for each task and sort them by client priority, so I can easily follow up with the relevant account managers.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur main vendor just had a system outage, impacting hundreds of tasks across multiple projects,…+
Our main vendor just had a system outage, impacting hundreds of tasks across multiple projects.
Our main vendor just had a system outage, impacting hundreds of tasks across multiple projects, particularly those related to 'External Integrations'. I'm afraid of missing critical dependencies or not communicating the impact quickly enough to the affected teams, which could delay our Q4 deliverables. I can't tell the executive team we don't have a clear picture yet. What's the likely diagnosis of the most immediate risk, and what's the best next move to quickly identify all impacted tasks and their immediate owners?
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 losing time trying to pull specific task lists for individual team members or specific…+
I keep losing time trying to pull specific task lists for individual team members or specific project phases.
I keep losing time trying to pull specific task lists for individual team members or specific project phases, especially when a stakeholder asks for an ad-hoc report. This makes me feel reactive and less in control of the project narrative. What habit should I change to make exporting targeted task data quicker and more predictable, so I can respond to requests efficiently?
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.