Let's Connect
enterprise ai readiness assessment

Enterprise AI Readiness Assessment

Find out what needs to change before you put AI into a workflow. Check the work, the information and the people around it, then leave with a practical next step.

Claude
Claude
ChatGPT
Gemini
M365 Copilot
GitHub Copilot
Public resources

Start with something you can inspect

Use the example and working files before deciding what help you need.

8
The worksheet covers the work, its sources and the people responsible.
3
A printable PDF, blank CSV and completed CSV example.
1
An invented support-team review you can inspect and adapt.
Ajaia

Before AI enters the workflow

1
A problem worth solvingWhat is slow, unreliable or expensive today? Observe the current task. Keep a few examples and record the effort, including review and rework.
2
Sources people can trustAre the instructions and records current and consistent? Check a few real source documents for conflicting instructions, missing dates and unclear ownership.
3
Clear information rulesWhich information can this workflow use? Check the rules for the chosen tool and task. Include access, sharing, retention and any sensitive records.
4
Access that worksCan the people doing the work use the required features? Try the intended steps with their accounts, permissions and files. A successful login is only the start.
5
A sensible place in the processWhat happens before and after the AI step? Walk through the handoffs, systems and exception cases. Identify any step that sends, changes or approves something.
The work

Find the obstacle before choosing the solution

A new tool can leave an old problem in place. Look at the current task, the sources and the handoffs before deciding whether the answer is AI, a simpler process or focused practice.

Check what is getting in the way
×
Conflicting or out-of-date instructions
×
Unresolved access or information questions
×
Answers that look plausible but need correction
×
No owner for changes after the test
The next action may be a source fix, an access decision or a clearer review step.
Invented support-team review
Example
Input
Review
8
Areas reviewed
Counts describe this example, not a readiness score.
Ready
2
Needs work
3
Unknown
3
Actions recorded
8
Owners suggested
8
Completion checks
8
Fix sources and review first
Then compare the work
A useful sequence

Turn a review into an action list

Work through one task from its starting material to the finished result. Record evidence, an owner and a completion check.

01
Choose one workflow
Name the input, expected result and person responsible. Keep an example of the current process.
02
Check the starting point
Read the sources, test access and agree what information may be used.
03
Inspect a result
Compare the answer with its sources and the usual work standard. Keep unanswered questions visible.
04
Assign the next action
Give each gap an owner, a concrete action and a way to check whether it is resolved.
05
Review before expanding
Compare similar work, including checking and corrections. Decide whether to continue, change the approach or stop.
What to check

One workflow. Eight useful checks.

Use the questions with people who do the work. The downloadable worksheet has room for evidence, actions, owners and completion checks.

Working material

Start with what you can observe

A problem worth solving: What is slow, unreliable or expensive today?
Sources people can trust: Are the instructions and records current and consistent?
Clear information rules: Which information can this workflow use?
Access that works: Can the people doing the work use the required features?
Use “Unknown” when you do not yet have evidence.
A sensible place in the process
What happens before and after the AI step? Start with a manual handoff where that is enough. Define and test any integration or automatic action separately.
A way to check the result
How will someone notice a plausible but wrong answer? Create a short review checklist and decide when the work needs a specialist or should stop.
People who can do the task
Can users explain the result and correct a mistake? Use focused practice for the gaps you observe. Fix access or source problems rather than teaching around them.
Someone to keep it working
Who owns changes, questions and the next review? Agree who updates the material, handles exceptions and decides whether to continue.
How to use it

Choose a next step that fits the gap

A completed worksheet records findings. It does not approve a production deployment.

01
Fix the source
Resolve conflicting instructions and check whether the corrected material solves the problem.
02
Resolve access and information questions
Ask the authorised owner to decide. Keep the first practice made up while that decision is open.
03
Try a small comparison
Compare the current process and a simpler template with an AI-assisted attempt. Include checking and rework.
04
Build or teach what is missing
A handoff may need engineering. A skill may need practice. Give the actual problem an owner.
05
Keep a review point
Check the evidence after the change and decide whether another team or task is ready to start.
Useful material

Read, download or discuss

Public samples are available without an email address. We agree any Ajaia engagement after a conversation.

Print the questions and keep a completed example beside your review.

What you can use
  • Eight areas to review
  • Evidence and open questions
  • Next actions
  • Responsible owners
  • Completion checks
  • A next decision
  • An invented worked example

Fill in one workflow with the people who do and review the work.

