Over 50% of the IT executives are aware of the Y2K issue in North
America. It drops dramatically when you move to Europe, and even
lower when you get to the Pacific Rim.
The proportion of companies actually doing some work on the Y2K issue
is even lower. Why?
It will cost millions of dollars to fix this problem. It means
putting development on hold, and maintaining the status quo.
It means CIOs have to face their board of directors and state the
company will be bankrupt unless we stop all development, and just fix
code. And they will have to admit they have been creating this
problem in applications for the last 30-40 years.
It means a major upgrade of every PC and software around the world.
It means that, unless all your suppliers, all your services you rely
upon, from water, electricity, paper, pens.... they all have to be Y2K
cognizant, or they may not work in the year 2000.
As learning organizations, what can we learn from this, before the
crisis hits. And how we can adapt the learning org principles to
awaken the interest of organizations?
Gary Scherling
Helping people help themselves
--GSCHERL@fed.ism.ca (GSCHERL)
Learning-org -- An Internet Dialog on Learning Organizations For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>