You're halfway through a client proposal when your laptop refuses to connect to the shared drive. You can stop and call IT, or you can try three workarounds and lose an hour anyway. Either way, your day has just been taken over by a problem that isn't your job.
The tension is real. You need IT's help, but asking for it costs you focus, and waiting for it costs you time. The good news is that most of that cost comes from how requests are made and handled, not from the problem itself. These five habits reduce it.
1. Check self-service first, but set a time limit
Most IT teams maintain a knowledge base or help portal covering common issues: password resets, printer setup, VPN connection, software installs. Many of these take under five minutes to fix yourself.
Give it ten minutes at most. If the answer isn't there, or the steps don't work, stop and file a request. Sinking an hour into a fix that was never going to work is the most expensive option.
2. Use the ticketing system, not the shoulder tap
A ticket is a written request logged in your IT team's tracking tool. It feels slower than catching someone in the corridor, but it gets you faster resolution overall. Tickets create a record, get prioritised alongside other work, and can be picked up by whoever is available, not only the person you happened to find.
Walk-up requests also interrupt your IT colleagues, which slows down everyone else's fix, including yours next time.
3. Write the request so it can be solved without a follow-up
The most common cause of delay is a ticket that says "my computer isn't working." Include these four things instead:
• What you were doing when the problem started• What you expected to happen and what happened instead
• Any error message, copied exactly or captured in a screenshot (on Windows, press Windows key + Shift + S)
• Impact and deadline, such as "I can't send invoices and payroll closes at 3pm"
A ticket like that can often be resolved in one exchange. A vague one usually takes three or four, each of which interrupts you again.
4. Pick the right urgency level, and be honest about it
Most ticketing tools ask you to rate urgency. If everything is marked urgent, the label stops meaning anything, and genuinely critical issues get buried.
A useful test: is the work blocked entirely, and is there no workaround? If yes, flag it as high priority and say why. If you can still work around the problem, say so and let it go in the normal queue. IT teams respond better to people who help them triage.
5. Know the escalation path before you need it
Find out now, not during an outage, what happens when a ticket stalls. Look for the stated response times (often called a service level agreement, or SLA) and who to contact if you haven't heard back within that window. Usually it's a team lead or the service desk manager.
If your request is genuinely urgent and sitting unanswered, a short, polite follow-up that references your ticket number is more effective than a flurry of emails to different people.
Schedule what can wait
Not every issue needs fixing right now. A slow application, a software upgrade, or a new peripheral can often be handled during a quiet window. Ask IT whether they offer scheduled appointments or remote sessions, and book them for a gap in your calendar, such as the first half hour of the day or just after a meeting block.
How these habits add up
Each of these steps saves a few minutes on its own. Together they change the pattern. Self-service clears the simple problems. Well-written tickets cut the back-and-forth on the rest. Honest urgency ratings put real emergencies at the front of the queue. Scheduled fixes keep non-urgent work out of your peak hours.
Better IT support doesn't require more interruptions. It requires a bit of structure on both sides, and the first piece is yours: next time something breaks, spend two minutes writing it up properly.