feature – what is the role of middle managers in a transformation and how can we ensure they can fulfil that role – instead of being blamed for the failure of the initiative and even excluded from it?
words: eivind reke and nadja böhlmann
for years, middle managers have been one of the most common scapegoats for failed improvement programs, implementations in which they often end up being bypassed . in this article, we suggest that instead of excluding or altogether removing middle managers from transformations, we should relieve them of exhausting coordinating work and administrative tasks and give them the space and means to think and act.
but how did we even get here? to understand the struggle of the middle manager, we can go back to one of masaaki imai’s most important points. he once said: “there are three most important requirements if you want to be successful and embrace kaizen and lean. the first of course is the top management commitment, second is the top management commitment, third is top management commitment.” with quite a bit of water having now flowed under the kaizen and lean bridge, it seems that the majority of lean companies have taken this point to heart. there can be no lean without a lean ceo, we are told. but where does this leave middle managers? how can a lean organization motivate middle managers and organize their work?
first of all, we need to clearly define the role of the so-called middle managers. these are our team leaders, line leaders, department managers, etc. in fact, there can be many levels of middle management in an organization (anywhere between three and ten), depending on its size and structure. each middle manager is responsible for the daily delivery of their factory, department, line, group, or team, and for the translation and implementation of the latest strategic program cooked up by the executive suite, regardless of how much (or little) sense it makes.
in short, it’s tough to be a middle manager! hired for their coordination and “political” skills and not necessarily for their ability to develop people and their technical capabilities, chances are they will often be held in little regard by the same employees they lead. in the worst case, they even lack a basic understanding of the work they are tasked with managing. their daily activities usually include answering emails, attending endless meetings, putting out fires, coordinating deliveries (“do this”, “stop that and do this instead”, etc) and overseeing – when they are not side lined, that is – the implementation of new processes, tools or systems. the modern-day middle manager is truly caught between the proverbial rock and a hard place. so, what is the lean alternative to this?
learning by improving
middle managers are often promoted internally from non-managerial positions or recruited from the outside to occupy a seat on the next level of the corporate ladder. congratulations on your promotion! now get on with it. this seems to be the approach in a lot of organizations: the pressure of delivery means little to no real training and it’s sink or swim. to succeed with kaizen and lean at each level of the organization, all employees must be given the opportunity to grow and learn what is necessary to succeed in their job. that’s why it’s important to develop a learning culture and invest in kaizen or lean academies. just like the rest of employees, middle managers need to be given the opportunity to learn and to understand how important their role is. they need to be able to step back from ever-day problems and gain an overview of their responsibilities so they can learn to prioritize.
once middle managers are given the right tools and knowledge, they should engage in the following sequence of activities:
- start with kanban
freeing middle managers from the mundane task of telling others what to do can only really be achieved when people can easily tell what their next task is. depending on the type of work and organization, you can rely on a fifo supermarket, a one-piece-flow production line, or a digital or analogue visual management board. regardless, kanban removes the burden of having to coordinate the work and is a prerequisite for the “sell one, make one” or “use one, procure one” idea that lies at the heart of just-in-time. kanban also shows us where the weak points in our systems and processes are. to easily track the problems and issues arising from these weak points, the next step is visual management and regular collaboration.
- use visual management and hold regular stand-up meetings in the obeya
visual management is key to separating normal work from abnormal work and spot non-compliances. it is also a great tool for showing progress, what the next steps are, and how the process is performing in real time. gathering data at least once a day to discuss key element – how the team is doing, what the plan is or where improvement is needed – will help the team and our middle managers to better understand the delivery process, its weak points and where change is necessary. visual management with kanban is unforgiving, but when things do wrong it also helps to remove blame from people. instead of asking, “why didn’t you finish the job?” we can ask “why was this kanban card not delivered?”. by focusing on problems rather than people and by aligning the team on quality, instructions, problems and improvements, visual management helps middle managers to facilitate the growth of team members. this way, people will develop their technical capabilities and become more autonomous and confident, which in turn will make them more inclined to try new things and look for kaizen opportunities. relieved of their coordination duties, our middle managers can now start worrying about quality.
- manage weak points
quality issues are great learning opportunities, because they reveal weak points in our processes. weak point management means finding and facing these quality issues every day. the only way to do so is to go and see, talk with workers, and think more deeply about why the issues we see are occurring.
most often quality issues can be broadly divided into three categories: local quality accidents, process quality problems, and design quality problems. local accidents are often related to difficult working conditions or lack of training and can usually be solved with in-line support. process issues are related to some aspects of the support systems that make it difficult to do the work seamlessly and effortlessly. finally, design issues are misconceptions in the design thinking that led to the creation of the service or product, resulting in systemic flaws. these different types of quality issues are not always easy to see: in fact, the closer they are to the design stage, the more difficult they are to pick up on. that’s why we need a system that flags them up.
- track performance vs goals
as part of efforts with visual management and weak point management, we must give our middle managers the ability to track the performance of their team and look at performance loss. how are we doing? how should we be doing?
again, we can see these as three levels of performance loss: promise loss, performance loss, and process loss. promise loss consists of design issues that disappoint the customer. they are often related with the limitations of internal systems and processes that determine what we think we can deliver. performance loss happens when we don’t deliver what we have promised. it’s typically defects that need to be scrapped or reworked. finally, process loss is what occurs when the process doesn’t perform as intended. even when the problem is corrected before it reaches the customer, it burdens our delivery system with extra work. process losses are a great place to start when we are trying to discover our misconceptions on process/product design.
- act to change systems
middle managers must have the ability to act to sustain quality and the space to reflect on their decisions. there are three fundamental questions that should always be asked: 1) which feature is affected by what loss? 2) which system do we need to change to reduce this loss? 3) what will the impact be of the change on features and systems? with the ability to act comes a stronger sense of responsibility. asking these three questions over and over again is key to developing leadership that has quality at heart. finally, we need to give middle managers the opportunity to grow by reflecting on their own actions and help them see how the decisions they make – even small ones – affect the overall ability of the organization to perform. it’s important they appreciate the impact they have on people, product and process.
a freer and more effective middle management will need to shift their attention and responsibility from the coordination of the work to worrying about quality, from the implementation of programs to the improvement of systems and processes, and from assessing performance to building trust, psychological safety and relationships.
eivind reke is a lean author and chairman of los norge.
nadja böhlmann is group kaizen promotion officer and program manager at teknos group oy. she has been a guest speaker at several conferences.