01Fictional studyRelease queue
Relay
Problem
Release managers read a long, mixed queue to work out what is actually shippable. State is repeated in several places, filters reset on reload, and a blocked item looks much like a ready one at a glance. The cost is not a wrong click; it is the item nobody notices.
Approach
- One column of releases, ordered by the release window, with state written as text next to each version.
- State filters that stay visible, show how many releases each one holds, and announce the result count as it changes.
- Rows open in place, so owner and blocking reason sit next to the item instead of in a second screen.
- Full keyboard reach: filters are buttons, rows are buttons, and open state is announced.
Outcome
The queue became readable in one pass: what is ready, what is stuck and who owns it. Blocked work is described by its blocker rather than a colour, so the reason travels with the item.
No client, product data or performance figure is represented in this study.
Try it
Filters, row expansion and counts run in the browser with eight fictional releases. Nothing is sent anywhere.
8 releases shown
Sign-off complete. Waiting for the release window on Thursday.
Owner Ade