The engineering plan looks healthy. The purchasing plan looks healthy. The launch still slips because the two plans depend on different dates for the same component. A shared project room is useful when it exposes that mismatch early enough to act.
The Lean Enterprise Institute’s explanation of obeya describes a “big room” used for visual management, particularly in product development. Goals, timing, progress and countermeasures are made visible to support communication. Filling a room with charts is only the physical part of the idea.
Start with one decision the team struggles to make
For an illustrative launch project, place the target outcome, the next milestone and the unresolved dependencies together. A component approval should be visible beside the activity that cannot proceed without it. Give each open issue an owner and a date for the next decision.
During the meeting, ask what changed, what is now at risk and what help is needed. Avoid a tour in which every team reads its own report while nobody examines the links between reports. If an issue needs a separate technical session, name its participants and return date.
Keep the information current enough to support those conversations. A beautiful chart from last month can be less useful than a plain note updated this morning. Show the date of the information and distinguish a forecast from an agreed commitment.
Do not turn visibility into public blame. If people learn that displaying a problem brings punishment, the room will become a display of reassuring colours. Leaders need to make it possible to raise uncertainty before it becomes a missed deadline.
A practical first experiment is one project, a small set of linked measures and a regular short review. After several meetings, examine whether decisions became clearer and dependencies were resolved earlier. Remove displays that nobody uses. The test of the room is the quality of the coordination it enables, not how impressive the walls look to a visitor.