Getting accurate data requires understanding the source of the data and the detail of how it is defined. The data may be correct but unless we have correctly defined the question to the correct level of detail it may not give us the accurate readout we need.
This is easiest explained using a few examples:
- An engineering team reports 99.9% product uptime. The head of customer services says there has been a big uptick in customers complaining of product instability. The explanation for the conflict was “99.9% uptime” referred to the engineering team’s software product – the company hosting the software was having a lot of problems which was causing the poor customer experience but this wasn’t included in the KPI definition.
- The customer support team reports 80% of customers are extremely happy. What’s missing is only 20% of customers are responding to the survey. We know that many customers only reply when they are either extremely happy or very unhappy and we are missing the point that 80% of customers are not engaged.
- The marketing team reports that the number of opportunities in the pipeline has grown by 50% in the last year. The hurdle for getting on the pipeline is to have a meeting with someone at the prospect. What’s missing is many of the meetings are with people unrelated to the opportunity and there is no indication that an opportunity actually exists.
- The sales team reports that on average they increase the value of a deal by 100% over the course of a sales cycle. What’s missing is many of the deals have no value entered in the system at the start of the sales cycle and in reality many deals that do have a value entered go down.
It is critical to understand the data and make sure it is accurate.
For more information on how we are helping companies to get where they want to go please visit