A tired developer rests his head on his hand while working at a laptop.

← Back to overview

Last-Minute Changes, No Time for Risk

Ownership.

Illustrative

Before

Before

A team crowds a table and a board of notes, moving fast through a plan.
Photo: fauxels / Pexels

Trigger

Plan for simplicity

Under pressure, teams skip compliance, explainability and auditability.

Someone sits at a bright desk by a window, seen from the side.
Photo: Mizuno K / Pexels

Process

The unplanned

The ministry's complexity surfaces late. Every change ripples through, and administrators push the developers.

A tired developer rests his head on his hand while working at a laptop.
Photo: Andrea Piacquadio / Pexels

Result

Fragmentation

Developers face constant short-term changes. There is frustration and no room to discuss social risks.

Proposed

What the role paths change

After (speculative)

After

A small team stands around one laptop, checking in before the work moves on.
Photo: fauxels / Pexels

Trigger

Mixed standups

VTS runs mixed standups with developers, designers, compliance, social workers and policy analysts.

A small group sits with a facilitator, learning the change before it goes live.
Photo: Mikhail Nilov / Pexels

Process

Training and feedback loops

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.

Colleagues sit along a sunlit table, writing and listening without the rush.
Photo: Jason Goodman / Unsplash

Result

A shared pace

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.

From the interviews

  • 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

Where it goes wrong, and where the path steps in

Where it goes wrong, and where the path steps in Before After Strategy ✕ ✓ Amira · Product Owner Commission ✕ ✓ Amira · Product Owner Design ✕ ✓ Lena · UX/UI Designer Build ✕ ✓ Jannik · Developer Operate ✕ ✓ Sabine · Caseworker Citizen

Guardrails used

  • Stakeholder mapping
  • Context documentation
  • Acknowledging complexity rather than hiding it

Checklist aligned with the risk functions: Map · Measure · Manage · Govern

What each employee does

Sabine Krüger Caseworker

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.

Lena Richter UX/UI Designer

Where the employee waits.

Maps the wait and what they're told.

Checks the map with the receiving team.

Handoff map.

Jannik Voigt Developer

How a correction is found.

Logs corrections so similar cases are found.

Checks the log keeps the detail.

Correction log.

Amira Haddad Product Owner

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.