What Is an Obeya Room? A Complete Guide With Examples

A BI (Business Intelligence) team went from 24% on-time delivery to 55% in three months, using one room and six visual boards.

What is Obeya Room?

An Obeya is a physical or virtual space where activities live on visual boards. It may include charts, sketches, plans, and customer feedback. It also includes the open problems. The whole point is that a cross-functional team can walk in, see everything at once, and decide what to do next.

The word means “large room” in Japanese. Toyota started using Obeyas in the 1990s during the Prius program, and Lean practitioners have been adapting the idea ever since. Today, you find Obeyas in software teams, hospitals, banks, and creative agencies, wherever multiple specialists need to coordinate quickly.

What sets it apart from standard project tools is what happens in the room, not what’s on the walls. An Obeya gives the team the full picture of the project’s issues and forces a weekly conversation about what to change. The visibility is half of it. The conversation in front of the visibility is the other half.

Origins: From Toyota to Tech

In the 1990s, Toyota was building the Prius. Chief Engineer Takeshi Uchiyamada had three teams pulling in different directions: the engineers, the designers, and the production line. They had different priorities, different deadlines, and different definitions of “done.” His fix was almost embarrassingly simple. He locked the leads in one room, two or three afternoons a week, in front of the actual plans on the wall, and refused to let them leave until they had decided what to do next.

The Prius hit the market 10 years before its competitors.

The method spread from there. It now runs in software teams, hospitals, banks, and creative agencies, anywhere the people who decide need to see the same picture at the same time.

Key Components of an Obeya Room

These components show what a typical Obeya can include. The actual boards depend on the type, see “Three Types of Obeya” below.

An Obeya is where real-time project management and problem-solving happen in front of the team. The walls hold whatever the team needs to see: charts, sketches, timelines, the KPIs that matter that week, and the problems still being worked on. The point is not the artifacts. The point is that everyone is looking at the same picture at the same time.

The boards I see most often in an Obeya:

• Vision and Objectives. The goals and mission of the project, in plain language. If the team cannot point to why the work matters, nothing else on the wall will save them.
• Client Feedback. User or customer insights, in the customer’s own words, when possible. Quotes beat summaries.
• Product Representation. Prototypes, diagrams, or product models. Whatever shows what is actually being built.
• Macro and Micro Plans. The roadmap on one wall, the detailed timeline on another. Most teams put the macro plan at eye level and the micro plan within arm’s reach.
• Key Performance Indicators (KPIs). A short list of measures the team reviews every week. Three to five, not twenty.
• Problem-Solving Boards. Open issues with names attached, usually structured as A3 Problem-Solving reports.

Three Types of Obeya

Not all obeya rooms serve the same purpose. The boards you put on the wall or create digitally, the people in the room, and the conversations that happen depend on one thing: what you are trying to manage. Across my engagements so far, I have built three types. Each starts from a different question.

Project Obeya : “Are we delivering on time and within quality?”

A project Obeya starts from a plan and tracks execution against it. The walls typically show milestones, timelines, defects, structured problem-solving, and delivery status. In tech organizations, this is typically led by an IT project manager who needs to see dependencies, milestone collisions, and quality gaps across concurrent projects or tasks in one view. The team meets weekly to review progress, surface risks, and solve blockers. The people in the room are project managers, tech leads, and delivery teams.

The wall reveals the gap between planned and actual. It prevents issues as a discovery tool. When a project slips or defects spike, everyone sees it at the same time. 

See the full case study: From 24% to 55% On-Time Delivery: A Project Obeya Room Case Study

Management Obeya : “Are we running this business in the right direction?”

A management Obeya starts from the strategy and tracks business health. The walls typically show client satisfaction, revenue, margin, commercial pipeline, HR metrics, and structured problem-solving. The leadership team meets weekly to review performance, act on client feedback, and solve business-level problems. Use a management Obeya when you lead a department, division, or service line and need your leadership team to be aligned on the same facts every week. The people in the room are directors, managers, and functional leads.

The wall reveals performance gaps across the organization. The focus is on running the business.

See the full case study: Management Obeya: How an IT Services Team Built Their Own War Room

Product Obeya : “Are we building the right thing for the right people?”

A product obeya starts from the customer and works backward through product definition, MVP scoping, and feature prioritization. The walls typically show the voice of the customer, the target product vision, feature mapping, the MVP perimeter, and delivery indicators (for example: quality, cost, timeline, and risks). In my experience, this is typically run by a product manager or, in larger organizations, by the team responsible for product creation and delivery: product managers, designers, engineers, and sometimes customer-facing roles.

The customer is not just a metric here. The customer is the reason the room exists. Every board traces back to what users need and whether the team’s builds meet that need. 

