There is a specific kind of organizational frustration that Lean and Agile leaders know well. The transformation has been running for two or three years. The training is done. The coaches have been through. The shop floor is more disciplined, the sprint cadence is holding, waste has been reduced in the places it was targeted. And yet the strategic initiatives on the leadership dashboard are still stuck. The organization is running better and going nowhere faster.
This is not a failure of Lean or Agile. It's a misunderstanding of what those frameworks are designed to solve — and a blind spot about what they were never designed to touch.
What does Lean actually solve — and what does it leave untouched?
Lean is one of the most powerful operations improvement systems ever developed. Rooted in the Toyota Production System, it gives teams precise tools for identifying waste, standardizing processes, reducing variation, and building quality into work rather than inspecting it out afterward. Lean also provides team-level operating rhythm through daily standups, tiered daily management, and PDCA cycles — structured moments where teams review what happened, what's blocked, and what needs to change.
Lean even has an answer to strategy translation: Hoshin Kanri, also called Policy Deployment, is a planning methodology that cascades strategic goals down through the organization using a "catchball" process — targets and improvement priorities are negotiated up and down until alignment is reached. Done well, it's a genuinely powerful way to connect leadership intent to operational priorities.
The limitation of Hoshin Kanri is that it is a planning tool, not an operating rhythm. It creates alignment at the start of a planning cycle — typically annually. What it doesn't provide is a cadenced, real-time mechanism for the leadership team to review whether the strategy is on track, what operational signals need to change the plan, and what decisions need to be made together right now. Once the year is in motion, the translation layer needs active, ongoing maintenance. Hoshin Kanri sets the direction; it doesn't maintain the connection.
When that ongoing layer is absent — when priorities shift, when assumptions prove wrong, when operational reality diverges from the plan — Lean produces local optimization that doesn't add up to strategic progress. Teams get better at executing a plan that has quietly become the wrong one.
"Lean can make the machine run beautifully. Hoshin Kanri points it in a direction. Neither one keeps that direction current."
Where does Agile run into the same wall?
Scaled Agile frameworks go further than Lean in acknowledging the leadership layer. SAFe (Scaled Agile Framework) adds program-level planning through PI (Program Increment) planning events, involves Business Owners in reviewing team objectives, runs quarterly Inspect & Adapt workshops, and maintains a Portfolio Kanban to connect strategy to delivery. LeSS (Large-Scale Scrum) takes a more minimalist approach — fewer roles and ceremonies, more emphasis on direct Scrum scaling — but similarly creates structured touchpoints between strategy and execution at the program level.
These are genuine contributions. The reason the table below marks them as "partial" on leadership operating rhythm is specific: the leadership touchpoints in both SAFe and LeSS are organized around delivery — what is the program committing to, how well did it deliver, what impediments need to be removed? They are not organized around the full scope of leadership decision-making: strategic direction, organizational performance against indicators, tough cross-functional problems, and real-time organizational response.
In SAFe, Business Owners attend PI planning to review team objectives and score confidence. That's valuable — but it's a delivery review, not a strategic leadership session. The Inspect & Adapt workshop runs quarterly and surfaces systemic impediments — again valuable, but bounded to the delivery context. What's missing is a forum where the leadership team — not just in its role as program sponsor, but as the body responsible for organizational direction — reviews the full picture together on a cadenced rhythm.
The question that Agile at any scale doesn't fully answer is: are we delivering the right things? When strategy is clear and stable, Agile's cadence is enormously powerful. When leadership doesn't have a shared, current picture of where the organization is headed and how it's performing, sprints fill with work that feels productive but doesn't accumulate into strategic outcomes. Velocity goes up. Strategic progress does not.
What is the missing layer — and why is it always skipped?
The layer that both frameworks leave largely unaddressed is the leadership operating rhythm: a set of structured, recurring meetings in which the leadership team addresses strategic direction, organizational performance, tough problems, delivery plans, and daily response — each in its own dedicated session, with its own cadence, and with shared visual information in front of them.
This is not a management meeting. It is not a status review. It is a practice of shared sense-making — a regular moment where the people responsible for direction and the people responsible for execution are in the same room, looking at the same information, having the same conversation.
It gets skipped for a straightforward reason: Lean and Agile frameworks focus on improving the work. Coaches are trained to go to the gemba, to the backlog, to the sprint board. The leadership team's operating rhythm sits above all of that — and it looks, from the outside, like a leadership problem rather than a methodology problem. So the methodology doesn't touch it, and the leadership team continues to operate the way it always has, just with better-running teams below.
| What it addresses | Lean | Agile (SAFe / LeSS) | Obeya |
|---|---|---|---|
| Process waste elimination | ✓ | — | — |
| Team-level delivery cadence | ✓ standups, PDCA | ✓ sprints | — |
| Strategy deployment (planning) | ✓ Hoshin Kanri | ✓ PI planning | — |
| Program-level coordination | — | ✓ | — |
| Leadership operating rhythm | — | Partial * | ✓ |
| Real-time strategy tracking | — | — | ✓ |
| Shared visual management for leaders | — | — | ✓ |
* SAFe includes Business Owner reviews and Inspect & Adapt workshops, but these are delivery-scoped — not a full leadership operating system for strategic direction and organizational performance.
How does Obeya complete the system?
The Leading with Obeya method was not designed to compete with Lean or Agile. It was designed to sit above them — as the leadership layer that makes both more effective by ensuring they're pointed in the right direction.
Where Lean and Agile focus on improving and accelerating the work, Obeya focuses on the leadership team's ability to direct that work with clarity and coherence. Its five boards — Strategic Direction, Performance, Tough Problems, Plan to Value, and Act & Respond — each address a distinct leadership question. And critically, each board has its own dedicated meeting, its own participants, and its own cadence.
Strategic Direction is reviewed quarterly — setting the framework everything else runs inside. Performance is reviewed every two weeks — tracking indicators and deciding where to intervene. Tough Problems has its own sessions one to two times per week — structured root-cause work on the issues the team doesn't yet know how to solve. Plan to Value is reviewed on a separate bi-weekly rhythm — milestones, resource allocation, delivery against commitments. Act & Respond runs three times a week — the fast loop for emerging issues, decisions, and daily coordination.
This is the operating rhythm that Lean and Agile teams need their leadership to be running above them. Not a single all-hands review, but a set of purpose-built meetings — each with a clear focus, a clear cadence, and a clear output. The result is that strategic decisions reach teams faster and in clearer form. Operational signals reach leaders before they become crises. The translation layer that most organizations are missing gets built — not below the leadership team, but at it.
What does adding Obeya to an existing Lean or Agile program look like?
The practical answer is simpler than most leaders expect: it starts with the leadership team, not the shop floor. The teams below don't need to change their ways of working. The sprint cadence keeps running. The kaizen events keep happening. What changes is how the leadership team above them operates.
The boards go up — physical or digital — with the five information domains. The leadership team then establishes its operating rhythm: five distinct meetings, each tied to a specific board and a specific cadence. The Act & Respond session runs three times a week for fast-loop coordination. Tough Problems runs one to two times a week for structured problem-solving. Performance runs every two weeks. Plan to Value runs every other two weeks. And Strategic Direction is reviewed quarterly to reset the frame. In the first weeks, the most common discovery is that half the indicators on the Performance board are empty — not because the data doesn't exist, but because nobody had ever defined which indicators actually mattered at the leadership level. The operating rhythm surfaces that gap immediately and gives the team a concrete starting point.
Within a few months, the teams below start to notice something: decisions come down faster, more consistently, with clearer rationale. Escalations get resolved rather than deferred. The strategic priorities that were previously abstract start to show up as concrete guidance for how the next sprint or kaizen event should be prioritized. The improvement work below gains traction because the leadership above has gained direction.
This is the layer that Lean and Agile leave open. It's not a criticism of either framework — it's the natural boundary of what they were designed to solve. Filling that layer is what Obeya is built to do. And in organizations that have already invested in Lean or Agile, adding it is the highest-leverage move available, because the infrastructure for operational improvement is already there. The only thing missing is the leadership system that directs it.
If you're working in an organization with an existing Lean or Agile program and want to explore what the leadership layer could look like, the free Obeya webinar is the fastest way to see the method in action. Or explore the full range of Leading with Obeya training programs designed to build it.