Article
Here is a line that will save you a lot of grief: exceptions are not edge cases. They are part of the product.
If you run a service business, the exception often is the work. It is the special request. The weird customer. The rush job. The "can we do it this way" message that lands at 4:55 on a Friday like it pays rent.
If you ignore that and automate only the happy path, you will build something that works beautifully right up until real life shows up.
What an exception actually looks like
These stop feeling like edge cases when they happen every week. A few common ones:
- A customer needs a different invoice format.
- The job needs a second site visit.
- The delivery window changes.
- The request comes from a different email than usual.
- The team has to chase one missing detail before anything can move.
None of that is exotic. That is just business under field conditions.
A real example
Say a business automates onboarding. Payment comes in, the welcome email goes out, the folder gets created, and kickoff times are offered. On paper, it looks great.
Then the client says, "We need to add a second contact," or "We have a PO process," or "Our legal team needs to review this first." Now the workflow branches.
If nobody planned for that branch, the automation stalls, people start scrambling, and the team slides right back to manual work with a few extra steps for flavour.
The simple fix
Before you build anything, do one short exercise.
1. List the top 10 exceptions
Not every possible exception. Just the ten that keep showing up and making a mess.
2. Decide what you accept
Some exceptions are worth supporting. Some are not. Write one simple rule, like:
- "We accept rush jobs only if we have 48 hours."
- "We support PO invoicing only for repeat clients."
3. Design the workflow for reality
Add the branch on purpose. That can be as simple as:
- "If exception, create a task for the owner."
- "If exception, pause automation and notify ops."
The point is not to automate every possible twist. The point is to stop acting surprised by the work you do every week.
Why this matters
Exceptions drive cost. They drive stress. And they are usually where a clean-looking workflow starts to come apart.
If you design for exceptions first, your automation gets steadier and your team spends less time babysitting it.
If you want help with this, book a discovery call.
What is the exception that shows up the most in your business?