Lorem ipsum dolor sit amet, consectetur adipiscing elit lobortis arcu enim urna adipiscing praesent velit viverra sit semper lorem eu cursus vel hendrerit elementum morbi curabitur etiam nibh justo, lorem aliquet donec sed sit mi dignissim at ante massa mattis.
Vitae congue eu consequat ac felis placerat vestibulum lectus mauris ultrices cursus sit amet dictum sit amet justo donec enim diam porttitor lacus luctus accumsan tortor posuere praesent tristique magna sit amet purus gravida quis blandit turpis.
At risus viverra adipiscing at in tellus integer feugiat nisl pretium fusce id velit ut tortor sagittis orci a scelerisque purus semper eget at lectus urna duis convallis. porta nibh venenatis cras sed felis eget neque laoreet suspendisse interdum consectetur libero id faucibus nisl donec pretium vulputate sapien nec sagittis aliquam nunc lobortis mattis aliquam faucibus purus in.
Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque. Velit euismod in pellentesque massa placerat volutpat lacus laoreet non curabitur gravida odio aenean sed adipiscing diam donec adipiscing tristique risus. amet est placerat.
“Nisi quis eleifend quam adipiscing vitae aliquet bibendum enim facilisis gravida neque velit euismod in pellentesque massa placerat.”
Eget lorem dolor sed viverra ipsum nunc aliquet bibendum felis donec et odio pellentesque diam volutpat commodo sed egestas aliquam sem fringilla ut morbi tincidunt augue interdum velit euismod eu tincidunt tortor aliquam nulla facilisi aenean sed adipiscing diam donec adipiscing ut lectus arcu bibendum at varius vel pharetra nibh venenatis cras sed felis eget.
This is Part 3 of a series on the top problems with Project Management Tools. See Part 1: Old Tools, New Rules and Part 2: The Illusion of Control to catch up.
It’s not going out on much of a limb to say that the role of Project Manager in most organizations is frustrating. It can quickly feel like an endless cycle filled with what Lean experts might call ‘waste’.
My intent is not, of course, to have all the PMs reading this in tears. Perhaps I should have prefaced this post with a warning. Instead, my goal is to point out the futility of the place we find ourselves today, sadly attempting to change the future without learning from the past. It’s time to break the cycle!
I’ll preface this section by saying that I fully expect to get some pushback from PMs who object to any part of their process being labeled as waste. In an optimal world I would tend to agree. The role of a PM is to deliver a project on time and on budget, maximizing the success criteria defined at the project’s kickoff. One might argue that any activity that moves the team in that direction is high value.
Unfortunately, we don’t live in an optimal world. As we covered in Part 1: Old Tools, New Rules, and in Part 2: The Illusion of Control, we’re using tools and processes to try to control projects that exist in a radically faster and more agile world than anyone who designed those tools and processes could likely comprehend. Keeping that in mind, it’s much less of a surprise when you realize that many of the steps you take day-to-day might be deemed wasteful in that they fail to add value to the project or help make it any more successful. A modern day update to the age-old Zen koan: “If no one looks at a project plan, does it still control the outcome of the project?”
Many of you will be familiar with the Lean manufacturing system, which came out of the Toyota Production System (TPS) and was famously adapted into the excellent book The Lean Startup by Eric Ries. Lean helpfully defines several different types of ‘waste’ that can occur in the manufacturing process, some of which can be borrowed to explain the PM cycle described above. There are tree types of waste (muri, mura, and muda), but we’re specifically interested in the third:
Muda (無駄) is a Japanese word meaning “futility; uselessness; wastefulness”, and is a key concept in lean process thinking.
There are two types of Muda, known as:
We often serve two levels of customers as PMs: our internal customers who are working on the project and our external customers who are receiving the end result of the project. In both cases, much of the busywork that makes up today’s PM efforts (complex project plans no one follows, endless status updates no one reads, etc.) could be labelled Muda Type II.
To get a little lower level, there are seven types of Muda that we might focus on, often remembered through handy short forms like TIM WOODS (leading to generations of self-conscious operations experts named Tim Woods).
The relevant ones for us are Inventory (making stuff that sits in piles either between steps or after all the steps are done), Waiting (the time that stuff sits in piles between steps), and Over Processing/Production (spending time and effort on steps that don’t add value recognized by our internal or external customers).
Consider your detailed project plan that lives in Microsoft Project on your laptop. Since many of us are knowledge workers, the concept of Inventory may seem surprising. It’s not like we’re cranking out widgets in a factory! Except we are. That project plan is inventory. So are your status reports. They are the output of the work you do, and so the more inventory you build up that isn’t directly useful in driving customer value, the more Muda you have. Now think about the handoffs between everyone in your project’s path, critical or otherwise. How many times does someone end up waiting at those handoffs because the team one level up the waterfall hasn’t finished? More Muda. Lastly, think about the over processing that happens when you take your eye off a task and the team involved gold plates their requirements, or misunderstands them, or just plain does more than they needed. Muda.
“Okay, fine.” you say. “I’m knee deep in waste. But even the time I’ve spent reading this eloquent post has created more waste. How do I break the cycle?” Glad you asked. Three deceptively simple steps:
Those three steps aren’t going to unlock some magical PM paradise (sorry!), but they are going to help you break the cycle and evolve toward a future of orchestration and a much, much smaller pile of Muda.
