[1] http://www.startuplessonslearned.com/2009/07/how-to-conduct-...
In the training example, it’s quite possible that the first hour of training will cover 80% of the problem, with subsequent hours offering diminishing returns. The point is to discover it while avoiding waste.
He’s acknowledging that “root cause” is a club that can be used for bureaucracy; handled wrongly it looks a lot like premature optimization or CYA. What he’s describing is what I consider empiricism.
The second half was a little more confusing with proportion of time in solving the problem. I understood the solution but now how it directly related to using the 5 whys analysis.
That's my interpretation, anyway: Imagine that you have 20 different issues related to training, but that you have the same conversation about training 20 times :)
http://news.ycombinator.com/item?id=3564378 of course, perhaps in most cases Eric is right and successful. Please don't shoot the messenger.
PPS. start the flame war! rise and fall of the JAPAN manufacturing empire. SONY will eventually go bankrupt. too many nitpicking fault finders and little creativity in the big corp HQ in earthquake prone Tokyo. All the factories clustered in Thailand (how convenient for Japanese male execs to go!) which is flooded.
PS. How do I solve problems? I use the FIVE WHO. I take the strangest assortment I can find. Throw them together in a 'party' and then induce/abduce the answer. Since 'birds of a feather' flock together, the 'corporate dodo bird' is doomed to extinction (to mix metaphors).
~
There's also something of an assumption that the root cause always ends up as a human problem and not a technical one which is only sometimes the case.
This ends up turning a very powerful process and tool into being a very convoluted MBA speak on process and team dynamics.