The Best Analytics Project Had Nothing to Do With Data

Over two years. And counting.

That’s how long we’ve been working with one client. Not because the analytics were complicated. Because building capability takes time.

The project delivered a 45% productivity increase. But the analytics weren’t the differentiator. The relationship was.

What actually drove the results

When people ask about our methodology, they expect me to talk about data models. Algorithms. Visualisation techniques.

The truth is simpler and harder: we built trust before we built dashboards.

The first 90 days weren’t about analytics at all. They were about listening. Understanding how decisions actually got made. Learning the language people used when they talked about their business. Discovering the questions they were afraid to ask.

Only after that did we touch the data.

The three ingredients that mattered

Relationship-building came first. Before anyone would trust our analysis, they needed to trust us. That meant showing up consistently. Following through on small commitments. Being honest when we didn’t know something.

Debate was encouraged, not avoided. The best insights came from disagreement. When the commercial team pushed back on our analysis, we didn’t defend -we investigated. Often, they were right. Their market knowledge caught things our data couldn’t.

Kind communication made hard truths acceptable. We delivered uncomfortable findings regularly. “Your top performers are actually average.” “Your incentive scheme is driving the wrong behaviour.” “Your customer list is 30% wrong.” These conversations only worked because we’d built enough trust to have them.

The productivity gains were a side effect

45% productivity improvement sounds like a headline. It wasn’t the goal.

The goal was building a team that could identify and solve productivity problems on their own. The 45% was what happened when that capability emerged.

If we’d just delivered dashboards and recommendations, we might have hit 20%. The gap between “good analysis” and “changed behaviour” is where most analytics projects fail.

We closed that gap by being present. In the field. In the meetings. In the difficult conversations that determine whether insights become actions.

What this partnership taught me

Analytics projects fail for human reasons, not technical ones.

The data is usually fine. The visualisations are usually adequate. What’s missing is the trust that turns insight into action.

Building that trust takes longer than most projects allow. It requires patience that most consultants don’t have. It demands honesty that most relationships don’t survive.

But when it works, the results compound. A team that trusts the data makes better decisions daily. A team that knows how to question assumptions keeps improving after we leave.

That’s why we stay. And keep building.