Flanksource
Data dev dashboard redesign
Flanksource began as a Kubernetes consulting firm. Teams were drowning in data but lacked context. Mission Control was built to close that gap.
They had metrics dashboards, log tools, and Git for config, but nothing tying them together. Engineers needed one place to understand the health of their systems and act on it.
The Challenge
What we were up against
Engineers needed context, not more data. Existing tools created noise without signal.
Key components were siloed across separate views with no single entry point.
Actionable items were buried inside individual tools. Nothing surfaced by default.
Unfamiliar terminology required deep domain learning before any design could begin.
Brief
Dashboard redesign
Design a single dashboard that surfaces actionable insights and system health, consolidating five major platform components into one scannable view.
Five components to unify
01
Topology
System relationships and infrastructure map.
02
Playbooks
Runbooks for responding to incidents and alerts.
03
Catalogue
Service catalogue with metadata and ownership.
04
Health Checks
Real-time pass/fail state of services.
05
Notifications
Alerts and updates requiring attention.
Process
Domain immersion
Logged into the beta platform. Learned terminology and understood each component function before touching Figma.
Data visualisation exploration
Explored methods to communicate system health clearly, balancing density with scannability.
Ideate and wireframe
Translated component data into dashboard layouts. Mapped what surfaces by default vs. on demand.
Structural design
Produced final dashboard representations for review with the Flanksource product team.
Before and after
Before
After
Insights
Engineers needed context, not more data
Key components were siloed across separate views
Actionable items were buried in individual tools
Unfamiliar terminology required deep domain learning
Outcomes
Unified dashboard communicating key system health metrics
Consolidated five major components into one view
Improved operational visibility for engineering teams
Reflection
Domain immersion is non-negotiable for unfamiliar products
Data density requires strict visual hierarchy