Operator's console
worth buildingLinear · Vercel · Sentry
The closest thing here to the actual product. It arrived at pipeline stages down the centre, a run history rail on the right, and a discrepancy table underneath — which is very nearly the information architecture I would have argued for. It even wrote “Running every 15 minutes” unprompted.
Against it — It is also the safest and most familiar choice. Nobody will remember it.
Trading terminal
worth buildingBloomberg at 3am
Density as the entire aesthetic: six-pixel sparklines, a live settlement feed crawling the bottom, exception rows with owners and ages. For a technical round this reads as “built by someone who works with money” rather than “built by someone who works with dashboards”.
Against it — Green phosphor is a strong flavour, and a monospace wall is genuinely harder to read for anyone not already fluent in it.
Engineering blueprint
worth buildingTechnical schematic · drawing title block
This one draws the pipeline as an annotated machine — seven source systems on the left, ingestion, normalisation, matching, reconciliation, control totals — with a revision-numbered title block in the corner. It explains the architecture and shows the numbers in the same image.
Against it — It is a diagram, not a dashboard. Wonderful as one screen; hard to sustain across three.
Brutalist control panel
worth buildingWim Crouwel · exposed grid
REVENUE set edge to edge, then everything else in a hard monospace beneath it, with a single red figure for the contested total. Total confidence, zero decoration. The contested number being the only coloured thing on the screen is exactly the right emphasis.
Against it — Loud. It will divide a room, which may be the point.
Editorial infographic
worth buildingThe Economist
Annotated charts with hand-placed callouts explaining what happened in which month, small multiples along the bottom, a genuine source line. This is the only direction that treats the numbers as something to be *narrated* rather than merely displayed.
Against it — The annotations would have to be generated, and a wrong auto-annotation is worse than none.
Swiss annual report
workableMüller-Brockmann
One enormous set number, a flat vermilion bar per clinic, hairline rules, and a great deal of confident white space. Reads as printed documentation of a business rather than as software.
Against it — Sparse to the point of thin — one screen's worth of information stretched across a whole screen.
Museum label
workableGallery wall · subtraction
A single colossal serif number, one line of caption, and three whispered figures in the far corner. As the closing shot of a demo — the number, alone, after fifteen minutes of terminal — it would land hard.
Against it — It is a poster, not a tool. Viable only as one view among three, never as the whole dashboard.
Mission control wallboard
flawed renderFlight control
The wallboard inside the photograph is a real direction: five pipeline stages as illuminated chevrons with one lit amber, huge glanceable numbers, readable across a room.
Against it — It rendered a photograph of a control room with people in it rather than a screen. Useful as mood; the actual design is only about a third of the frame.
Paper ledger
flawed renderBound accounting book
Beautiful object — ruled columns, a red CONTESTED stamp at an angle, blue-pencil marginalia reading “reconcile to GL 4450”. The stamp is a genuinely good idea worth stealing for the exception register.
Against it — It is a photograph of a book, not an interface. Skeuomorphic paper is also a hard sell as a working tool.
Luminous fintech
cannot useStripe
I named Stripe as a reference and the model returned Stripe’s own dashboard — their wordmark, their navigation, their colour, their deferred-revenue chart.
Against it — Not a direction we can take. Building this would be copying a specific company’s product, and their mark is on it. Shown for completeness, not as an option.