Situation
Two markets entered a high-incident stabilisation period without consistent reporting, prioritisation or ownership.
A repeatable cadence was necessary to bring transparency to stakeholders.
My scope
Andrew owned or led
- •Cadence design and director-level reporting
- •Market-side prioritisation and incident triage
Partner or external ownership
- •Engineering incident remediation and hotfixes
- •Production release deployment gate
Decisions & execution
Decision 01
Established daily incident-status cadences and director-level change reporting during post-migration stabilisation
Why it mattered
Provided visibility and ownership when post-migration reporting was inconsistent.
Key Execution Actions
- Co-ordinated the resolution of 26+ production incidents.
- Chaired daily incident cadences across vendor and IT teams.
Outcome & attribution
Outcome & System Change
A repeatable governance rhythm covered 26+ identified incidents, multiple changes and formal RCAs.
Individual Contribution & Boundary
Established daily status cadences, managed triage for 26+ incidents, and delivered director-level change reporting.