AI readiness and maturity assessment
Understand which prerequisites constrain a credible AI initiative
Leaders need to choose between a pilot and foundation work. The decision is how to understand which prerequisites constrain a credible AI initiative. The work begins with your actual workflow and looks for the evidence that separates intended behaviour from a consequential exception. It is particularly relevant to technology sponsors and business readiness owners. A useful outcome is an explicit account of what was examined, what remains uncertain, and which decision the evidence can support.
The operating choices relationship
- Data access
Establish the basis for data and access.
- Operating ownership
Confirm who can run and accept the work.
- Readiness profile
Retain the scoped finding and its unresolved dependencies.
Decision
Frame the decision around data and access
Questions and the evidence they need
- Data and access
- Inspect data access for the relevant constraint or observation.
- Operating ownership
- Inspect process stability for the relevant constraint or observation.
- Control evidence
- Inspect skills for the relevant constraint or observation.
The decision is how to understand which prerequisites constrain a credible AI initiative. This is relevant to technology sponsors and business readiness owners when leaders need to choose between a pilot and foundation work. Name the affected workflow, the consequence of a wrong decision, and the owner who can act on the result. The initial discussion should establish which evidence is already available and which uncertainty is material enough to investigate.
The specific failure hypothesis is that a maturity score looks strong while a critical dependency such as permitted data access is missing. It remains a hypothesis until examined in the deployment. Existing internal tests or operating records may already resolve it; identify the uncovered question before commissioning additional work.
Mechanism
Readiness is specific to the proposed workflow
Relationships within operating choices
- Data and access
- Check whether the intended task can use representative inputs.
- Operating ownership
- Confirm who can run and accept the work.
- Control evidence
- Expose blockers hidden by an average maturity rating.
What this specialty examines
Readiness assessment should focus on the intended workflow’s prerequisites. Evidence might cover process stability, permitted data, skills, ownership and controls. A broad maturity dimension is useful context, but a missing critical input can block a specific initiative despite strengths elsewhere.
The review should assess evidence by dimension and identify blockers for the specific intended workflow. Identify the normal route, relevant exceptions and the authoritative record of the outcome. Inspect the relevant business-system record, enforcement event or process evidence alongside any reported status. Keep incomplete cases visible, with an explanation of what their absence prevents the owner from concluding.
The tradeoff to make explicit
For this decision, broad assessments reveal patterns while workflow-specific blockers determine the next practical step. Compare the available design or operating choices against the same intended outcome. If one option removes a required control or changes the task boundary, describe that difference before treating its apparent simplicity, speed or lower effort as an improvement. The decision should expose the tradeoff instead of burying it in an aggregate score.
Preparation
Connect the working inputs to the boundary being examined
Evidence packet for data and access
Illustrative working format
- Data access
- Establish permitted access, provenance, and which task conditions it represents.
- Process stability
- Check its relationship to the relevant workflow and expose missing context.
- Skills
- Identify the accountable role and verify its decision rights or availability.
- Ownership
- Identify the accountable role and verify its decision rights or availability.
Start with data access, process stability, skills, ownership and current control evidence. Identify the owner, revision and operating context of each source. Sanitised examples may support initial design, but differences from actual conditions should remain explicit. Where direct access is unsuitable, a customer-controlled evidence or execution route may be considered, with agreed handling and retention.
The scope also needs the business sponsor, agreed expectations for a representative business hypothesis, and the authority to inspect the relevant boundary. Specify what evidence would distinguish the failure in which a maturity score looks strong while a critical dependency such as permitted data access is missing from acceptable behaviour. If stakeholders disagree about intended behaviour, resolve the interpretation before classifying the observed difference as a defect.
How the work proceeds
Carry data and access through to an accountable finding
From the scoped material to a decision record
- Data access
Establish the existing process and its constraints.
- Operating ownership
Apply the scoped check to control evidence.
- Readiness profile
Record the evidence, open dependencies, and the owner’s next decision.
Establish the problem and comparison baseline
Bring data access, process stability, skills, ownership and current control evidence into a working session with technology sponsors and business readiness owners. Separate observed process conditions from stakeholder preferences and future estimates. Describe the current approach and at least one credible alternative, including simpler process improvement where relevant. The preparation output is a comparison brief with the unresolved assumptions, accountable owner and observations that would justify advancing or rejecting the proposed option.
Examine options and challenge assumptions
Separate demonstrated readiness from plans and purchased tools. Describe dependencies and the proof needed to resolve each gap. The next recommendation may be a small foundation task rather than a broad pilot or another maturity exercise.
Choose the next bounded commitment
Develop a readiness profile with dependency gaps and a proposed next investment from the examined alternatives. Distinguish immediate dependencies from questions that a bounded experiment can answer, and name who owns the operating or benefit measure. Recommend an advance, hold, revise or stop decision with a specific next observation. Any later expansion should depend on the agreed learning result and available capacity, rather than the completion of planning activities alone.
Indicative artefact
Make the readiness profile usable by its owner
Readiness profile
Illustrative working format
- Readiness profile
- Identify the assessed workflow, revision, and decision boundary.
- Dependency gaps
- Name the missing evidence, responsible owner, and condition for revisiting the decision.
- Next investment
- Name the unresolved condition, next action, and accountable owner.
A useful decision artefact is a readiness profile with dependency gaps and a proposed next investment. Supporting material may include selected cases, configuration or process records, evidence references, a disagreement log and prioritised actions. Retain the case selection rationale and material disagreements alongside the result; otherwise the result may be mistaken for complete coverage.
Illustrative scenario
Examine control evidence through a constructed exception
A constructed case and its decision paths
Illustrative scenario
- Data and access
An enthusiastic sponsor has neither approved data nor an accountable release owner.
- Operating ownership
Check access, environment, and release ownership for one intended workflow.
- Control evidence
Hold the dependent pilot until its concrete prerequisites exist.
Consider a fictional situation: a department has trained staff and tooling but cannot access the source records needed for its chosen use case. The scenario is illustrative, with no client engagement, executed test or measured improvement implied.
For unavailable source records, establish whether an approved access route exists. Synthetic data may support learning but not every business conclusion. The sponsor should understand which parts can proceed and which claims remain unsupported until representative evidence is available.
Scope and next action
Keep the conclusion within the stated business hypothesis
Confirm fit before the next commitment
- Data and access
- This review is limited to the stated business hypothesis.
- Data access
- The relevant owner must confirm access and the intended operating conditions.
- Readiness profile
- Commitment depends on the sponsor’s evidence review.
A strategy or business-case model is decision support. It does not establish demand, guarantee financial returns, commit staffing or authorise organisational changes. Any engagement depends on an agreed scope, qualified team, authorised access and confirmed availability. Bring the affected workflow, its current configuration or process, the triggering change and the evidence already available. The immediate scope question is prompted by the situation in which leaders need to choose between a pilot and foundation work; confirm which missing observation would change the owner’s next action.
Ways to engage
Related engagement scopes
AI Readiness Assessment
Find what must change before an agent belongs in your workflow. Review the data, ownership, controls and operational dependencies together.
AI Agentic Vendor Selection
Choose against your workflow requirements. Compare agent platforms through agreed scenarios, integration constraints and operating responsibilities.
AI Transformation Sprint
Move from an interesting use case to a deliberate adoption decision. Connect workflow value, organisational readiness and the changes needed to take the next step.
Continue exploring
Related insights and resources
Choose the work before the agent
Compare agentic work with simpler alternatives, expose the dependencies behind a promising demonstration, and fund a bounded experiment with a clear decision at its end.
Measure the work that improves
Connect agent activity to accepted business outcomes, establish a credible comparison, and distinguish useful capacity from realized financial value before deciding whether to scale.
Before the pilot: five questions for agent readiness
A compelling demo leaves important questions open. Use a five-dimension rubric to examine the data, authority, evidence, ownership and people behind your next agent initiative.