Operational Improvement Needs More Than Four Capabilities
The recent HBR model gets the sequence right, but leaders in complex businesses need a tougher interpretation of what those four capabilities actually require.
A recent Harvard Business Review article argues that lasting operational improvement depends on four cumulative capabilities: Discover, Improve, Align, and Transform. It is a strong argument, especially because it moves the discussion away from tools and toward organizational muscle. Too many companies still believe that Lean, Six Sigma, dashboards, and action lists will somehow produce advantage on their own. HBR is right to say they will not.
But the framework also needs pressure-testing.
Because most companies do not fail at operational improvement for the reasons executives like to say out loud. They do not fail because they “lack continuous improvement culture” or because teams are not trying hard enough. They fail because the organization sees problems but does not force decisions. It improves work locally without improving the economics of the business. It confuses alignment with polite agreement. And it talks about transformation as if it begins after operational discipline is built, when in many industries the operating model already needs redesign now.
The HBR framework is useful. It just becomes far more powerful when you read it with less romance and more executive realism.
Why the HBR argument matters
The HBR article makes an important point: companies using the same operational improvement practices get very different outcomes because practices do not create sustained advantage by themselves.
What matters is whether the organization builds reinforcing capabilities over time.
The sequence HBR identifies is Discover, Improve, Align, and Transform.
That is an important correction to the way many leadership teams still think. They sponsor improvement activity, not capability development. They launch events, stand up PMOs, run kaizens, add review meetings, and refresh KPI packs. Then they wonder why the business remains slow, politically fragmented, and vulnerable to recurring issues.
Why this matters:
The insight matters because it shifts the question from “What method are we using?” to “What organizational capability are we actually building?” That is a far better executive question.
What to do:
Treat every improvement initiative as a capability investment. Ask not just whether the issue was fixed, but whether the business became better at detecting, deciding, coordinating, and sustaining change.
Discover is only valuable if governance turns signal into action
The first HBR capability is Discover. The idea is simple and correct: better operators see what others miss. They detect risk, waste, drift, and friction earlier.
The problem is that many companies do not actually lack discovery. They lack decision discipline.
They already know the recurring warning signs. The same supplier instability keeps surfacing. The same projects go amber every month. The same customer complaints hint at the same root conditions. The same operational bottlenecks are visible in every review. What is missing is not awareness. It is the governance mechanism that forces a decision when the signal appears.
Why this matters:
If discovery is not tied to action thresholds, it becomes observation theater. Leaders feel informed while the organization remains unchanged. Signal accumulates. Risk matures. Everyone can say they saw it coming, which is precisely the problem.
What to do:
Turn discovery into a governed mechanism. Every leading indicator should have an owner, an escalation threshold, and a defined decision forum. If a signal can appear three months in a row without changing resources, priorities, or accountabilities, then discovery is not a capability in your business. It is just reporting.
A better executive rule is this:
No signal without a consequence.
Improve often strengthens the wrong system
HBR’s second capability, Improve, emphasizes moving from one-off fixes to learning loops. That is right in principle. The strongest operators do not just solve problems once. They create routines that improve future performance.
But this is where many leaders get seduced by the language of improvement.
A process can improve and the business can still lose.
An approval workflow can become faster even though it should have been removed. A plant can raise utilization while hurting service performance. A quality gate can become tighter while slowing throughput and increasing hidden cost. A function can optimize its own metric while degrading enterprise value.
Why this matters:
Improvement work is often politically visible before it is economically relevant. Teams improve what is measurable, what is local, and what is sponsor-friendly. They do not always improve the constraint that matters most to strategy, customer performance, or EBITDA.
What to do:
Before approving an improvement effort, ask one harder question: What enterprise constraint does this change actually relieve?
That forces the discussion away from activity and toward business effect. It separates true improvement from local optimization. It also exposes a common executive mistake: funding many valid improvements that do not materially change enterprise performance.
A better rule is this:
Do not improve a process until you know whether
it is part of the bottleneck,
the control architecture, or the waste.
Align is not agreement
The third capability in the HBR framework is Align. Again, the logic is sound. Improvement efforts need to connect across the system rather than remain fragmented.
But alignment is one of the most abused words in executive language.
In too many organizations, alignment means the deck was presented, nobody objected loudly, and each function walked away believing its own priorities remain intact. The appearance of agreement masks the absence of shared tradeoffs.
Real alignment is harder. It shows up when leaders commit the same scarce resources to the same few priorities, use the same decision logic, and accept the same consequences when tradeoffs become painful.
Why this matters:
Without operational alignment, improvement efforts compete instead of compound. The operations team pushes for throughput, quality pushes for control, commercial pushes for responsiveness, finance pushes for efficiency, and each function can make a rational case. The business stalls not because people disagree, but because nobody resolves the disagreement structurally.
What to do:
Define alignment in operational terms:
one named executive sponsor
one operating owner
one review forum with decision rights
one agreed metric of business effect
one escalation path when cross-functional conflict blocks progress
If those mechanisms do not exist, the organization is not aligned. It is coexisting.
A better rule is this:
Alignment is only real when it changes resourcing,
decision speed, and cross-functional behavior.
Transform cannot wait until the end
HBR positions Transform as the culminating capability. There is a clean logic to that. Organizations discover, then improve, then align, and eventually transform.
That sequence is elegant. It can also mislead.
In many sectors, transformation cannot be treated as the final maturity stage. The operating model is already under pressure from digital traceability, regulatory expectations, customer responsiveness, supply volatility, and cost compression. In those contexts, leaders cannot assume that better discovery and local improvement will save an outdated operating architecture. Related HBR commentary on transformation also emphasizes that many efforts fail because leadership behavior and organizational design are not equipped for the change being attempted.
Why this matters:
A company can become very disciplined at improving a model that no longer fits the market. That is a dangerous form of competence. It creates confidence without adaptability.
What to do:
Use transformation as a design lens early, not just a destination later. Ask:
Has complexity outgrown our current governance?
Are current decision rights slowing the business?
Is our reporting structure obscuring true accountability?
Are digital, quality, safety, and commercial systems working as one operating spine or as parallel bureaucracies?
A better rule is this:
Do not wait to “earn” transformation if the business model has already changed.
The missing capability is proof
This is the biggest gap in the HBR model.
A company can discover, improve, align, and even claim transformation, yet still fail because it cannot prove what changed and whether the result will hold. HBR is rightly focused on cumulative capabilities, but executive teams also need verifiable evidence that those capabilities are producing business effect.
Why this matters:
Without proof, operational improvement becomes narrative-driven. Leaders start relying on confident language, curated dashboards, and selective examples. Progress sounds real before it is real. That is how executive teams walk into board meetings with motion but not traction.
What to do:
Add a fifth leadership discipline: Proof.
Proof requires:
source data
named ownership
mechanism changed
validation logic
visible trend over time
business effect, not just activity completion
This is where many improvement programs fail the executive test. They show effort. They do not show durable performance shift.
A better rule is this:
No improvement claim without traceable evidence of sustained effect.
The D-I-A-T-P Operating Test
Use this five-part test in any operational review.
Discover
What early signal are we seeing before the KPI moves?
Improve
What mechanism are we changing, not just what action are we taking?
Align
Who owns the cross-functional tradeoff, and where is it decided?
Transform
Does this issue point to a local fix or an operating model redesign?
Prove
What evidence shows the result is real, repeatable, and economically relevant?
This framework hardens the HBR model into something leaders can actually govern.
Executive review agenda for operational improvement
Use this agenda for a weekly or biweekly leadership review.
Signal review
What has changed before outcome metrics moved?
Constraint review
Which issue most threatens value, risk, or customer performance right now?
Decision review
What tradeoff must be made today on priority, resource, or ownership?
Validation review
Which claimed improvements have proof of sustained effect?
Redesign review
Which recurring issues indicate the operating model itself needs to change?
This keeps the meeting from collapsing into status narration.
If you only do one thing
Redefine operational improvement from project activity to capability building.
Require every significant signal to trigger a defined decision path.
Add proof of sustained business effect before calling anything an improvement.
Common objections
“We do not have time to redesign governance”
You already spend the time. You just spend it in escalations, repeated reviews, duplicated work, and recovery efforts. Weak governance does not save time. It redistributes waste into management calendars.
“This will not work here because our business is too complex”
Complexity is exactly why this matters. In simple environments, informal coordination can carry the load. In complex businesses, it collapses. The more regulated, cross-functional, or multi-site the enterprise becomes, the more dangerous it is to rely on goodwill and local heroics instead of explicit operating mechanisms.
Close
The recent HBR study makes a valuable contribution because it moves the conversation beyond tools and toward cumulative capability. That is the right direction. But leaders should not stop at admiration. They should interrogate the model. Discovery without governance is passive. Improvement without constraint logic is wasteful. Alignment without tradeoff discipline is theater. Transformation treated as a distant phase is too slow for many businesses. And without proof, all of it can still turn into narrative.
Operational improvement is not won by the company with the most initiatives. It is won by the company that can convert signal into decisions, decisions into coordinated action, and action into evidence faster than risk accumulates.
That is where execution stops being a slogan and becomes a system.
About PIOL
We translate complexity into signal, helping leaders see what is changing, what it means, and where attention is required before risk compounds or opportunity passes.
If you’re new to PIOL – Practical Intelligence for Organizational Leadership, you can follow for free to get future issues or paid to expanded views for actionable guidance.
The PIOL Platforms
PIOL Radar™ Intelligence and risk monitoring for faster, better-informed decisions.
PIOL CertPath™ Guided certification readiness from gap to audit-ready.
PIOL StrategyOS™ Strategy-to-execution discipline for leadership teams.
PIOL Offer2Close™ Deal execution from accepted offer to clean close.
Visit piol.ai to learn more.