◆ Asana

Report Asana outages

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 taskOur team's project board is completely blank, and nothing is loading. Check the system status…+
Our team's project board is completely blank, and nothing is loading. Check the system status page and report back if there's an outage affecting us. If it's down, tell the team by 9:30 AM.
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 tell the team about the outage, make sure I have all the key details. What's the…+
Before I tell the team about the outage, make sure I have all the key details. What's the expected downtime, which features are impacted, and what's the official word on a fix? I need to sound credible.
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 project board is completely unresponsive for my team, but the official status page shows…+
The project board is down again, but the status page says everything is green.
The project board is completely unresponsive for my team, but the official status page shows all systems operational. This happened last month too, and it turned out to be a regional issue they weren't reporting. My team is already getting frustrated, and I'm worried about losing a day's work. What's the most likely reason for this discrepancy, and should I escalate internally or trust the public status?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing credibility with my team when the project tool acts up, and I can't get a clear…+
Recurring frustration when the project tool seems down but isn't officially acknowledged.
I keep losing credibility with my team when the project tool acts up, and I can't get a clear answer on whether it's truly down or just us. It wastes an hour every time. How can I quickly diagnose these 'phantom' outages myself without always waiting for an official word, so I can give my team a reliable answer faster?
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.