Obeya

Obeya gets confused for a fancy meeting room because the most famous obeyas in lean literature are Toyota's product development centers. In practice, a small shop obeya is a corner of an existing room with butcher paper on the walls and a recurring 7:30 standing meeting. The point is not the square footage. The point is that the whole state of a complicated project lives on the walls of one physical place, so anyone who needs to make a decision about it can walk in, read the walls, and decide.

"If the room is empty when the meeting ends, you have a meeting. Not an obeya."

How an obeya works

An obeya has four working pieces.

The first is the walls. The visible state of the project is mapped across distinct panels. The standard panels are: the project timeline with milestones, the target condition or success criteria, the open issues with owners, the experiments in progress, the metrics being tracked, and the decisions made to date. The exact layout varies; what matters is that every piece of information someone might need to act is somewhere on the walls and is current.

The second is the meeting. The cross-functional team gathers in the room daily, usually 15 to 30 minutes. The meeting walks each panel in order: where are we against the timeline, what changed in the issues, what experiments closed or opened, what decisions need to be made today. The meeting is structured, short, and identical in shape from day to day. The discipline is what produces the meeting's compactness.

The third is the open door. The obeya is not a private war room. Anyone in the organization who needs the project's state walks in, reads the walls, and acts on what they read. The owner walking through at 4 p.m. learns more in three minutes than a 30-minute status email could carry.

The fourth, often overlooked, is closure. When the project ends, the obeya is taken down. The decisions and learnings are captured in a brief reference document; the walls are stripped; the room returns to its prior use. Obeyas that linger after the project ends turn into permanent meeting venues without a job. Closing the room is part of what keeps the next obeya credible.

Where obeya fits on the shop floor

Imagine a 35-person electronics assembly shop taking on a new product launch with a customer who needs first production runs in 90 days. The launch will touch engineering, supply chain, production, quality, and the customer service team. Status meetings have been multiplying. Emails are crossing. Decisions are getting made in hallways and not communicated.

The owner reads about obeya and stands one up in the back of the engineering area. Three walls get butcher paper. Six panels go up: timeline, target conditions, open issues, experiments, key metrics, decisions log. The cross-functional team meets there at 7:30 every morning for 20 minutes, walking through each panel. By week two, the email volume on the project drops noticeably because people walk into the room to read instead of writing. By week six, the launch is on track and the engineering lead can run the meeting without the owner.

At day 95, the launch ships. The team holds a closing review, captures three pages of learnings, takes down the walls, and the room goes back to engineering use. The next obeya, six months later for a different customer, will stand up in the same place faster because the team has the muscle.

Common mistakes with obeya

• Empty walls between meetings. If the room is dark when the meeting ends, you have a meeting, not an obeya.
• Stale panels. Better four current panels than ten neglected ones.
• Treating it as a private war room. Open access is part of how the room replaces email and status reports.
• Skipping closure. Obeyas that outlive their project turn into permanent meeting venues with no purpose.
• Setting it up too soon for too small a project. Small projects do not need an obeya. The daily huddle and idea board are enough.

Obeya and related Lean tools

Obeya is one of the most spatial tools in visual management. It connects to the broader tiered meetings system but operates on a different cadence and purpose, project versus operations. The cross-functional, target-driven nature of an obeya makes it a natural home for hoshin kanri strategy deployment, and many lean shops run their annual planning out of an obeya wall. Its daily heartbeat is the daily huddle, just held in front of the project's walls instead of the production board.