Command Center
Our own studio operating system: the ops dashboard we run on daily, and the console design system behind it.
Project Command Center
Discipline Web Development
Year 2026
Detail 01 Illustrative map.
Detail 02 Illustrative flow.
Detail 03 Illustrative scores.
Detail 04 Illustrative audit.
Running the studio day to day meant checking messages, tasks, tickets, and the memory behind our own AI systems across a handful of separate services, one login at a time, just to know where anything actually stood. None of those services were built to talk to each other, so the work of piecing together a real picture of company-wide status fell on whoever needed it, every time.
What we built
We built Command Center as our own internal ops surface: one glanceable view of company-wide project status that pulls all of that together without logging into each service on its own. Rather than design one fixed dashboard and stop there, we treated the dashboard itself as a design problem, the same way we'd treat a client's. We built a pipeline, nord-console, that fans a design system out through research, iteration, evaluation, and review, generating real variations of individual components rather than one guess at each. That pipeline produced 275 distinct options across 55 components, and we assembled the version of Command Center we run today from that library, not from a single first draft.
Where it stands
We run Command Center's ops surface daily. It is the tool that tells us where the studio's work actually stands, without a round of logging into separate services first. The nord-console pipeline behind it stands on its own as proof of a design and development process we can point to: a reusable component library built to assemble custom dashboards from, whether the dashboard is ours or a client's.
Role: Build, Operate