Why this matters

Another tool won't fix how a team decides

Most organisations now have AI tools. Far fewer have a shared way for every role to use them safely, together.

The numbers

The tools are there. The results aren't.

People aren't prepared.

Mistakes are already happening.

Leadership alone isn't reaching people.

It's now a legal duty in the EU.

The gap isn't the technology. It's whether people in different roles know how to work with it, and with each other.

Figures from independent studies, 2025–2026. Surveys differ in method and sample.

Three common assumptions

The tool will solve it.

often heard from developers

Belief. A new platform or agent brings the structure.

Reality. Tools speed up the work. They don't decide who checks it, who's accountable, or what happens when it's wrong for the person on the other end.

Managing it is my job.

often heard from managers

Belief. Clear management keeps AI on track.

Reality. Managers can't see every AI output. The judgement sits with each role, and each role needs to know what to look for.

We've done the training.

often heard from compliance and L&D

Belief. A policy and an e-learning course cover it.

Reality. Generic training isn't tied to real work. People pass the course, then meet a case it never mentioned.

What's already out there, and what it leaves open

What existing offers do, and what role paths still add
CategoryExamplesWhat it does wellWhat it leaves openHow role paths fit
AI coding agents and orchestratorsAIDEN, GitHub Copilot, CursorSpeed up building. Some, like AIDEN, add a spec to approve and a review step before code is mergedThey review the code, not the consequence for the person who receives the outputEach role learns what to check in its part of the chain, not only in the code
Code and delivery platformsGitHub, GitLabVersion control, pull-request reviews, traceability of changesA review approves a change, not a decision about a citizenAdds a named reviewer for AI decisions that affect people
Work trackingJira, Azure BoardsTasks, handoffs and status in one placeA ticket can close while nobody owns the outcomeNames an owner and a recovery route for critical handoffs
Team methodsScrum, RACIRhythm and recorded responsibilityThey say who, not how to judge AI outputRehearses the decision, not just the name in the box
Generic AI trainingE-learning, AI literacy coursesShared basics and vocabularyThe same course for everyone, unconnected to the team's real workRole-specific paths, practised on a real workflow
Governance frameworksNIST AI RMF, ISO/IEC 42001, EU AI ActDefine what must be governedSay what, not how each role does it day to dayTurns requirements into each role's tasks and handoffs
Monitoring toolsMLOps, model monitoringTrack model performance and driftCan't see the citizen who got a confusing letterConnects technical signals to frontline feedback

Your tools record who does what. Role paths teach people how to do it, together, when AI is involved.

Why it has to be role-based

In my research, failures happened between roles: risk was "another team's job", fairness was left to the developer, and nobody owned the effect on the citizen. A tool or a course aimed at everyone misses those gaps. Role paths give each person what they need for their part of the chain, and the team rehearses the handoffs together.

See the four stories → Meet the personas → How the learning works →

Want to close the gap in your organisation?