Products

Relay

It already ranked the work. It never said why.

Role
Designer and engineer
Years
2026
Team
Solo, public case study
Status
Public case study
4014106440 + 14 + 10 = 64

In one paragraph

The dashboard sorted orders by urgency, but people couldn’t see why one task beat another, so they second guessed it. I made the score readable, and gave managers exceptions instead of surveillance.

Before. Red is people’s model; the grid is the system.

The distance

The system ranked every item. It never said why. People couldn’t predict the next task, so they didn’t trust it.

The working

One hero task, with its reason in plain words and a score you can open: “Time 40 + Orders 14 + Impact 10 = 64”. Four tiers. A real finish line, so a shift can end with “done”.

Wire mode zeroes all colour to prove the ranking holds without it. Press 0 on this site to try the same idea here.

Receipts

  • Zero axe violations, Lighthouse 95 or higher, copy at grade 8 or lower, all as build gates.Receipt0 axe violationsRelay quality gateMethodBuild fails on any axe violation, Lighthouse below 95, or copy above grade 8.SourceFoundey Relay case studyChecked
  • 283 unit tests, 304 end to end tests and 48 visual baselines.Receipt283 unit, 304 end to end, 48 visualRelay test suiteMethodCounted from the project’s test runs.SourceFoundey Relay case studyChecked

Keyboard shortcuts

Single keys never fire while you type in a field.

?
Open or close this sheet
W
Show the working on case files
R
Switch plain and institutional wording
N
Night edition on or off
0
Wire mode: zero all colour
[
Previous case file or entry
]
Next case file or entry
Esc
Close any sheet or popover
Motion