Years leading a technical support desk, translating the same handful of support-ticket patterns into clear, plain-language troubleshooting guides.
Kevin's background is in technical support, including several years leading a help-desk team fielding day-to-day computer and printer issues from non-technical users. That role gave him a close view of exactly where people get stuck — not the exotic edge cases, but the same small set of causes showing up again and again, phrased a hundred different ways by people who just want their printer working again without needing to become an expert in it.
Kevin writes the site's most common troubleshooting guides — offline errors, stuck print jobs, "no printers found," and the general diagnostic content that applies across every brand. His writing draws directly on support-ticket patterns: which fix resolves the issue most often, which explanation actually makes sense to someone without a technical background, and which step people tend to skip that ends up being the one that matters.
Kevin's approach is shaped by years of walking people through fixes over the phone, where an instruction that makes sense to a technical person can completely lose someone else. He writes every troubleshooting guide assuming no prior knowledge, orders steps by how often each one is actually the answer rather than by technical complexity, and avoids jargon unless he can explain it in the same sentence — the same standard he held himself to on live support calls.
Start with the most common troubleshooting guide on the site.
See the "offline" troubleshooting guide