Obeya

Origin. Toyota product development; the word means "big room" or "war room." Formalized by Takeshi Uchiyamada during the development of the first Prius (1990s).

Mechanism. Cross-functional teams work in a shared space with visual displays showing project status, problems, and decisions. The physical co-location accelerates communication and decision-making. Information radiates from the walls; anyone entering the room can quickly understand the state of the project. Problems are visible and addressed immediately rather than hidden in reports.

Procedure. Designate a physical room (or persistent virtual space) for the project. Display key information visually: schedule, open issues, decisions, metrics, current focus. Bring cross-functional team members together regularly in the space. Use the walls as working memory: post problems, track countermeasures, visualize dependencies. Conduct standing meetings at the displays. Decisions made in the obeya are binding; do not re-litigate elsewhere.

Applies to. Product development, complex projects, any initiative requiring sustained cross-functional coordination.

Limitations. Obeya as meeting room rather than working space. The value comes from continuous presence and updated displays, not from scheduled meetings. Also: visual management without action — walls covered in charts that no one uses for decisions. The information must be current, relevant, and acted upon.