How to Choose. Ask one question: what are you trying to manage? If the answer is project delivery, build a project Obeya. If the answer is a business unit, build a management Obeya. If the answer is a product, build a product Obeya. Some organizations run two or three at different levels. A CTO might use a management Obeya for the department while each product team runs its own product Obeya. They connect through shared KPIs and escalation paths.

In practice, these types overlap. A product Obeya often includes a delivery planning wall. A project Obeya may start with strategic alignment. The labels describe the primary focus, not a rigid template. Start from your biggest problem and build the boards that make it visible.

The key point is to use Obeya as a discovery and learning tool about what you are managing.

How to Run an Obeya: The 6 Animation Practices

The key to obeya is not the obeya. It’s you.

A wall full of charts changes nothing on its own. What makes an Obeya work is the person who runs it: the animator. It is someone who walks into the room every week, points at the data, asks the hard questions, and refuses to let problems sit unresolved on a sticky note for three weeks in a row.

Without an animator, the room becomes wall decoration. With one, it becomes where the team thinks together.

Who Animates the Obeya

In a project obeya, the animator is usually the lead project manager. In a management Obeya, the business unit director is in charge. In a product obeya, the product manager or whoever owns end-to-end delivery.

The animator is the integrator, connecting what the customer wants, what the strategy demands, what the team can build, and what the data shows. When those four things stop aligning, the animator surfaces the gap and drives the fix.

From my experience, a good animator is customer-obsessed, comfortable on both technical and functional grounds, and visionary without losing pragmatism. Most people are strong on two of those three dimensions. The role forces you to develop the third.

The 6 Practices

The weekly Obeya meeting is the most visible practice. It is not the only one. Across my engagements, the teams that get real results run six practices:

1. Run the weekly Obeya meeting. Sixty to ninety minutes, at the same time every week, in the room (physical or virtual). The team walks the boards, reviews indicators, surfaces problems, and sets the focus for the week ahead.

2. Coach team members through PDCA. When a problem lands on the wall, someone owns it. The animator coaches the owner by clarifying the problem, identifying root causes, and testing countermeasures.

3. Steer the work daily. A 10-minute check-in around the task board catches blockers that would otherwise wait a full week. I see most Obeyas die because the team meets weekly and lets issues fester between sessions.

4. Replay the plan every week. The animator walks the macro plan end to end and asks: what changed, what’s at risk, which milestone slips if we don’t act now? This is what turns the Obeya from a status board into a forecasting tool.

5. Animate design problem-solving. When the wall reveals a hard design problem (architecture, performance, user experience), the animator runs parallel exploration. Two small sub-teams build two prototypes, and the team converges on the better one, supported by evidence.

6. Go to the gemba. The animator leaves the room to sit with a developer, watch a user test the product, or observe a handoff between two teams. The wall shows symptoms. The gemba shows causes.

The first practice is easy to start. The other five are what separate teams that treat the Obeya as a status report from those that use it to run the work.

Case Study: BI Projects Transformation

A global enterprise IT department ran 18 Business Intelligence projects across four continents. Only 24% of projects shipped on time. Releases averaged 38 defects. Customer satisfaction sat at 5.5 out of 10. Two senior project managers tracked their own work separately in spreadsheets and email threads, with no shared view of the full portfolio.

I designed a “project Obeya” with the team, built around three zones: a strategy wall connecting every project to the CIO’s goals, a performance dashboard with six handwritten charts updated weekly, and a macro planning wall showing all 18 projects on one timeline. The team ran daily 15-minute reviews in the room and weekly Obeya sessions. Three structured PDCAs solved the most critical problems. After three months: on-time delivery increased from 24% to 55%, defects decreased from 38 to 19, and customer satisfaction increased from 5.5 to 9.4.

See the full case study: From 24% to 55% On-Time Delivery: A Project Obeya Room Case Study

Case Study: Management Obeya for an IT Services Team

An IT services agency director ran his team through weekly meetings and slide decks. Strategy was set in January and rarely revisited. Client issues surfaced only when they escalated. The commercial pipeline lived in spreadsheets that nobody reviewed together.

I designed a “management Obeya” with his leadership team. Unlike a “project Obeya” that tracks deliveries, this one tracked the health of the entire business: client voice, vision and objectives, commercial development, performance indicators, and structured problem-solving. Seven modules on the walls of one room, reviewed weekly in 90-minute sessions. The agency director used it to replace opinion-based discussions with data-driven decisions.

See the full case study: Management Obeya: How an IT Services Team Built Their Own War Room

Benefits of an Obeya Room

An Obeya changes how teams work.

Discovery before delivery. Problems appear on the wall weeks before they appear in a status report. That’s the whole game. Fix it cheap, fix it early, or pay ten times more later. Teams also stop guessing what users want, because the customer’s voice is right there on the wall, in the customer’s own words.

