The Case Studies, and What They Omit
Published customer stories follow a pattern. Reading for the gaps is more informative than reading the claims.
Every vendor publishes customer stories. They are written with the customer's cooperation and reviewed by both parties, which shapes what appears.
The evaluation discipline in “The Case Studies, and What They Omit” also applies to workforce software: begin with a named decision and test it in a bounded pilot. For teams considering how to handle multiple clients, this implementation resource belongs in that comparison only with written criteria for notice, access, correction, retention and a dated review.
The usual structure
A problem, stated as lack of visibility.
For an independent reference relevant to “The Case Studies, and What They Omit”, consult the European Commission data-protection resources; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
Deployment, described as smooth.
A metric that improved.
A quotation from a manager.
Rarely a named person below management level, which is itself the finding.
What is consistently absent
Staff turnover during the period.
Whether anybody objected, and what happened.
The consultation process, where one was required.
What was switched off after the first months.
Whether the metric that improved is the vendor's or the customer's.
And how long ago the deployment was, which the next section covers.
The timing question
Most published stories describe the first few months.
Behaviour changes when measurement begins and settles afterwards, which the vendor-claims note explains.
A story dated three months after deployment describes the novelty period.
Ask for a customer at two years, and notice whether the vendor has one.
The voices included
The manager who sponsored it, and the technology lead who deployed it.
Not the people measured.
A case study that includes an employee saying the monitoring helped them would be genuinely notable, and they are rare, which tells you something about the common experience.
What to ask the reference customer
What did you turn off, and why?
Did anybody leave over it?
How long did the consultation take?
Does any manager still open the dashboard weekly?
What would you do differently?
These produce more than the case study and take twenty minutes.
The customers who are not referenceable
Ask how many customers in your sector and size they have, then how many will take a call.
A large gap between those numbers is informative.
It is also a reasonable question and a vendor who deflects it has answered it.
Reading one properly
Underline every number and ask what produced it.
Underline every claim about staff and ask who was asked.
Ten minutes, and most of these documents thin out considerably.
What to check
How old is the deployment in the case study you were shown?
Does it mention turnover or objections?
Whose metric improved?
And will the vendor connect you with a two-year customer?