Every team has one. The person who just handles it. The invoice that never quite imports, the report that breaks on the first of the month, the customer whose order needs a nudge through the system. Ask how it got fixed and the answer is a name. Ask what they actually did and the room goes quiet.
That person is doing two jobs. The one on their job description, and a second, invisible one: absorbing the cost of a process that does not work. Their competence is the reason the failure survives. If the fix were painful for everyone, it would have been repaired properly years ago. Instead it is painful for one person, quietly, every week, and quiet pain does not get budget.
The vacation test
You find out how much of your operation lives in one head the week that head goes on holiday. The first of the month arrives. The report breaks. Three people discover at the same time that nobody else knows the workaround, because the workaround was never a process. It was a person.
This is not a people problem. The reliable person is not at fault for being reliable. The fault sits with a system that let their reliability become load-bearing without anyone noticing, writing it down, or paying for it.
The tell is repetition
Broken processes do not announce themselves. They repeat. The same fix, applied by the same person, on a rhythm you could set a calendar by. Every repeated manual fix is a process admitting it cannot carry its own weight.
Counting these is uncomfortable and quick. Ask each reliable person on the team one question: what do you fix over and over that should not need fixing? Most can answer in under a minute. They have been waiting for someone to ask. The list you get back is your real technical debt register, the one that never made it into a planning document because each individual fix only takes twenty minutes.
Twenty minutes a week is seventeen hours a year, for one fix, for one person. Most teams have five of these per reliable person.
What to do with the list
Do not start by fixing everything. Start by making the invisible work visible. Write down each repeated fix: what breaks, how often, who catches it, what they actually do. That single page changes the conversation, because a workaround with a name and a frequency is no longer a favor someone does. It is a maintenance cost the business is paying, and it can be compared against the cost of a real fix.
Some items on the list will turn out to be cheap to automate or redesign. Some will turn out to be fine as manual work, once they are acknowledged, documented, and shared by more than one head. Both outcomes beat the current one, where the business does not even know what it is spending.
The reliable person usually does not want to be the hero. They want the Tuesday back.
If your team runs on quiet workarounds and you keep meaning to untangle them, that is exactly what we build and fix. OCTYN finds the repeated fixes, turns them into real processes and systems, and keeps them running. Talk to us.
Top comments (0)