◆ Asana

Export Asana data to PDF

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 taskGet a PDF of the 'Q4 Marketing Campaign' project for the leadership team meeting on Friday.…+
Get a PDF of the 'Q4 Marketing Campaign' project for the leadership team meeting on Friday. Make sure the task descriptions and due dates are visible, and include the completed tasks from last month.
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 send this 'Client Onboarding Redesign' project PDF to the new VP of Operations, make…+
Before I send this 'Client Onboarding Redesign' project PDF to the new VP of Operations, make it easy for her to grasp the critical path. Highlight overdue tasks and dependencies, and ensure the assignee names are clear. She'll be looking for potential bottlenecks.
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 client just asked for a project update on the 'Website Relaunch' project for their board…+
The client just asked for a project update in a format they can easily share, but I know the raw data is too overwhelming.
The client just asked for a project update on the 'Website Relaunch' project for their board meeting tomorrow, and I'm worried a standard export will just confuse them. They need a high-level overview, not every subtask. I can't tell them we're behind, but I need to show progress without overwhelming them with detail. What's the best way to package this for a quick, positive review without hiding critical information?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI spend hours every week re-formatting project data for different stakeholders – the executive…+
I keep losing time formatting project reports for different stakeholders every week.
I spend hours every week re-formatting project data for different stakeholders – the executive team wants a summary, the dev team needs granular detail, and clients want a high-level overview. It feels like I'm always starting from scratch, losing time and sometimes missing key details. What habit can I change to streamline how I present project progress to different audiences?
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.