Imagine learning how to run, but in ski boots. You can work hard and get better at it, but it may get so exhausting that you skip the marathon and go watch TV.
That’s what happens frequently in modern day organizations — we decide on building a strategy around real time marketing, but most of the time it just takes too much effort to manage proper adoption and the results don’t seem as revolutionary as we anticipated.
A big part of the solution is to realize that we don’t need a protein bar — we need to ditch the ski boots.
Companies are feeling the pressure to constantly evolve as their customers’ problems and expectations change. In the data- and process-driven world we work in, real time conversations with our customers through sophisticated software solutions set the golden standard.
But there's a problem. There are some real flaws in how we abstract and design this golden standard, and this creates gaps in the tools and processes we use to execute. The good news? These problems are fundamental, which means that fixing them will also have a very fundamental effect on results.
To bring things into context, while the model for real time marketing is much better and more sophisticated than it was a year ago, or five years ago, it still has flaws. A lot of the decisions we make are still based on assumptions and opinions — and we all know they are mighty difficult to argue about. Former CEO of Netscape, Jim Barksdale said it best: "If we have data, let’s look at data. If all we have are opinions, let’s go with mine."
Here are few of the key problems with some of these assumptions:
Assumption #1: The Funnel is Linear
You acquire customers by guiding their journey through a funnel, where you lose a few folks along the way, but some convert and move forward in a linear fashion.
The Problem: A linear system can never work in a finite space. Let’s assume you have a really high conversion rate — say 10 percent — of anyone who ever visits your website. That means you lose 90 percent. Let’s say you get 1000 visitors a day, and you lose 900. Now unless your consumer base is growing at rate of more than 10 times, you are eating off your market segment fast.
The good part of this picture is that it’s not what happens in the real world of business — folks do come back. There’s churn, there’s retention, there is word-of mouth, visitors use different devices, which makes them harder to track.
So if not a funnel, what exactly do we need as a figure? A cycle, a bow-tie perhaps? Only data science has a meaningful way of extracting structure from data points, but we may have to accept that the funnel is fundamentally not the best way to describe our customer’s journey.
The solution is to build a new customer journey model that takes all these considerations into account and is impacted by the questions you want answers to, without necessarily carrying over old-school concepts.
Assumption #2: Lead Scoring is the Best Way to Improve Velocity
This one is particularly fun to challenge. The theory behind lead scoring is that one way to increase the velocity of the funnel is to find that sweet spot, the moment when your prospects are likely to convert to the next step and before they go cold. Then you need to provide them with something shiny, something relevant or start a conversation. But in order to decide what this moment is and what will be relevant to them, we establish a framework of numbers — some calculation of that lead score.
There's a lot of statistical theory behind lead scoring, but the current established technique for it has major flaws. Chances are a bunch of people in the company argue for a few months about what gets scored and how, and then we assign those numbers to activities and visitors start accumulating some points, or gold stars or special dots (the measurement unit doesn't seem to matter). Then you decide on a number of points, stars or dots that deem the lead qualified, send some more emails and then it’s sales’ problem. This has the benefit of being both extremely inaccurate and subjective, as well as very demanding to maintain, because it doesn’t account for the dynamic nature of the dependencies that it is trying to measure.
- The Problem With Yammer? People Don't Use It
- Can You Name the Top 10 IoT Companies?
- Did Forrester Get Its Digital Experience Wave Right?
- A Man, a Blouse and an Awesome Customer Experience
- Microsoft Kicks Oracle's Big Data Butt
- SAP Jam's Approach to Social: It's All in the Work Patterns
- Facebook Thinks You'll 'Like' Enterprise Collaboration