I've enjoyed reading the postings on this thread. I admit, like Rick
(note in LO 10794), I'm concerned if we drift off too much in the computer
technology aspects. But as several postings have illustrated, the Year
2000 problem is a wonderful real and live illustration of many of the
aspects of what it means to do organizational learning.
It's very amusing, to me at least, that a group of people I thought were
trained to think systematically (computer programmers and systems
analysts) got us into this mess.
I wonder what other potential "Year 2000"-like problems are out there,
waiting to be discovered?
I also wonder if the efforts to "correct" the Year 200-programming
situation will go beyond just adding another two digits to every piece of
old software, and will surface some of the underlying causes - so when
this is all (hopefully) resolved, we can say we really "learned"
something.
Bob Tomasko
RMTomasko@aol.com
--Learning-org -- An Internet Dialog on Learning Organizations For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>