The resource utilization trap

Henrik Kniberg explains the resource utilization trap, how it impacts our ability to deliver and what we can do about it.

Camera and editing: Jimmy Janlén

Here's a live version of the demo, from a talk in Norway:
(starts at 4:26)

[FabrizioGibilaro]

I can't understand why so many manager are still obsessed with resource utilization above everything else. This is a great explanation. Thank you!

[touchph]

This has been the single best explanation about why a pull methodology create efficiency.

[carnub]

I've been trying to find a nice and easy way to present this to my colleagues for a long time now. Thank you. Tack!

[fuzzydunlop]

Excellent demonstration! Also, the video URL contains the word "Cost" - LOL

[paulaarmoa]

Amazing video Henrik! Thanks for such a clear explanation!

[scoogsy]

This was a really easy visualisation to follow. Would be simple to run this demo with my team!

[MrLittleW]

So simple. I'm bookmarking this, because I have seen so many companies fall into this trap.

Thanks for teaching these Lean concepts in such a visual way.

[PerLundholm]

That was a really simple and clear way of explaining it.

[apjmostert]

Incredible, what a simple way to explain what most fin difficult to understand.

[rashmireddy]

Great explained i got clear picture about resource utilisation it is not keeping busy it should be something value delivered to customer

[ChristopherDiller]

Can I "thumbs-up" this more than once? :)

[amandegar]

Wonderful video, but Henrik in reality how we can keep the balance between the teammates who have load of work and the one who don't commit to enough work?

[PtolemySoter]

Pull is restricted by managers dictating outcomes and restricting pull by offering task partially understood by them, not by the team. Irrelevant managers is always a bottleneck. Generic management is the problem in many companies.

[LarsBuhlSchamaitat]

A great (and fun) demonstration.
Cold you make one, where one of the workers is slower thank the others (or perhaps even absent)?

[adlapl]

One-piece-flow rediscovered ... thank you ... an element reducing LT and time-to-customer. However, for the resource utilization it is more complex to define whether batch-based production or a piece-flow-based one is better. It depends on type of production (not always discrete or assembly process), its layout, supply chain characteristic, even legal regulations (pharmacy) and of course high/low-mix/volume dependencies. To some extent those aspects should be also discussed - otherwise someone may become immediately biased. In other words - every solution has its weaknesses - not discussing them may be a sign of an unprofessional education. Anyway - nice workshop. I like "pause" moments.

[grugruu]

Very very interesting and insightful.
One issue I see is that some tasks aren't one-man's jobs. For instance in the world of software development, one typical step is the code review stage, which takes time and is on the critical path to delivery. But it's not the job of a single person, I mean no one would agree to only do this all day. Devs will typically do it in addition to their other coding tasks.
So in the metaphor here, it's as if the 4 guys were often changing place according to some arbitrary rules, which would definitely slow down the delivery even in pull mode.
Still very inspiring, thanks!

[lduberger]

Is there an infographic of this video? I would like to share it with colleagues but of course, youtube is blocked at work..

[TimSchraepen]

To anyone watching this video “today”, notice how long ago this was published on YouTube. Then think about what your current work situation looks like.

[eugenepugin]

thanks a lot, Henrik :) - you're fantastic demonstrator!