LeadSuite is the flagship product at LeadsOnline, a B2B SaaS platform used by law enforcement to work cases and surface insights. I led the redesign of the core person profile and case detail experience, turning an information-dense legacy interface into a structured, scalable investigative tool.
*This work involves sensitive law-enforcement investigations, so I can't share full details publicly. These visuals are representative of the live product, and I'm glad to walk through the complete case study and design decisions in conversation.*
The Challenge
LeadSuite was originally a quick reskin of a low-adoption legacy product, carrying over its structure with no rethink of investigative workflows or modern UX patterns. A UX audit before touching anything confirmed the full scope: a person profile with no structure, and a case detail view that made it hard to follow the thread of an investigation.
Design Question: How do you redesign a tool investigators rely on daily so the disruption makes them faster, not just more comfortable?
What We Were Up Against
Wall of noise
The person profile loaded every data point simultaneously with no visual hierarchy. Investigators had to scan the entire page to find what they needed, with no tabbed structure, no grouping, no clear entry point.
Hard to follow, harder to discover
The original timeline and map design required cumbersome dual-axis scrolling to navigate. Enough functionality was buried or unclear that investigators, including me during the audit, were missing it entirely.
Vague requirements
PM asks were directional, not defined. 'Make it easier to use' was the brief. I used the audit findings as a foundation, then facilitated team discussions to translate directional asks into specific, buildable decisions.
Person Profile
The redesign introduces a tabbed structure - Cases, Associates, Activity Log, and a new 'Deep Background' tab that consolidates public records, criminal history, and other investigative data sources into one view. Each tab gives investigators a direct path to what they need instead of forcing them to scan the entire page.
Case Detail
The case detail page is where investigators spend most of their time. I restructured it around a vertical navigation with distinct views: an overview with the case summary and map, a timeline and map view for spatial-temporal analysis, and an evidence tab. Each view serves a different mode of investigative thinking without cluttering the others.
Timeline + Map
I redesigned the timeline as a full-width horizontal view, synced to the map, so investigators get two representations of the same facts for two different ways of thinking through a case. Events scroll chronologically left to right, and selecting one highlights its location on the map below.
Leads
Leads is a net new feature, built in close collaboration with one of the developers. He brought the concept, and we workshopped it together until it became a focused workspace where investigators could track threads tied to a case, separate from the raw data views. It's designed to feel like a working surface, not a report.
What's Next
The redesign launched first to beta users, then expanded to a controlled subset of existing LeadsOnline customers, with a full rollout weeks away. Alongside the core redesign, two new features are in active design: a Dashboard surfacing personalized investigative activity and trend detection, and an AI-powered search. The vision for where these features lead is covered in Unifying an Investigative Platform.
Reflection
Real usage, real validation
Beta testers gravitated to the redesigned person profile first, and it became the most-used page within weeks of launch. That signal confirmed the tabbed structure was solving a real navigation problem, not just a visual one.
Scalable structure pays off
The tabbed model has already absorbed two new data source integrations without touching the core layout. Building for growth wasn't over-engineering, it was the right call given the product roadmap.
Ambiguity is a design surface
The vaguest asks often point to the most important problems. "Make it easier to use" turned into a full information architecture rethink.