◆ Asana

Balance team assignments

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 taskThe design sprint starts Monday and three copywriters and two designers are double-booked.…+
The design sprint starts Monday and three copywriters and two designers are double-booked. Redistribute the five tasks so no one exceeds 30 hours this week, assign a primary owner for each task, and mark which can be pushed to next week. Confirm with Priya and Theo before finalizing.
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 message the team, make it obvious who is overloaded. Show total hours per person, flag…+
Before I message the team, make it obvious who is overloaded. Show total hours per person, flag tasks causing conflicts, suggest two alternate reassignment plans (one that keeps skill match, one that prioritizes availability), and list tasks safe to delay without impacting the launch on Friday.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentWe have a Friday launch, designers Maya and Connor are both primary on the critical hero mock…+
I just noticed two designers are assigned to the same critical mock.
We have a Friday launch, designers Maya and Connor are both primary on the critical hero mock and each already has 18 hours booked. I cannot tell whether Maya can drop a lower-priority task without breaking her other deliverable because she’s handling client calls. What’s the most likely safe reassignment and the best message to get consent quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery sprint I end up reassigning work the day before launch because we underestimated design…+
Recurring last-minute overloads before launches.
Every sprint I end up reassigning work the day before launch because we underestimated design effort and left approvals late. Which habit should I change to stop firefighting: stricter upfront capacity planning, mandatory task time estimates from assignees, or a deadline buffer? Recommend the single habit that will yield the biggest reduction in last-minute reassignments and how to embed it into our sprint kickoff routine.
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.