An obeya, Japanese for "big room," is a dedicated visual space where a cross-functional team meets frequently with all project status, plans, problems, metrics, and decisions posted on the walls, so everyone sees the same picture and decisions get made fast. Toyota pioneered it developing the first Prius.
Most projects die of fragmentation. Engineering knows one thing, the floor knows another, scheduling a third, and the whole picture exists only in a status deck that is stale the moment it is printed. An obeya fixes that by putting the entire project on the walls of one room and getting the people who own each piece into that room together, often. It is visual management scaled up to run a whole program, and it is one of the most practical tools in lean for keeping a complex effort aligned and moving.
What Is an Obeya Room?
An obeya is a physical (or increasingly digital) room where all the information needed to run a project or manage a value stream lives on the walls, and where the cross-functional team gathers on a regular cadence to see status, surface problems, and make decisions together. Nothing important hides in an inbox or a private spreadsheet; if it matters to the project, it is on the wall where everyone can see it. The Lean Enterprise Institute describes obeya as a large room used to enhance effective communication and speed decision-making by bringing people and visual information together (Lean Enterprise Institute, Obeya).
The magic is not the room; it is the co-location of information and people. When the plan, the actual progress, the open problems, and the metrics are all visible at once, and the people who own them are standing in front of them together, a decision that would take three meetings and a week of email happens in ten minutes at the wall.
Where Did the Obeya Room Come From?
The obeya was born at Toyota in the early 1990s, during the development of the first Prius. Chief engineer Takeshi Uchiyamada faced a problem no single person could solve: commercializing a hybrid drivetrain nobody had mass-produced, against aggressive targets for cost, performance, and schedule. He recognized that he lacked the technical depth to direct every discipline himself, and that no one at Toyota had it either. What the program needed was an unprecedented level of collaboration, transparency, and speed of decision-making.
His answer was the obeya. Uchiyamada gathered the required technical experts into one room every few days, with all the pertinent information posted on the walls, and used that shared picture to integrate their work and keep the program on its no-compromise targets. The Prius shipped, reset the industry's expectations for fuel economy, and the obeya, credited as a major contributor to that success, became a development staple at Toyota and spread across lean practice worldwide.
What Goes on the Walls of an Obeya?
An obeya's walls are organized so that anyone can walk in and read the state of the project in minutes. The exact zones vary, but a well-run obeya almost always makes six things visible together:
Strategy and objectives anchor why the project exists and what "done" means. The plan shows the timeline and milestones. Status shows plan versus actual, honestly, including where the project is behind. Problems and countermeasures make the current obstacles and who is working them visible. Metrics show the handful of numbers that matter. And decisions and actions capture what was agreed, by whom, and by when, so nothing decided at the wall gets lost.
How Do You Run an Obeya?
An obeya is a habit, not a display. The walls are worthless without a disciplined cadence of people standing in front of them and acting. A workable operating rhythm:
- Assemble the cross-functional team. Bring the people who own each piece of the project, engineering, operations, quality, scheduling, into the same standing membership. The obeya only works if the decision-makers are in the room.
- Set a fixed cadence. Meet on a regular, frequent beat, daily or a few times a week for an active program, short and standing. Toyota's Prius team met every two to three days; the point is rhythm, not marathon meetings.
- Walk the walls in order. Move through the zones the same way each time, objectives, plan, status, problems, so the review is fast and nothing is skipped. The visuals carry the meeting; slides are not needed.
- Surface problems without blame. Make it safe to post red. An obeya where status is always green is theater; the value is in exposing what is behind and swarming it, the same instinct as an andon pull.
- Decide and assign at the wall. Convert discussion into named actions with owners and dates, posted where everyone sees them. Speed of decision is the obeya's whole reason for existing.
- Keep the walls current. Update the visuals before each session so the room always shows reality. A stale obeya loses trust fast, and a room no one trusts empties out.
How Is an Obeya Different From a War Room or a Status Meeting?
An obeya looks like a war room, but two things set it apart. A war room is usually temporary, spun up for a crisis and torn down when it passes; an obeya is a standing part of how the work is run. And a status meeting reports information, often through slides prepared to look good, whereas an obeya works information, standing in front of the raw, current visuals to make decisions. The obeya is closer in spirit to a gemba board or a kamishibai board scaled to a whole program: the same principle that the truth of the work should be visible, shared, and acted on where it is posted, not buried in a deck.
What Are the Common Obeya Mistakes?
Most obeya failures are cultural, not visual, and they show up in a few predictable ways. The first is the all-green wall: if every status is green and every problem is quietly hidden, the obeya has become a place to look good rather than a place to solve problems, and it is worse than useless because it launders bad news into false confidence. The second is the stale wall, updated the night before a big review and left to rot in between; a plan-versus-actual board that lags reality by a day teaches the team to stop believing it. The third is the meeting without decisions, where the group walks the walls, discusses, nods, and leaves with nothing assigned, which turns the obeya into an expensive standing report. The fourth is the wrong people, an obeya staffed by delegates who cannot commit their function, so every real decision gets deferred to a conversation that happens somewhere else. Each of these hollows out the room. The cure in every case is the same discipline: make red safe, keep the picture current, and end every session with owned actions. None of that requires a bigger room or a better screen; it requires a leader who protects those three habits even when the schedule is tight and the temptation to skip the session is highest.
Does an Obeya Have to Be a Physical Room?
No. The original obeya was a physical room with paper on the walls, and for a co-located team that is still hard to beat, because the room itself pulls people together and standing at the wall shoulder to shoulder changes the conversation. But distributed teams now run "digital obeya," a shared virtual board that holds the same zones, strategy, plan, status, problems, metrics, decisions, and the same disciplined cadence. What must not change, physical or digital, is the substance: one shared, current picture, the right people meeting on a beat, problems visible, and decisions made and owned at the wall. Get those right and the medium matters little; get them wrong and the fanciest screen is still just a status meeting.
The hardest part of a digital obeya, and of any obeya, is keeping the picture true and current without a person manually re-typing numbers off the floor every morning. An obeya is only as honest as its freshest data, and a plan-versus-actual wall that is a day stale quietly teaches the team to stop trusting it. That is the practical case for feeding an obeya from a live signal off the line rather than a hand-updated spreadsheet, the same idea as real-time visibility over the systems you already run no rip-and-replace, so the status wall shows this hour's reality, not yesterday's. It connects naturally to the plant's daily strategy deployment and to the alignment work of nemawashi that happens in the smaller conversations around the same walls, and it is the visual backbone of the kind of connected-worker operation we describe in our CLS rollout. Much like leveling with heijunka an obeya turns a scattered, reactive effort into one the whole team can see and steer together.