When I joined LimaCharlie, the product had been built feature by feature, by different engineers at different times, with no shared visual language and no consistent information hierarchy.

My first move was to map the entire product into a coherent information architecture: primary navigation, universal controls, and clear work areas, along with repeatable patterns across onboarding flows, action states, and data displays. To keep the work grounded and defensible, I built a board to track the relaunch and ran weekly sprint calls with the engineering team throughout. I worked directly with the VP of Engineering on scope and sequencing, and interviewed internal and external subject matter experts so design decisions held up under scrutiny, not just preference.

We split the rollout into three phases, each with its own success criteria. The first, a five month soft launch, focused on the most used features, the restructured IA, and a consistent visual system. The second carried that same system through the rest of the app. And the third introduced major new capabilities, including a search console and new dashboards. "Sexy data" is what our sales team took to calling these, since they helped them explain the product and engage with the data visually.