Blog Archives

Micromanaging…Or Lean Leadership?

I am a couple of weeks behind on this one, but I thought it was a good blog and worth mentioning.

If You’re Not Micromanaging, You’re Not Leading” was the title of a blog post by Michael Schrage at the Harvard Business Review blog site.

The title hijacked me right away.  Title alone goes against everything lean is about.  Then I read the article and found Michael was actually advocating for lean leadership behavior without calling it that.

…this vignette affirms my belief that leaders need to “go to the source”even before they turn to their best people. Seeing the data raw instead of analytically pre-chewed can have enormous impact on executive perceptions.

Sound familiar.  Michael is talking about directly observing the work.  A foundational principle of lean.  He gives a second example of why directly observing is important.

At one global telecommunications giant, for example, a critical network software upgrade was not only slipping further behind schedule, but the bug density was slowly creeping up, as well. The program managers’ key performance indicator dashboards showed nothing alarmingly unusual except the seemingly usual slippage and delays associated with a complex project with moving parts worldwide. The executive responsible for the deliverable (but not the software engineering itself) felt something amiss. The error rates felt too high and the delays too long, given the clarity of project milestones. He wasn’t technically sophisticated enough to read the code or analyze the testing, but he asked several project managers to share how their code was being documented. The raw material astonished and appalled him. The code was both hastily and poorly documented; the result was confusion and ambiguity that not only created delays but introduced errors into the software. The deadline-driven programmers, unfortunately, thought nothing of improvising just-in-time documentation via email, and misunderstandings and typos quickly propagated program-wide. The result was a worsening mess.

The executive intervention — making documentation a priority, streamlining version coordination, and changing the testing protocols — didn’t get the complex program back on schedule, but stopped things from getting worse, and dramatically improved both product quality and post-launch maintainability. It could never have happened unless leadership had the courage and competence to go to the source.

Great examples to bring drive home the point of how important directly observing the work is.  But, I do disagree with Michael on one thing…

Is this micromanagement? You bet! But real leaders are constantly called upon to create new contexts for people to succeed. Sometimes holding people accountable is the path of least resistance rather than what’s best for the organization.

I don’t think so.  Understanding current reality is not micromanaging.  It is necessary to be a great leader.

Micromanagement is telling your employees how they should be doing their job.  Worrying about how each detail is done which is different than worrying about what are the details and understanding the current reality.  There are quite a few comments below the blog mentioning similar thoughts also.  Micromanagement is more than just understanding the process and current reality.  Micro-managers fret about HOW you got the raw data or HOW you completed the work and try to tell you HOW to do the work.

Overall, a very good post.  I just hope it does not lead people down the path that understanding is micromanaging and then it carries over to be a black mark for lean.

What do you think?  Directly obrserving work or going to the source, Micromanaging?  Or not?

Pre-emptive Strike on Micromanaging

Recently, there were a couple of great blog posts about micromanaging over at the Harvard Business Review blog.  You’re Probably a Micromanager and Why People Micromanage.

One of the reason Ron Ashkenas sites for micromanaging is the manager worries about being disconnected from what is going on.  I have seen this be true in a lot of cases.  The manager has a hard time trusting what is going on with the work and needs the comfort of being involved in order to be relaxed about the situtation.

One thing I have found to help with micro-managers is the pre-emptive strike.  Try getting out in front of the work and give regular updates without being asked to do so.  Once a week or after a meeting, send the manager an email with what work has been completed to date and what work is next to be completed as well as how you feel the work is going.

In most cases, this can start to build trust with the manager.  The manager can start to do less micromanaging.  The key is to take on doing the updates without being asked to do so.  If the manager asks, then it will seems as task the manager wants to keep an eye on you.  If you take the initiative to update the manager, the manager respects it can starts to build some trust which can allow the micromanaging to start to subside.  When that does yo feel better about the work and working for the manager.

This may not work all the time, but it is a place to start.