A person stands at a service counter, seen from behind.

← Back to overview

The Case That Doesn't Fit

Process.

Illustrative

Before

Before

Empty chairs line a quiet public waiting room.
Photo: Renee B / Pexels

Trigger

Doesn't want to apply online

A citizen doesn't want to apply online and asks a caseworker about her documents.

A caseworker sits side-on at a desk, working at a screen.
Photo: Tima Miroshnichenko / Pexels

Process

No workaround

The AI assistant loads, then doesn't understand. There is no workaround.

A person stands at a service counter, seen from behind.
Photo: Christiann Koepke / Unsplash

Result

Policy before the person

The case no longer fits the system. Policy comes before the person.

Proposed

What the role paths change

After (speculative)

After

A caseworker at the desk turns to greet the person who has come to the counter.
Photo: FAKHRUL HASSAN / Pexels

Trigger

The same question

The same question comes in.

A hand writes notes on a clipboard, a phone on the table beside it.
Photo: Alex Green / Pexels

Process

Override and escalate

Sabine, the caseworker, overrides the assistant, records why and escalates the case.

Two people shake hands in an office, closing the case.
Photo: Cytonn Photography / Unsplash

Result

A person answers

The citizen gets an answer from a person, and the pattern goes back into the shared library.

There is no MA after scenario for this case. This after row is a proposal.

From the interviews

  • Caseworkers are close to both the data and the citizen, but have little say in how AI is designed.

    MA research note. MA research note

Where it goes wrong, and where the path steps in

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

Guardrails used

  • Human override
  • Structured override reasons
  • Escalation route

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

What each employee does

Sabine Krüger Caseworker

When and how to override the assistant.

Overrides the answer, records why and calls the citizen.

Escalates the case through the agreed route.

Override reasons to Jannik, the developer, and Amira, the product owner.

Lena Richter UX/UI Designer

Stopping as easy as approving.

Designs override as easy as approve.

Tests it with admin staff.

Override screen.

Jannik Voigt Developer

What an override event records.

Captures overrides as a learning signal.

Checks the event records why.

Override log.

Amira Haddad Product Owner

How to read the override log for patterns.

Reviews overrides regularly with the team.

Makes a working override a release criterion.

Fixes, back into the shared library.