Directly Linking Improvement to Strategy: Why Focus Beats Effort Every Time

 


Lean Nation;

Every organization wants to improve. Most have already invested in the tools to do it — trained staff, kaizen events, process maps, dashboards. Some have gone further and built real leadership commitment to changing the culture, not just the metrics.

And yet, year after year, a huge number of these organizations fail to produce a single breakthrough result. Not because they lack capability. Not because leadership doesn't care. They fail because of one avoidable leadership flaw: a lack of focus.

This isn't a minor tactical issue. It's the single biggest reason well-resourced improvement efforts quietly stall out, one initiative at a time, until nobody can quite explain where all the effort went.

The Trap Most Organizations Fall Into

Picture an organization with several hundred trained improvement specialists spread across multiple sites. Most are part-time — they hold full-time roles elsewhere — but collectively, that's a serious amount of improvement capacity. Add to that a leadership team that's genuinely willing to resource projects, and on paper, this company should be unstoppable.

Now add one detail: this organization was tracking and expecting improvement in over 150 key measures.

Not 15. Not 50. 150.

No one in the building could clearly say which of those 150 measures actually mattered most, how they were calculated, or why they'd been chosen in the first place. So naturally, every team picked its own lane. One group chased a quality metric. Another went after a cost measure. A third focused on something in delivery. Scattered pockets of improvement popped up here and there — a process tightened here, a defect rate reduced there — but nothing that moved the needle at the organizational level.

Why? Because improvement work behaves like force applied to an object. Spread thin across 150 directions, it produces motion everywhere and momentum nowhere. There was never enough critical mass behind any single priority to actually move a "big dot" — a result significant enough to matter to the business, or to the customer.

The damage didn't stop at diluted results, either. With everyone chasing different priorities, teams ended up competing for the same scarce resources — IT support, supply chain bandwidth, engineering time. Managers spent real energy arguing over whose project deserved attention first. Leaders bickered over priority instead of aligning on it.

All of that friction — the competition, the debate, the redundant effort — is 100% waste. And it's entirely self-inflicted.

Leadership's First Job Is Choosing What Matters

Here's the uncomfortable truth: asking an organization to track, improve, and report on 150 different things isn't ambitious. It's close to negligent. No team — however capable — can hold that many priorities in its head, let alone execute against them with any real discipline.

The single most important thing a leadership team can do is decide, explicitly and narrowly, what the organization's priorities actually are. (The second most important thing, worth a quick mention, is making sure the right people are in place to do the work. But even great people can't outrun an unfocused strategy.)

So what does "focused" actually look like in practice? A world-class organization typically operates with somewhere between three and seven top-level priorities — full stop. Lean organizations in particular tend to converge on around five areas of focus.

These aren't arbitrary categories. They map directly to what's known as True North measures — the handful of outcome dimensions that represent genuine breakthrough performance from a customer's point of view:

  • Quality
  • Delivery
  • Cost
  • Growth
  • Human Development — because none of the other four happen without engaged people

Everything an organization tracks should ladder up to one of these five dimensions. If a measure doesn't connect to True North, it's a strong candidate for the cutting-room floor.

A Word on Hoshin Kanri (and a Warning)

The formal lean discipline for translating strategy into a small number of breakthrough objectives is called Hoshin Kanri — also known as policy deployment or strategy deployment. It's a well-documented process for developing, refining, cascading, and managing an organization toward a handful of strategic breakthroughs, and there are excellent books dedicated entirely to how it works.

This isn't a deep dive into Hoshin Kanri itself — plenty of other resources cover the mechanics better than a short post can. But if your organization is considering adopting it, one warning is worth repeating clearly: don't go in halfway.

Hoshin Kanri requires unwinding your existing strategic planning process, along with the operational and financial review cycles that currently support it. If you try to run Hoshin Kanri alongside your legacy planning system, you'll end up managing two competing systems — and the new one will lose, every time. There's no effective hybrid version of this. Either commit fully to the standard work of policy deployment, or don't adopt it at all. Half in, half out simply doesn't work.

From 150 to 7: A Realistic Path, Not a Leap

If your organization is sitting on a sprawling list of measures — 150, 50, even 30 — don't expect to jump straight to five or seven priorities in a single planning cycle. That leap is not just difficult; for most organizations, it's simply not achievable on the first attempt.

A more realistic milestone: get from 150 down to around 20. That's still a major narrowing exercise, but it's achievable, and it puts the organization meaningfully closer to the eventual goal of five to seven true breakthrough priorities. Treat it as the first lap of a multi-cycle journey, not a one-time fix.

What Great Organizations Do Differently

The organizations that consistently move big dots aren't smarter or better resourced than everyone else. They simply do a few things leadership-driven organizations often skip:

  1. They clearly articulate the critical few breakthrough strategies — not a laundry list, a short list.
  2. They resource those priorities properly, rather than spreading the same people and budget across dozens of competing efforts.
  3. They maintain active oversight of execution, rather than setting objectives and disappearing until the next review.
  4. They intervene quickly when something drifts off track, instead of waiting for a quarterly report to reveal the problem.

That combination — focus, resourcing, oversight, and fast course-correction — is what actually links day-to-day team-level improvement work back to organizational strategy. Without it, even a highly trained, well-intentioned improvement team will keep producing scattered pockets of progress instead of results that matter.

The Bottom Line

If your organization's improvement efforts feel busy but directionless, the problem probably isn't your people, your tools, or your training. It's very likely a focus problem sitting squarely with leadership.

The fix isn't more initiatives. It's fewer — chosen deliberately, resourced fully, and tied directly to the handful of True North measures that actually define breakthrough performance for your customers. Start narrowing the list. Even getting from 150 down to 20 is real progress toward the discipline that separates organizations that move big dots from those that just stay busy.


How many strategic objectives do you have?


Lean Blessings,

Ron

Ron Bercaw
President and Sensei
Breakthrough Horizons LTD.
www.breakthroughhorizons.com
2-time Shingo award winning author

Comments

Popular posts from this blog

Explaining the Lean Management System - Part 1 - The Key Elements

Explaining the Lean Management System Part 3 Managing for Daily Improvement

Explaining the Lean Management System Part 2 Production (or Process) Control