System context and decision constraints
Create a one-page map of a customer journey, data and trust boundaries, dependencies, owners, constraints, unknowns, and decision rights. A system diagram is useful only when it changes a safe decision.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Safe promotion and high-blast-radius change
Write a risk-tiered promotion plan with immutable identity, environment differences, named authority, abort criteria, rollback or forward-recovery boundary, and stakeholder cadence.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Reliability investment decisions
Rank reliability work with customer impact, burn rate, capacity, cost, toil, uncertainty, and a named risk owner. Error-budget information informs a bounded decision; it is not an automatic freeze.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Control evidence and recoverable security
Classify controls as preventive or detective, define staged enforcement and a time-bound exception, and require auditable emergency access. A control that blocks recovery without a reviewed escape route is incomplete.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Migration and lifecycle governance
Lead a cohort migration with an explicit source of truth, write authority, invariant checks, abort criteria, support communication, and decommission evidence. Do not promise rollback where a forward recovery is required.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Recovery evidence and exercise governance
Translate RTO and RPO claims into a measured exercise scorecard. A backup or secondary region is a capability hypothesis until detection, authorization, capacity, routing, and reconciliation evidence are recorded.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Architecture decisions and alignment
Facilitate a time-boxed decision that names the owner, options, assumptions, dissent, guardrails, exception route, review trigger, and exit path.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.
Technical leadership and escalation
Delegate investigation, communicate uncertainty, and leave durable ownership and coaching artifacts. Escalate when data integrity, regulatory exposure, missing authority, or a breached abort threshold exceeds the approved boundary.
- •Start with an observable fact, then state what it does and does not establish.
- •Use a bounded, read-only exercise before recommending an authorized, reversible action.
- •Record the owner, decision boundary, and next update or escalation condition.