The Four Actions Framework – Sometimes Less Is More
Why product complexity is usually self-inflicted — and how subtraction creates competitive advantage
At DMCA Solutions, we repeatedly observe a counterintuitive pattern in industrial product development:
When performance declines or sales slow down, companies add features.
This instinct feels logical, but it is often the root cause of product complexity, cost inflation, and customer confusion.
In most cases, the issue is not missing functionality.
It is excessive functionality.
The Bias Toward Addition
Industrial organizations naturally default to adding rather than removing.
Three structural reasons explain this:
Adding features is visible and politically rewarded internally
Customer requests are interpreted as product requirements
Competitor benchmarking drives reactive expansion
Over time, this creates product portfolios that are technically rich but strategically unclear.
The Four Actions Framework
A more disciplined approach is based on four structured questions:
Eliminate: What provides no meaningful customer value?
Reduce: What is over-engineered relative to actual need?
Increase: What is under-delivered in terms of value impact?
Create: What critical gap remains unaddressed?
Importantly, the sequence matters.
Most companies start with “Create”.
High-performing organizations start with “Eliminate”.
Why Subtraction Creates Advantage
Subtraction improves:
cost structure
usability
manufacturing complexity
decision clarity for customers
In many industrial markets, simplicity is more valuable than marginal performance gains.
Because simplicity reduces operational risk.
The Strategic Misunderstanding of Innovation
Innovation is often associated with addition:
more features
more capability
more variants
However, in mature industrial categories, innovation frequently comes from:
fewer components
simpler systems
reduced operational burden
This is particularly true in high-reliability environments.
DMCA Perspective
In sourcing and product specification analysis, we often see over-engineered components introduced to address edge cases that represent a very small share of real usage.
When these elements are removed, the system often becomes:
more robust
more cost-efficient
easier to integrate
The result is not reduced performance — but improved fit-for-purpose design.
Key Takeaway
Most product complexity is accumulated, not required.
The Four Actions Framework forces disciplined simplification — which is often where real competitive advantage emerges.
Comments