What Is an AI Readiness Assessment?

For a small firm, an AI readiness assessment is a go, limit, or stop decision about one named workflow, not a generic maturity score. Inspect the accountable owner, input and data access, decision boundary, acceptance artifact, evaluation set, permissions, escalation path, monitoring, and recovery plan. Record each item as present, partial, or missing. If the evidence supports a test, choose one bounded pilot. Write its acceptance test and stop condition before work starts.

This operator definition is Jungle Roots' editorial method. Formal risk work remains a separate task. NIST says its AI Risk Management Framework is voluntary and is intended to help organizations incorporate trustworthiness considerations into AI design, development, use, and evaluation (NIST AI RMF). Microsoft and HBS publish their own readiness dimensions; neither establishes a universal score (Microsoft; HBS Online).

The official sources cited on this page were checked on October 16, 2026.

How do you conduct an AI readiness assessment?

Conduct an AI readiness assessment by tracing one named workflow from its start event to its accepted result, then deciding whether the evidence supports a bounded pilot. Use this compact sequence:

1. Name the workflow, its start event, expected output, and accountable owner.
2. Locate the evidence for approved inputs, source access, allowed actions, acceptance, evaluation, permissions, escalation, monitoring, and recovery.
3. Mark each evidence item present, partial, or missing; record its location and any material gap.
4. Resolve which decisions stay human and which actions the workflow may never take.
5. Define an acceptance test from representative inputs and expected results.
6. Write the stop condition and the safe recovery path.
7. Decide to run one bounded pilot, keep the workflow limited, or stop.

The output is an inspectable decision record, not a company-wide percentage. Reassess when a material input, permission, action, model, provider, or acceptance condition changes.

What is the editorial verdict on AI readiness scores?

My editorial verdict is that a readiness percentage hides the evidence an operator needs. This is my opinion, not the result of a portfolio experiment, and no portfolio experiment is claimed. A percentage can compress unlike gaps into one neat figure. An operator still needs to know whether the workflow has permission to read the source, who may approve an action, and what happens when the output fails.

Microsoft's wizard illustrates why a score must be read in context. Microsoft says its tool is based on its research and customer work, identifies five drivers of AI value, and asks ten questions before suggesting an area of focus (Microsoft). That is Microsoft's model. HBS uses another frame: strategic intent, data and technology foundations, people and culture, and governance and risk management (HBS Online).

Editorial call: Keep any vendor score as that vendor's summary. Keep the evidence packet as the operating record your team can inspect.

Can a questionnaire or AI assessment tool determine readiness?

A vendor or tool questionnaire can organize evidence, but it cannot make the operating decisions that establish readiness for a specific workflow. It can prompt discussion, group answers, expose omissions, or apply the vendor's model. It cannot choose the accountable workflow owner, verify that approved sources are actually accessible, approve a decision boundary, or certify safety or compliance.

Use a questionnaire as an intake aid. Preserve its questions, answers, model, date, and any generated score. Then verify the underlying artifacts with the people who own the workflow and its risks. Do not turn a vendor result into a universal benchmark, and do not select a “best AI tool” before the workflow, evidence gaps, permissions, acceptance test, and stop condition are known.

Microsoft's readiness wizard is one documented example of a vendor model, not a universal certification (Microsoft). Qualified legal, privacy, security, and domain reviewers must decide which additional reviews the use case requires.

How do you measure AI readiness?

Measure readiness by checking inspectable evidence against one workflow, not by asking whether the organization feels ready. Name the workflow in plain language, such as “draft a proposal from approved source documents.” Name the person accountable for its result. Then ask to see the artifacts that define inputs, allowed actions, expected outputs, tests, access, and failure handling.

Use present only when a reviewer can open the artifact or observe the control. Use partial when the evidence exists but leaves a material question unanswered. Use missing when the team relies on memory or intent. These labels are Jungle Roots' editorial scoring method, not NIST ratings.

NIST's Playbook offers suggested actions across Govern, Map, Measure, and Manage and says the suggestions are not a checklist (NIST AI RMF Playbook). The packet below borrows that inspectable, action-oriented posture. It does not claim NIST endorsement or a product guarantee.

Measurement rule: A spoken assurance is context. A named, reviewable artifact is evidence.

What are the three pillars of AI readiness?

There is no universal set of three AI readiness pillars in the authorized sources (Microsoft; HBS Online). If a team needs a compact working model, Jungle Roots proposes workflow value, operating evidence, and responsible control. Those are editorial buckets, not a standard.

Workflow value asks which business decision or output the workflow serves and who owns it. Operating evidence covers data access, inputs, the decision boundary, the acceptance artifact, and the evaluation set. Responsible control covers permissions, escalation, monitoring, and stop or recovery.

Microsoft's wizard names business strategy, technology and data strategy, AI strategy and experience, organization and culture, and AI governance & security as its drivers (Microsoft). HBS asks leaders to audit strategic intent, data and technology foundations, people and culture, and governance and risk management (HBS Online).

Pillar warning: Attribute a pillar count to its source. Do not present an editorial grouping as a law, benchmark, or consensus.

