A Successful Obeya Requires Collective Leadership

Collective leadership is "sharing one version of reality together, so that we're all rowing in the same direction, seeing beyond just functional boundaries," explains Dr. Mohamed Saleh in the latest episode of Behind the Curtain: Adventures in Continuous Improvement. Absent collective leadership, obeyas may be nothing more than well-decorated conference rooms.
Listen on Apple buttonListen on Spotify buttonListen on iHeartRadio buttonListen on Podbean button

Why do popular lean tools seem to energize some organizations and bring no benefit to others? A tool is a tool, right?

Not exactly, suggest John Dyer and Dr. Mohamed Saleh, hosts of the Behind the Curtain: Adventures in Continuous Improvement podcast. They argue that certain behaviors are necessary to make lean and Six Sigma tools successful, and over the past few episodes, they’ve shared their thinking about the behaviors behind such tools as PDCA, leader standard work, hoshin kanri and others.  

In this episode, the duo continue their review of lean and Six Sigma tools, tackling the tool of obeya, also known as an obeya room. The thrust of their discussion is collective leadership, the behavior they say is necessary for obeya to be successful. What follows is an excerpt of their conversation.

John Dyer: Today we're going to talk about obeya rooms. Now, obeya just means a big room, and these rooms are usually set up with a lot of information about what's going on in the organization, a lot of metrics, key metrics, with red, green indicators as to are those metrics hitting the objectives or not. (It) might include some information about the strategy. Might include some A3s, which are just big documents. An A3 is just the size of the paper that it's on, but it's basically broken down into plan, do, check, act type categories to show the progress that a team's made on a particular project that they're working on or a problem that they're solving. But again, (an obeya is) meant to be a room with a lot of information. My experiences are usually that there are no chairs in this room because it's not meant to be a long, sit-down meeting. It's meant to be a stand-up, walk-around meeting where you literally take the time as a leadership team to walk around the room, to look at the various bits of information, and then to discuss what needs to be focused on: Where do the various improvement teams need to focus their attention? So that's a little bit about obeya room and Mohammed, what's the behavior behind this that we'll be talking about, and what are your experiences with obeya rooms?

Mohamed Saleh: So you know, one of one of the things, John, just for our listeners as we dive into this, is many organizations create obeya rooms. It's not a really new concept. It's something that is very popularized in many companies, and they usually cover the walls with strategy and metrics and projects and action plans, hopefully, and leaders gather, they review their own sections, and then they leave—at least that's what I've experienced from many of the companies that I've assisted. But one of the things that I learned is being in the same room does not mean the organizations are leading together. And I've seen this over and over again. And so the real question becomes: Are we making decisions as a whole enterprise in that room, or has it become territorial where we're protecting our own functions within that room? And you'll see like, oh, this is the employee engagement hoshin or strategy, and so like the person that's protecting it is the HR person, or this is something around supply chain shortages and initiatives behind it, and where the supply chain person is protecting it.

Many Versions of Obeya Rooms

MS: And so it becomes this wall where we defend why certain things are happening or certain things are not happening, and that for me defeats the purpose of that room. Now, one of the other things before I dive into your question that I've also learned over the years is, historically, when I was first introduced this to the term obeya, which, like you said, it means just big room, I misunderstood what that meant. In my head, it was strategic priorities, performance gaps, project progress, resource conflicts, decision and action, things like that would be in the room. And as I started visiting some of the mature organizations that are doing this … I've learned that there are many versions of obeya rooms. It's not a one thing, and there are hoshin obeya rooms or strategy obeya rooms that are intended to highlight those strategic priorities, those annual improvement priorities, the objectives behind them, and what are the actions we're doing around these projects this year. And then there is also, if you look at the daily management system at the top level, there's also a performance obeya or a daily management obeya, where really it's the daily conflict, daily issues that are escalating that rapid response system to closing daily gaps, and at Toyota they called that obeya as well. And I have some very dear colleagues of mine visit Toyota in Europe, and they went into the people development obeya, and they got to see how they create succession plans, how they develop their people, and it was a people development obeya. And so, the more and more I dive into this concept, the more and more I learned that it just means a big room. You still have to give it some type of purpose.

MS: Now, for our conversation today, we're going to be talking about the hoshin obeya more and the strategies and stuff like that that goes within it, but I just want for our listeners: When you hear the term obeya, you have to understand which obeya are we talking about, because they're not all one to one. However, regardless of which obeya it is, it is the senior leadership team of that site, and so there needs to be some kind of collective leadership still, and so the behavior behind it here is collective leadership, regardless of the context of what kind of obey it is.

