The same exception keeps landing on the same busy person. It gets resolved, and the resolution feels like the job done. The next week it lands again, on the same person, and gets resolved again. Read once, this looks like a workload problem: someone is busy, an exception arrived, it got handled. Read across a month, the pattern says something different. The same question keeps coming back because no one ever made the decision that would stop it.
The recurrence is the signal
A one-off exception is work. A recurring exception is a decision that was never made. The distinction matters because the two call for completely different responses, and most organizations apply the first response to the second. The one-off gets handled and disappears. The recurring exception gets handled and returns, because handling the instance never touches the decision underneath it.
The distinguishing feature is that the same question keeps coming back. A different exception every week is a workload pattern. The same exception every week, landing on the same person, is a decision that has been deferred, made informally each time, or never assigned to an owner. Every instance pays interest on that deferral, and the interest is paid in the busiest person's time.
Why it gets misread as workload
The exception arrives as work. It lands on whoever is senior enough or available enough to resolve it under pressure, which is usually the busiest person in the company. It gets resolved. The resolution feels like completion, because work was done and the immediate question was answered. The cost stays hidden because it is paid in the time of someone who was already fully loaded, and fully loaded people do not keep a ledger of the decisions they are absorbing for the organization.
So the pattern repeats, and each repetition reads as another instance of the same workload problem rather than as evidence that a decision upstream was never made. The busy person gets busier. The founder considers whether the busy person needs help, or a meeting to clear the backlog, or an escalation path. Every one of those moves treats the landing, not the cause. The cause is a decision that has no owner and no rule.
The same exception, resolved differently each time
Take a forty-five-person commercial print shop where the same exception about rush-order surcharges keeps landing on the production manager. A customer wants a job pushed ahead of the queue. The production manager decides case by case, sometimes adding a surcharge, sometimes eating the cost to protect the relationship, sometimes asking the owner to decide. The billing disputes that result show up almost monthly in the same handful of accounts. Each dispute gets resolved. The surcharge rule never gets written. The same exception lands again the next week, resolved differently, by the same person, with the same person also running the production floor.
Three things are true in that shop, and none of them is a workload problem. The surcharge decision has no owner. The surcharge rule does not exist. And the production manager is paying the interest on both of those gaps in their own time, every week, on top of the job they were actually hired for. The owner sees the disputes and the busy manager, and reads the fix as either a billing memo or a second pair of hands, both of which miss the decision that has no owner and no rule.
The fix is upstream, not downstream
Adding capacity does not fix a recurring exception, because the exception is not caused by a shortage of capacity. Holding a meeting does not fix it, because discussion is a different activity than a decision, and decision debt is commonly misdiagnosed as a meetings problem. Building an escalation path does not fix it, because routing the exception more efficiently to the same person is a faster way of not making the decision. Every downstream move preserves the deferral.
The upstream fix is to make the decision once. Name an owner for the question, and write the rule that owner will apply. The two have to be addressed together. Writing a policy without naming who is accountable for applying it does not resolve the debt, because the policy still has no one enforcing it and the exception still lands wherever it landed before. Naming an owner without writing the rule does not resolve it either, because the owner still decides case by case and the inconsistency continues. The debt is paid down when the decision has both an owner and a rule, and the recurrence stops on its own once it does.
The interest compounds
Every unresolved recurring exception adds to the volume of judgment calls the same person has to make, which crowds out everything else they were hired for. Over time this concentrates authority in a small number of people, because the only people who can resolve the exceptions are the ones who have been resolving them all along. That concentration is a cost the organization is paying every week, and it is a different cost from the workload it gets mistaken for. The workload cost is the time. The compounding cost is the quiet accumulation of unowned authority in the people who never formally accepted it. The person who keeps resolving the exceptions is also the person with no time left for the work only they can do, and the trade moves in the same direction every week.
This is where the recurring exception connects to a risk the owner is already carrying. Decisions that accumulate in one person's head, without a written rule, become a form of concentration. The person who has been resolving the same exception for three years holds the accumulated judgment behind hundreds of ad hoc decisions, and the organization has no record of any of them. The deferral that looked like a workload convenience has been building a standing exposure the whole time.
A recurring exception is a decision asking to be made once
Read recurrence as the signal, and the response changes. The exception that keeps landing on the same person is asking for the decision that has been deferred every week to be made once, given an owner, and given a rule. Make that decision upstream, and the exception stops recurring on its own, because the condition that produced it is gone. Leave it, and the same question comes back next week, landing on the same person, paid for in their time, with the interest running until the day that person is no longer there to absorb it.