What evidence belongs in the readiness scorecard?

The scorecard should show the artifact, the question it resolves, and the status a reviewer can verify. The rows below are Jungle Roots' editorial evidence scorecard. They are not a NIST, Microsoft, HBS, or OECD scoring system.

The decision boundary should agree with permissions. The acceptance artifact should agree with the evaluation set. Escalation should agree with the stop and recovery record. If these pairs conflict, mark the item partial and record the conflict instead of averaging it away.

Get the operations audit for an operator review of the evidence packet before a tool purchase or agent build.

How do you assess a client's AI readiness?

Assess a client's AI readiness by asking for evidence about one named workflow and handing back a decision record the client can inspect and own. Do not infer readiness from interviews alone, and do not imply that an editorial method is a client experiment.

The consultant handback should contain:

• Named workflow: the exact start, end, expected result, and accountable owner.
• Evidence locations: links or references to the artifacts reviewed, without copying restricted material into the report.
• Status: present, partial, or missing for every scorecard item.
• Material gaps: the unanswered facts that could change the decision.
• Owner: the person responsible for resolving each gap or accepting the residual decision.
• Allowed next step: run one bounded pilot, keep a stated limit, gather more evidence, or stop.
• Acceptance test: representative inputs, expected results, reviewer, and pass condition.
• Stop condition: the event or result that prevents further action and triggers recovery.
• Unresolved review needs: any legal, privacy, security, procurement, accessibility, or domain review still required from qualified people.

End the engagement by confirming who maintains the record and which material changes reopen it. The consultant can structure and challenge the evidence; the client remains responsible for naming owners, granting access, approving decisions, and obtaining the reviews its use case requires.

What are common AI assessment questions?

Good assessment questions ask for a decision or artifact, not a hopeful yes or no. Use the scorecard while asking:

• What named workflow are we assessing, and who is accountable for its completed result?
• Which approved inputs and data sources may it access?
• Which decisions may it make, draft, or recommend, and which decisions are prohibited?
• What artifact proves acceptance, and who signs it off?
• Which evaluation cases represent normal work, edge cases, and unacceptable output?
• Which identity and permission does each action use?
• Where does an exception go, and what context travels with it?
• What record lets the owner inspect runs, errors, and system changes?
• Which condition stops the workflow, and how does the operator recover safely?

These are Jungle Roots' proposed questions. NIST's Playbook can be used as a separate source of voluntary risk-management actions across its four functions (NIST AI RMF Playbook). A business process automation brief can hold the workflow boundary and acceptance evidence.

How do you turn the assessment into one bounded pilot?

Turn the assessment into one bounded pilot only when the owner can inspect the evidence and enforce the stop condition. Use this sequence:

1. Name the workflow, start event, expected output, and accountable owner.
2. Collect the artifacts for data access, allowed decisions, acceptance, evaluation, permissions, escalation, monitoring, and recovery.
3. Mark each scorecard row present, partial, or missing and record the evidence location.
4. Define the pilot's acceptance test from the evaluation set.
5. Write the condition that stops the pilot or keeps it from taking an affected action.
6. Record the decision to proceed, keep the workflow limited, or stop.

The final decision is local to the organization and use case. This editorial scorecard does not issue a certification or guarantee safety or business value. NIST describes its RMF as voluntary; its page says the framework is meant to improve how trustworthiness considerations are incorporated (NIST AI RMF).

Use the AI governance framework to place this workflow record inside the organization's roles and policies.

Which responsible-AI principles belong beside the scorecard?

Readiness evidence does not prove that the OECD's responsible-AI principles have been met (OECD AI Principles). The OECD's values-based AI principles include human rights and democratic values, fairness and privacy, transparency and explainability, robustness, security and safety, and accountability (OECD AI Principles). Use those principles to challenge the workflow's purpose and controls. Do not treat a completed scorecard as proof that every principle has been met.

NIST supplies a voluntary risk-management framework and Playbook actions (NIST AI RMF; NIST AI RMF Playbook). OECD publishes principles for trustworthy AI (OECD AI Principles). These sources do not provide a product evaluation for the selected workflow (NIST AI RMF; OECD AI Principles).

Boundary: Use the evidence packet to expose missing operating facts. Use qualified legal, security, privacy, and domain review where the workflow requires it.

Which readiness decision should a small operator make next?

Choose the next decision for the named workflow: run the bounded pilot, keep the workflow limited, or stop. Resolve any missing evidence that can change that decision before comparing tools. If ownership is missing, name the accountable person. If the decision boundary is vague, write allowed and prohibited actions. If the evaluation set has no expected results, define them with the people who can judge the work. If recovery is unknown, keep the workflow from taking the affected action.

This is an editorial recommendation, not a claim that one sequence produces a particular return. Preserve the dated packet, the decision, the unresolved gaps, and the owners. Reopen it when a material input, permission, action, model, provider, or acceptance condition changes. That is a change trigger, not an unsupported calendar rule.

Get the operations audit to turn one proposed workflow into an inspectable operating brief.

What are the frequently asked questions?