obeya

Obeya (Lean)

Updated November 2026 · reviewed for today
In short

Obeya is Japanese for “big room”: a dedicated space where a cross-functional team posts the charts, plans and open problems of a project on the walls and meets there on a fixed rhythm to decide. The practice is credited to Takeshi Uchiyamada, Toyota’s chief engineer for the Prius, launched in December 1997, and it became a standard tool of Toyota product development and of lean management.

Obeya (Lean): hand-drawn explainer by The Business Engineer
Drawing by The Business Engineer.

How it works

01
One room, all the facts
Charts and graphs show program timing, milestones, progress against targets and countermeasures to timing or technical problems, so everyone sees the same picture.
02
Everyone who decides is present
Project leaders and the technical experts each part of the program needs work or meet in the room, which gives horizontal alignment across functions instead of a chain of separate reports.
03
A cadenced meeting
The Lean Enterprise Institute stresses that visual walls become a management system only when combined with a regular meeting structure; Uchiyamada met his experts every two to three days.
04
Shorter PDCA loops
Because problems surface quickly, the team can plan, do, check and act faster, which is the stated purpose of the room.

Where you see it today

Hospitals and service operations

The obeya has moved beyond car design. The Lean Enterprise Institute describes healthcare versions whose walls show performance on patient safety, care quality and efficiency, so a management team can see quickly where it is off plan.

Digital obeya on BI dashboards

Many teams now build the walls in software. One documented case put every department’s KPIs into a shared Microsoft Power BI dashboard, and the planning team’s weekly meeting moved onto it (Sousa et al., 2021).

Virtual rooms for distributed teams

Researchers have built web-based “virtual obeya” tools so that lean workshops and engineering reviews can run when people are not in one building (Terenghi et al., 2014).

AI-era dashboards

Live data and AI-generated summaries can fill a wall automatically. The lean lesson still applies: a screen nobody discusses on a fixed cadence is a report, not an obeya. The value sits in the people deciding in front of it.

Obeya and related practices

Obeya
What it isA big room with the whole project on the walls and a meeting cadence
How it differs from obeyaThe reference point: cross-functional, decision-making, visual
War room
What it isA room set up for a crisis or a deadline
How it differs from obeyaUsually temporary; obeya is a standing system for a whole program
Kanban board
What it isCards showing work items and their flow
How it differs from obeyaTracks tasks; an obeya also shows targets, problems and countermeasures
Gemba walk
What it isLeaders go to where the work is done
How it differs from obeyaMoves people to the work; obeya brings the program's information to one place
Digital dashboard
What it isKPIs shown in software
How it differs from obeyaCan be one wall of an obeya, but needs the meeting rhythm to count as one

How to use it

  • Pick one program that crosses several functions and give it a single room or a single shared board.
  • Put up only what drives decisions: targets, the schedule, current problems with owners, and countermeasures.
  • Set a short, fixed meeting rhythm in front of the walls and keep it even when things look on track.
  • Show problems in red without blame, so people raise them early instead of hiding them.
  • If the walls are digital or AI-generated, check that each item still has a named owner and is discussed, not just displayed.
The Business Engineer lens

AI makes information cheap to produce and easy to display, so the scarce resource in a company becomes shared attention and fast decisions. The Business Engineer reads the obeya as an operating rhythm for that problem: one set of facts, the people who can act, and a fixed cadence.

Read: The New Organizational Architecture →Explore everything we publish →

Related: Kanban · Jidoka · Gemba walk · PDCA cycle · Lean methodology

Frequently asked questions

What does obeya mean?

Obeya is Japanese for “big room”. In lean management it is a dedicated space where a cross-functional team posts a project's information on the walls and meets there to make decisions.

Who invented the obeya?

The Lean Enterprise Institute credits Takeshi Uchiyamada, Toyota's chief engineer for the first Prius, with creating the obeya management system.

Is an obeya the same as a war room?

They look similar, but a war room is usually set up for a crisis, while an obeya is a standing management system with a regular meeting cadence for a whole program.

Can an obeya be virtual?

Yes. Teams use shared digital boards and dashboards, and researchers have built virtual obeya tools, but the walls still need owners and a fixed meeting rhythm.

Sources

The full guide

The complete explainer, cleaned up and reformatted for mobile.

Obeya, a Japanese concept, represents a physical space used by cross-functional teams to collaborate, visualize work, and make decisions. It aims to promote transparency, collaboration, and problem-solving. Obeya incorporates visual boards, metrics, and improvement actions, and finds use cases in project management, daily stand-ups, and problem-solving sessions. The roles of team members, facilitator, and leadership play a crucial role in the Obeya process.

Purpose of Obeya

The primary purpose of Obeya is to create a space where teams can

  • Collaborate: Obeya breaks down silos by bringing cross-functional teams together. It fosters open communication and collaboration among team members.
  • Align: Teams use Obeya to ensure that everyone is on the same page regarding project status, goals, and priorities. It serves as a visual representation of the organization’s objectives.
  • Problem-Solve: Obeya facilitates the identification of challenges and provides a platform for generating actionable solutions. It encourages a proactive approach to problem-solving.

