Lean
- 12 minute read
Discover how Gemba Walks revitalize organizational culture and enhance operations. Explore their benefits, tips, and practical uses.
Why iObeya
Most manufacturers don’t lack lean tools. They have a 5S program, Kaizen events, KPI dashboards, and even a strategic plan signed off by the executive committee. What they lack is the link between that strategy and what actually happens on the shop floor every morning. Leadership says “improve quality by 15%.” The team leader has never heard of it. This is exactly the gap operational excellence is designed to close.
If I had to define operational excellence, I’d put it this way:
Operational excellence (or OpEx) is a management system that aligns strategy, processes, and teams, so that every level of the organization makes day-to-day decisions that create value for the customer, reduce waste, and reinforce the company’s long-term objectives.
This guide details what operational excellence actually means, the five pillars that structure it, what it looks like in real plants, the management rituals that keep it alive, and a four-step approach for starting to build it in your own organization.
Operational excellence is often reduced to “being efficient.” In practice, it is more specific than that. It describes a state (and an ongoing effort) where the organization’s strategy is visible and actionable at every level, where problems are escalated and solved as close as possible to where they occur, and where improvement is part of daily work rather than being treated as a separate project.
The table below breaks the definition down into its core components, and what each one looks like once it’s actually in place on the shop floor.
| Concept | What it means | What it looks like on the shop floor |
|---|---|---|
| Strategic alignment | Leadership objectives are translated into goals every team can own | A Hoshin Kanri board breaks the annual plan down into quarterly targets by line |
| Visual management | Performance and problems are visible to everyone, in real time | SQCDP boards on every line showing safety, quality, cost, delivery, and people |
| Daily rituals | Structured routines to check the system's status and react quickly | Escalation meetings every morning, from the operator up to the plant manager |
| Continuous improvement | Waste and variability are systematically identified and removed | Kaizen events and problem-solving A3s tracked through to closure |
| Digital foundation | Systems and teams are connected across the organization | A shared digital management system, replacing paper boards and spreadsheets |
Put together, these five components are what distinguishes a plant that talks about excellence from a plant that practices it.
Most operational excellence frameworks converge on the same five pillars. Each one answers a different question about how the organization creates and protects its value.
A company can roll out tools without ever reaching operational excellence (tools installed with no alignment or lasting behavior change), and a company can practice continuous improvement without formally adopting the lean mindset (problem-solving habits without the specific toolkit).
Conceptual frameworks are useful, but operational excellence is ultimately judged by what changes on the shop floor. Three examples from iObeya customers illustrate what this looks like, at different scales.
The common thread across these three examples: operational excellence shows up as faster, more consistent decisions, not as a poster on a wall.
A conceptual framework stays theoretical until it’s embodied in routines that teams actually practice. These five rituals are how operational excellence principles become a daily practice.
Organizations that succeed with operational excellence rarely start by rolling out every pillar and every ritual at once. They build progressively, roughly in this order.
It’s also worth noting that these four steps rarely unfold in a strictly linear fashion. In reality, programs loop back: a pilot reveals that the initial assessment missed a key constraint, or a company-wide rollout surfaces a site whose process maturity is too low for the standard rituals to take root. Treat this sequence as a cycle to revisit, not a checklist to tick off once and for all.
Many organizations launch an operational excellence effort with good intentions and a sizable budget, then watch the momentum fade within twelve to eighteen months. The pattern is almost always the same: tools get rolled out, training gets delivered, early wins get highlighted, and then, without renewed management attention, the rituals gradually empty out. Meetings still happen, but without real discussion. Boards still get updated, but no one really looks at them anymore.
What separates efforts that last from those that don’t is rarely the sophistication of the framework chosen. It’s management consistency: leaders who keep showing up on the shop floor months, even years, after the initial launch; standards that evolve based on feedback rather than being frozen once and for all; and a genuine tolerance for mistakes when they serve collective learning. Conversely, the moment problems raised in a meeting stop getting a concrete response, team trust collapses, and the whole system goes with it.
There’s also a dimension that often gets overlooked: consistency between what’s said and what’s rewarded. If an organization presents continuous improvement as a priority but keeps judging teams solely on short-term volume metrics, the message sent on the shop floor contradicts the official line. Operational excellence requires that recognition systems, individual objectives, and management rituals all tell the same story.
