◆ Asana

Troubleshoot common problems at 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 taskThe 'Sales Enablement' project isn't showing up for Mark. Check his permissions and make sure…+
The 'Sales Enablement' project isn't showing up for Mark. Check his permissions and make sure he has full access.
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 acceptThe marketing team is complaining that their task dependencies aren't working correctly in the…+
The marketing team is complaining that their task dependencies aren't working correctly in the 'Holiday Campaign' project, causing confusion about who should start next. Look at the setup for tasks assigned to Sarah and Tom and suggest why the order isn't sticking.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMultiple people on the 'Product Feature X' project are saying their tasks are randomly…+
Several team members are reporting that their tasks are disappearing or not updating, and I can't figure out why.
Multiple people on the 'Product Feature X' project are saying their tasks are randomly disappearing or not showing updates, especially after working offline. I've checked their internet connections, but it keeps happening, and it's causing missed deadlines. I don't know if it's a sync issue or something else. What's the most likely cause, and what's the first thing I should check to diagnose this quickly?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly interrupted to fix small, repeatable issues like incorrect permissions, broken…+
I spend too much time manually fixing small, recurring issues that slow down the team.
I'm constantly interrupted to fix small, repeatable issues like incorrect permissions, broken dependencies, or tasks not syncing, which eats into my day and frustrates the team. This pattern makes me feel like a help desk. What habit can I change to empower the team to self-diagnose or prevent these common problems, freeing up my time?
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.