SEE IT
The first element of the Capability Method — and the first thing any engagement actually delivers.
You cannot steer or keep something you haven’t first seen honestly. Most organisations “see” a capability by asking the person closest to it how it’s going. SEE IT replaces that impression with a number, read directly off the record itself.
What It Actually Is: the Readiness Score
A 0–100 score, scored on the record itself — not sampled after something breaks downstream, not inferred from a survey. Every point deducted names the exact field responsible, so no one is asked to fix a score they can’t explain.
How the Score Is Built
- A control set, agreed not imposed. The domain’s readiness dimensions are weighted together with the client, not handed down as a fixed template.
- Critical controls cap the score. One critical failure caps it outright; two or more cap it lower. A missing compliance check can’t be averaged away by everything else scoring well.
- Bands turn the score into a work list, not a report. Ready · Acceptable · At risk · Critical — every record below Ready comes with the specific controls that failed and a named owner for the fix.
The Same Pattern, Any Domain
The anatomy doesn’t change from domain to domain — only what’s being scored does. The same Readiness Score structure has been designed for master data domains including Customer, Material, Vendor, Finance, HR/Workforce, Asset, Supply Chain, Project, Quality & Compliance, Governance & Enterprise Structure, and AI/Analytics/KPI — each with its own readiness dimensions and its own critical controls, built on one shared design.
What You Receive
- A score design for your domain — the control set, weighted and banded, agreed with you before anything is scored
- A scored baseline across a real sample of your own records, not a hypothetical one
- A work list: the named controls that failed and an owner for the fix, for every record below Ready
The Proof
SEE IT was checked, not just written down: scored across 165 capabilities in 11 domains. The Readiness Score is not expected to look the same everywhere — eleven domains produce eleven different profiles. It isn’t expected to be constant. It’s expected to be honest.
Where This Starts
SEE IT is where the Business Case’s Baseline gets its evidence. Every benefit line’s Confidence Level — Confirmed, Estimated or Directional — is only as good as what backs it, and a scored Readiness baseline is exactly that kind of evidence: a real number read off the record, not an impression. It’s also one of the things worth re-checking at Harvest — did the underlying readiness actually improve, not just the benefit figure on paper.
Measured, Executed, Proven
A Readiness Score is a baseline, not a one-off reading. Data-Driven Leadership is where that number is followed forward — checked monthly against real progress, not scored once and left. The Governance Heatmap is where it sits alongside every other domain’s score, so no Readiness Score is ever read in isolation.
Related: Business Case · Inside the Method · Home
