This section has no reviewed German translation yet. The English edition 1.0 is shown below.

READER MODELong-form reading surface.

§9.2 · BUILDING · 4 MIN READ · EDITION 1.0

The go-live checklist

Go-live is a controlled release, not a deployment event: it needs a named owner, a rollback path, a first-week review cadence and a communication to affected users.

Confirm the qualified configuration matches what is actually deployed before flipping the switch; configuration drift between evaluation and production is a common, avoidable failure.

Tell the people who will use the capability what it is approved to do, what it is not approved to do, and how to report a problem — silent rollout invites scope creep from day one.

PUT THIS INTO PRACTICE

  1. 01Verify deployed configuration matches the qualified configuration.
  2. 02Communicate intended use and limits to users before go-live.
  3. 03Define the first-week review cadence in advance.

RELATED INSTRUMENTS

CITE THIS SECTION

§9.2 · Edition 1.0 · The go-live checklist

English is the authoritative text of this edition. Where a translation differs, the English text governs.