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.
Before
Trigger
Teams run focus groups and expect users to surface the risks. The model uses synthetic data. No risk framework, and edge cases stay open.
Process
The model performs poorly on real data. New iterations push the problems later.
Result
Older users receive confusing letters about changing procedures. Edge cases fall out, and exclusion and fraud risk grows.
Proposed
After (speculative)
Trigger
Developers and designers spend time with administrators and citizens, hold conversations and analyse edge cases.
Process
The ministry, VTS and older citizens co-develop risk mitigations with a risk-aware innovation toolkit.
Result
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.
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
Checklist aligned with the risk functions: Map · Measure · Manage · Govern
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.
What the agent must see.
Shows the date and tests if agents notice.
Checks the screen with an agent.
Test notes.
A suggestion needs its source.
Shows the version and tests a policy change.
Blocks a suggestion with no date.
Policy-change test.
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.