TJ Hoag

Root Cause vs Business Impact in Tickets

TJ
Timothy J. Hoag
IAM & IT Operations Specialist

A ticket titled "printer issue" and a ticket titled "can't print" look almost the same. They are not.

Root cause and business impact are two different questions, and most ticket taxonomy only tracks the first one.

Same Root Cause, Different Problem

Working a queue across 30-plus institutions taught me this the slow way. A jammed printer in a supply closet and a jammed printer at the only workstation running exam accommodations have the same root cause. They are not the same problem. If the subject line only says "printer issue," nobody triaging the queue can tell which one they are looking at without opening it.

The technician needs the root cause. That tells them where to start and what to fix. But the queue needs the business impact. That tells triage where the ticket actually belongs relative to everything else waiting.

Most intake forms are built around root cause categories: hardware, software, network, access. Those categories help with routing and reporting. They do not help with prioritization, because they do not capture who is affected or what is at stake.

What to Capture at Intake

Three things I try to capture at intake, not after the fact:

Who actually cannot do their job because of this. Not just what broke, but who is blocked. A broken printer in an empty office is a maintenance task. A broken printer that is preventing a department from processing patient paperwork is an operational disruption. The root cause is identical. The urgency is not.

Whether there is a deadline attached. A shift starting, an exam window closing, a compliance report due by end of day. Deadlines do not change the technical fix, but they change when the fix needs to happen. A ticket without a deadline can wait for the next available technician. A ticket with a two-hour window cannot.

Whether the fix is fast but the impact is not small, or the fix is slow but the impact stays contained. A quick cable swap that restores a department's only shared drive is a five-minute fix with high impact. A complex server migration that only affects a test environment is a multi-day fix with low impact. Knowing both sides helps triage allocate time accurately.

Why Taxonomy Defaults to Root Cause

Ticket systems are built for reporting, and reports aggregate by category. "How many hardware tickets did we close this month?" is an easy question to answer when every ticket has a hardware or software tag. "How many tickets this month had a direct operational impact on a department?" is a harder question to answer because the taxonomy was never designed to capture it.

Root cause tells the technician where to start. Business impact tells the queue where the ticket actually belongs relative to everything else waiting.

The other factor is speed. At intake, the fastest thing to capture is what the user described: "printer is jammed," "can't connect to Wi-Fi," "application crashed." That becomes the category. Asking follow-up questions about who is affected and what is at stake takes longer, and when the queue is moving fast, those questions get skipped.

Bridging the Gap Without Slowing Intake

Adding business impact to intake does not require a new ticketing system or a redesigned form. It requires two additional questions asked consistently:

  • Who is affected beyond the person reporting it?
  • Is there a time constraint on when this needs to be resolved?

Those two questions add maybe thirty seconds to intake. They save significantly more time in triage by giving the queue enough information to prioritize without every ticket needing to be opened and read.

The ticket title does not need to change. The taxonomy does not need an overhaul. The difference is whether the ticket captures only what broke, or also captures what the break is costing.

Opportunities
Open to Remote Roles

IAM Analyst, Junior Systems Administrator, or IT Operations Analyst - ideally in healthcare or higher education. Direct hire, W-2.

Discuss opportunities