A Knowledge Map, start to finish.

The inputs

40 tickets over four weeks and 20 business days, from a two-person support desk. 16 of the 40 were escalated, a 40% escalation rate. Seven rankable categories, plus three one-offs.

Minutes lost is a derived figure, not a measurement. It is the difference between how long escalated tickets took and how long the same category took when the desk answered it alone, compared within a category so the category's inherent difficulty cancels out.

The finding

Spec and dimension lookups are 12.5% of ticket volume and 0% of escalation cost. Warranty decisions are 15% of volume and 36% of escalation cost.

Ranking by frequency would have put spec lookups above RMA, firmware, and consumables in the ingestion order. They cost nothing, because the desk already answers them from a datasheet. The expensive questions are the ones the desk is not allowed to answer alone.

Troubleshooting and policy account for 246.5 of the 266.5 ranked weekly minutes, 93%. That is the interrupt tax, and it is why troubleshooting and policies get ingested before product specs.

What the data could not tell you

This section ships with the map, because a number without its limits is a guess.

Minutes lost is an upper bound where escalated tickets are also harder tickets, which is likely on warranty.

Four weeks cannot see seasonality. The winter temperature derate drives low-flow volume that this window under-represents, so rank 3 is probably understated.

Two of the low-flow escalations may be a firmware reporting artifact. If so, part of rank 3's cost belongs to rank 5, and rank 5 is understated.

Escalations were self-reported. An escalation handled by walking to someone's desk leaves no record, so the real rate is at or above 40%, not below it.