What you can use
  • Name the task
  • Describe a useful result
  • Mark what is unknown
  • Record evidence
  • Choose a next action
  • Assign an owner
  • Agree the review point

See how source, access, review and ownership questions lead to different actions.

What you can use
  • Conflicting guidance
  • Permitted information
  • Tool access
  • Human review
  • Practice needs
  • Source ownership
  • A decision before expansion
Worked example

Should this support team use AI for replies?

Invented example. The team, findings and actions below are made up. A support team searches help articles and rewrites similar answers. It wants AI to draft replies, with a person checking each one before sending. Three reviewers can use the approved workspace. Two help articles give different return instructions, and the team has not agreed whether real customer messages may be used.

Written example
The situation
Invented exampleReview the sourceKeep gaps visible
A support team searches help articles and rewrites similar answers. It wants AI to draft replies, with a person checking each one before sending. Three reviewers can use the approved workspace. Two help articles give different return instructions, and the team has not agreed whether real customer messages may be used.
Open the sample
Written example
The task and information rules
Invented exampleReview the sourceKeep gaps visible
A problem worth solving: The team expects faster replies but has not measured searching, drafting and checking. Next action: Time a few comparable replies using the current process, standard replies and AI-assisted drafts. Suggested owner: Support lead. Done when: The comparison includes review time, corrections and answer quality. Clear information rules: The team does not have an agreed answer about using real customer messages. Next action: Ask for a decision about the proposed information use. Keep the first comparison test made up. Suggested owner: Information owner. Done when: The decision and any limits are recorded for the team.
Open the sample
Written example
The sources and access
Invented exampleReview the sourceKeep gaps visible
Sources people can trust: Two help articles give different return instructions. Next action: Choose the current instruction and correct the conflicting article. Suggested owner: Help-content owner. Done when: Both articles point to the same approved instruction. Access that works: All three reviewers completed the intended drafting steps in the approved workspace. Next action: Recheck access if the test expands to more people or different features. Suggested owner: Tool administrator. Done when: Each new participant can complete the same steps.
Open the sample
Written example
The decision
Invented exampleReview the sourceKeep gaps visible
Fix the conflicting articles and create a shared reply checklist first. Then compare standard replies with AI-assisted drafts using made-up questions. Keep real customer messages out until the information owner has agreed their use.
Open the sample
Check the result

Keep the next action clear

These are worked examples and suggested checks, not measured customer outcomes.

Questions

Before you get in touch

Useful details about the sample, responsibilities and a possible engagement.

Can I use the worksheet without contacting Ajaia?
Yes. Download the blank CSV and PDF, then record the evidence, actions, owners and completion checks with your team. The completed example is public too. No email or meeting is required.
Should we assess the whole organisation at once?
Start with a workflow and the people who own it. An organisation-wide view can then compare the findings across workflows, teams and systems. One ready task does not establish that every proposed use is ready.
What if our main problem is poor data or a broken process?
Record that as the next piece of work. Clearer source material, a permission change, a standard reply or a redesigned handoff may help before training or an AI build. Compare the simpler option too.
Does a completed worksheet approve an AI deployment?
No. It records findings and next actions. The relevant owners still decide permissions, information use and deployment. It does not replace a security review or a specialist audit.
How should we measure whether AI helps?
Compare similar tasks using the current process and the proposed approach. Include checking, corrections, support and any new costs. Record the quality of the result as well as time spent, and keep estimates separate from observations.
What does Ajaia help with?
We can review the workflow with your team, investigate gaps and turn the findings into a prioritised plan. The follow-on may involve source cleanup, process design, tool setup, engineering or targeted practice. We agree the scope and deliverables after a conversation.
Can we start without sharing private records?
Yes. Explain the task with made-up or suitable public material first. Keep private records out of the inquiry form. Agree any later access and information-handling arrangements before sharing real work material.
Can we ask for customer references?
Customer references available upon request. Tell us what kind of workflow or project you want to hear about. We arrange references individually.
Related

Help with the next question

Choose the work you need to do next.

Learning plan
AI Upskilling Strategy
Decide what different roles need to practise and how the work will be checked.
Explore the page
Next step

Work through the next decision with Ajaia

Bring a short description of the task and the gaps you have found. We can help review the workflow and prioritise changes to sources, tools, process, engineering or practice.

Customer references available upon request. Agree the scope, facilitator, timing, support and price before delivery.
The work
Name the task
The tools
Check access
The people
Agree roles
The review
Keep an owner