How AI-native is your team, out of 30?
Score 10 habits from 0 to 3. Get your band, your first 3 moves and a 90-day plan built from your weakest lines.
10 linesAbout 3 minutesNothing stored
Northwind
17 / 30
A start, no engine band 10 to 19
Some pieces are in place and some people are good at it, but nothing keeps it moving when the keen people get busy.
3 points to Almost there.
Score your team
Pick the sentence that is true today on each line, not the one you plan. When two people disagree, take the lower score.
The 4 bands
| Score | Band | What it means |
|---|---|---|
| 0 to 9 | You bought seats | The licences are paid for, but nothing turns them into habits. Use is up to each person, and most of the value is still on the table. |
| 10 to 19 | A start, no engine | Some pieces are in place and some people are good at it, but nothing keeps it moving when the keen people get busy. |
| 20 to 26 | Almost there | The structure works. A few weak lines hold back the loop of finding, shipping and measuring new workflows. |
| 27 to 30 | AI native | AI work has an owner, a rhythm and a number. The job now is to keep the loop honest and raise the bar each quarter. |
The 90-day plan
Every team gets the same 3 months. Your scores mark each step start, tighten or keep.
Month 1
Set up
Name the AI champion, pin a 1-page policy, start the session library, book weekly office hours and the first live training.
Month 2
First loop
Rank the use cases by hours saved. Ship 2 workflows and time them, post the wins, then ship 2 more.
Month 3
Hackathon
2 weeks of building, then a demo day judged 50% on hours saved, 30% on how many would use it and 20% on reuse.
The AI champion
The plan starts with one person. Not the most technical person in the company. The champion makes AI normal for everyone; engineers can help them build. Print the role card.
Role card
AI champion
Who fits
- Curious: tries new tools without being asked, and says what did not work.
- Close to the work: knows how the team spends its day, not only what the slides say.
- Trusted: people already ask them how to get things done.
- Plain-spoken: can explain a tool to a new hire without jargon.
Not the most technical person in the company. The champion makes AI normal for everyone; engineers can help them build.
The 5 jobs
| Try one new tool or feature, and give it a verdict: adopt, watch or skip. | Every week |
|---|---|
| Run the live training session on a real task from the team. | Every month |
| Keep the session library current: add new recordings, remove stale ones. | Every month |
| Rank the use-case list by hours saved with the department reps. | Every 2 weeks |
| Hold office hours where anyone can bring a task and leave with a way to do it. | Every week |
About 5 hours a week, written into the role and protected by their manager.
Score from your agent
No key and no sign-in. Connect the MCP server, then ask: Score how AI-native my team is and give me a 90-day plan.
The agent asks you the 10 lines and calls score_ai_native_team.
Claude Code
claude mcp add --transport http tenrung https://tenrung.openkrill.app/mcp
Cursor
{
"mcpServers": {
"tenrung": {
"url": "https://tenrung.openkrill.app/mcp"
}
}
}Any MCP client
https://tenrung.openkrill.app/mcp
Frequently asked questions
Is anything I type stored?
No. The 10 numbers and the optional team name go into the result link itself. There is no account, no database row and no email.
Who should fill it in?
The person who would answer for AI at the company, with one manager from outside that team. If the two disagree on a line, take the lower score.
Is a high score proof the team is good with AI?
No. It is a self-assessment of habits, not an audit of results. Line 10 is the check: hours saved, measured and shown to leadership.
How often should we score again?
At the end of each 90-day plan. The plan's last step is a rescore, so you see which lines moved.