This technique is called a 5-Why in lean manufacturing. Useful tool in digging into a root cause, and helps people think deeply about the causes of issues that are not inherently obvious. Also, 5 is just the "suggested"…
I had a boss that worked in Continuous Improvement. As a manager he was great because he was very good at coming up with the nucleus of an idea. He was terrible about implementing the idea, but had a crew that was great…
When writing crappy code you are either not thinking long term at all, or you are just "kicking the can down the road", in that you'll pay for it later when there isn't a time crunch. Not that I've ever done something…
They don't even use step 4. They just raise the "non-participation" penalty so high that you, for all intents and purposes, have to participate. The company I work for charges a $50 per week penalty for not…
The same thing happens with an actual police force, though. Too much adrenaline and the "shoot first, ask questions never" mentality.
This technique is called a 5-Why in lean manufacturing. Useful tool in digging into a root cause, and helps people think deeply about the causes of issues that are not inherently obvious. Also, 5 is just the "suggested"…
I had a boss that worked in Continuous Improvement. As a manager he was great because he was very good at coming up with the nucleus of an idea. He was terrible about implementing the idea, but had a crew that was great…
When writing crappy code you are either not thinking long term at all, or you are just "kicking the can down the road", in that you'll pay for it later when there isn't a time crunch. Not that I've ever done something…
They don't even use step 4. They just raise the "non-participation" penalty so high that you, for all intents and purposes, have to participate. The company I work for charges a $50 per week penalty for not…
The same thing happens with an actual police force, though. Too much adrenaline and the "shoot first, ask questions never" mentality.