Invisible waste driver - people don't see the complexity retained that will cost them for years. Designing, developing and delivering something that should no longer exist is a complete waste.



Invisible waste driver - people don't see the complexity retained that will cost them for years

Designing, developing and delivering something that should no longer exist is a complete waste.

Michael Hammer coined the phrase, “Obliterate don’t automate!”

Before any project solution is selected or designed the business needs need to be identified and either eliminated or simplified. Not marginally ‘improved’ by, say, 10%; but significantly simplified by, say, 40% or more.

Take 40% or more of the process steps out of your current processes and you reduce the complexity of both:

  • the project (less complexity to deign, develop and deliver)
  • AND future operations (less complexity to operate, train people in and resource).

Many business analysts and other process worker’s work is superficial - achieving less than 15% improvement (if any improvement is attempted at all). One brand name consultancy took 12 months to achieve a 13% process step reduction; TOP took 4 weeks to achieve a 35% reduction.

The top 5% of firms avoid retained complexity by simplifying the current state BEFORE approaching solutions or designs. Simplification of operational complexity by over 40% can be common. And, the real payoff is that you can subsequently manage a simpler, lower cost and more flexible organization on an ongoing basis.

Relying on predefined software solutions to define your requirements leads to unnecessary complexity and often causes workarounds to be created to fit the solution into the existing business - another source of waste.

The top 5% use their simplified process definitions to evaluate and select exact match software solutions, avoiding customizations and operational gaps that perpetuate waste.
TOP calls this Business Simplification
For further information

 

Topics: Strategy Execution

Further Reading

 




Footnotes

[1] ...





Revision History

First published: Simms, J. (Dec 2014) as "Retaining Unnecessary Complexity"

Updated: Chapman, A. (March 2020), Revisions and Corrections