Clarity at scale
TLDR
Problem & Constraints
Navigating the reporting system required too many steps, too much context switching, and too much tribal knowledge about where anything lived. When something went wrong, the team had to dig instead of diagnose.
The issue wasn’t a lack of data, but a failure to surface the right signals at the right time, especially for the people doing the diagnosing.
On top of that, the solution needed to evolve into a client-facing product, so it had to be built with that future in mind.
Process & Key decisions
Dashboard
The goal was clarity at a glance, with depth one click away.
This is the entry point. It answers one question fast. Is this company healthy or not?
I combined security, device, and user data into a single view so teams don’t have to piece it together themselves. Key metrics like Defender status, exposure levels, update gaps, and device trends surface immediately.
From there, every data point is clickable. You can move from a high-level score straight into the exact devices or users causing the issue.
Device Exposure & Risk
This section is built for action.
Instead of listing issues, it prioritizes risk. High exposure devices and critical gaps surface first, with clear indicators of what’s wrong.
The insights panel calls out common failures like disabled firewalls or outdated signatures so teams don’t have to hunt for patterns.
A quick inventory view sits alongside it, giving immediate context. You can see the problem and the affected devices in the same moment.
Device Inventory
This is where teams go when they need detail.
I structured it to move from summary to identity. Start with overall stats, then narrow into specific users, devices, or applications.
Each identity view pulls everything into one place. Usage, authentication, group membership, and risk signals all live together.
No more switching tabs or tools just to understand one user.
Design System & Components
I built a lightweight design system based on Tailwind to keep the app consistent as it grows, including support for light and dark mode.
To manage complex, data-heavy interfaces, I focused on a flexible set of reusable components, including tables, filters, stat blocks, and detail panels, all built on shared logic and interaction patterns.
This made the experience more predictable for users, faster to build for the team, and created a scalable foundation for the future client-facing version without redesigning core pieces.
Final Experience
What came out the other side was a tool that actually fits how Summit works. You open it, you know where you are, you know what needs attention, and you know where to go next. There's no learning curve to fight and no moment where the interface makes you slow down to figure out what it's trying to say.
The navigation logic follows the natural arc of a support session: start with a health overview, drill into risk areas, get into specifics when you need them. The visual language stays consistent so context doesn't have to be rebuilt every time you move between sections.
When the second stage ships to clients, the foundation is already there. The design scales. The component system scales. The information architecture scales. This wasn't built to solve today's problem and be replaced in a year.
