Are you ready for AI? A 15-point self-check
Score yourself across three areas — team, tools and habits — and walk away with a concrete gap list before you adopt AI at work.
Most teams do not fail at AI because the technology is weak. They fail because nobody checked the basics first: a usable tool, a shared rule for what data may be used, and people who actually repeat the new behavior. This manual checklist takes about 15 minutes. Go through all 15 items, mark each one Yes (1 point) or No (0 points), then total your score out of 15.
Team readiness — five items
- We have a written, shared rule for which company data may (and may not) go into AI tools.
- At least one person on the team owns AI experiments and can answer teammates' questions.
- We have explicit permission to use a specific AI tool — we are not guessing with shadow IT.
- We review AI output for accuracy before it reaches a customer, candidate or manager.
- We agree on what a good AI-assisted draft looks like, so quality does not slip.
Tool readiness — five items
- We have one approved chat-style AI tool that runs in a normal browser.
- It handles our working language (English or Chinese) at production quality, not toy quality.
- We know how to paste long documents into it and how to export the result cleanly.
- We have a second tool for a specific job, such as meeting notes or spreadsheet cleanup.
- Access works on our regular work devices without an IT ticket every time.
Habit readiness — five items
- We use AI at least 3 days per week, not as a one-off experiment.
- We keep a running note of which prompts actually save us time.
- Each week we spend 10 minutes comparing a human draft with an AI draft.
- We fact-check numbers, names and quotes before anything AI wrote leaves our desk.
- We protect a 30-minute weekly slot to share tricks with teammates.
How to read your score
| Score out of 15 | What it means | Your next move |
|---|---|---|
| 0–5 | Early stage. Tool access may exist, but the habit does not. | Pick one repetitive task (e.g. drafting routine emails) and repeat it with AI daily for two weeks. |
| 6–10 | Workable setup. You use AI sometimes; the gaps are predictable. | Close your biggest No item — usually the written data rule or the team owner. |
| 11–15 | Ready to scale. The basics hold. | Document what works, then move from chat-based prompts to small workflows. |
How it works
- Copy the 15 items into a note file and answer each one Yes or No honestly, item by item.
- Total your score out of 15 and find your band in the table above.
- Turn your biggest No into one specific next action you finish this week.
About 15 minutes. Fifteen Yes/No items, five in each area (team, tools, habits), plus two minutes to total your score and read the band.
That is normal for most teams in 2026. Treat the missing written data rule as your biggest No item: write a one-line personal rule yourself about which information may go into any AI tool, and follow it until the company publishes one.
No. Readiness for a non-technical role is about choosing an approved tool, using it several days a week, and fact-checking its output. Coding only matters if you want to build agents yourself later.
Once a quarter. Your score should climb 2-3 points each time as you close gaps; if it is flat, you are probably experimenting with AI without building a habit.
Habits. Teams usually have tools within a week, but the people who actually benefit are the ones who repeat AI use at least three days per week. Build the habit first, then upgrade tools.
Who this tool is for
This check is written for a team of two to fifteen people, and it works just as well for one person answering about their own setup. Team leads in HR, admin, marketing and operations use it before a rollout; individual contributors use it before asking for a licence. It assumes no technical background and no dedicated AI budget. If your organisation already has a central AI platform team, some items will be trivially true and the tool will feel basic — that is expected.
It measures preparation, not ambition. A high score does not mean your team uses AI well, only that the conditions for using it are in place.
How to read your result
Fifteen items, five per area, one point each; nothing is half-true. The total runs from 0 to 15 and the table turns it into one of three bands. Zero to five is early stage: access may exist but the habit does not. Six to ten is a workable setup with predictable gaps. Eleven to fifteen means the basics hold and the next step is documenting what works before moving to workflows.
The area subtotals matter more than the total. Mark which five items belong to team, tools and habits, then compare. A common pattern is tools at four or five, team at three, habits at one or two: the licence arrived, the rule did not, and nobody repeats the behaviour. That profile points to a different next action than a uniformly low score, even when both totals read eight.
The checklist does not rank your No items for you. Pick the one that other items depend on. A missing written data rule usually sits upstream of review habits and of permission to use a specific tool, so fixing it first tends to unlock two more points.
A worked example
A five-person HR operations team at a retail company works through the list together in a meeting room. Team readiness scores four: they review output before it reaches candidates, they agree on what a good draft looks like, one person owns experiments, and they have permission for a named tool. The missing item is the written data rule, which nobody has seen.
Tools score three. They have an approved browser-based assistant and know how to paste long documents, but the second dedicated tool for meeting notes or spreadsheets has not been chosen, and access still needs an IT ticket on some laptops.
Habits score two. AI is used in bursts rather than three days a week, and no one keeps a note of prompts that saved time. The weekly comparison and the thirty-minute share slot do not happen.
Total: nine, the middle band. The team writes the biggest No on a whiteboard: no written rule. Their action for the week is a one-page document naming the approved tool, listing the categories that must never be pasted (candidate identity documents, salary bands, incident reports), and naming the person to ask when a case is unclear. They schedule fifteen minutes to review it, and put the prompt note on the agenda for the following month.
Common mistakes
Scoring a partly true item as a point is the most frequent problem. We sort of have a rule means the item is a No until someone can open the document.
Teams also answer about the company rather than the group in the room: headquarters may have a policy, but if this team cannot find it, the practical answer is still No. A tool demonstration is not a habit, and one enthusiastic user is not a team owner. Marking the permission item Yes because nobody has objected is not the same as written approval.
Finally, do not chase fifteen. A perfect score on a first attempt usually means the questions were read as aspirations. Repeat the check quarterly, and treat a flat score as information about the habit items rather than a reason to abandon the effort.