
“It’s the Search, Stupid” is a twist on an old campaign slogan that applies to customer reference program success. If you’re old enough, you may recall a famous quip from a political advisor in 1992 concerning what he thought should be a presidential campaign messaging priority.
“It’s the economy, stupid.”
There were plenty of concerns and priorities back then, as there always have been, but at the end of the day, if voters didn’t feel the economy was working for them, they wouldn’t care about anything else—a sort of voter Maslow’s Hierarchy of Needs. Sometimes the priority is that straightforward and simplistic.
Similarly, many factors make a customer reference program tick or not. Our customer success team has a checklist full of best practices related to program promotion, user training, executive support, cross-functional coordination, member recruiting, and more. Yet even when all these “pistons” are firing, the stakeholder’s experience comes down to one simple thing: Can they find the reference(s) they need? It doesn’t matter whether you’re a salesperson, a PR manager, event coordinator, or executive; if the search doesn’t result in what you need, the rest doesn’t matter much.
Reading this observation, it seems pretty obvious, right? But how does that translate into how a reference database is built and maintained? It is not unusual for program managers to put out a request for customer reference candidates then gratefully accept whatever comes back in the “net.” Unfortunately, this thinking does not result in a well-built database. Imagine 100 new customers come into the database. If the primary demand is for director-level, IT references in banking and insurance using products A and B together, and only four of those 100 additions match the need, what was the value of the recruiting effort? If these 100 new customer references are touted as a major success, then, with great expectations, users go to do their first search and can’t find what they need, the program gets a black eye. Users return to their old, inefficient way of finding references: Slack, Chatter, Teams, email, etc.
This is no small misfire. Consider the consequences:
So how do you avoid such a setback?
To answer these questions, we recommend having a formal or informal advisory board for your program. Members will tell you what they need. For instance, marketing stakeholders will have calendars for press releases, events, and analyst calls. It’s good to know of any deadlines involving advocates and as far in advance as necessary. Your advisors will also ensure you understand how they need to search. If they don’t have the means to filter as needed, the data may as well not exist. For more on advisory boards, see this post.
Once you have this information, you’re ready to start recruiting, which is an art and science unto itself. The exact methods and channels used will vary based on the needs you’ve uncovered. For instance, if you found that VP and CxOs are a priority, then you’ll likely find that your company’s executives, not salespeople or CSMs, are in the best position to act as recruiters to at least initiate the conversations. For more on recruiting best practices, check out this post. Completing the described exercise helps ensure that your colleagues’ time is well-spent and produces many, many successful reference searches building confidence in the program and stakeholder support that keeps on giving in a virtuous cycle.