Walk into any modern manufacturing facility and you will eventually
find a room with walls covered in charts, metrics, sticky notes, and
process maps. Someone will proudly call it the “Obeya” — the Japanese
word for “big room.” They will explain how Toyota pioneered the concept
to coordinate the Prius project, how it brings cross-functional teams
together, how it accelerates decision-making. Then ask when the team
last met there. Watch the silence that follows.
Obeya is one of those Lean concepts that sounds simple enough to
implement that nobody bothers understanding it deeply. Put some charts
on a wall. Add a table. Invite people. Done. But the gap between a
functioning Obeya and a decorated conference room is the gap between a
cockpit and a waiting area. Both have screens. Only one is designed for
flying.
What Obeya Actually Is
The Obeya originated at Toyota in the 1990s during the
first-generation Prius development. The program director, Takeshi
Uchiyamada, needed a way to coordinate hundreds of engineers across
multiple disciplines working on an aggressive timeline. Traditional
communication channels — email, memos, scheduled meetings — were too
slow. He created a physical space where all critical project information
lived on the walls, and where the people who needed that information
could access it without barriers.
The core idea is not the room. It is the simultaneous
presence of information and people. When a problem surfaces,
the people who can solve it are already in the room. The data they need
is already on the wall. There is no “let me get back to you on that” or
“I’ll send you the latest version.” Everything is live, visible, and
shared.
An effective Obeya has four characteristics:
-
Visual transparency — Every critical metric,
project milestone, and pending decision is displayed visually. Anyone
walking in can assess project health in under sixty seconds. -
Cross-functional co-location — The people in the
room represent every function needed to move the project forward:
engineering, quality, production, supply chain, finance. Not delegates.
The actual decision-makers. -
Structured cadence — The room is not a drop-in
space. It operates on a rhythm: daily stand-ups, weekly reviews,
milestone tollgates. Each meeting has a purpose, a duration, and an
output. -
Action orientation — Every meeting ends with
specific actions, owners, and due dates. These are posted on the wall.
Next time you walk in, the first thing you see is whether yesterday’s
actions were completed.
Where Obeya Goes Wrong
Most organizations skip directly to the visual part. They designate a
room, print some A3 reports, tape them to the walls, and declare
victory. Six months later, the room is used for storage, the charts are
outdated, and nobody remembers why it was created.
The failure modes are remarkably consistent across industries:
The Museum Room
Charts go up but never come down. The walls become a historical
archive of metrics from three quarters ago. Nobody updates the
information because nobody defined an update cadence. The room looks
impressive during executive tours but serves no operational purpose.
Visitors admire it. Workers avoid it.
The Status Meeting in
Disguise
The team gathers in the Obeya but proceeds to have the same status
meeting they would have had in any conference room. Each person reports
on their area. Others listen passively. No decisions are made. No
problems are solved. The walls might as well be blank. The Obeya adds
zero value over a phone call.
The Exclusive Club
The same four people attend every Obeya session. They are senior
enough to be decision-makers but too detached from the actual work to
know what is happening on the floor. When a production issue surfaces,
they cannot answer it. When a design question arises, they defer to
someone who is not in the room. The Obeya becomes a bottleneck instead
of an accelerator.
The Performance Stage
The room is kept pristine for executive visits. Real work happens
elsewhere — in side conversations, email threads, and corridor
discussions. The Obeya is a showroom, not a workspace. The metrics on
the wall are curated to tell a comforting story. Red items are quietly
converted to yellow. Escalations are handled privately so the room
always looks green.
Designing an Obeya That
Actually Works
Building a functional Obeya requires as much engineering discipline
as the product it tracks. The physical space, the information
architecture, the meeting protocols, and the behavioral norms all need
deliberate design.
Physical Layout
The room should be large enough for the core team to stand
comfortably — typically eight to fifteen people. Walls must be usable:
magnetic or push-pin-friendly surfaces, or large whiteboards. A
projector is useful for sharing digital dashboards, but the primary
information medium should be physical. Paper on walls forces simplicity.
Digital dashboards encourage detail that nobody reads.
Arrange the room so that the most critical information is on the wall
facing the entrance. This is the “headline” wall — project status, top
risks, key milestones. Side walls hold supporting information: detailed
metrics, action item logs, problem-solving boards. The wall opposite the
entrance should hold the team’s working agreements, the project charter,
and the escalation path.
Information Architecture
Every piece of information on the wall should answer a specific
question. If you cannot articulate the question, the chart does not
belong there.
| Wall Section | Question Answered | Typical Content |
|---|---|---|
| Project Status | Where are we against plan? | Milestone tracker, Gantt summary |
| Quality Metrics | Are we delivering to spec? | Defect rates, FPY, open NCRs |
| Top Risks | What could derail us? | Risk register with mitigation status |
| Action Log | Who is doing what by when? | Open actions with owners and dates |
| Problem Board | What is blocking us now? | Active issues with escalation level |
| Voice of Customer | What does the customer need? | Key requirements, feedback summaries |
Avoid the temptation to display everything. An Obeya with fifty
charts communicates nothing. Twelve well-chosen visual elements will
always outperform a dense wall of data. If a metric is not driving a
decision, it is decoration.
Meeting Protocols
The daily stand-up is the heartbeat. Fifteen minutes maximum.
Standing only — no chairs. The team walks the wall from left to right,
top to bottom. Each person speaks briefly: what they completed, what
they are working on, what is blocking them. Blockers are captured on the
problem board immediately.
Weekly reviews go deeper. Thirty to sixty minutes. The focus shifts
from individual updates to systemic issues: trends in the metrics, risks
that are escalating, actions that are overdue. This is where decisions
get made — not in side conversations afterward, but in the room, with
the information visible to everyone.
Milestone tollgates are the most rigorous. A full review of project
health against predefined criteria. Green items get brief
acknowledgment. Yellow items get a plan. Red items get an owner, a
deadline, and an escalation. If a tollgate cannot be passed, that
decision is made in the Obeya, not deferred to a committee.
Behavioral Norms
The hardest part of Obeya is not the setup. It is the cultural shift
required to use it effectively.
Silence is not consent. If someone disagrees with an
assessment on the wall, they must say so in the room. Passive agreement
followed by corridor complaints destroys the system.
Escalation is expected, not punished. When a problem
exceeds the team’s authority, it gets escalated visibly. The escalation
path — who is notified, how quickly, with what level of detail — should
be posted on the wall. Teams that hide problems to avoid looking bad
will never benefit from visual management.
The room is for working, not presenting. If someone
brings a polished PowerPoint to the Obeya, they have misunderstood the
purpose. The information should already be on the walls. The meeting is
for discussion, decision, and action — not for information transfer that
could have been an email.
Obeya in the Digital Age
A common question: can Obeya work virtually? The honest answer is:
partially, with significant effort.
Distributed teams can approximate Obeya using digital whiteboards
(Miro, Mural, Microsoft Loop) and video conferencing. The visual
principles transfer. The meeting protocols transfer. What does not
transfer is the ambient awareness — the ability to glance at the wall
while walking past, to overhear a conversation and contribute, to feel
the collective energy of a team working on a shared problem.
For hybrid arrangements, consider a physical Obeya at the primary
site with a continuous video feed for remote participants. Some teams
install cameras that remote members can control to pan and zoom on
specific wall sections. This is not perfect, but it preserves more of
the Obeya’s intent than a purely digital approach.
The biggest risk with digital Obeya is that screens become
scrollable. Physical walls have a forcing function: if you run out of
space, you must remove something. Digital boards expand infinitely,
which means they accumulate clutter. Apply the same discipline: if a
chart is not driving a decision, remove it.
Measuring Obeya
Effectiveness
How do you know if your Obeya is working? Look for these
indicators:
-
Decision velocity: Are decisions being made in
the room, or deferred? Track how many decisions are made per week in the
Obeya versus escalated elsewhere. -
Action completion rate: What percentage of
actions posted on the wall are completed by their due date? A healthy
Obeya maintains above 85%. Below 60% means the action log has become a
wish list. -
Problem dwell time: How long do problems stay on
the board before being resolved? If the same issue has been on the wall
for three weeks, the team is either under-resourced or avoiding a
difficult conversation. -
Participation breadth: Are the same people
speaking every meeting, or does the conversation rotate? An effective
Obeya draws input from every function represented. Silence from a
function usually means they are not engaged — or they are solving
problems outside the room. -
Visitor comprehension: When someone unfamiliar
with the project walks into the Obeya, can they understand the current
status in under two minutes? If not, the visual design needs
simplification.
Common Pitfalls to Avoid
Do not let the Obeya become a reporting tool for leadership. The
moment the room is optimized for upward communication rather than team
collaboration, it loses its value. Executives are welcome visitors, but
the room exists for the people doing the work.
Do not over-engineer the visuals. Hand-drawn charts updated daily are
more valuable than professionally printed posters updated quarterly. The
signal is in the freshness, not the aesthetics.
Do not assign a single “Obeya owner” who maintains the walls alone.
Every team member should be responsible for updating their own metrics.
When one person becomes the curator, the rest of the team stops engaging
with the information.
Do not use the Obeya as a performance evaluation tool. The moment
metrics on the wall are tied to individual performance reviews, people
will start gaming them. The room must be a safe space for honest
assessment. Reward problem-solving, not problem-hiding.
The Bottom Line
Obeya is not a room. It is a management practice that happens to use
a room. The physical space is the enabling infrastructure; the real work
happens in the behaviors, protocols, and norms that the team commits
to.
If your team is considering implementing Obeya, start small. Pick one
critical project. Identify the eight to twelve people who can make
decisions. Define six to ten metrics that actually drive decisions.
Establish a daily fifteen-minute stand-up and a weekly thirty-minute
review. Run it for ninety days. Then assess: are decisions being made
faster? Are problems being surfaced earlier? Are actions being
completed?
If yes, expand. If no, the problem is not the room. It is the
culture, the cadence, or the selection of people. Fix those before
investing in better charts or bigger walls.
The most sophisticated quality management system in the world cannot
compensate for a team that will not talk to each other honestly, in the
same room, looking at the same data, making decisions in real time. That
is what Obeya was designed to enable. That is what it still does — when
it is done right.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality, Lean transformation, and
management system design. He has implemented Obeya practices across
automotive, electronics, and medical device industries, and writes about
the gap between quality theory and shop-floor reality at
IAEC.online.
