Trigger
Advice without a risk policy
An external consultancy advises the ministry to introduce an AI verification assistant, framed as efficient and low-risk. No risk maps or safety frameworks are created.
Before
Trigger
An external consultancy advises the ministry to introduce an AI verification assistant, framed as efficient and low-risk. No risk maps or safety frameworks are created.
Process
The project is led for speed. AI risks are deprioritised, roles are unclear, and there is no escalation route.
Result
Older users feel confused and excluded and become more vulnerable to scams. The public sees the system as driven by hype.
Proposed
After (speculative)
Trigger
The consultancy and the ministry agree a governance-first approach, aligned with Verifiland's AI law and data protection.
Process
VTS leads development with risk mapping, human oversight and compliance checkpoints at every stage.
Result
Older citizens feel confident using the assistant. It is clear and transparent, and they feel taken seriously.
The before row is drawn out on purpose. The after row is deliberately hopeful.
There is no formal framework for non-technical or long-term risks.
Innovation developer. Interview insight, paraphrased
There is pressure to show impressive results, but no clear way to assess AI risks.
Innovation manager. Interview insight, paraphrased
Checklist aligned with the risk functions: Map · Measure · Manage · Govern
Signs a citizen is confused or at risk of scams.
Flags confusing AI answers from real calls.
Escalates the cases that are at risk.
Real examples to Lena, the UX/UI designer, and Amira, the product owner.
Plain language for uncertain states.
Rewrites it as “still being checked”, with a next step.
Tests the wording with an affected user.
Revised message.
Mapping statuses to allowed messages.
Blocks “ineligible” unless the status is final.
Adds tests for pending, missing and failed statuses.
Test results.
What a governance-first AI project needs before it starts.
Asks the advisers for a risk plan before agreeing the scope.
Names the reviewer and escalation route in the team agreement.
A signed-off agreement to the team and the ministry.