We’ve been fortunate to consult with organizations whose communities we would define as runaway successes (Facebook, SAP, Oracle etc…). One major difference between these companies and those communities that are ‘doing ok’, is the former’s incredible commitment to constant improvement. The runaway successes are constantly benchmarking, testing, and refining what they do. The organizations that aren’t doing so well will ask questions like “What should I measure?” or “What are some good benchmarks for [x]?” In this post, I’m going to explain how we approach community measurement with these kinds of clients and some of the processes we put in place. Remember, this is the final week you can sign up for our strategic community management course. We won’t be running this course again for a while, so I hope you can join us. The Measurement Fallacy Almost everyone we’ve worked with is measuring something. But when we ask what they do with those measurements, the answers are either really vague “well, it tells us what’s working or not working” or redundant “I send them to my boss and colleagues” Our clients (and course participants) will have an answer like: “If the number of useful tips created by our top experts rises by 10% as expected next month, we’ll spend more time building relationships with the insider group and less time on our newsletters. If it rises by less than 10%, we’ll try pushing the leaderboard system as the core tactic instead” This is the difference between having something you measure for fun and actually having a system to drive ongoing improvement. You should only measure the things you want to improve. If you don’t know what to do with the data, why waste time collecting it? If you don’t know what will happen if a metric rises or falls, why measure it at all? The Interpreting Problem But interpreting data is a huge problem, even if you have benchmarks, to begin with. Let’s imagine your goal is to increase customer satisfaction. You randomly survey a large group of active members each quarter and track results. You discover that customer satisfaction has stayed the same in the last three months. What would you do differently with this data? Actually, take a second and think about it…. Some of you might conclude that the community isn’t working and may need to be scrapped. But what if customer satisfaction fell everywhere else except in the community? That could be a game-changing win. You can’t make any decent analysis unless you have the right context. This means working on four levels; execution, tactics, strategy, and objectives. Analyzing The Four Levels For Context If customer satisfaction scores aren’t rising, is community the wrong approach? Or is it because you had the wrong objectives, strategy, and tactics? Let’s imagine one of your objectives to increase customer satisfaction is to get more experts sharing product tips. Your strategy might be to build a sense of competition among them to generate the best tips (jealousy). One tactic to fulfill that strategy is to build a leaderboard of those that share the best tips ranking everyone with an expert badge. But if customer satisfaction scores aren’t rising, did you have the wrong objective, strategy, or tactics? Or perhaps the tactics were just badly executed? We tackle this by using a framework with four levels. At each level, you are constantly learning and refining what you do. It’s a campaign of hard work, but it helps turn a static community into a runaway success. LEVEL 1: Was The Tactic Well Executed? It’s impossible to know if you had the wrong objective, strategy, or tactic until you know if the tactic was well executed. This means three things:
- Did it reach a large percentage of the target audience?
- Did it significantly change the behavior of the audience it did reach?
- Did that behavior change last for a long time?