Here are some illustrations of the impact that's possible with the dramatic improvement framework.
There are always solutions as impactful as these to be found even - especially - when situations seem intractable, at the start.
We've enhanced the dramatic improvement framework significantly since some of these solutions were implemented - especially in the creating and sustaining change dimension.
So the impact you can expect is at least as significant as what we share below: no matter how intractable your situation may seem.
As you can see, the solutions are deceptively simple - and obvious in hindsight. Beware the trap of thinking that your situation is different!
Client | Before | After |
---|---|---|
Global Distributor | 20 units/month demand | 100 units/month demand |
Insurance Company Claims | 15-day decision | 90 days to onboard | Same day decision | 3 days to onboard |
Telco Project | $7M cost | 13 month duration | $360K cost | 3 month duration |
Construction Company | 14 week ave project duration | 8 week ave project duration |
Bank Sales | 49% of budget | 270% of budget |
Manufacturer - Production | 60 units/day | 140 units/day - on lower costs |
Software Developer/Integrator | 13 month ave project duration | 7 month ave project duration |
Orthopedic Clinic | 2h40 visit duration | 0h48 visit duration + increased capacity |
Before
10-20 units per month
From
100+ units per month
Before
Average claim decision (the 62% that don't need to go to Claims Committee) took 3 weeks - and it took a new claims specialist 3-6 months before being able to make those decisions unassisted.
After
Average claim decision in 15 minutes. New claims specialists make valid decisions in 3 days.
Before
$7M of development cost forecast over 13 months to complete the implementation of a new biling system.
After
$360K development cost over 3 months - better outcome (greater billing flexibility).
Instead of replicating a subsidiary's front-end and back-end for the new billing middleware system, develop shims between the subsidiary's front-end and the middleware and between it and the the subsidiary's back-end.
(At least a decade before this was a known solution and long before the days of API's.)
Before
14-week average duration (school block projects).
After
7 weeks and 2 days average project duration.
Before
49% of sales budget.
After
270% of sales budget.
Before
60 units per day working a single 13-hour shift ($25K in rebates for poor quality per month).
After
148 units per day on two overlapping 8-hour shifts ($200 in rebates per month).
Accelerate the end-to-end flow-bottleneck and synchronise the previous steps to ensure that the bottleneck is never starved of carefully checked and prioritised work.
(Adapted version of the TOC Production Solution).
Before
13 month average project duration and low customer satisfaction. (Legal threats).
After
7 month averge project duration and high customer satisfaction. (Testimonials).
Before
2h40 average patient visit duration, 5-8 hour long clinics and a growing waiting list.
After
Average claim decision in 15 minutes. New claims specialists make valid decisions in 3 days.
Patient flow-sequencing and -streamlining:
A good starting point is to improve operations performance, because the results are so tangible and immediate.
The dimensions to improve include:
The key to improving throughput is to improve bottleneck throughput - improving throughput elsewhere is pointless. (This may seem too obvious to be profound, but few people (much less teams) even know where the bottleneck is - never mind how to relieve it.)
The conventional approach is to improve things that can be improved the most, rather than things that will improve the end-to-end the most. So it's no wonder that bottleneck performance is hard to improve - if it was easy, we would have done it already.
If you aren't confident of dramatic improvement in throughput, you either don't have consensus on where the bottleneck is and what to do about it - or your consensus is mistaken.
2. Staff Engeagement
Copyright © Prodsol International, 1998-2024.