Stress-test an i18n freeze by proving that each cutover window and string rule can place locales inside the planned lane, survive override pressure, and avoid trapping operators inside a green freeze slide that hides long-lived exceptions.
i18n freezes often list a calendar while leaving string lock behavior, override authority, and abort ownership implicit. Those edges decide whether a late product ask stops inside the catalog or leaves a broken string live under launch load. The exercise should follow actual catalogs, build tools, and on-call paths rather than a clean localization deck.
Inventory the freeze path
List every product or market with its freeze window, string lock rule, override behavior, owners, and notification channels. Mark paths that cannot reverse without a manual catalog edit. Attach the last three freeze incidents with raw timelines and any waivers. Include the source of truth for open string counts during the observation window.
Define the phases for schedule, cutover, observe, abort, and communicate. Each phase needs an owner and an exit condition. Write the point after which a stuck string would require a different procedure, then review whether that action is still permitted. Capture maximum acceptable requester friction in measurable units, including which cohorts are excluded from the freeze and why.
Include the calendar of known events for the next two quarters: market launches, partner cutovers, and support peaks that shrink the usable change window. A freeze budget that ignores those dates will look calm until the week they land.
Failure drills
- A minority high-revenue market keeps a side-channel while the aggregate freeze dashboard stays green.
- A freeze has already left a partner build without a trusted string count.
- The primary catalog dashboard lags beyond the planned observation window.
- An operator skips a freeze gate because a renewal is close.
- Source and translated strings collide under the new lock rule.
- Abort authority is unclear at launch week and the page lands on the wrong rotation.
For each drill, identify detection time, customer impact, containment, and the authority to force a freeze rollback. Require commands and dashboard links in the runbook. A statement that monitoring will catch it does not establish which alert fires or who receives it.
Prove freeze changes are timed and owned
Run the package in Pingpong with localization, product, support, and engineering seats. Ask support which market decision becomes unsafe first if strings still drop after the claimed window. Ask engineering whether capacity can absorb a forced override. Ask localization to show the exact catalog version or freeze export used as the exit condition.
Related reviews include the localization lead seat, a locale priority list review, and a translation vendor switch review. Browse the war-game decisions hub for adjacent controls.
Authorize the published freeze only after a timed drill restores usable i18n hygiene inside the documented budget without an undocumented manual step.