Failure pattern 04
The exception swamp
The exception swamp is when the normal path of a workflow runs fine but the exceptions, such as change orders, missing parts, access problems and warranty questions, are handled by phone, memory and improvisation. Exceptions become most of the day, and nobody can see how many there are.
What it looks like
The crew arrives and the equipment is not what the work order described. The lead calls the office, the office calls the customer, someone agrees to an extra charge on the phone, and nobody writes it down in a place billing will see.
How to tell you have it
- The best people spend most of their time "putting out fires".
- Extra work agreed in the field regularly fails to appear on the invoice.
- New staff struggle because the real process lives in experienced people's heads.
- Disputes come down to who remembers the phone call.
What it costs
Unbilled changes, disputes, and a dependency on a few people who know how things really work.
What fixes it
Naming the few exceptions that account for most deviations and giving each a short, recorded path to the person who decides and to billing. The standard path stays as it is.
What does not fix it
Writing a longer procedure manual. Exceptions happen at speed, on site, and the manual is in the office.
Questions people ask
What is the exception swamp?
It is the part of a workflow that has no defined path. The standard job is documented and works. Everything that deviates from it is handled by whoever happens to pick up the phone, and that informal handling grows until it dominates the week.
Aren't exceptions unavoidable?
Individual exceptions are. The swamp is not. Most exceptions repeat: the same few kinds of change, delay or missing information. Once they are named and routed, they stop being surprises.
How do I measure it?
Count, for one week, how often the standard path was not followed and why. Most operations find a handful of reasons account for most of the deviations.
Why do exceptions matter to billing?
Unrecorded exceptions are often unbilled work. A change agreed in the field that never reaches the office is labor given away.
What does a fix do?
It gives the common exceptions a defined path with a place to record them, a person who owns them, and a way to reach billing, instead of leaving each one to be solved from scratch.