What an AI adoption diagnostic actually examines

An AI adoption diagnostic is a focused review of the gap between the tools a business has and the value its people get from them. Its purpose is to help leaders make decisions, rather than produce another broad list of AI possibilities.

Tools and access

The starting point is an inventory: what the organisation pays for, who has access and what each tool is intended to support. Licence and usage records help identify questions worth investigating.

An apparently unused licence is a signal to examine, not an automatic saving. The person may have the wrong permissions, need occasional access or be waiting for a suitable workflow. Recommendations should reflect that context.

People and capability

A short assessment can explore confidence, task selection and checking outputs. Interviews add the detail: what people already do, where they struggle and what support would make a difference.

The resulting map should state which teams participated and where evidence is incomplete. It should not imply that a small interview sample proves how every employee works.

Workflows and requirements

Useful opportunities begin with actual work: repeated tasks, information handoffs, delays or quality problems. For each candidate workflow, clarify the inputs, output, owner and review requirements.

This also identifies where a process change or straightforward automation may be more appropriate than AI. Vendor-neutral advice includes the option not to buy another tool.

Usage and value

Usage data helps show where activity is concentrated. Conversations and task examples help explain why. Where possible, connect the evidence to a baseline of time, quality or another operational outcome.

If a reliable baseline does not exist, the diagnostic should say so and specify how to establish it. A precise-looking score should not hide missing evidence.

The decisions at the end

The output should distinguish what to keep, what to change, what to investigate and what to stop. A prioritised plan gives each action an owner and a reason for its place in the sequence.

In the Ornis three-week diagnostic, the intended deliverables are a findings report, team capability view, role-based tool recommendations, licence review, ranked opportunities, baseline scorecard and 90-day plan. Coverage is agreed before kickoff.

How to prepare

• Name a leadership sponsor and a practical point of contact.
• Gather licence records and whatever usage information is available.
• Agree the teams and roles to include in assessment and interviews.
• Confirm access permissions and how employee information will be handled.
• Bring the decisions you need to make, such as renewal, coaching or pilot priorities.

The three-week review is the starting point. Implementation and ongoing adoption support are separate choices once the evidence and priorities are clear.