Lean
- 5 minute read
Foster a culture of continuous improvement and empower Lean transformations with real-time data visualization.
Why iObeya
An Obeya (大部屋, literally “big room”) is a visual management space, physical or digital, where a leadership team brings strategy, performance, and problem-solving together in a single place, to make decisions faster than by going through separate meetings. The concept originated at Toyota in the 1990s, as a steering room for vehicle program chief engineers.
Today, the word covers two very different realities depending on whether the room exists on a wall or in a piece of software. The table below sets out that initial distinction, before this guide goes into the detail of both approaches further on.
| Physical Obeya | Digital Obeya | |
|---|---|---|
| Medium | Walls, sticky notes, markers, paper boards | Connected platform, accessible remotely |
| Scope | One room, one site | Multiple sites, in real time |
| Update | Manual, during meetings | Continuous, fed by existing systems and humans |
| Main limit | Only works for co-located teams | Requires a change of tool and of habit |
Both versions share the same intent: making visible, in one place, the elements a team needs to decide fast.
This initial distinction, however, says nothing about what actually belongs inside an Obeya. Many rooms look like an Obeya without following its principles: a wall of indicators with no regular review ritual, for instance, isn’t one. The following sections detail what sets a properly built Obeya room apart from a simple display.
The Obeya originated in the Toyota Production System, where the “Chief Engineer” role required overseeing an entire vehicle program, design, quality, cost, timeline, without direct hierarchical authority over every team involved.
The Obeya room was the practical answer to that problem: gather representatives from each function in the same place, with up-to-date information in front of them, so decisions could be made in hours rather than weeks of cross-validation. Jeffrey Liker, in The Toyota Way describes this mechanism as one of the structuring levers of Toyota’s product development system, more than just a display tool.
The principle has since spread well beyond the automotive sector. In the pharmaceutical industry, sites such as Sanofi’s have adopted the Obeya logic to steer production performance across multiple plants, with the added requirement of traceability and regulatory compliance specific to that sector.
In aerospace, programs have applied the same pattern to coordinate complex supply chains, where a delay at a supplier needs to be visible before it becomes a delivery problem. In logistics, operators such as ID Logistics have extended the method to dozens of warehouses, where the challenge is no longer coordinating a single program but keeping a steering model consistent everywhere it’s replicated.
What hasn’t changed since the Toyota workshops of the 1990s is the core idea: an Obeya isn’t just another meeting room, it’s the place where information crosses silos faster than it would through the usual chain of command.
This transposition is, however, far from automatic. A vehicle program at Toyota and a pharmaceutical production line don’t operate on the same timeline or under the same compliance constraints. What gets transposed isn’t the room itself, but the organizing principle: bring the right people together, with the right information, often enough that decisions don’t sit in an email queue or a calendar of disconnected meetings. Each sector has had to adapt the frequency of its rituals and the nature of its walls to its own constraints, without giving up that underlying principle.
These six elements exist independently of the physical or digital medium. This is precisely what makes it possible to carry the method over from a wall of sticky notes to a connected platform without losing what matters.
An Obeya with no regular meeting turns back into a decorative wall within a few weeks. The meeting is what keeps the six elements alive.
For the daily ritual, attendance stays deliberately narrow: the relevant team or line leaders, plus the site facilitator. Fifteen to twenty minutes is enough. The performance wall is reviewed first, what’s drifting, what’s under control, then the problem-solving wall, to check that actions opened the day before have actually progressed. The strategy wall generally isn’t reopened every day: it serves as backdrop, not as a daily agenda item.
The weekly ritual brings together a wider circle, site managers, sometimes support functions, and runs longer, often thirty to forty-five minutes. This is when the strategy wall gets explicitly reconnected to the week’s performance: is the current trajectory holding the quarterly target? It’s also when escalations left unresolved at the daily level get settled, with an actual decision rather than a mere observation.
In both formats, the rule that separates a productive Obeya from an ordinary status meeting stays the same: you don’t read numbers out loud, you discuss the deviations.
If a team spends its time stating what the wall already shows, it’s wasting time in the meeting. The decision gets made in the room, in front of the wall, not in a follow-up email exchange; this is the discipline that justifies the time spent standing in front of a board rather than sitting around a table.
How decisions get logged deserves to be made explicit from the moment the ritual launches. A decision made in an Obeya needs a name attached, a deadline, and a way to verify it; otherwise it dissolves into the meeting notes, and nobody knows, the following week, whether it was actually carried out. This detail, more than the room’s format itself, is often what separates an Obeya that produces measurable results from an Obeya that simply moves the meeting from one place to another.
When does it make sense to consider digitizing your Obeya room? The digital Obeya changes the scale at which the method can operate. A physical room only serves one site; a connected platform makes it possible to replicate the same structure across multiple plants, with data fed continuously from existing systems rather than copied by hand before each meeting.
Based on iObeya customer deployments, as of 2026, teams switching to a digital Obeya reach an average of 95% frontline adoption in under 30 days, roughly three times faster than with traditional visual management tools, with most of the time saved coming from teams finding a meeting structure they already know, simply carried by a different medium.
What doesn’t change, either way, are three fundamentals: the ritual has to happen at the intended frequency, the accountability for each action has to stay visible to everyone, and visual discipline, a wall readable in a few seconds, has to take priority over the completeness of the data displayed. A poorly designed digital Obeya, overloaded with dashboards, fails exactly the way a physical wall overloaded with sticky notes does: nobody knows where to look first anymore.
The choice between the two isn’t always binary, either. Many organizations start physical at a pilot site, long enough for the team to own the ritual without depending on a tool, then move to a digital version once the discipline is in place and the need to replicate elsewhere becomes concrete. Reversing that order, deploying a digital tool before the team has experienced the rigor of a physical Obeya ritual, works too, but requires more sustained change support, since the team is discovering the method and the tool at the same time.
iObeya transposes the six elements of the Obeya, the strategy wall, the performance wall, the problem-solving wall, action tracking, the escalation path, meeting cadence, into a shared digital workspace, accessible from any site. Each wall stays organized using the same logic as a physical room, which reduces the adjustment time for teams used to the paper format.
The platform connects performance walls to real data from existing systems, ERP, MES, quality, limiting the manual entry that eventually causes a paper Obeya to drift. The escalation path and action tracking become visible in real time across every site involved, letting a manufacturing leadership team compare multiple plants using the same reading grid, with no travel required.
Manufacturers like Sanofi, across more than 90 sites, or ID Logistics, with more than 80 sites and more than 200 digital Obeya rooms, use this approach to keep the rigor of the Obeya ritual at a scale a single physical room could never cover. Stellantis, with 33,500 users on its platform, illustrates what the method becomes once deployed at the scale of a large industrial group.
To see how these six elements take shape in practice on the platform, a demo remains the fastest way to judge what fits your organization.
Whatever the starting point, a pilot room at a single site or a multi-plant rollout from the outset, the method ultimately gets judged on the same criterion: how fast a deviation spotted on a wall turns into a decision actually made. An Obeya that respects this discipline, physical or digital, eventually becomes an organization’s default reflex rather than a ritual run out of obligation.
