◆ Asana

Perform data cleanup and maintenance

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 taskFind all tasks in the 'Marketing Content' project that are assigned to 'Unassigned' and have no…+
Find all tasks in the 'Marketing Content' project that are assigned to 'Unassigned' and have no due date. Assign them to me and set their due date for next Friday.
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 the end of the week, go through all projects and identify any tasks that have been…+
Before the end of the week, go through all projects and identify any tasks that have been marked 'complete' but still have open subtasks. For each, either mark the subtasks complete if appropriate, or re-open the main task and notify the original assignee so we can ensure accuracy.
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 just discovered several critical tasks for the 'Vendor Contract Renewal' project are…+
I just discovered several critical tasks for the 'Vendor Contract Renewal' project are duplicated, some with different assignees and due dates.
I just discovered several critical tasks for the 'Vendor Contract Renewal' project are duplicated, some with different assignees and due dates. I'm afraid to delete any without knowing which is the 'real' one, and I can't risk losing important context or confusing the team. What's the best way to untangle this mess and ensure we have one accurate source of truth for each task without causing disruption?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find old, irrelevant tasks cluttering up project views, making it hard to focus…+
I consistently find old, irrelevant tasks cluttering up project views, making it hard to focus on current priorities.
I consistently find old, irrelevant tasks cluttering up project views, making it hard to focus on current priorities. This makes it harder for the team to find what they need and adds noise to reports. What habit should I change to regularly archive or clean up outdated tasks, ensuring our project spaces remain lean and focused on active work?
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.