Why Managers Are Bottlenecks
Quite often, whether on the shop floor or in the office, a process grinds to a halt when frontline employees have to go seek manager approval for something. Whether it is for spending that exceeds a prescribed threshold, when two employees want to swap work stations to stay fresh, or to sign off on a repaired product after a defect is corrected, if a manager is not immediately available, work flow is disrupted.
In some cases, the manager even intentionally develops a batch process to avoid interruptions. Perhaps she reviews all new spending requests on Thursday morning. Great if you come up with an idea on Wednesday afternoon, but not so good if you have your flash of brilliance at the start of the shift on Friday.
So, to combat the review processes in your company, I recommend you look at every manager approval your organization requires. The goal is to determine the underlying reason that the check is in place. Then, see if any of the assumptions that drive the review process are valid, or if they are obstacles that can be removed.
Why go through this drill? For two main reasons. The first, as mentioned in the opening paragraph, is that approval processes disrupt flow. They also add copious amounts of waste. The manager is interrupted and has to figure out what is going on, which takes their time. And, of course, there is also the time the employee spends explaining what is happening, or gathering and documenting information. Plus, and perhaps most problematic, when a file is sitting in a stack waiting to be looked at, a customer is frequently not being served.
The second, and far more important reason, though, is that approvals send the wrong message to employees. If you want a continuous improvement culture with an empowered workforce making decisions that strengthen the company, leaders have to actually give authority to their teams. Requiring sign-offs, especially for minor things, doesn’t scream empowerment.
Some common reasons approval processes exist include:
- Lack of a Process: Some managers use ‘gut feel’ decision making. For example, when deciding whether to let someone have a day off of work, a manager probably considers several factors, but likely doesn’t use the same criteria each and every time. By defining a process, a team could easily develop its own vacation process and manage it themselves.
- Lack of Training: When a process is in place, but is not known by teams, it is the same as having no process. Teach teams how to think the same way that a manager does, and they will get the same results.
- Access to Information: Managers generally have access to more information than employees do. A prime example is the budget. An employee making a decision about a purchase may not know where the team is in terms of expenses. Give your teams more information, and they will make better decisions. When they are thinking in terms of actual dollars, they will also be more likely to weigh the costs and benefits of the decision, and will even filter out some of their requests on their own.
- Risk: Asking someone to take risks requires that they get more substantial rewards. Many people will feel uncomfortable making decisions ‘above their pay grade’. Managers should keep the riskier decisions to themselves, but in truth, most frontline employees don’t want to take on deciding whether to roll out a new product or where to build a factory. They would, however, love to be able to decide to purchase a new computer monitor to replace one with a bad flicker. And they don’t want to have to jump through a bunch of hoops.
- General Convention (AKA “We’ve always done it that way”): History is tough to overcome. If the best answer you can find about why a manager makes a decision is that the manager before made that decision, it is time to work on eliminating that approval process.
- Psychological Factors: Some managers like having power. They like having control. They like feeling important. There’s probably even a psychological term that describes how people lacking control in one area of their lives grasp onto it in another area to compensate. This situation is particularly hard to deal with because reason and logic often don’t play a major role. If you suspect this is the case, an anonymous request to a more senior leader for a specific process improvement project, or a conversation with a trusted mentor or HR rep can help get this barrier removed.
- Fear: When a manager has been bitten by a problem in the past, he is less likely to give up control in the future. Look at the reasons for past issues, and consider the root causes that led to the failure. You’ll find that most of those reasons could have been prevented by clearly defining a policy or process, and by making sure employees knew, understood, and followed it.
1 Comment
Il meglio della blogosfera lean #89 — Encob Blog · May 20, 2011 at 11:32 pm
[…] utensili in maniera corretta e quale è il vero significato delle 5s… (traduzione automatica)Why Managers are Bottlenecks dal blog Gotta Go Lean di Jeff Hajek: I processi di approvazione sono davvero necessari, o sono, […]