As an analyst on Forrester's Customer Insight's team, I spend a lot of time counseling clients on best-practice customer data usage strategies. And if there's one thing I've learned, it's that there is no such thing as a 360-degree view of the customer.
Here's the cold, hard truth: you can't possibly expect to know your customer, no matter how much data you have, if all of that data 1) is about her transactions with YOU and you 2) is hoarded away from your partners. And this isn't just about customer data either -- it's about product data, operational data, and even cultural-environmental data. As our customers become more sophisticated and collaborative with each other ("perpetually connected"), so organizations must do the same. That means sharing data, creating collaborative insight, and becoming willing participants in open data marketplaces.
Now, why should you care? Isn't it kind of risky to share your hard-won data? And isn't the data you have enough to delight your customers today? Sure, it might be. But I'd put money on the fact that it won't be for long, because digital disruptors are out there shaking up the foundations of insight and analytics, customer experience, and process improvement in big ways. Let me give you a couple of examples:
BI professionals spend a significant portion of their time trying to instill the discipline of datadriven performance management into their business partners. However, isn’t there something wrong with teaching someone else to fly when you’re still learning to walk? Few BI pros have a way to measure their BI performance quantitatively (46% do not measure BI performance efficiencies and 55% do not measure effectiveness). Everyone collects statistics on the database and BI application server performance, and many conduct periodic surveys to gauge business users’ level of satisfaction. But how do you really know if you have a high-performing, widely used, popular BI environment? For example, you should know BI performance
Efficiency metrics such as number of times a report is used or a number of duplicate/similar reports, etc
Effectiveness metrics such as average number of clicks to find a report and clicks within a report to find an answer to a question and many others
Metric attributes/dimensions such as users, roles, departments, LOBs, regions and others