Enlist the support of important clients to strengthen Y2K funding requests. Concentrate on resolving only the Y2K problem in itself. Do not attempt to simultaneously improve the functionality or other features of existing systems. Slow down or postpone new IT development to conserve resources. Remember that Y2K projects carry pitfalls of typical IT projects including overly optimistic scheduling, poor documentation and incomplete debugging.
Projects have a tendency to drag on longer that initially planned.
Make a contingency plan at an early stage. Include a worst-case scenario in the contingency plan. Document all Y2K efforts from the beginning. That written evidence may be invaluable later. Y2K compliance is a major business issue, the alternative is often a closure of operations.