From Individual Skill to Organisational Capability
Part 2 of 2 in the Transformation Stack series
TL;DR
Individual AI fluency and organisational AI capability are not the same thing
The pathway from individual skill to systematic capability requires coordination. That is a leadership decision, not a training outcome.
The emotional dimension of the transition is the most consistently mishandled part.
The question is not whether your employees can use AI. Increasingly, many of them can. The question is whether your organisation can deploy that capability systematically.
Most organisations investing in AI capability have a skills problem they have already started to solve, and a coordination problem they have not yet named.
After two or three years of serious AI adoption, the skills are more widely distributed than most leadership teams realise. People are using tools, building personal workflows, finding genuine productivity gains in their own work. The investment in training and access has produced results at the individual level. The frustration is that those results have not aggregated into something the organisation can point to, deploy systematically, or build on.
This is the distinction that changes how you think about the next phase of AI investment: individual skill and organisational capability are not the same thing, and they do not develop through the same means.
What Individual Skill Can and Cannot Do
An individual builds AI fluency through practice and feedback. They learn which prompts work, which tools fit which tasks, how to integrate AI into the rhythm of their specific role. These gains are real and they show up in personal productivity. The problem is that they do not automatically aggregate into something the organisation can deploy systematically.
When a skilled employee leaves, their personal AI workflow leaves with them. When a team develops a high-value application, it often stays within that team - undocumented, unscaled, unknown to the rest of the organisation. Individual capability accumulates in people. Organisational capability accumulates in processes, shared knowledge, and structures. Building the second requires deliberate coordination that no training programme, on its own, can produce.
Wade Foster, CEO of Zapier, encountered this directly. After a concentrated week in which 87% of employees tried at least one AI tool, the internal conversation shifted from whether to use AI to how to use it better. That was genuine progress. But it was still individual capability. The next challenge - turning those wins into coordinated, scalable ways of working - required something different: selecting which experiments to accelerate, building shared infrastructure around what worked, and concentrating resources deliberately rather than spreading energy across every promising idea.
Zapier eventually allocated 60% of their AI budget to three high-priority initiatives, 25% to foundational capabilities including training and shared resources, and 15% to continued experimentation. The individual skills had existed for months. The organisational capability emerged only when the coordination arrived. Within two quarters, the sales team had added significant pipeline capacity without adding headcount.
The Coordination Gap
The gap between individual skill and organisational capability is a coordination problem - and coordination is a leadership decision, not a training outcome.
Closing that gap requires three things that most AI programmes have not yet invested in:
Selection. Identifying which individual experiments and team-level applications are worth scaling, and which should remain localised. Most organisations are still letting everything run in parallel, which disperses energy and produces no clear winners to build on.
Infrastructure. The shared resources - documented workflows, prompt libraries, evaluation criteria, review processes - that allow one person’s learning to become the organisation’s asset. Without this, every team starts from scratch, and the organisation’s cumulative AI investment depreciates every time someone changes roles.
Integration. Connecting AI capability to the processes, performance frameworks, and role definitions that determine what people are actually rewarded for doing. Skills that exist outside these structures produce activity. Skills embedded within them produce organisational change.
Most AI programmes have invested heavily in access and training - the conditions for individual skill. Few have invested seriously in these three. That is where the coordination gap lives, and closing it is a leadership decision that no vendor, no training programme, and no technology rollout can make on the organisation’s behalf.
The Dimension Most Leaders Misread
There is one aspect of this transition that deserves particular attention because it is the most consistently handled poorly: the emotional dimension.
An HR business partner at a telecommunications company described a mistake his organisation had made. They led their AI rollout with capability, explaining what the technology could do, how it would increase efficiency, and when training would happen. What people heard was that their work was being automated away and their relevance was in question. Adoption stalled. Not because of the tools. Because of the framing.
When AI reshapes work, people respond as professionals whose expertise and sense of contribution are being called into question. An operations manager at a logistics company described the moment when AI began proposing routing solutions he would never have chosen - and they worked. His first reaction was not curiosity. It was the fear that a decade of expertise had become irrelevant.
Months later, his view had shifted. His role had not disappeared; it had changed in character. He focused on complex exceptions, carrier relationships, and strategic trade-offs, while AI handled pattern recognition at scale. His expertise mattered more than before, applied differently than before. That transition did not happen without deliberate leadership attention.
The HR business partner eventually adjusted his approach, reframing the message this way: AI will take over the parts of your job you raise in every team meeting, freeing you for the work you trained years to do. Same technology. A very different reception.
The people dimension of AI transformation is not only about skills development. It is about helping people find a new relationship with their own competence. That requires more than a training rollout can provide - and it requires a different kind of leadership conversation than most organisations have been willing to have.
The question most organisations should be asking at this stage of AI investment is not whether their employees can use AI. Increasingly, many of them can. The question is whether the organisation has the processes, structures, and shared knowledge to deploy that capability systematically - and whether leadership is treating the coordination gap as its own problem to solve.
This framework is part of a broader playbook I’m developing for leaders navigating AI, the AI Strategy Playbook: From Zero to 100. If you’d like early access to the book and related materials as they become available, you can join the waitlist here.