Twenty questions across four dimensions — strategy, data, skills, governance. Not
to rate your organization on a scale. To find the three gaps that will block the
workflow you're piloting next, before it does.
Time
~30 min · one leader
Format
Runs in your browser. CSV or JSON export.
Requires
Nothing. Score "0" wherever you don't know.
You leave with
A profile and three named gaps
Not a maturity score
No levels. No badges. No certificate. No external benchmark. The output is a profile of what's documented, in use, and tested across four dimensions — and the three questions where you scored lowest, each with the specific page that fixes it.
The point is not to compare you to other organizations. It's to find the constraint you fix first — the one that will silently sink the workflow you pilot next if you don't.
The scale
Every question uses the same five-point scale. The specific wording under each question tells you what each level looks like for that question — a "4" on Strategy-1 is not the same as a "4" on Governance-3. The pattern is:
0Not yet. No answer to the question. Score 0 freely — "not yet" is a real and useful state.
1Aware. The question is on your list. There's no answer yet.
2Draft. An answer exists. It isn't documented or evidenced.
3In use. Documented, and referenced in at least one real decision.
4Tested. Documented, in use, and revised by experience.
1
Strategy
5 questions · max 20
Direction, portfolio, business case, decision rhythm. Strategy isn't the deck — it's
whether you've named the workflow, tied it to a metric the board tracks, and set a
decision on a date. Without these five, the pilot is a science project.
2
Data
5 questions · max 20
Workflow-level data mapping, access, quality, ownership. Data isn't a platform — it's
whether you can name every input — at start and mid-stage — and whether you can
reach it today. Most pilots stall here, not on the model.
3
Skills
5 questions · max 20
Operators, strategists, engineering capability, executive literacy, change capability.
Skills isn't a training program — it's whether a named person owns the workflow, a
named engineer can ship it, and a named executive understands the success metric.
4
Governance
5 questions · max 20
Review flow, tiering, autonomy guardrails, approver, evaluation cadence. Governance
isn't a committee — it's whether every workflow has a documented review, whether the
review is sized to risk, and whether someone named signs off before production.
Your profile
Four dimensions, each scored 0–20. This is not a maturity score — there is no benchmark,
no threshold that means "ready," and no comparison to other organizations. It's a
picture of what's documented, in use, and tested — so you can see the constraint you
fix first.
Strategy
0/ 20
Not started
0 of 5 answered
Data
0/ 20
Not started
0 of 5 answered
Skills
0/ 20
Not started
0 of 5 answered
Governance
0/ 20
Not started
0 of 5 answered
Overall
0/ 80
Answer questions above to see your profile build in real time. There is no pass threshold — the score exists to be seen, not judged.
Your three gaps
Each gap is a specific question where you scored lowest, and the page that addresses it. Fix these three before the next workflow — not after.
Answer at least 10 of the 20 questions to see your gaps. They update live, so you can watch them shift as you answer.
Where to go next
The assessment is the first tool in the chain. With three gaps named, the scorecard is what turns them into a workflow shortlist. The worksheet then turns one workflow into a plan.
No. There are no levels, no badges, no certificates, no external benchmark. It's a profile of four dimensions — strategy, data, skills, governance — each scored from 0 to 20, plus the three specific questions where you scored lowest.
The point is not to compare you to other organizations; it's to surface the constraint you fix first. A high overall score with one very low dimension is not "mostly ready" — it's a single constraint that will fail the pilot.
Where does my data go?
Nowhere. Every answer is saved to your browser's localStorage on this device so you can close the tab and return. Nothing is sent to a server. No email, no account, no cookie, no analytics event tied to your answers.
Use the CSV or JSON download to move the results to a team drive or attach them to a document. If you clear your browser data, the saved assessment is cleared with it — download before clearing.
How long does it take?
About 30 minutes for one leader answering from what they know. Some teams do it in a session with two or three people, which runs closer to 45 minutes — the calibration conversation is often the useful part.
Answer "0 · Not yet" generously if you genuinely don't know. The profile is honest either way.
What if I don't know the answer to a question?
Score it 0. "Not yet — this isn't answered" is a real state, and it's the most useful signal the assessment can produce. A profile full of zeros is not a failure; it's a clear starting point.
A profile of invented threes is worse than useless — it hides the gap you'll hit in week three of a pilot. The scale assumes honesty is the point.
Can my team take it separately and compare results?
Yes, and it's a useful exercise if the comparison is between perspectives, not between people. The four profiles often disagree — marketing sees data readiness one way, IT sees it another.
Reconcile to a single agreed score per question, and the disagreements themselves become the roadmap's first tasks. Download CSV and merge in a spreadsheet.
What do I do with the three gaps?
Each gap names a specific question you scored low on, and links to the hub page that addresses it. Fix the three gaps before you start the next workflow — not after.
The gaps are usually faster and cheaper to close than the pilot is to rescue once it stumbles on an unmapped input or a missing data owner.
Do I need to use all four dimensions?
No. Each dimension stands alone. But the whole assessment is 30 minutes and the interaction between dimensions is where the real signal is — you can have strong strategy and weak data and stall entirely, or strong data and weak governance and never reach production.
Score all four; the constraint is usually not the dimension you'd have guessed.
What's next after this?
The Use-Case Prioritization Scorecard — the second tool in the chain. The assessment tells you where you stand; the scorecard ranks the workflows you could pilot against value, feasibility, and risk.
Together they give you the shortlist the Pilot Plan Worksheet then turns into a plan.