Definition
Obeya is a dedicated physical room where cross-functional team members regularly gather to manage a complex project or program. The walls of the room display the project schedule, current status, open problems, key metrics, and pending decisions — making the entire state of the project visible at a glance. The purpose is to enable rapid, face-to-face alignment and problem-solving among people from different functions who would otherwise communicate through reports, emails, and meetings.
The obeya is not a meeting room that happens to have charts on the wall. It is a management method — a structured practice of gathering the right people in front of the right information at a regular cadence to identify and resolve problems before they compound.
Japanese Origin
Obeya (大部屋) combines 大 (o, “big” or “large”) with 部屋 (heya, “room”). The word is ordinary Japanese — it simply means “big room” and has no special manufacturing connotation. Toyota adopted it as a management practice name because the method is exactly what the name describes: put everyone in a big room with all the information on the walls.
History at Toyota
Prius development, 1993-1997 — The obeya method is most famously associated with the development of the Toyota Prius, led by chief engineer Takeshi Uchiyamada. The Prius project faced extreme technical uncertainty (hybrid powertrain technology had never been mass-produced) and an aggressive timeline. Uchiyamada established a dedicated obeya where engineers from powertrain, body, chassis, electronics, manufacturing, and other functions gathered regularly. Problems were posted on the walls, and cross-functional decisions that might take weeks through normal channels were made in minutes.
Rooted in Toyota’s chief engineer system — The obeya formalized a practice that Toyota’s chief engineers had long used informally. The chief engineer (shusa) is responsible for the entire vehicle program and must coordinate across all functional departments. The obeya gave this coordination a physical center and a visual management structure.
Spread beyond product development — After the Prius, the obeya method spread within Toyota to other complex programs: new plant launches, major quality campaigns, and supply chain recovery efforts. The method works whenever a complex initiative requires rapid cross-functional coordination.
How It Works
Physical setup:
- A dedicated room (not shared or multipurpose) with wall space for visual displays
- Project schedule and milestones displayed prominently
- Current status of each workstream, updated regularly
- Open problems and issues listed visibly, with owners and due dates
- Key metrics and targets posted for tracking
- Space for A3 reports on active problem-solving efforts
Cadence:
- Regular standup meetings (often daily or every few days) where team members review status, surface problems, and make decisions
- Meetings are short and focused — the visual displays replace the need for lengthy presentations
- The chief engineer or project leader facilitates, but the expectation is that every function reports status and raises issues directly
Decision-making:
- Problems that cross functional boundaries are resolved in the obeya, not escalated through separate management chains
- Because all the relevant people and information are in one place, decisions happen faster
- Decisions and their rationale are posted on the wall for transparency
Common Mistakes
Creating an obeya without authority. If the people in the room cannot make decisions — if everything must be escalated to functional managers outside the room — the obeya becomes a reporting exercise, not a management method. The obeya works because it concentrates both information and decision-making authority.
Using the obeya only for status reporting. The value of the obeya is in surfacing and solving problems, not in broadcasting status updates. If meetings consist of each person reading their status and no problems are discussed, the obeya is not functioning.
Neglecting the visual management. The walls must be kept current. Outdated displays destroy trust in the obeya as a management system. If the information on the walls does not reflect reality, people stop looking at the walls and revert to separate communication channels.
Making it virtual by default. While remote tools can support distributed teams, the power of the obeya comes from physical co-presence — standing in front of the same wall, pointing at the same chart, making eye contact during difficult conversations. Virtual obeya implementations lose much of this immediacy and require deliberate effort to compensate.