◆ Asana

Troubleshoot network issues affecting Asana

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 taskMy internet connection is spotty, and the project tool is constantly freezing. Run a quick…+
My internet connection is spotty, and the project tool is constantly freezing. Run a quick network diagnostic and tell me if it's my Wi-Fi or something else. I need to get this proposal out by 3 PM.
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 call IT, help me figure out if this network issue is just me or if others on the team…+
Before I call IT, help me figure out if this network issue is just me or if others on the team are seeing it too. What are the common signs of a local network problem versus a wider office issue? I need to give them a smart report.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy internet speed tests are great, I can stream video, but the project tool is still glacially…+
My internet is fine for everything else, but the project tool is unusable.
My internet speed tests are great, I can stream video, but the project tool is still glacially slow, making it impossible to update tasks. Sarah next to me says hers is fine. I'm afraid of looking incompetent if I complain to IT about 'my internet' when it's clearly not. Is there a specific network setting or local cache issue I should check before calling IT, or is this a known problem for some users?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI waste too much time every week trying to figure out if my network is impacting the project…+
Constantly losing time troubleshooting my own network issues when the project tool lags.
I waste too much time every week trying to figure out if my network is impacting the project tool, or if it's the tool itself. It's a constant drain. What's a simple, consistent habit I can adopt to quickly rule out my local network as the problem, so I can focus on the actual work or escalate intelligently?
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.