Gavin Ritz praises the K-T problem solving method and concludes "From an
engineering point of view, cannot find a better method."
I, too, am a student of problem solving methods and, like Gavin, think
highly of the K-T method. However, it is best suited for a certain class
of problem, namely, the kind in which some unforeseen, unwanted change
leads to a deterioration of previously acceptable results. In short, the
K-T method is most useful in those situations in which something goes
wrong.
The K-T problem solving method is recognizable for what it is -- a fault
isolation or troubleshooting methodology -- and, when something goes
wrong, employing such a methodology is a smart thing to do.
Unfortunately, in complex systems such as organizations and the work
processes found therein, many problems are not amenable to treatment using
a fault isolation methodology. Moreover, even when "causes" can be found
it might not be possible to simply undo them and thus restore previously
acceptable conditions.
So, my own view of the K-T process is that it is a dandy technical
troubleshooting approach but not at all an engineering approach.
List members interested in pursuing these ideas in more detail can go to
my articles web site http://home.att.net/~nickols/articles.htm and check
out some of the articles in the problem solving section there. In light
of this thread, I recommend two: "Reengineering the Problem Solving
Process" and "Solution Engineering: The Short Version."
Regards,
Fred Nickols
Distance Consulting
http://home.att.net/~nickols/distance.htm
nickols@worldnet.att.net
(609) 490-0095
--Fred Nickols <nickols@worldnet.att.net>
Learning-org -- Hosted by Rick Karash <rkarash@karash.com> Public Dialog on Learning Organizations -- <http://www.learning-org.com>