Problems on walls get solved. When an issue sits on a dashboard nobody opens, it can live there for months. Stick the same issue on a wall in a room where six people meet every Tuesday, and by the third Tuesday, someone will be annoyed enough to fix it. The room generates social pressure that no Jira board ever has.

Decisions get faster because nobody has to chase the data. The leader walks in, looks at the wall, asks why a number moved, and makes a call before the meeting ends. There’s no “let me check with the team and get back to you.” Architecture trade-offs get sharper for the same reason. Anyone making a hard technical call can see the customer constraint, the current build, and what’s already broken, all in one glance.

Nothing hides in an Obeya. You can see where each project stands. You can see who owns the next move. If something is slipping, it’s slipping in public, and a leader will spot it in week two instead of finding out in week ten when the deadline is gone.

Everyone is looking at the same picture. The executive sees what the team sees. When the customer walks in, they see what the executive sees. That removes the most expensive thing in any organization: the gap between what leadership thinks is happening and what is actually happening.

Conclusion

The numbers in the BI case study are real successes: 24% to 55% improvement in on-time delivery, defects cut in half, and customer satisfaction from 5.5 to 9.4. All that happened in three months.

The point is what happens when a team stops reporting status and starts thinking together in front of the work. The leaders see what is actually happening. The problems get owned by name and resolved, with the team learning as they go. The customer’s voice sits on the wall next to the plan it is supposed to inform.

You may have a project, management, or product Obeya. It could be physical or virtual. Whichever Obeya you build, the rule is the same: show up every week, look at the wall, decide what to change, and learn. The discipline is what makes the Obeya room work. The room itself is just paint and paper until someone runs it.

Frequently Asked Questions About Obeya Rooms

What exactly is an Obeya Room?

An Obeya is a place where the work lives on the walls. There are charts, plans, customer feedback, and problems being solved. All of it is visible at once. The term means “large room” in Japanese. Toyota built the first one during the Prius program in the 1990s, and the idea spread from there into software, hospitals, banks, and design agencies.

An Obeya does not work on its own. To start being useful, it requires facilitation skills and Lean techniques. The minimum is weekly reviews, root cause analysis, and structured problem-solving.

I have coached a project leader to create an Obeya to pilot the delivery of a payment product on time and to the required quality. He created a beautiful, up-to-date Obeya for the project sponsor’s visit. After that milestone, he abandoned the Obeya. He was not using that on a weekly basis to pilot the project. Eventually, the planning drifted, and nobody knew where the project stood.

Do Obeya Rooms work for remote teams?

Yes, they do,  but the discipline matters more than the tool. You can use Miro, Mural, Google Slides, or a Notion page. Any of them works if the team actually shows up every week and looks at the wall together. None of them works if the meeting becomes optional.

From my experience, virtual Obeyas outperform physical ones. In virtual mode, the animator can set screen dynamics that force everyone to focus on the same artifact simultaneously.

I have also seen virtual Obeyas die in three weeks. The team treated the dashboard as something to scroll past.

I’ve coached a tech team organized over 4 time zones. The virtual Obeya was well-crafted Jira boards. We managed to create the habit of using it during daily meetings. That habit-building was all about managing the focus on the board. 

What makes Obeya different from traditional project management tools?

First, you have the codified visual boards and the performance gap they surface. In addition, all that triggers a structured problem-solving that changes the way people manage problems.

I used to say that it is not about the data, but the conversation that happens in front of them.  

Traditional tools are built for tracking. An Obeya enables discovery but is built for thinking. You walk into the room, you see the project, and you talk about what to change. That last part is the whole point. Without the weekly conversation, an Obeya is just a more expensive dashboard.

What’s the biggest mistake companies make with Obeya Rooms?

It is treating the Obeya as a status report instead of a working space. I’ve seen this many times.

Companies set up the walls (physical or virtual), take the photos for the internal newsletter, and then nothing changes. The meetings become update sessions. Nobody asks why a number moved, and consequently, nobody owns a problem long enough to solve it. The wall becomes wallpaper.

The Obeyas that work are those in which a team member, usually backed by the animator, refuses to let a problem sit on the wall without progress.

Which industries gain the most from Obeya Rooms?

From what I know, manufacturing and software get the most press, but the method has already spread everywhere. There are Obeyas in hospitals, financial services, creative agencies, and more. The pattern is consistent: any team where multiple specialists need to coordinate under time pressure benefits from putting the work on a wall, physical or virtual.

A team managing 18 Business Intelligence projects across four continents successfully improved on-time delivery from 24% to 55%, thanks to the Obeya practice they developed. That included managing all the external sponsors they had.