In one line: A “big room” where a complex program’s status, problems and decisions are visible on the walls to everyone at once. It replaces slow reporting chains with shared, real-time understanding.
Core idea
Obeya is Japanese for “large room.” The practice comes from lean product development: a chief engineer gathers the program’s key information (schedule, targets, open problems, test results, cost) on the walls of one room, and the cross-functional leads meet there regularly. It borrows from the lean factory’s visual management, where the state of operations is visible at a glance (andon boards) and anyone can stop the line to fix a problem. The same idea is applied to development work, where the “line” is invisible unless someone makes it visible.
How it works
- One place, one picture. Status is posted, not presented, so everyone sees the same truth.
- Organized by flow. The walls typically show the plan against actuals, the key metrics, the top problems with their owners, and upcoming decisions.
- Short, frequent stand-ups. Leads meet in front of the walls and talk about problems and decisions, not status recitals.
- Problems are surfaced, not hidden. The visual format makes a slipping item hard to ignore and easy to help with.
- It can be virtual. Distributed teams use shared dashboards and boards, but the discipline (one source of truth, owned problems, regular reviews) matters more than the room.
In practice
In a matrix organization, Obeya does for information what RACI Charting does for decision rights: it removes the friction of people working from different versions of reality. A practical first step for an engineering team is a single shared board of the top ten open issues, each with an owner and a date, reviewed weekly with everyone present. The effect is often less reporting effort, not more, because the board replaces the slide decks.
Questions to ask yourself
- Where does my program’s “single source of truth” live, and does everyone use it?
- How long does it take bad news to reach the person who can act on it?
- What would we put on the wall first?
Connections
- Companion tool: RACI Charting. Context: Product Development Organizations.
- Roots: Lean visual management. Content it displays: Project Scheduling, Quad Charts.
- Capabilities exercised: Communicating and Advocacy, Connecting Across Disciplines, Realizing the Vision.
Sources
- Course module on Obeya and RASIC; no public source.