◆ Asana

Manage team workloads

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 taskShow me the current workload for the marketing team for next week. I need to see who is over…+
Show me the current workload for the marketing team for next week. I need to see who is over capacity.
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 present the marketing team's workload to Sarah, make sure it's clear and actionable.…+
Before I present the marketing team's workload to Sarah, make sure it's clear and actionable. Highlight who is genuinely overloaded, suggest tasks that could be reallocated, and flag any upcoming deadlines that are at risk. I need to come with solutions, not just problems.
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 workload report for the design team shows everyone is at 75% capacity next week, but I'm…+
The workload report looks balanced, but some team members are complaining of burnout.
The workload report for the design team shows everyone is at 75% capacity next week, but I'm hearing whispers of burnout and people staying late. I'm afraid to challenge the report directly without solid evidence, but I also can't ignore the team's stress. What factors might the report be missing that could explain this discrepancy, and how can I get a more accurate read on true capacity without micromanaging or causing more stress?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself surprised by team burnout or missed deadlines, even when workload reports…+
Consistently misjudging team capacity based on reports, leading to burnout or missed deadlines.
I often find myself surprised by team burnout or missed deadlines, even when workload reports look fine. It feels like I'm always reacting. What's a proactive habit I can adopt to better understand and anticipate my team's actual capacity and potential bottlenecks, beyond just looking at the numbers, so I can prevent issues before they escalate?
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.