◆ Asana

Coordinate cross-team work

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 taskCoordinate the cross-team work needed for the Q4 microsite: engineering for backend endpoints…+
Coordinate the cross-team work needed for the Q4 microsite: engineering for backend endpoints (owner Ravi), design for UI (owner Ana), content for copy (owner Mei), and analytics for tracking (owner Lian). Create tasks with clear dependencies: design first draft due Sept 10, engineering API ready Sept 20, content draft Sept 25, integration complete Oct 2, and launch Oct 6. Add weekly syncs Tuesdays at 10 a.m. and document decision owner for any scope changes.
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 circulate this coordination plan to stakeholders, make it easy for each team lead to…+
Before I circulate this coordination plan to stakeholders, make it easy for each team lead to see only what they must deliver: summarize each lead's responsibilities, surface cross-team blockers with owners, and flag any handoffs that lack a named approver. Highlight where work requires two-party sign-off and the acceptable SLAs for responses.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentAna in design handed over a layout that depends on a backend flag Ravi hasn't implemented and…+
Design delivered a layout that needs a backend flag we don't yet have.
Ana in design handed over a layout that depends on a backend flag Ravi hasn't implemented and hasn't budgeted. I have Ravi, Ana, and the product manager Mei in the thread. I'm afraid integration will slip and launch credibility will suffer, but I don't know whether the flag is essential or a nice-to-have. How should I triage this: fast technical assessment, stakeholder negotiation, and the recommended decision path for whether to scope the flag now or adjust the design?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several microsites we lose momentum at the design-to-engineering handoff because unclear…+
Handoffs between design and engineering frequently cause hold-ups.
Across several microsites we lose momentum at the design-to-engineering handoff because unclear acceptance criteria lead to rework. Which habit should we adopt to reduce rework, who must own the change, and a short enforcement checklist that fits our Tuesday syncs and preserves delivery speed?
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.