Principles of Obeya

Obeya operates on several core principles, including

  • Transparency: Obeya emphasizes the importance of sharing information openly. Visual boards and data displays ensure that everyone has access to real-time information.
  • Collaboration: Cross-functional teams collaborate in the Obeya space, promoting diverse perspectives and a holistic approach to decision-making.
  • Problem-Solving Culture: Obeya fosters a culture where problems are not swept under the rug but are addressed proactively. It encourages teams to seek root causes and implement solutions.

Components of Obeya

Obeya spaces typically incorporate the following components

  • Visual Boards: These boards display critical information such as work progress, key performance indicators (KPIs), improvement actions, and project milestones. Visual boards provide a snapshot of the current status and performance.
  • Metrics and KPIs: Obeya relies on data-driven decision-making. Metrics and KPIs are prominently displayed, allowing teams to track performance and identify areas for improvement.
  • Information Radiators: Data is visualized in a way that is easy to understand and interpret. Information radiators ensure that everyone in the room has access to relevant and up-to-date information.
  • Improvement Actions: Actionable steps to address identified issues are prominently displayed. This component drives a culture of continuous improvement.

Use Cases for Obeya

Obeya finds application in various scenarios, including

  • Project Management: Obeya helps project teams track milestones, dependencies, and risks. It provides a centralized space for project-related discussions and decisions.
  • Daily Stand-ups: Teams conducting daily stand-up meetings benefit from the visibility and transparency that Obeya offers. Real-time updates and issue resolution are facilitated.
  • Problem-Solving: When tackling complex problems or conducting root cause analysis, Obeya serves as an ideal environment for cross-functional teams to collaborate and develop solutions.

Roles in Obeya

Several key roles contribute to the effectiveness of Obeya

  • Team Members: Team members actively participate in Obeya activities. They share updates, collaborate on solutions, and contribute to the collaborative environment.
  • Facilitator: A facilitator ensures that Obeya meetings run smoothly. They encourage participation, manage discussions, and keep the sessions focused.
  • Leadership: Leadership plays a crucial role in providing support, allocating resources, and setting the direction for the teams working in Obeya. They help align the activities with the organization’s strategic goals.

Examples

  • Product Development Obeya:
    • Scenario: A company is developing a complex product with multiple teams working on different aspects, such as design, engineering, and testing.
    • Obeya Application: The organization sets up an Obeya room where representatives from each team gather regularly. Visual boards display the product development progress, issues, and dependencies. This collaborative space allows teams to identify bottlenecks, align their efforts, and make swift decisions. It fosters cross-functional collaboration and accelerates product development.
  • Healthcare Operations Obeya:
    • Scenario: A hospital aims to improve patient flow and reduce emergency room wait times.
    • Obeya Application: An Obeya space is established with visual boards showing patient admission and discharge processes, ER capacity, and key performance metrics. Cross-functional teams, including doctors, nurses, and administrators, meet regularly to review data and identify areas for improvement. This approach enhances patient care, reduces wait times, and streamlines hospital operations.
  • Lean Manufacturing Obeya:
    • Scenario: A manufacturing facility seeks to optimize production processes and reduce defects.
    • Obeya Application: The organization implements Obeya in its production area. Visual boards display production schedules, quality metrics, and continuous improvement initiatives. Cross-functional teams consisting of operators, quality inspectors, and engineers meet daily to review performance and address issues promptly. This approach leads to improved product quality, reduced defects, and increased production efficiency.
  • Software Development Obeya:
    • Scenario: A software development company wants to enhance its agile development processes.
    • Obeya Application: An Obeya room is established with visual boards displaying sprint backlogs, user stories, and defect tracking. Scrum teams, product owners, and developers meet regularly for sprint planning, daily stand-ups, and sprint reviews. This collaborative space fosters transparency, quick decision-making, and alignment of development efforts, resulting in faster delivery of high-quality software.
  • Retail Merchandising Obeya:
    • Scenario: A retail chain aims to optimize its merchandising and inventory management strategies.
    • Obeya Application: The organization sets up an Obeya space where visual boards showcase sales data, inventory levels, and merchandising plans. Cross-functional teams, including merchandisers, store managers, and supply chain professionals, meet regularly to analyze data, adjust inventory levels, and plan merchandising strategies. This approach improves inventory turnover, reduces stockouts, and enhances overall retail performance.
  • Construction Project Obeya:
    • Scenario: A construction company is executing a complex building project with multiple subcontractors.
    • Obeya Application: An Obeya room is established to track project progress, subcontractor schedules, safety metrics, and quality standards. Regular meetings involving project managers, subcontractors, and safety officers ensure alignment and quick issue resolution. This collaborative space enhances safety, quality, and on-time project delivery.

