The situation
High-visibility state platforms carry a specific kind of risk: every outage, security gap, or usability failure lands on real people waiting for benefits — and then in the press. This modernization had three hard fronts running at once: security remediation that couldn't wait, operational transformation that couldn't disrupt service, and UX improvement on workflows residents already found difficult. Work was moving, but without an operating rhythm connecting the fronts, nobody could say with confidence what was on track, what was slipping, and who owned the slippage.
What I did
As Agile delivery lead, the first job was the one the Sapper Method calls stabilize: stand up the governance cadence the program had been missing. Not more meetings — a weekly operating rhythm where reporting told the truth, risks had named owners, and decisions got made instead of deferred. From there, delivery discipline across a 20-person distributed team.
- Stood up the missing governance cadence — weekly executive reporting built from the system of record, risk burn-down with named owners, and escalation paths that got used.
- Led Agile delivery across security remediation, operational transformation, and UX improvement simultaneously — three workstreams with different clocks, one view of program truth.
- Managed a 20-person distributed team, fully remote, with the delivery standards and cadence discipline to keep three fronts moving without trading one off against another.
The outcome
The clearest signal a government client can send about delivery: the engagement expanded into a multi-year commitment. State agencies don't extend programs that aren't working — they extend the ones where the operating rhythm produces visible, defensible progress quarter after quarter.