The Bit Laboratory

0

Skip to content
03Analytics Software2024

Project Vantage

A reporting tool that became a product, rebuilt from strategy through launch.

Project Vantage, Analytics Software

Sector

Analytics Software

Engagement

Strategy to launch

Scope

Design and engineering

Year

2024

Context

01

Reports nobody trusted twice

The existing product produced a great deal of output and very little confidence. Numbers disagreed between screens, queries took long enough that people exported instead, and the roadmap had become a queue of one-off charts requested by the loudest customers.

Rebuilding the interface alone would have preserved the underlying problem: there was no agreed definition of the metrics the whole product depended on.

Approach

02

Define the metrics, then the screens

We ran a definition phase that produced a semantic layer, a documented set of core metrics, and the three workflows that had to feel effortless on day one. Everything outside those three was explicitly scheduled for later.

That boundary is the reason the build stayed calm. Late requests became visible decisions rather than silent additions.

Craft

03

Speed as a feature

Latency reads as complexity in dense tools, so performance was scoped as product work: pre-aggregation, honest loading states, and filtering that responds instantly rather than eventually.

The visual language stays quiet and typographic, letting the data carry the emphasis. Density is tuned per screen based on how often it is used rather than applied uniformly.

In practice

Two seconds of latency reads as complexity. Performance was a design decision before it was an engineering one.

Outcome

One definition

Shared semantic layer for core metrics

Instant filtering

Performance scoped as product work

Focused v1

Three workflows taken all the way

What we did

  • Product Strategy
  • Product Design
  • Full-Stack Development
  • Data Architecture

Next step

Have something like this in mind?