GCC Build OSv0
/api
Home/bootminds.pmo/decisions/pmo.dec.gate_definitions_lock

Lock programme gate definitions (which gates, in what order, with what criteria)pmo.dec.gate_definitions_lock

P0 GCC

Summary

Lock the canonical set of programme gates that govern phase progression. After lock, adding/removing gates requires Steerco; changing exit criteria for a gate requires the gate's own approval chain.

Rationale prompt skeleton

Rationale should reference the gate definitions question, the evidence-standards question, and the gate approval-chain question. Note any wave structure and how gates compose with milestone progression.

Default options (3)

standard_six_gate_model Standard 6-gate model (Discovery exit / Design exit / Build entry / Cutover ready / Go-live / Stabilisation exit)

Canonical transformation-programme gate set. Covers the major phase transitions of a 12-24 month build.

Pros
  • + Well-understood model; aligns with how most transformation methodologies talk
  • + Each gate is meaningful; no theatrical gates
  • + Maps cleanly to the IT pack's milestone structure
Cons
  • − May be too heavy for very short programmes (<6 months)
  • − Stabilisation gate often skipped in practice; commit to running it
compressed_three_gate_model Compressed 3-gate model (Design exit / Cutover ready / Go-live)

Lean gate set for shorter or lower-risk programmes.

Pros
  • + Lower governance overhead
  • + Fewer gate-prep distractions for the programme team
Cons
  • − Fewer chances to catch drift
  • − Discovery and Build can blur into each other without explicit entry gates
wave_indexed_gate_model Wave-indexed gate model (gates duplicated per transition wave)

For multi-wave cutovers (e.g., country-by-country rollout), gates are run per wave rather than once per phase.

Pros
  • + Each wave gets its own gate discipline
  • + Risk is contained per wave
Cons
  • − Significantly higher governance overhead
  • − Risk of gate fatigue across many waves

Default approval chain

  1. Admin
  2. ExecutiveViewer

Linked evidence questions (4)

id prompt workstream
pmo.q.gate_definitions Which phase gates govern this transformation? For each, capture name, position in timeline, exit criteria, and approval chain. pmo.gate_management
pmo.q.gate_evidence_standards What standard of evidence is required to pass each gate? Define what 'evidence sufficient to approve' looks like (e.g., 'all P0 questions answered AND classified Reviewed'). pmo.gate_management
pmo.q.gate_approval_chain Who must approve each gate, and in what order? Capture the named approval chain per gate type. pmo.gate_management
pmo.q.conditional_gate_policy What is the policy on conditional gate approvals (Go with caveats)? When are they permissible, what evidence must be tracked, and what triggers a follow-up gate review? pmo.gate_management