◆ Asana

Create project reporting dashboards

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 new project reporting dashboard for the 'Website Redesign' project that shows task…+
Create a new project reporting dashboard for the 'Website Redesign' project that shows task completion status and overdue tasks.
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 share the 'Q3 Performance' dashboard with the executive team, make it easy for them to…+
Before I share the 'Q3 Performance' dashboard with the executive team, make it easy for them to grasp the key takeaways. Highlight projects at risk, show budget vs. actual spend clearly, and flag any areas where we're significantly off track from our goals.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI need to create a project reporting dashboard for the 'New Product Development' project for…+
I need to create a dashboard for the 'New Product Development' project, but I don't know what metrics truly matter.
I need to create a project reporting dashboard for the 'New Product Development' project for the CEO. I'm afraid of showing irrelevant data or, worse, missing a critical metric that would indicate a problem. I can't tell if they care more about budget, timeline, or resource allocation at this stage. What are the most impactful metrics I should include, and how should I present them to give a clear, actionable overview?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy project dashboards are often ignored or misunderstood by stakeholders, leading to repeated…+
My project dashboards are often ignored or misunderstood by stakeholders.
My project dashboards are often ignored or misunderstood by stakeholders, leading to repeated questions and a lack of confidence in our progress. This means I spend too much time explaining data instead of moving projects forward. What habit should I change when I create project reporting dashboards so that they are consistently clear, actionable, and effectively communicate project status to diverse 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.