Y2KWiz

In the past Y2K era , there have been lots of lessons learened that are worth noting and keeping.

The importance of this is NOT from a historical viewpoint to document the past, but because of the importance of the topic and its extension into the present under different names and revelations including

1. Risk Management
2. Information/IT Security
3. Contingency Planning 
4. Business Continuity/Disaster Recovery
5. Mass-scale Natural/Industrial disasters

This is what I call the Y2K++  era !  One (+) sign indicates the extension in time infinitely (unlike the Y2K thing), and the other (+) sign indicated the increasing complexity, sophistication and challenging nature of these issues

The beauty of the Y2K era is that like many other similar topics, it includes elements from business, technology and lots of culture aspects.  It was an era that had its own wisdom too that can be applied in many other emerging situations demanding rational thinking, clear priorities and strict policy administration

• Triage principle ...  applicable in medical and non-medical situations where decision making needs to be done based on life and death criteria 
• The difference between these "technology-originated" threats and "terrorist-originated" threats is that you can possibly negotiate with the later one, not the first !
• Simplification .... In case of emergency, complex processes and procedures can be replaced by "word of mouth" agreements/instructions based on good will and mutual trust
• Master Planning ... global (wide stretched) and fundamental issues/challenges need sort of a master plan  to deal with quite effectively. 
• Replace if you can. Fix if you must ! .. Nice way for proper cleanup and upgrade ..  Replacement by functionally equivalent alternatives including those demanding reverse-engineering based on black-box/white-box analysis 
• Project/Program Management Office (PMO) .. is very often needed in these situations to coordinate, control and synchronize the different projects, programs,initiative and actions
•  Business Impact Analysis ... is often needed in most of these topics to maintain focus on the business considerations for technology and/or people originated issues
• The cost of dealing with these issues ... vs ... cost of leaving them and having the problems 
• Dependency and Inter-dependency Analysis
•