Contents
Most transformation reports are too green. Not because anyone lies, but because at every level people honestly report what is allowed to be reported. A Reality Scan doesn't measure reports — it measures lived experience. This framework shows how to do that without alienating the organisation.
Why this matters
The reality gap between the official status report and lived experience is the single most common reason transformations arrive late, over budget, and off target. A Reality Scan makes that gap visible — as a manageable variable, not an accusation.
The four layers
- Understand: has the target picture landed with people — concretely enough to act on it?
- Can: do people have the skills, tools, and conditions to execute?
- Want: does motivation hold? Where does it flip into cynicism or quiet quitting?
- Allowed: do the real incentives, processes, and leadership patterns permit the new behaviour — or punish it?
Seven steps to a defensible Reality Scan
- Make the target picture explicit. Without a concrete target, execution can't be measured. One sentence, three behaviour examples, no adjectives.
- Operationalise the four layers. For Understand, Can, Want, Allowed, formulate two to three experience-based questions each — no ratings.
- Sample across hierarchy and site. Not representativeness but contrast: leadership, middle, operational; HQ, plant, region.
- Design an experience-based guide. 'Tell me about a situation in which …' instead of 'How do you rate …?'
- Cluster patterns. From 60 to 120 conversations, five to eight patterns per layer typically emerge.
- Name the reality gap. The report shows where status reporting and lived experience diverge — with verbatims, not colour codes.
- Make it a cadence. One scan per quarter or half-year makes movement visible. One-off scans are photos, not films.
Pitfalls
- Rating questions instead of experience questions. Ask for grades and you get reports, not reality.
- Sample too small per layer. Below three conversations per contrast, the pattern is missing.
- Anonymity claimed but not ensured. Re-identification via combined attributes is the most common trust breach.
- Reality gap framed as blame. The framework is for steering, not accusing.
Frequently asked questions
How does the Reality Scan differ from a pulse survey?
A pulse survey measures mood in numbers. A Reality Scan measures experience in language — and therefore delivers cause, not symptom.
How often should you scan?
For ongoing transformations, quarterly. For single programs, at minimum before launch, after 90 days, and after 180 days.
Who should own the Reality Scan?
Not the program itself. An independent owner (insight team, external partner) makes sure the results aren't polished against expectations.
