Fox & SantiagoTechnology, applied.Call (877) 244-9687

Failure pattern 04

The exception swamp

The exception swamp is when the normal path of a workflow runs fine but the exceptions, such as changes, shortages, missing information and disputes, are handled by phone, memory and improvisation. Exceptions become most of the day, and nobody can see how many there are.

A whiteboard crowded with overlapping sticky notes

What it is

Most workflows are designed for the case where everything goes right. Real days are full of the other cases. When those cases have no path, they get solved one at a time by phone and memory, and the answer lives nowhere anyone else can find it.

How it shows up across industries

  • Field service: the crew finds equipment that does not match the work order, someone agrees to an extra charge on the phone, and nobody writes it down where billing will see it.
  • Distribution: a short shipment, a damaged pallet or a substitution gets settled by email, and the credit never reaches the customer's account.
  • Healthcare practices: a denied claim is worked by whoever knows that payer, and the fix never becomes the rule for the next one.
  • Law firms: a client asks for work outside the engagement letter, and it gets done without a change in scope or fee.
  • Restaurants: an eighty-sixed item, a comped meal or a late delivery is handled on the floor and never shows up in the numbers.
  • Property management: a tenant disputes a charge, and the history of what was agreed is spread across three people's texts.
  • Manufacturing: a rush order or a material substitution goes through on the supervisor's say-so, and the routing and costs still show the old plan.

How to tell you have it

  • The best people spend most of their time "putting out fires".
  • Extra work agreed with customers 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, credits given twice or never, disputes, and a dependency on a few people who know how things really work. When one of them leaves, the process leaves with them.

How we solve it

We come on site and count the exceptions for real: which ones repeat, who handles them, and where the answer gets lost. Then we build on the systems you already run so each common exception has a short, recorded path to the person who decides and to billing. The standard path stays as it is, and the record stays in your system of record, never in a second one.

What does not fix it

Writing a longer procedure manual. Exceptions happen at speed, in front of the customer, and the manual is on a shelf.

Talk to us

If your best people spend their days putting out the same fires, book a free fit call or call (877) 244-9687.

Where this pattern shows up

Questions people ask

What is the exception swamp?

It is the part of a workflow that has no defined path. The standard case 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 with a customer that never reaches billing is work 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.