Blog / Operations

Operations
July 22, 2026 · 5 min read · Nexus Team

What a device page should show a technician at 4pm on a Friday

The device detail page is the screen a technician has open more than any other, and it is almost never opened casually. It gets opened because something is wrong, somebody is waiting, and the person opening it needs to establish what is true about one machine as fast as possible.

Design for that moment and a few things stop being matters of taste.

Unknown has to look like unknown

The failure we cared most about is a health indicator that renders green because no data arrived. A machine that has not checked in is not healthy — it is unobserved, and those are opposite conditions that a lot of dashboards render identically because green is the default and absence is not handled.

So unknown states render as unknown. It is a less satisfying screen and a more useful one: a technician who sees "we have not heard from this device" investigates connectivity, while one who sees green investigates everything except the actual problem.

A dashboard that cannot distinguish healthy from unmonitored is not reporting health. It is reporting the absence of bad news.

Nothing disappears in a redesign

The second rule was that no existing device action could quietly vanish. Redesigns are where capabilities go missing — not deliberately, but because a rebuild starts from what the new layout accommodates rather than from what the old screen could do. Then a technician goes looking for the thing they used last month and it is gone, with no announcement, because nobody registered its removal as a change.

The full system inventory came back in the same pass, in a more compact form: printers, graphics, memory modules, lifecycle, connectivity, running processes, startup items, and browser extensions — the dense grids tucked behind a disclosure rather than deleted for looking cluttered.

Built out of parts

The rebuild produced reusable presentation components rather than another bespoke page, which is the difference between fixing one screen and improving the next five. It is also the least visible thing in the release and the one most likely to matter in six months.

Follow the build as it ships.

Nexus is live in our own MSP operations and opening to a limited design-partner cohort. Join the private-preview list.