◆ Asana

Track task completion progress

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
See the prompt↓All Asana tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe campaign backlog shows 46 open tasks and the weekly status meeting is in two hours. Produce…+
The campaign backlog shows 46 open tasks and the weekly status meeting is in two hours. Produce a progress report: count completed tasks this week, percentage complete per milestone, list overdue items, and highlight any tasks blocking the creative review. Share it in the meeting doc and tag the two owners to update estimates.
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 progress to marketing leadership, make the dashboard readable: surface percent…+
Before I present progress to marketing leadership, make the dashboard readable: surface percent complete for each milestone at the top, convert task counts into time-to-finish estimates, flag any milestone behind by more than one day, and underline which task updates are unverified by owners so I can call them out in the meeting.
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 weekly delta shows completion for the email build milestone fell from 80% to 62% overnight.…+
I ran the weekly report and completion dropped from 80% to 62%.
The weekly delta shows completion for the email build milestone fell from 80% to 62% overnight. I don’t know whether tasks were reopened, removed, or mis-tagged. Who is most likely responsible, what checks should I run first to diagnose, and what quick action restores credible numbers before the meeting?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery week the completion percentages swing wildly because tasks get reopened, tags change, or…+
Numbers shift unpredictably across weekly reports.
Every week the completion percentages swing wildly because tasks get reopened, tags change, or people forget to mark done. Which tracking habit would reduce these swings: strict naming conventions, a pre-meeting verification step with owners, or locking completed tasks from edits? Recommend one change and a two-step process to enforce it for the next four sprints.
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.