While Lean and Six Sigma share similar goals, they operate differently. Lean focuses on reducing waste and maximising value, while Six Sigma uses data and analysis to minimise variation and defects. Together, they form a comprehensive approach to process improvement that translates surprisingly well to software product development.
Identifying Digital Waste
Waste in software development often goes unnoticed. Unlike a factory floor where inefficiency is visible, digital waste hides in plain sight. Examples include:
- Cancelled projects that consumed weeks of planning and development
- Abandoned backlog items that nobody is ever going to build
- Unstructured meetings that produce no decisions or actions
- Approval bottlenecks that delay delivery without adding value
- Excessive stakeholder involvement at the wrong stages
Technical debt represents another significant waste category - it creates future rework, slows down developers and compounds over time if left unaddressed.
The Value-First Approach
A core Lean principle is that any activity lacking direct customer value constitutes waste, regardless of how useful it might feel internally. This insight prompted me to reconsider my prioritisation approach as a Product Owner.
It sounds obvious, but it's easy to fill a sprint with work that feels productive without asking whether it moves the needle for the customer. Doing less can sometimes deliver more - if it means focusing on the right things.
Data-Driven Decision Making
Six Sigma introduced me to a more disciplined approach to measurement and analysis. Too often, product decisions rely on anecdotal evidence, loud stakeholder voices or gut feel rather than objective data.
Structured frameworks like RICE, MoSCoW and the Eisenhower Matrix provide a more defensible basis for prioritisation - and they create a shared language that helps teams align without the politics.
Defining Defects Broadly
In Six Sigma, a defect isn't just a bug. It's any output that falls outside customer requirements - which means both under-delivering and over-delivering count. Building a feature that nobody asked for is a defect. Shipping something that doesn't meet the acceptance criteria is a defect.
The DMAIC framework - Define, Measure, Analyse, Improve, Control - provides a structured methodology for tackling these problems systematically rather than reactively.
The Takeaway
Efficiency isn't about working harder or faster. It's about working smarter - combining Lean's relentless focus on value with Six Sigma's emphasis on data and process rigour. For Product Owners, that means fewer initiatives done better, not more initiatives done quickly.