MS: Now, for our listeners, the term collective leadership sounds like collaboration. There needs to be some kind of collaboration, and so just to kind of level set what that means, collective leadership is sharing one version of reality together, so that we're all rowing in the same direction, seeing beyond just functional boundaries, and being able to act as one collective team, confronting conflicts together and not being territorial about it. So John's problems are my problems, and my problems are his problems. And collectively, as a leadership team, our job is to make everything here green, not my function green. And so, making decisions as a whole, and then walking out of that team as a single unit, rather than walking out and having a meeting after the meeting of things that you didn't agree upon. And so, leaving with clear individual commitments is important, but leaving also with collective ownership is important as well. And so I think the behavior behind an obeya room is really that collective leadership.

MS: I wish I could tell you that that's a common trait. That is not a common trait. Sometimes we view it as window dressing, or as you call it, facade, where you have some of the most beautiful obeya rooms that I've seen in companies. And I walk in, and I see strategies everywhere, and I see how they're broken down with a work breakdown structure into projects. They have the rails or Gantt charts of how they're going to execute on it. Some of people even have X matrices. It looks very pretty when you walk in the room. You have planned strategies, emergent strategies, and you're like, "Wow, this this company really knows its stuff." But when I sit in and I listen, there is no collective leadership. It's very territorial, and thing that I see sometimes go wrong in these obeya rooms is that it's a decorated conference room, really, and that decorated conference room has a wall of charts, but not one issue. Everything is green. A sequence of functional presentations (is) being done of how we're progressing, but no one is really challenging the red. There's a monthly status or a weekly status reporting of each area, but nothing really gets collective support. It's really still that individual that is reporting out: “Here's my team's barriers. Here's what we're doing about it.” But the team in the room isn't saying, “How could I serve you?” It's “I'm hearing a presentation to understand your status update,” and so it doesn't feel like a collective leadership. It feels like a command center controlled by the highest-ranking leader in that room.

JD: And we've discussed this in the past a few times, right? About what drives that silo mentality, and there's several things. If each of those leaders has individual goals and objectives, then that's what they're focused on, is achieving their individual tasks in order to make themselves more recognizable for future promotions. Or on the other hand, they may be focused on protecting their own individual team. So it's almost like, to use a football analogy, if you walk into that obeya room and one leader feels like they're the Chicago Bears, and another leader feels like they're the Green Bay Packers, and another leader feels like they're the Seattle Seahawks, on and on, then they're basically walking into that room expecting a challenge, a fight. Hey, I'm protecting my team, my team's colors. So if I'm the head of human resources, I'm going to do everything I can to protect my team versus the understanding that there is only one team, and that's the organization as a whole. Because again, you could have the best purchasing department in the world, and if your operations stink, your customer's not going to buy your stuff anymore, and you're going to go out of business.

Breaking Down Barriers, Removing Silos

JD: So the sooner that people recognize that you're all on the same team… So what are some things that could be done to break down those barriers? Well, first, to have some sort of collective objective that they're all measured against. Whether it's customer satisfaction or growth or profit margins, whatever that needs to be, but something where they all feel like they're succeeding or failing together as a unit. That's important, and then having some sort of clear definition of what a promotable candidate looks like. That it's more than just their department hitting their objectives, but how much did they help everybody else achieve their objectives? How selfless, selflessness and humbleness need to be a key component. Or if they get promoted, then you're just going to have silos at a higher level. It's just going to keep destroying the company. And then, of course, it all boils down to the foundation of drive-out fear, which we've talked about many times, right? Dr. Deming's eighth point. So if you walk into that obeya room full of fear—fear of being accused of wrongdoing, fear of exposing bad information, fear of the fact that you tried something new that failed. If that is part of the culture, then your natural tendency will be to put up the shield, make everything look green, and deflect any blame away from your team and try to pin it on one of the other teams.

How to Assess Collective Leadership Maturity

MS: One of one of the roadmaps, or I would say the mental models, when I sit in on some of the executives' obeya rooms and kind of assess the maturity of where they sit, there are a few things I observe for, to look for collective leadership and if that behavior exists or not. And at the most basic level, like you said, the foundation: Where are we against that objective? And do we understand what's off track? Like what's driving that gap? And if I hear that people understand what's driving that gap, I try to hear: Do we understand the dependencies that are blocking that progress? What are the obstacles that are underway, and what is the decision that this collective group needs to make? Now, what is the decision that that individual needs to make? What's the decision that is coming to this team that we collectively need to make, and do we understand who owns it? And I'd say the key ingredient here, if the leaders start debating whose data is correct, then I'm going to tell you this organization is not really ready yet to debate what to do, and there is no collective leadership yet. There is fundamentally fear, like you said, and fundamentally a lack of trust. But if we are operating off this one shared room, which requires shared truth, and so for operating with that shared truth, then the room becomes actually useful.

