Make your own free website on
Recommended Resources Offshore havens, asset protection, global investing and other useful techniques.
The Year 2000 Bookshelf Books to help your evaluate the Y2K problems you face.

Gary North's Y2K Links and Forums - Mirror

Summary and Comments

(feel free to mail this page)




1997-03-07 00:00:00


10 Things Businessmen Need to Know About the Problem


This list was prepared by Karl Feilder, a South African programmer and expert in the effects of the Year 2000 Problem on desktop computers. Here he provides a basic outline of the general Y2K problem from the businessman's perspective.


From: "Karl W. Feilder" > Subject: 10 Things you need to know > Date: Wed, 5 Mar 1997 05:20:06 -0000 > > Thanks to everyone who contributed to the following. The information was > used in The Sunday Times in South Africa last Sunday. > > 10 things you need to know about the year 2000 problem - 1034 days / 33 pay > days to go [on Sunday March 2 1997]. > > Collated by Karl W Feilder of Greenwich Mean Time from responses on year > 2000 mailing list by consultants and end users who are already working on > the problem. > > 1. Don't panic. Historically, 80% of IT projects are late. Although > this project has an immovable deadline, the problem is finite given enough > time and money. Many problems will be hidden until they occur. > > 2. The Domino Effect - your business depends on suppliers and > customers - if they do not address the issue you will be at risk. If you do > not address the issue, some of your customers may not wish to deal with you > any more. > > 3. Directors are liable. This problem is foreseeable. If a director > chooses to ignore this he may be trading negligently and hence liability > for damages may be unlimited. Auditors, bankers and insurers of your > company may withdraw their support for your company if you do not have an > active plan for dealing with the problem. > > 4. There is no silver (magic) bullet. There are some tools that will > help speed up the process, but there is no simple fix. > > 5. This is a business problem based on a technical oversight. The > problem is real, it affects all sizes of companies, and it is bigger than > expected (British Telecom has budgeted 700 Million to fix it and the US > Govt. has budgeted $3.5 Billion). It may affect any computerized system you > use. You do not know what will be affected unless you check every piece of > computerized equipment that touches your life. > > 6. Focus on business survival not IT survival and make a backup plan. > In many cases this may be a paper-based system. Prioritize, and fix what's > most important first. > > 7. Budget now and start work now. Otherwise your bonuses, profits, and > share price will certainly be affected in the future. > > 8. The problem belongs to you. There will be no government handouts > for this issue (they have their own problems) and no one cares as much > about your business as you. > > 9. Your auditors may refuse to sign your annual accounts if you do not > have an active plan in place, which will result in loss of confidence in > your business. > > 10. While you shouldn't bet your business on worthless promises or > documents from your suppliers, it is valuable to force them into activity. > > Karl W. Feilder, > Greenwich Mean Time > > Dedicated to raising global awareness of PC and client/server Year 2000 issues

Return to Category: Introduction

Return to Main Categories

Return to Home Page