Design guidance is mostly written for interfaces people visit. Operational software is inhabited. When someone spends their working day inside a screen, generous whitespace becomes scrolling, and a friendly illustration becomes noise.
Density is a feature
The right question is not "does this look clean" but "how many decisions can someone make without scrolling". Comfortable spacing that halves the rows on screen has a real cost measured in navigation.
Reserve colour for state
In a dense interface, colour is the fastest signal available — which means spending it on decoration wastes the only channel that scans instantly. Keep the surface near-monochrome and let colour mean something: overdue, flagged, blocked.
And never let colour carry meaning alone. Shape, position and label carry it too, for accessibility and for the person on a badly calibrated monitor.
One table primitive
Most operational software is tables wearing different hats. Building one table component that handles sorting, filtering, column sets, saved views and keyboard navigation — then using it everywhere — cuts both design surface and code, and gives users one interaction model to learn.
- Keyboard navigation on high-volume screens, always.
- Saved views instead of re-applying filters daily.
- Explicit empty states that suggest the nearest match.
We wrote this because we had to solve it. See what we built or tell us what you're working on.