Every improvement initiative promises to make work easier. Some leave employees doing the new work and the old work at the same time.
The old process never quite leaves
A new system goes live. Training is complete. Leadership celebrates the launch.
Months later, managers still maintain their old spreadsheets. Teams enter the same information in two places. Reports are reconciled by hand because departments use different definitions. A new governance meeting appears, but the old one stays on everyone's calendar.
People may have accepted the new system. Their workload has still grown.
There's another cost that rarely appears in the business case: the time people lose moving between systems. They interrupt one task to find information in another application, reconcile conflicting records, check whether something was completed correctly, or repeat work that should only have been done once.
Each interruption may seem minor. Across hundreds of transactions, those minutes accumulate. And when employees must continually shift between systems, the cost isn't just the extra steps. It's the time and attention required to regain their place in the work.
Adding is easier than subtracting
Project plans are detailed about what needs to be built, configured, tested, communicated, and taught. They are often less specific about which existing work will stop.
Sometimes the old work remains for good reasons. Controls may be legally required or necessary during a transition. Sometimes it stays because nobody has been given authority to retire it, or because leaders are more comfortable adding a process than removing one.
The cost gets scattered across multiple departments, which makes it easy to overlook.
Put removal on the plan
For each proposed improvement, ask: What task should disappear if this works? Which report, approval, workaround, or duplicate entry will be retired? Who can authorize that change? What conditions must be met first? How will we know the old work has actually stopped?
These questions help distinguish necessary safeguards from habits that simply survived.
Measure the net change
A new tool can save ten minutes in one activity while creating additional work elsewhere. Employees may spend that time switching applications, reconciling records, checking results, correcting errors, or repeating work. If those costs aren't measured, the organization can report an improvement in one activity while overall productivity declines.
Measure the full effort required to complete the work, including handoffs, interruptions, verification, rework, and the time spent maintaining parallel systems. The benefit isn't the time saved by one application. It's the improvement in the entire process.
The measure of an improvement isn't how much new capability we introduced. It's how much better the work performs afterward.
Peloton Consulting helps leaders identify obsolete work, clarify retirement decisions, and recover usable capacity from transformation investments.