An older woman holds a stack of letters, trying to make sense of them.

← Back to overview

Innovation First, Risks Later

Knowledge.

Illustrative

Before

Before

A workshop group clusters sticky notes on the wall while testing an idea.
Photo: You X Ventures / Unsplash

Trigger

Innovation first

Teams run focus groups and expect users to surface the risks. The model uses synthetic data. No risk framework, and edge cases stay open.

Someone sits beside a laptop in a bright office, looking over the work.
Photo: Tima Miroshnichenko / Pexels

Process

Missed risk signals

The model performs poorly on real data. New iterations push the problems later.

An older woman holds a stack of letters, trying to make sense of them.
Photo: Karolina Grabowska / Pexels

Result

Confusion and risk

Older users receive confusing letters about changing procedures. Edge cases fall out, and exclusion and fraud risk grows.

Proposed

What the role paths change

After (speculative)

After

A younger woman leans in beside an older man, listening as he explains.
Photo: Kampus Production / Pexels

Trigger

Time with the people affected

Developers and designers spend time with administrators and citizens, hold conversations and analyse edge cases.

A small group works through a session together, one person leading from the front.
Photo: Mikhail Nilov / Pexels

Process

Risk-aware innovation

The ministry, VTS and older citizens co-develop risk mitigations with a risk-aware innovation toolkit.

An older woman smiles and nods while someone beside her explains.
Photo: Andrea Piacquadio / Pexels

Result

Trust and clarity

Older users report trust and clarity. They feel the system is respectful and fair.

The before row is drawn out on purpose. The after row is deliberately hopeful.

From the interviews

  • People think risk and impact analysis slows innovation down.

    UX researcher. Interview insight, paraphrased

  • Teams focus on technical risks that interface work can solve.

    UX/UI designer. 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 Design ✕ ✓ Lena · UX/UI Designer Build ✕ ✓ Jannik · Developer Operate ✕ ✓ Sabine · Caseworker Citizen ✕ ✓ Lena · UX/UI Designer

Guardrails used

  • Bias and fairness audits
  • Uncertainty checks
  • Scenario-based testing

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

What each employee does

Sabine Krüger Caseworker

How to log the cases where people get stuck.

Collects edge cases from her desk every week.

Reports patterns, not just single complaints.

An edge-case list to Jannik, the developer, and Lena, the UX/UI designer.

Lena Richter UX/UI Designer

What the agent must see.

Shows the date and tests if agents notice.

Checks the screen with an agent.

Test notes.

Jannik Voigt Developer

A suggestion needs its source.

Shows the version and tests a policy change.

Blocks a suggestion with no date.

Policy-change test.

Amira Haddad Product Owner

That testing on synthetic data hides real edge cases.

Plans a risk check as a release gate.

Holds the release until real cases are tested.

A release decision with its reasons.