In my writing about automated decisions, I became interested in what happens after a result appears. A status on a screen still needs to mean something to the person reading it.

If it is wrong, where can they correct it? What records will they need? Who will deal with the issue?

I would rather check those questions on a particular page than describe a whole system as “transparent” or “easy to use”. Can someone tell which action the result relates to, understand the explanation and find a way to raise a concern?

Following the user's next steps can reveal information that is missing from an otherwise complete-looking process.

Read the full essay ↗