You've Got Muda On Your Shoes
From the pmStudent Blog
by Josh Nankivel
Ranting and raving about project management and systems engineering.
Recent Posts
The Problem with Project Management
The Problem with Project Management
The Problem with Project Management
LinkedIn Recommendations Are Easy
The Catch-22 of Project Management Certification and Experience
Categories
Agile,
Career Development,
Certification,
Change Management,
Communications Management,
Cost Management,
Documentation,
Earned Value Management,
Education,
Integration and Test,
Kanban,
Leadership,
Lean,
Lessons Learned,
Methodology,
Misc,
Multitasking,
New Project,
Operations,
Planning,
PMP,
Productivity,
Professional Development,
Project Estimation,
Project Leadership,
Quality,
Requirements Management,
Risk Management,
Schedule Management,
Scope Management,
Software,
Systems Thinking,
Tools,
Video,
Work Breakdown Structures (WBS)
Date
Waste.
There is almost nothing I despise more.
Muda is a Japanese word meaning waste; activity that does not add value.
Why would you do such a thing?
Why?
“There is nothing quite so useless, as doing with great efficiency, something that should not be done at all.” ? Peter F. Drucker
Shoveling Muda
For a long time now corporate offices have been intent on efficiency, on productivity. We have been shoveling value littered with muda, in some cases mostly muda.
We have been focused on getting better at shoveling. More efficient shoveling is the only way to get more done, right?
In our current mindset, yes. If you aren’t able to change the content of what you are shoveling, you are doomed to go on shoveling a mix of what’s valuable and a great deal of what’s not. We bring in machines to automate the shoveling to make it go faster. Sometimes this means even more muda seeps into the mix, but we’re moving more tons per hour so it must be good.
And then we use our fancy tractor shovel to dump the mixture of half value, half muda on to our customers.
Self-Induced Muda
Now what if I tell you the muda involved in the above scenario is mostly self-induced? We’re actually creating the muda ourselves in many different ways.
We start with a pile of diamonds, but bring along some mud ourselves which we throw onto the pile of value. We tell ourselves the mud is necessary to keep the diamonds from moving around so much, or perhaps our supervisors require us to use mud. We see no useful purpose of the mud in this process, but we go along like good employees and do it the way it’s always been done.
Many times the mud had a purpose once, but now we are mining something entirely different than when the mud was introduced originally. However the old timers have always used mud, so we keep using it too.
Eliminating Muda
What if there was a way to go about delivering what the customers wanted, without the mud? Or at least without bringing along our own mud to the project?
Well, there is. It’s called Lean Thinking.
You can start by asking Why. And then ask Why again, and again. I’m not talking about the 5-Whys technique, that’s a different topic.
I mean every time you or your teams partake in an activity of any kind, ask these questions:
-
Why are we doing this?
-
What’s the value of doing this?
-
Who gets value from doing this?
By the way, an answer like “upper management gets value because hey, they asked for it” is not good enough. Doing something just because somebody wants it isn’t good enough. Why do they want it? Are you sure they want it?
I’ve seen people produce reports by hand for years, and email it out to executives every day and then find out that no one ever, ever opened them. The reports were started at some time because a director asked for them. She probably used them for a week and got the information she needed, and then they became irrelevant.
But no one asked why. They just added it to the daily reporting deck, assuming it was valuable.
Well, it wasn’t. And as a result, some people’s entire jobs are almost entirely spent producing waste, when they could be producing value instead.
Think about the project(s) you are currently managing. What is their value to muda ratio?
Posted on: May 01, 2012 08:47 AM |
Permalink
Comments (10)
Please login or join to subscribe to this item
Wai Mun Koo
PMO Director| Intergraph PP&M
Singapore, Singapore
Josh, nice article. Most pet projects usually deliver white elephants which cost a lot to the company to maintain them when no one is actually getting any value. The three questions listed above are pretty valid which should be addressed at the business case level. Unfortunately most business case selection processes I have seen are not as rigor as we would like and often biaised (depending on who is the sponsor).
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
Thanks Wai -- wouldn't the world change dramatically if every business decision started with those questions?
Wai Mun Koo
PMO Director| Intergraph PP&M
Singapore, Singapore
Josh, I agree, but it also depends more on how the questions are being answered. :-)
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
True, true :-)
I should have added...value from the customer's perspective.
Keep in mind that most muda is produced in operational duties, though it can occur when reutilzing previous project plans.
But sometimes, muda is actually value that the company has forgotten about. This is usually due to employee churn and/or changing biases as a result of the churn.
A variable amount of my time is spent on operational duties. For these duties, I have created a value register, describing the duty, frequency, value it brings and a RACI model. Usually 1/yr I try to hold a meeting with the RAC members of my duties to review if the value proposition is still there or if it needs to changed or eliminated and inform the I''s accordingly.
For my projects, I use a similar value register during the planning phase. In my wbs, I add a note or a column called expected value to help determine why a step is necessary and how is it related to scope.
During revisions and or changes this gives the team a quick reminder why things are being done the way they are and if they are still valid. During closure, this also allows an additional structural step for the lessons learned, which allows the lessons learned summary to be a lot faster and more robust then a free form meeting especially for a long term project.
In addition, when a similar project comes along, and you are pulling out old project plans, I find that updating the wbs becomes a lot easier if you know why certain steps were taken in the past + the RACI inclusion gives you an idea who to turn to on how to perform certain steps, even if that person is not part of the new team.
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
@Alexander, I really like the idea of adding a description of value specifically to the WBS. I'll have to try that!
I think where muda can be found is going to vary from organization to organization. My company is almost entirely projectized and our projects are years in duration, so momentum and whatnot set in and project work almost seems to become operational work at times.
Brad Egeland
Business Solution Designer| Bradegeland.com
Las Vegas, Nv, United States
Nice article Josh...and how true this all is. Yes, some individuals' entire jobs are spent on wasteful output. Because it's always done this way or because the exec management team is not a good reason to just do it. We should be asking those questions. Sometimes it's tough to do when we as project managers are overloaded with 5-7 hot projects...it's those times where we still often have to 'just do it' and not ask those questions. But as we free up, we need to proactively engage in the lean thinking you are describing. Thanks!
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
@Brad thanks for the comment. I'd even argue that we shouldn't wait for our time to get freed up, because most of the time that will never happen. The time for sharpening the saw should be factored in to our daily work activities, otherwise continuous improvement never happens. What happens instead is a single lessons learned meeting at the end of a project nicely documented that never actually changes anything. :-)
Naomi Caietti
Senior Project Manager | ePMO | Higher Education | Healthcare & IT| Linkedin.com/In/NaomiCaietti
Timely article especially since organizations are doing more with less. This challenge or opportunity (I think) enables organizations to take an introspective look at business process and a 360 degree view of value for the organization and customers(s). The real opportunity is for the organization to consider sustainabilty, innovation, new products and markets, return on investment and competitive differentiation. Sometimes it just takes a little disruption to shake up the "muda". Thanks, Josh.
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
Disruption can be a positive change agent! Thanks Naomi.
Please Login/Register to leave a comment.
|
"Don't go around saying the world owes you a living. The world owes you nothing. It was here first."
- Mark Twain
|