For thirty years, we’ve designed business systems around one fundamental premise: business processes follow a predictable bell curve. Build for the middle 80%, document exceptions for the edges, and everything runs smoothly.
This assumption shaped every ERP system, every workflow automation tool, every “best practice” implementation. Design for the average case, standardize the process, measure compliance, and keep it above the threshold.
The problem? Real business doesn’t follow bell curves.
The Insurance Claims Reality Check
You get into an accident on a Thursday evening while driving back from an assignment at a customer’s project. It’s a fender bender with clear fault – everything points to a straightforward claim. Three weeks later, you’re still waiting because your claim doesn’t fit the standard workflow:
-
Car was a rental
-
During a business trip
-
Personal items damaged
-
The other driver’s insurance company just changed their claims system
Each of these kicks your claim out of the straight-through processing path into manual review queues, approval chains, and department handoffs that weren’t designed to happen.
But Why Did We Build This Way?
When ERPs and process automation emerged in the early 1990s, they were revolutionary – bringing sanity to paper-based chaos. They offered:
-
Unification across different departments and org units
-
Reviewable audit trails and compliance
-
Massive efficiency gains
-
Elimination of human errors in routine tasks
But there was a price to pay:
-
We picked consistency over flexibility
-
Process compliance over customer outcomes
-
Efficiency over effectiveness
-
Standardization over adaptation
It was a reasonable trade-off for taking a massive step forward.
But the Playing Field Has Changed
Customer expectations: Personalized experiences are now table stakes. Every case and every customer is unique and expects to be treated that way.
Market dynamics: Volatile markets require rapid adaptation, not process consistency.
Regulatory climate: Regulations change rapidly and compliance is a must.
Data availability: Real-time information enables context-aware decision making – something static workflows can’t leverage.
The Real Cost of the Trap
Disgruntled customers aren’t the only issue with current ERPs. The bell curve trap creates:
-
Innovation paralysis: “The system is not designed to do it this way”
-
Employee burnout: Constant workarounds and manual exception handling
-
Competitive disadvantage: Slow response to market changes
-
Data silos: Information that can’t be shared and utilized
-
Customer churn: Poor experiences in an age of high expectations
The solution isn’t better workflows or more sophisticated exception handling. It’s fundamentally rethinking how we design business processes for a world where variation is the norm, not the exception.
In the next post, we’ll dig into what this “lowest common denominator” approach actually costs organizations – and why the hidden expenses dwarf the superficial efficiencies of ERPs.