Write the runbook
Why documentation is the highest-leverage thing on a helpdesk, and the lightweight KB format my team actually uses.
Read note →7 years keeping offices running — the person who resets the password at 8:59 before the 9:00 board call, images the new starter's laptop before lunch, and quietly patches the thing that would've broken on Friday. Calm under a full ticket queue, and I speak human, not just jargon.
I fell into IT support fixing my dad's shop computer and never left, because it turns out I love the specific satisfaction of taking someone from 'everything is broken and I have a deadline' to 'oh, it's working' in under ten minutes. Seven years later I've done that roughly twelve thousand times.
I've run the helpdesk for a 400-person office, migrated a company off ageing on-prem servers to Microsoft 365 without a single lost mailbox, and been the calm voice on the phone while a panicking exec thought they'd deleted the quarterly report (they hadn't). The tickets I'm proudest of are the ones that never got opened because I patched the problem first.
If your team needs someone reliable at the front line — quick to respond, methodical under pressure, kind to non-technical users, and disciplined about documentation — my notice is thirty days and I'll happily start on the messiest queue you've got. Give me your oldest unsolved ticket as an interview.
Hardware to helpdesk, endpoints to the awkward legacy box nobody documented. Here's the range.
Anyone can close a ticket. The job is closing it so it doesn't come back — and explaining what happened without making the user feel stupid. Half of good IT support is technical; the other half is bedside manner. I fix the printer and I fix the panic, then I write the runbook so the next person on shift doesn't have to rediscover the fix at 2 a.m.
Front-line and escalation support for a 400-person hybrid office. Cut average ticket resolution time by 40% by building a searchable KB, led the M365 migration with zero data loss, and maintain a 99.9% desk-uptime record on the on-call rota.
High-volume L1/L2 helpdesk for a 24/7 operations floor: imaging, account provisioning, and the night-shift on-call where I learned to fix things fast and document them faster.
Retail and small-business support — hardware repair, virus removal, home-office setups. The best crash course in explaining tech to people who don't want to learn it.
Why documentation is the highest-leverage thing on a helpdesk, and the lightweight KB format my team actually uses.
Read note →How to explain a technical fix to a stressed non-technical user without condescending or confusing them. Scripts included.
Read note →Proactive maintenance as a mindset — the small patches and checks that quietly prevent the Friday-afternoon disaster.
Read note →Rohan reset access and had me back in two minutes before a board call, then followed up so it wouldn't happen again. That's rare.
Finance DirectorNovena TechnologiesHe migrated our entire company to M365 over a weekend and Monday morning nobody noticed anything except that it was faster.
IT ManagerFormer managerHe's the only IT person who's ever explained a problem to me in a way I actually understood. Patient, never made me feel dumb.
Office CoordinatorNon-technical user