Trigger
Plan for simplicity
Under pressure, teams skip compliance, explainability and auditability.
Before
Trigger
Under pressure, teams skip compliance, explainability and auditability.
Process
The ministry's complexity surfaces late. Every change ripples through, and administrators push the developers.
Result
Developers face constant short-term changes. There is frustration and no room to discuss social risks.
Proposed
After (speculative)
Trigger
VTS runs mixed standups with developers, designers, compliance, social workers and policy analysts.
Process
The ministry builds AI risk mitigation into its work through training and feedback loops.
The MA's own after scenario points to training and feedback loops. Role paths make that concrete.
Result
The product team works at a steady, risk-aware pace, with a shared understanding of the work.
The before row is drawn out on purpose. The after row is deliberately hopeful.
The system is so complex that any change creates errors.
IT administrator. Interview insight, paraphrased
A small change often becomes a total rebuild.
Production developer. Interview insight, paraphrased
Checklist aligned with the risk functions: Map · Measure · Manage · Govern
What each upcoming change means for citizens.
Brings the cases a change might break to the standup.
Confirms her support script is updated before the change goes live.
The effect on citizens, to Lena, the UX/UI designer, and Amira, the product owner.
Where the employee waits.
Maps the wait and what they're told.
Checks the map with the receiving team.
Handoff map.
How a correction is found.
Logs corrections so similar cases are found.
Checks the log keeps the detail.
Correction log.
How to spot when a small change carries a big risk.
Runs a short weekly standup for the whole team on complexity.
Pauses changes until their impact has been mapped.
Change notes to the team and the ministry.