The impact of experience versus data in decision-making

The impact of experience versus data in decision-making

As a data guy, I love nothing more than digging into the data to uncover insights – particularly when I uncover something which could lead to financial gains for the business I’m working with.

Sometimes the insights I’ve delivered have led to big decisions being made about marketing strategy and budget allocation. But sometimes they haven’t.

And honestly, it’s the inconsistency that bothers me most: in a single organisation, I’ll deliver one insight that leads to a decision being made, everything plays out like we’d hoped, and everyone’s high fiving. Then I’ll deliver a second insight to the same decision-makers, and, well nothing. No action is taken whatsoever.

So what’s the problem?

It’s clearly not an organisational issue – decisions have been made in these businesses previously. And it’s unlikely to be a trust issue – the people in the organisation trusted the data insights previously, but not this time.

Why is it that one insight landed and led to action, and the other was effectively ignored?

How decisions are actually made

In my experience, even in organisations which claim to be data or insight-led; many decisions are actually based more on what I’m going to call “experience” (a combination of actual historical experience, received wisdom, and gut feel), rather than data.

As such, I’m increasingly of the belief that when we’re delivering insights we need to acknowledge this, and frame our insights accordingly.

Before delivering our insights we need to ask ourselves: does this insight square with the experience of the decision-makers in the organisation?

If it does, we probably won’t encounter too many problems. But if our insight goes directly against the experience of the decision-makers in the organisation we’re going to need to work much harder in order to turn these insights into action.

To do this we need to understand the “experience” of the key decision-makers we’re working with, and tailor how we communicate with them. This is tough to explain in the abstract, so I’ll share an example:

Turning off “pseudo brand” paid search campaigns

For one of our apparel clients we uncovered a surprising insight – they were bidding on both “pure brand” terms, and a bunch of “pseudo brand” terms – and whilst the “pure brand” campaigns were performing well; the “pseudo brand” campaigns really weren’t.

For context, the “pure brand” campaigns were made up of terms which included their actual brand, and sub-brands, while the “pseudo brand” campaigns were made up of terms related to their historic brands and sub-brands.

On the basis of this insight, our recommendation was to turn off the “pseudo brand” paid search campaigns.

However, we recognised this was likely to be a tough sell, because this is the type of insight which goes directly against the experience of the decision-makers in the organisation. (And to be fair, if you were to ask me if turning off “pseudo brand” paid search campaigns was a good idea, generally, my gut reaction would be “nope, leave them on”).

As, a result when we delivered the insight, we included not just our recommendation, but a range of further evidence to support it:

  • We shared the performance of the pseudo brand campaigns
  • We shared the paid search competitor activity around these terms (no competitors were bidding)
  • We shared the organic rankings for these terms (our client was ranking well for the vast majority of these terms organically, and none of their competitors were)

Nevertheless, the client was still understandably nervous about turning off the pseudo brand campaigns. They didn’t give us a hard no; but instead asked: “How do we mitigate the risks here?”

And it’s a fair question, right? Our recommendation to turn off these campaigns is based on the assumption that people searching for those terms will click on our client’s organic listings instead; AND that their competitors won’t start either bidding or ranking organically for these terms.

We responded by putting a range of reporting in place so we were able to monitor both our client and their competitors’ organic rankings, their competitors’ paid search activity, and the activity of site visitors coming through these terms via organic search.

We suggested a short-term test; and the client agreed. (Oh, and it worked out great.)

But I think the key learning for me here was how we framed this insight. We didn’t just share the paid search performance data and expect that would be enough to enable our client to make a decision – we shared broader insights around the paid and organic search landscape for these terms; and put systems in place to enable them to mitigate the risks.

I think if we’d failed to do this, our client would still be bidding on these terms today.

Final thoughts

The next time you deliver an insight, take the time to consider the extent to which it aligns with the experience of the decision-makers you’re presenting to, and frame it accordingly.

If the insight squares with their experience, it’s likely to be an easier sell.

If it doesn’t, you’ll need to work harder to give the decision-makers the confidence to take action. That might mean providing further analysis of the broader landscape, and/or putting new systems in place to mitigate any risks.

Personally, I really like this approach because it forces me to go beyond data, and think about what I need to provide in order to help the people who are making the decisions. After all, our job is not just to generate insights, it’s to allow people to take action.



More articles →

Interested?

Get in touch and find out how Ringside could help take your brand’s marketing to the next level.