A support team answers a question about a particular step several hundred times a month. They have done so for two years.
Everybody knows about it. It has been mentioned in meetings. It is on a list somewhere. It has never been prioritised because it is not urgent, nothing is broken, and the support team absorbs it.
Two years of that volume is an enormous amount of skilled time, paid monthly, forever, for a fix that would take an afternoon.
The first failure: the cost is invisible
Distributed across a team as part of general workload rather than appearing anywhere as a figure attached to a cause.
The second failure: nobody owns the cause
Support answers it, product could fix it, and nobody is measured on the volume, so it persists indefinitely.
The third failure: urgency beats frequency
Nothing is broken, so it never reaches the top of any list, while considerably less expensive problems get fixed because somebody complained loudly.
The fourth failure: the volume is not counted by cause
Tickets are categorised by topic rather than by what produced them, which makes the pattern invisible.
The fifth failure: the fix is assessed without the ongoing cost
An afternoon of work looks expensive against a backlog and cheap against two years of monthly support volume.
The sixth failure: the team adapts
A macro is written, the answer becomes fast, and the problem is now efficient rather than solved, which removes the pressure to fix it.
The seventh failure: the debt compounds
Each new unfixed cause adds permanent volume, and a team that never fixes causes eventually spends all its capacity servicing them.
The eighth failure: it is confused with the backlog
A backlog is a queue and support debt is a structural cost, which is the distinction in queue backlogs that never actually clear.
The ninth failure: the recurring questions are normalised
Which is the volume described in the same twenty questions every single day.
The tenth failure: the business case is never written
Volume multiplied by handling time multiplied by twelve, which is a number nobody has calculated and which usually settles the argument.
The eleventh failure: the support team stops reporting it
After two years of raising something that never changes, people reasonably stop raising it.
The twelfth failure: the customer experience is discounted entirely
Several hundred people a month encountering the same confusion is a product problem regardless of how efficiently it is answered.
The thirteenth failure: the fix is assessed by the wrong department
A product team weighing an afternoon of work against its own roadmap does not see the support cost, and nobody presents it to them in a form that would appear on their side of the comparison.
The fourteenth failure: nobody calculates the interest
A problem generating a known volume every month has a twelve month cost that almost nobody has ever multiplied out, and the figure is frequently large enough to settle the argument immediately.
The fix: answer it automatically and keep reporting the cause
An assistant handling the recurring question removes the monthly payment immediately, and the record it produces is exactly the evidence needed to get the underlying cause fixed rather than permanently serviced. The repeating pattern is described in ticket volume from problems that repeat, and a common promotional example in how to handle discount and coupon questions with a. Start at try, see features, and the sector view sits under small business.