← BACK TO THE ARCHIVE

CASE FILE 015 / PREVENTION & PREPAREDNESS

The quiet midnight people worked for.

PRIMARY SOURCE LINKED · ABOUT 3 MIN

A calendar boundary became a vast repair effort. The uneventful parts are part of the story.

Rollover dateJanuary 1, 2000
reported federal critical-system readiness · Dec 199999.9%
CollectionPrevention & preparedness
event_sequence / CASE 015January 1, 2000

FOLLOW THE PREPARATION

How a risk became a coordinated response.

A condensed sequence, not a minute-by-minute reconstruction.

  1. 01
    THE RISK

    Date-related risks identified

  2. 02
    THE PREPARATION

    Systems repaired and tested with partners

  3. 03
    THE OUTCOME

    Rollover managed with contingency plans

  4. 04
Source record: GAO · Year 2000 lessons learned, September 2000 ↗
THE PREVENTION WORK

Systems repaired and tested with partners

A successful transition does not prove the original risk was imaginary. Evaluate the inventories, tests, repairs, and contingency actions behind the result.

Editorial interpretation of the failure pattern.

01 / THE PREVENTION EFFORT

What happened

The Year 2000 date transition put computer systems and the services depending on them under scrutiny. This exhibit focuses on the US federal response documented by GAO: inventories, repairs, testing, partnerships, and contingency plans before an immovable deadline.

Evidence: GAO · Year 2000 lessons learned, September 2000 ↗

02 / THE RISK

What was at risk

The risk crossed organizational boundaries. An agency could not establish readiness solely by examining its own applications; data exchanges, service partners, and continuity arrangements mattered too. GAO identified leadership, coordinated reporting, and sustained oversight as major contributors to the response.

QUESTION FOR YOUR TEAM

What evidence would show that your next major transition is ready?

03 / THE AFTERMATH

The outcome—and its limits

GAO reports that OMB’s stated readiness for mission-critical systems at 24 major federal departments and agencies rose from 21% in May 1997 to 99.9% in December 1999. Most federal Y2K errors reported during the century and leap-day rollovers were minor and did not affect services. This was not proof of zero errors, worldwide readiness, or a risk that never existed.

PREVENTION IS AN OUTCOME

Readiness was built before midnight.

MAY 199721%
DECEMBER 199999.9%

OMB-reported compliance of mission-critical systems at 24 major US federal departments and agencies, as described by GAO. These figures do not measure every computer worldwide.

  1. Know what exists.Inventory systems and their dependencies.
  2. Prove the transition.Repair and test, including exchanges with partners.
  3. Prepare for exceptions.Coordinate continuity plans and response.

This case covers the federal preparedness effort. A largely successful rollover does not mean that no errors occurred.

04 / TAKE IT WITH YOU

What preparation made possible

Practices to investigate in your own organization, informed by the federal readiness effort.

01
SAFEGUARD 1Maintain an inventory that includes system owners and external dependencies.
02
SAFEGUARD 2Test critical services end to end with partners.
03
SAFEGUARD 3Preserve readiness evidence and contingency plans after the deadline passes.

Go to the source.

A condensed editorial account. The lessons are our interpretation, not quotations. Consult the primary source for the full technical record.

GAO · Year 2000 lessons learned, September 2000 ↗
Practice your response ↗
Compare this case with another

ONE QUESTION BEFORE YOU GO

What does a quiet deadline tell you about preparation?

TAKE IT TO YOUR TEAM

What evidence would show that your next major transition is ready?

next_step.txtREAD → PRACTICE

TAKE THE LESSON FURTHER

Check the agreement.

Which interface assumption has never been tested?

The rehearsal is fictional; the case is historical. The review starts with unanswered questions.

CONTINUE THE CONNECTION

TRAIL 05The machine followed the rules.Three cases, one recurring question ↗