Key Highlights of Obeya – Collaborative Space for Decision-Making

  • Concept and Purpose: Obeya, a Japanese term meaning “big room,” signifies a dedicated physical space where cross-functional teams collaborate, visualize work, and make well-informed decisions.
  • Principles: Obeya is built upon principles of transparency, collaboration, and fostering a problem-solving culture within organizations.
  • Components:
    • Visual Boards: Display progress, key performance indicators (KPIs), improvement actions, and project milestones for clear understanding.
    • Metrics and KPIs: Track metrics to identify areas for continuous improvement and align efforts.
    • Information Radiators: Use visual aids to display data that aids comprehension and decision-making.
    • Improvement Actions: Showcase actionable steps to address identified challenges.
  • Use Cases:
    • Project Management: Obeya aids in tracking project milestones, dependencies, and potential risks.
    • Daily Stand-ups: It facilitates real-time updates and seamless communication among team members.
    • Problem-Solving: Obeya supports root cause analysis and the generation of actionable insights for problem resolution.
  • Roles:
    • Team Members: Active contributors who share updates, insights, and work collaboratively on solutions.
    • Facilitator: Ensures smooth meetings and encourages participation, ensuring the effective use of the Obeya space.
    • Leadership: Provides support, allocates resources, and offers strategic direction to teams utilizing Obeya.
Obeya (Lean)
DescriptionObeya, Japanese for “big room” or “war room,” is a physical or virtual workspace used in Lean management to facilitate collaboration, communication, and decision-making among cross-functional teams. It fosters transparency, alignment, and problem-solving by bringing stakeholders together in a dedicated space.
When to Apply– When implementing Lean principles and practices to improve organizational performance.
Kaizen (Continuous Improvement)
DescriptionKaizen is a philosophy and methodology focused on continuous improvement, emphasizing small, incremental changes to processes, products, or services. It encourages employee involvement, innovation, and problem-solving to drive organizational excellence over time.
When to Apply– When seeking to foster a culture of continuous improvement and innovation within an organization.
5S Methodology
Description5S is a workplace organization methodology consisting of five principles: Sort, Set in Order, Shine, Standardize, and Sustain. It aims to improve efficiency, safety, and morale by organizing the workplace, eliminating waste, and standardizing processes.
When to Apply– When organizing workspaces, improving workflow efficiency, and promoting safety and cleanliness in the workplace.
Value Stream Mapping (VSM)
DescriptionValue Stream Mapping is a visual tool used to analyze and improve the flow of materials and information required to deliver a product or service to customers. It identifies value-adding and non-value-adding activities, bottlenecks, and opportunities for process optimization.
When to Apply– When identifying opportunities for process improvement, reducing lead times, and eliminating waste in production or service delivery processes.
PDCA Cycle (Plan-Do-Check-Act)
DescriptionThe PDCA Cycle is a four-step problem-solving and continuous improvement methodology: Plan (identify a problem and plan a solution), Do (implement the plan), Check (evaluate results and compare to objectives), and Act (make adjustments and standardize improvements).
When to Apply– When addressing problems, implementing solutions, and continuously improving processes, products, or services.
Kanban System
DescriptionThe Kanban System is a visual workflow management method used to visualize work, limit work in progress (WIP), and optimize the flow of work through the system. It helps teams prioritize tasks, identify bottlenecks, and maintain a steady pace of work.
When to Apply– When managing workflow, reducing lead times, and improving productivity in manufacturing, software development, or service delivery processes.
Gemba Walk
DescriptionGemba Walk is a Lean management practice where leaders go to the “gemba,” or the place where work is done, to observe operations, engage with employees, and gain insights into process inefficiencies and opportunities for improvement.
When to Apply– When leaders need to understand actual working conditions, identify waste, and support continuous improvement efforts at the frontline level.
Andon System
DescriptionThe Andon System is a visual management tool used to signal problems or abnormalities in production processes immediately. It allows operators to stop the production line, notify supervisors, and address issues promptly to prevent defects or disruptions.
When to Apply– When ensuring quick response to production issues, reducing defects, and promoting a culture of continuous improvement and problem-solving in manufacturing environments.
Heijunka (Production Leveling)
DescriptionHeijunka is a Lean manufacturing technique used to level the production schedule and maintain a consistent flow of work. It involves smoothing out demand fluctuations, balancing production across different product lines or time periods, and reducing inventory and overproduction.
When to Apply– When aiming to reduce production variability, minimize lead times, and improve resource utilization in manufacturing environments with fluctuating demand.
Jidoka (Autonomation)
DescriptionJidoka is a Lean manufacturing principle that empowers workers to stop the production process immediately upon detecting defects or abnormalities. It emphasizes built-in quality, error prevention, and continuous improvement to ensure customer satisfaction.
When to Apply– When prioritizing quality, preventing defects, and empowering frontline workers to take ownership of product quality and process improvement in manufacturing settings.

Main Case Studies

Scroll to Top
FourWeekMBA