Guest Post: How much is enough when it comes to Voice of Customer?

jl1Jonathan Levitt has spent the last 5 years as a pioneer in the voice of customer analytics space. Through his speaking, writing, and evangelism, he was instrumental in legitimizing voice of customer analytics at a time when traditional web analytics still dominated the online business intelligence conversation. Jonathan has worked with world leading brands like Bank of America, Verizon, Dell, Procter & Gamble, Ford, and Reebok and has been featured in several industry publications including 1to1 Magazine, ClickZ, DM News, and MediaPost.

One of the best sources of business intelligence for companies of any size is raw Voice of Customer data.

This is particularly true for start-ups, where early, frequent, and consistent interaction with customers is critical to getting off the ground. The more customer-centric your decision making processes are from day one, the more likely you will get to the next stage in the development and maturation of your business plan.

This explains the recent growth in the selection of free and low cost Voice of Customer collection tools. User Voice, Kampyle, Survey.io, 4Q Survey (disclaimer: I helped conceive and build 4Q) — all of these are examples of popular Voice of Customer collection tools that can provide site owners with a pipeline of cheap and actionable visitor-sourced insights.

Once you put on the VoC practitioner’s hat, however, questions about respondent count size inevitably come up. Simply put, you need a way of knowing how much data is enough.

At what point can you act on the findings coming through your shiny new tools, with full confidence that you have collected a representative sample of your audience? If you’ve been running a User Voice customer feedback tool for 3 weeks and you’ve only collected 20 respondents, is that enough to act on? These are certainly agonizing questions for a data-centric marketer.

Now’s the time to start glancing over enviously at the big sites, because they don’t have this problem. The laws of probability are such that feedback from 500 respondents is usually enough to deliver reliable data at even the strictest confidence intervals. A big site like Dell.com can pull in 500 respondents within a day or two; at that clip, statistical significance comes through in a heartbeat.

But since your traffic generation muscle isn’t likely to match Dell.com’s anytime soon, I’ll let you in on a little secret: for small, startup websites that want immediate answers to their questions, the size of your sample almost doesn’t matter.

Here’s why. [Read More]

brilliant example of surveying users about a feature before it is built

lightbulb.jpgThere’s been alot of talk lately on the idea of prototyping and demonstrating a product to solicit feedback.  The catch?  The product isn’t actually built.  This goes hand in hand with the MVP concept practiced by lean startups.

I was on BackType today, and I just witnessed an awesome example of this concept in action.

BackType is a search engine that indexes millions of comments across social media platforms and lets you query for particular topics that interest you.  Cool, right?  I performed a search query for “analytics”, and the resulting page had a small tab called “Trends”.

Curious, I clicked on it and was brought to this page:

backtype feature launchDrat, it’s not released yet!

Brilliant!  BackType has given me an excuse to come back and check to see if the tab is active.  Even better – they were able to collect my expectations before the feature has even been released (or built!).

This is product management crowdsourcing at its finest.

Well done, team BackType.