MS: So it's really hard to exercise that behavior if we're still designing the room in a way that's very functional. Like these are HR projects, these are IT projects, these are ops projects. We have to look at it as this is a collective whole. And the other litmus test for me is when if John presents on his hoshin, his annual improvement priority, how many people talk? Does John's peers talk to him about his barriers and see how they could help him, or is John only reporting to the GM or the COO or the VP, depending on the altitude of this obeya? And so, if this person is only reporting to the head of the table—hopefully there's no table—but that the head person in that room, then it's a status check. It's really not a collective leadership forum. But if I see everyone talking to John about what are the barriers? Help us understand this. Okay, what could we do to help you? Then there's collective leadership. But if it's John talking about, here's my obstacles, here's what I'm doing differently, here are my next steps, and no one else but the main person in the room is talking to John, then honestly, you could have just had that as a one-on-one. You didn't need the collective leadership. It's not an obeya room. It doesn't serve the purpose of why that room was created.

JD: Yeah, exactly. And can you imagine this happening? Let's say that you're struggling. Your department, whatever you're working on, is struggling. And let's say that I offer up some resources to temporarily move over into your team to help you get over these difficulties that you're encountering. First of all, would that ever happen? Well, you'd have to have that collective leadership, but at the same time … I would basically have to not have the fear of then someone saying, "Wait a minute, John, why aren't you hitting all your objectives?" So, in other words, if I take say three of my project leaders and temporarily move them over to your department because clearly that's where the need is for the whole organization to succeed. Well, whatever projects those three leaders were working on aren’t going to progress during that period of time. So if I'm still held on the hook for those projects, I have no incentive to share those resources, right? Or even if I believe that might happen, if in the back of my mind, if I feel like, boy, at the end of the year, my bonus is going to be impacted because those three projects didn't get done on time—even though, as a collective leadership team, we agreed that the need was much bigger in your area, and moving those resources was what was smart for the whole organization to succeed—then I'm going to be very reluctant to give those up. So again, it all goes back to the drive out fear. … I've got to have the ability to not be afraid to share those resources if the need is really the biggest in your part of the process.

MS: I'm going to say something that is that's probably going to ruffle some feathers here really quick. But say I'm a general manager of a site or a hospital, and we did the process correctly. The CEO talked about their vision, talked about where they want to be in the next five years. We broke that down into annual improvement priorities, and we understood year one what are our objectives. We broke that, we cascaded that through catchball to the sites. The sites figured out how they're going to contribute to that, and we created an obeya room that demonstrates that. And we, as a team in our site, have collective leadership. Collective leadership is not constrained just to the site, because if I'm the VP of HR, and I start cascading my own objectives to the sites, and I'm the VP of IT, and I start deploying my own objectives to the site, or I'm even the lean office that's in corporate, and I'm deploying my own lean stuff to the sites. In absence of that, there are hoshins in an obeya room that currently exist that are part of our planned strategies. Okay, and now there's this this isolation of initiatives that are now coming down to the sites that are outside of the obeya room. These individuals that are cascading have to understand that they're part of the collective leadership, and so it has to funnel through the obeya room because it has to have collective leadership. These people have to collaborate with the site. They can't just say you have to work on this. Well, what you're saying I have to work on is different than the hoshins I have in my room.

MS: So collective leadership is not just in the isolation of the president of the site and their senior leadership team, or the GM of the site and their senior leadership team. Collective leadership is the entire organization. Any initiative that's touching that site has to funnel through that. And yeah, well, then the GM gets to control it. Yeah, well the GM does control it because the support services are there to support and serve the sites, not the other way around, and so I think the importance of the collective leadership is to understand that we are building a behavior here to collectively collaborate and be able to challenge each other within that room. That's why some companies, I'm not a huge fan of this, but some companies call it the war room because it's where debates happen. This is not a room where whatever goes through, we have to say yes to. We could push back, we could debate, we could go back and forth, but we have to walk out as a unity. And if organizations, and I'm not just picking on corporate right now, I'm just using them as an example, start cascading their own strategies outside of the obeya, then we're destroying the collective leadership that could actually happen. And if they're worried that if they go through the room, there's going to be debates, well, the debate is very healthy. It's because if you do it any other way, it's actually going to be very destructive to the culture and to the importance of that behavior. So it's really, really critical to use the obeya room as the funnel, and everything needs to go through it, and be able to duke it out inside that room. But then walk out as a unity. And if you don't walk out as a unity, if you walk out as still functional, then the room was unsuccessful.

Sign up for our eNewsletters
Get the latest news and updates

Voice Your Opinion!

To join the conversation, and become an exclusive member of IndustryWeek, create an account today!