top of page
Search

Are We Making the Most of Analytics?

Writer: Steve Hulmes
Steve Hulmes
Sep 17
6 min read


Why activity isn't the same as impact


Your analytics team is busy. Many of the teams I speak to are.


There are reports to produce, dashboards to maintain, requests to answer and stakeholders waiting for analysis. There always seem to be more questions coming in, and never quite enough hours in the day to answer all of them.


And, of course, when a team is busy, it's very tempting to think that it must be adding value.

But experience tells me, it’s not necessarily true.


In fact, I'd argue that one of the biggest challenges facing analytics teams isn't that they aren't doing enough. It's that we don't always know whether the work they're doing is actually making much difference.


Most analytics teams are pretty good at measuring activity. We know how many requests we've completed, how many reports we've produced, how many projects we've delivered and how quickly we've turned them around.


All of that is useful. But there’s a big difference between measuring what the team does and what the team achieves.


Take two pieces of analysis.


The first takes three days to produce. It's technically sophisticated, beautifully presented and answers exactly what the stakeholder asked for.


The stakeholder is delighted. They thank the analyst, take the report into their next meeting and then move on to something else.


Nothing changes.


The second takes an analyst half a day. It's a relatively simple piece of analysis that identifies an opportunity to change how the business allocates its sales resource.


It's not particularly complex. It probably isn't going to impress anyone at an analytics conference. But the recommendation is acted upon. The business changes its approach and sees a significant improvement as a result.


Which piece of analysis created more value?


I don't think that's a difficult question. But how many organisations could actually tell you the answer?


From analysis to impact


This is something I've been banging on about for a while, because I think there's an important distinction between analytical activity and analytical impact. 


There's a journey between the two:


Analysis → Insight → Decision → Action → Outcome → Impact


And the further along that journey we go, the less control the analyst has over the eventual impact.


An analyst can produce brilliant analysis but they don't control whether somebody understands it, believes it or acts on it. They can certainly influence this, but ultimately it’s the stakeholder who makes the final decision. They don't necessarily control whether the organisation has the resources to implement the recommendation and, very often, they don't have any involvement in measuring what happened afterwards.


So maybe it's unfair to judge an analytics team's value purely on the impact that eventually results from its work. But equally, I don't think we should ignore that impact altogether.

Because if virtually none of the analysis your team produces ever changes a decision, an action or an outcome, then I'd suggest there's a bigger question to ask. 


It’s not “How good is my analytics team?" but rather "How effectively am I using them?".


It starts before the analysis


The potential value of analytical work can be determined before the analyst has even opened a dataset.


Imagine a senior manager comes to an analyst and says:

"I need a report showing our customer retention rate by region."


The analyst produces exactly that. The numbers are right, the report looks good and it’s delivered on time. Job done.


Except perhaps it isn't. What if regional retention isn't actually the problem?


What if the organisation has a much broader issue with customer experience and regional retention is simply the question the manager happened to think of first?


A good analyst might stop and ask a few questions.

  • What are you actually trying to understand?

  • Why is this important?

  • What decision are you trying to make?


And perhaps the most important one:

  • What are you going to do differently depending on the answer?


Those questions could lead to a completely different piece of analysis and potentially a much more valuable one. This is why I think the role of an analyst is changing.


Organisations don't need analysts who are simply very good at answering questions.


They need analysts who are prepared to ask whether we're asking the right question in the first place.


That requires a different relationship between analytics and the rest of the business.


But should this all be down to the analyst?


There's a tendency, when we talk about improving analytics, to put the responsibility firmly on the analytics team. We tell analysts they need to improve their communication skills, become more commercially aware and build better relationships with stakeholders.


But, whilst these are required, I think we're sometimes asking the analysts to solve a problem that actually belongs to the organisation and should be shared with stakeholders.


If you treat your analytics team as an internal reporting service, we shouldn’t be surprised when they behave like one.


You give them a question. They give you an answer. Then you give them another question. And another.


Before long, you've got a highly capable team spending most of its time producing things that are perfectly good, but may not be particularly important. And then we wonder why the team feels overloaded.


But if organisations bring analysts into the conversation earlier and give them permission to challenge the brief, they can bring their judgement rather than simply their technical skills. Ask them to help frame the problem, rather than just solve it.


Now you're using the same people very differently - the capability hasn't necessarily changed but the way you're using that capability has.


And that's why I think analytical leaders need to look beyond the usual measures of team performance.


Things like utilisation, productivity and turnaround times matter, but if that's where the conversation ends, we're missing something pretty important.


We're measuring how efficiently the team is producing analysis without necessarily asking whether we're producing the right analysis.


So what about AI?


Obviously, I can't write an article about the future of analytics without mentioning But I'm not going to predict that AI will replace all analysts by 2028.


What I do think is becoming increasingly obvious is that AI is impacting on the technical side of analytics. Writing code, manipulating data, producing reports, building models and even generating insights are all things technology can increasingly help us do faster.


That's not a threat to analytics -  it's actually a huge opportunity.


Because if we can spend less time doing the mechanical stuff, we should have more time to do the things that really require human judgement:-

  • Understanding the business problem.

  • Asking the question behind the question.

  • Challenging assumptions.

  • Working out what matters and what doesn't.

  • Helping someone understand their choices.

  • Having the confidence to say, "I'm not sure that's the question we should be asking."

..and then helping the business decide what to do about it. That's a very different role from being the person who produces the report.


It's closer to being an adviser.


And, personally, that's where I think the real opportunity for analytics lies.


So, how valuable is your analytics team?


Maybe the question is not "How busy is my analytics team?" or  "How good are my analysts?".


Perhaps the question we should be asking is:

"How effectively are we using the analytical expertise we already have?"


Because there's a big difference between having analytical capability and getting the full value from it. And I think that's going to become increasingly important as we move towards 2027.


Some of the organisations I work with are already recognising this. I was talking to one of my clients recently who told me they were starting to recruit more graduates from social sciences and humanities than from technical science degrees into their analytics teams. 


Their thinking was that, as coding and statistical skills become less of a differentiator, they could teach those skills where necessary. What they really wanted were people with strong analytical thinking and contextual intelligence – people who could understand the organisational problem, rather than simply the data, and recognise where analytics could genuinely add value. 


Because ultimately, the value of an analytics team isn't measured by how much analysis it produces. It's measured by how much better the organisation is at making decisions because of it.


The analyst doesn't own the impact, but they do have a responsibility to maximise their influence over it.


 
 
 

Comments


bottom of page