Hi took note of what you said.
Problem solving has always been an interest of mine. I have looked at many
techniques in this area and the best, my opinion, is the KT process
(Kepner-Tregoe) problem solving method, used in thousands of companies
around the world. Colleagues of mine have saved hundreds of millions of
dollars using this method. Their book the Rational Manager was printed way
back in the seventies. NASA has used it for years now too, it was even
used in the movie Apollo 13, when the cryotanks blew. From an engineering
point of view, cannot find a better method.
There are also linguistic problem solving methods with asking questions
without content, also pretty good stuff. But a little more difficult to
use, takes some getting use to. I have used these systems to assess
suitability for roles, see the LAB profile. Language and Behaviour
Laboratory Roger Bailey & Shelle Charvet.
Kindest
Gavin
Pilx wrote:
> >I'm a firm believer in the notion that language shapes thought and
> >thought shapes
> >behavior. The label placed on a problem, for example, invokes a frame of
> >reference that constrains and restrains the problem solver's efforts to
> >solve the problem. So, I guess I'm more inclined to explore the
> >"linguistic constructions" of problems than you might be.
>
> My comment may be so late that the tread is cold and or dying. My computer
> went down and I've been working. Anyway.
>
> I find you comment very interesting, because it supports and throws cold
> water on a point I make in Problem Solving Process classes. It is
> summarized below.
>
> It is necessary to define the problem and come to agreement on the
> problem. That definition helps focus energy of the team all in one
> direction...
[Big snip by your host...]
--Gavin Ritz <garritz@xtra.co.nz>
Learning-org -- Hosted by Rick Karash <rkarash@karash.com> Public Dialog on Learning Organizations -- <http://www.learning-org.com>