Map your team’s AI capability gaps
Rolling out AI across a team fails when training is generic. Some people already prompt fluently; others have never automated a task; one person may be the only one who knows your AI stack. This analyzer lets you rate each team member across four AI competencies, then surfaces the weakest team-wide skills and the risky single points of knowledge so your training budget goes where it actually moves the needle.
How it works
You add each team member with a role and rate them 1–5 on four skills: prompt writing, tool use, automation, and critical evaluation. The analyzer averages each skill across the team to find the weakest competencies, and scans for single points of knowledge — skills where only one person scores 4 or higher. It then produces a prioritised list of training recommendations, weakest team skills first, followed by the riskiest knowledge concentrations.
The four competency dimensions
Prompt writing (1–5) measures how well someone can instruct an AI to produce specific, useful output. A score of 1 is first-time experimentation; 5 is confidently using system prompts, chain-of-thought, and structured output formats. This is often the most unevenly distributed skill on any team.
Tool use (1–5) tracks familiarity with the AI tools the team actually runs — knowing which tools fit which tasks, understanding their limits, and operating them without constantly restarting or starting over.
Workflow automation (1–5) measures whether someone can connect AI into a real working process, not just run one-off queries. At level 5 they are building automations that save measurable hours. At level 1 they use AI only for isolated, ad-hoc tasks.
Critical evaluation (1–5) is the safety skill: knowing when to trust AI output, when to fact-check it, and when to discard it. Low scores here are the primary source of AI-introduced errors in team work.
What “single point of knowledge” means in practice
If only one person on your team scores 4 or 5 on automation, and they leave, resign, or go on leave, your automation capability drops to near zero. The analyzer flags any skill where only one team member holds that competency — these are the risks most organisations discover only after the fact.
Tips for an honest analysis
- Rate observed behaviour, not job titles. A senior engineer may be weak at automation; a junior marketer may be your best prompter.
- Fix broad gaps before niche ones. Lifting a skill that is low across the whole team beats deepening one already-strong person.
- De-risk single points of knowledge. Pair the lone expert with a learner so the capability survives if they leave.
- Re-run quarterly. Capability shifts as people learn; track whether your gaps are actually closing.
- Use the output as a budget brief. A prioritised gap list with named weaknesses is far easier to turn into a training proposal than a general request for AI upskilling.