Making a powerful tool usable.

The challenge

Helix Systems could ingest, transform, and query petabytes of event data faster than anything else in the category. Their engineers were proud of it, and rightly so. But the dashboard their customers actually used every day was a different story.

It had been built feature by feature over four years, each new capability bolted onto a layout that was never designed to hold them. By the time we arrived, a typical analytics view had 14 panels, three different date pickers that didn't agree with each other, and a settings drawer that required scrolling past the fold to find the save button. New customers churned inside their first two weeks, convinced the product couldn't do what the sales deck promised.

The irony was that it could do all of it, and more. The capability was there. The path to it was buried under accumulated complexity, and nobody on the team had the time or the mandate to dig it out. That's what we were hired to fix.

Our approach

We spent the first three weeks not touching the interface at all. Instead we sat with 19 customers across three segments — data engineers, product managers, and the executive viewers who only logged in once a week — and watched them work. What we found reshaped the entire project.

• Design for the question, not the data. Nobody opens an analytics tool to "look at data." They open it to answer a question. We rebuilt the dashboard around the six questions customers asked most, and made everything else reachable but not loud.
• Build a system before building screens. We created a 120-component design system — tokens, patterns, and documented reasoning — so the Helix team could ship consistently after we left.
• Make the powerful feel simple. Complex queries got a guided builder. Common ones got one-click presets. The defaults were tuned so a first-time user saw something useful within ninety seconds of signing in.
• Fix the date pickers. All three of them. There is now one.

For the first time, our customers are telling us the product is easy. We've never heard that word before.

A system that scales

The design system was the part that outlived the engagement. We built it in Figma with full documentation, then paired it with a React component library that mirrored it one-to-one. Every component had three things: the spec, the reasoning behind the decisions, and the edge cases it was designed to handle.

The dashboard itself became quieter. We removed more than we added — collapsing redundant controls, consolidating settings, and replacing the wall-of-panels default view with a single, configurable workspace that started simple and revealed complexity only when asked. The result was a product that felt lighter despite being, if anything, more capable than before.

Outcomes

The redesign shipped in stages over five months. Activation climbed, support tickets fell, and the churn curve bent in the right direction for the first time since launch.