Translating individual AI capability into organisational design: what to build, and where to start.
Last week's piece argued that AI capability is an organisational design problem, not a training problem. The most common question back was the obvious one: if it's a design problem, what specifically am I designing?
This week's piece answers that. Five organisational competencies change how AI actually gets used inside a business: distributed AI fluency, quality oversight for AI work, strategic use-case selection, adaptive capability building, and AI-integrated workflow design. The translation of the well-researched individual AI competencies (what a person needs to work with AI well) into the under-researched organisational ones (what an organisation needs to have for individual capability to compound).
Two clarifying notes before the five.
First: these are competencies of the organisation, not of the individuals inside it. The literature on individual AI competencies has expanded significantly in the past year (the WEF, LinkedIn, and McKinsey research cited last week is all individual-focused). The literature on organisational competencies is much thinner, partly because the question is newer and partly because the answer doesn't fit neatly into a course or a workshop. Most of what follows comes from my work with leadership teams over the past two years rather than from a single citable source.
Second: these aren't a checklist. They're a system. Each one depends on the others. You can't build one in isolation and call it done. More on that at the end.
Distributed AI fluency
What it is: the organisation's ability to use AI knowledgeably across functions, levels, and teams, not just in pockets where individuals have built personal proficiency.
Most organisations have AI fluency concentrated. Two or three power users in marketing. The technical team. A handful of curious executives. Everyone else either ignores AI tools or uses them tentatively for the most basic tasks. The organisation has some AI fluency. It doesn't have distributed AI fluency.
The distinction matters because AI changes work most where the work is collaborative and cross-functional. A marketing team that's AI-fluent but whose finance partner isn't will produce campaigns that finance can't model. A consulting team that's AI-fluent but whose client services partner isn't will produce work that doesn't flow into client delivery. The fluency compounds only when it's distributed.
What it looks like when an organisation has it: people across functions can describe what they use AI for, where they don't, and how they verify output. AI conversations happen casually in cross-functional meetings, not as set-piece training sessions. The Head of AI (if there is one) is a coordinator, not a bottleneck.
What it looks like when one doesn't: AI projects bottleneck through three people. The rest of the organisation either over-relies on those three or under-uses AI entirely. Capability doesn't accumulate, it concentrates, and then it leaves when someone moves on.
Where to start: stop treating AI training as an HR programme and treat it as a cross-functional rhythm. Monthly cross-team show-and-tells where people share what they're using AI for. Internal channels where successes and failures get written up. Visibility before depth: you want fifty people who can do something basic with AI before you want five people who can do something advanced.
Quality oversight for AI work
What it is: review and verification processes specifically designed to catch the kinds of errors AI produces, distinct from those designed for human errors.
Existing quality processes in most organisations were built for human error. The signature human errors are inconsistency, fatigue, knowledge gaps, and personal bias. Reviewers spot these. They don't reliably spot AI errors, which look different: confident assertions that aren't supported by underlying data, plausible-sounding output that's subtly wrong on specifics, generic content where specific content was needed.
The competency: a quality system that catches AI errors at the right scale and the right speed. Not every piece of AI output needs the same review. Internal drafts get one level of oversight. Customer-facing content gets another. Regulated content gets a third. The system has to know which is which.
What it looks like when an organisation has it: clear trust gradients, where AI output for X is signed off by Y level of reviewer, AI output for Z requires legal sign-off, and AI output for trivial internal use needs none. The review processes have been updated since AI arrived. Mistakes get logged and used to refine the process.
What it looks like when one doesn't: AI-generated content goes through review processes designed for human-written content. The errors that get through aren't the ones reviewers were trained to spot. By the time someone catches one, it's already gone out to a customer, a regulator, or a stakeholder.
Where to start: pick the three highest-stakes AI use cases in the organisation. Map the current review process for each. Ask: would this catch a confident-but-wrong AI claim? Where it wouldn't, redesign.
Strategic use-case selection
What it is: the organisational capability to decide what's worth doing with AI, not just what's possible.
The most common organisational mistake with AI right now is doing too much of it. Every team is encouraged to find AI use cases. Every function runs experiments. Every meeting agenda has "AI opportunities" on it. The result: a hundred small pilots, no significant wins, and a leadership team that can't explain what AI is actually doing for the business.
The competency is the discipline of choosing fewer, better use cases. Strategic use-case selection asks: where would AI shift the business meaningfully if it worked? Where are the costs of getting it wrong acceptable? Where is the workflow shape suitable for AI's actual strengths? Then it concentrates investment there.
What it looks like when an organisation has it: a clear short list of where AI is being used seriously, why those choices were made, and what the rest of the organisation is not doing with AI. Leadership can name the three or four AI initiatives that matter and explain why.
What it looks like when one doesn't: a hundred fragmented AI pilots, none of which justify themselves on impact. A growing sense that the organisation is "doing AI" without a way to tell whether it's working. Activity metrics (number of pilots, number of trained staff) substituting for outcome metrics.
Where to start: list the AI initiatives currently running across the organisation. Score each on two axes: potential impact if it works, and time and investment required to make it work. Cut the bottom half. Invest the freed capacity into the top quarter.
Adaptive capability building
What it is: continuous, peer-led, work-embedded learning systems that keep pace with how fast AI tools actually change.
Most organisations are running their AI upskilling through legacy training infrastructure: annual cycles, formal courses, structured certifications, learning management systems. The 80% of employers committed to AI upskilling are mostly doing it this way. It doesn't work for AI specifically because the tools change every quarter and the workflows around them change with them.
The competency: a learning system that runs at the speed of the tool change. That usually means fewer formal courses and more in-flow, peer-led, problem-driven learning. Demonstrations of actual use cases beat structured curricula. Internal champions beat external trainers. The talent-development function shifts from delivering programmes to designing the conditions where learning happens continuously.
What it looks like when an organisation has it: people learn AI by using it, with peers, on real work. The training function curates and accelerates rather than delivering set-piece programmes. New AI capabilities propagate across the organisation in weeks rather than years.
What it looks like when one doesn't: an annual AI upskilling programme that's already out of date by the time it rolls out. People learn AI by accident, or in their own time, or not at all. The organisation knows it's behind but the training calendar can't change fast enough to catch up.
Where to start: cut the annual training calendar's AI hours in half and reinvest in continuous peer-learning structures (internal show-and-tells, problem-driven cohorts, expert office hours). Most talent-development teams find this unsettling. Most CEOs find the result obvious within ninety days.
AI-integrated workflow design
What it is: deliberate design of how AI-generated work connects to human work, including the seams between the two.
Most AI implementation right now is happening inside existing workflows. Step three of a five-step process is now AI-assisted. Steps one, two, four, and five are unchanged. The work happens faster at step three. The bottleneck moves to step four. Sometimes the whole process is now slower because the increased throughput at step three has overwhelmed the human capacity downstream.
The competency: workflow redesign that accounts for what AI now does, what humans still do, where the hand-off happens, and what quality checks the hand-off requires. This is the most operational of the five and the one that produces the most visible productivity gains when done well.
What it looks like when an organisation has it: workflows redesigned around AI rather than retrofitted. The sequence of work, the hand-offs, the review points, the responsibilities have all been thought through together. Productivity gains show up in business metrics, not just in surveys about AI adoption.
What it looks like when one doesn't: AI inserted into legacy workflows with no design work. Bottlenecks move around but don't disappear. Adoption metrics rise; productivity metrics don't.
Where to start: pick one critical workflow. Map it before and after AI. Ask where the bottleneck moves when AI does part of the work. Redesign the whole workflow around the new shape, not just the AI step. Get it right for one workflow before scaling the approach to others.
Why these five are a system, not a checklist
These competencies aren't independent. They depend on each other in ways worth being explicit about.
You can't build quality oversight without distributed fluency: the reviewers who'd catch AI errors need to know how AI fails, which requires they've actually used the tools.
You can't do strategic use-case selection without quality oversight: the use cases worth investing in have to be ones the organisation can verify and trust.
You can't build adaptive capability without integrated workflow design: peer-led learning only spreads when there's real shared work to learn from.
You can't redesign workflows without distributed fluency, quality oversight, and strategic use-case selection: those three give you the inputs the redesign needs.
The organisations producing genuine AI returns are building all five in roughly parallel, not in sequence. The ones treating it as a checklist (picking one competency, building it, then moving on) find that the one they build alone doesn't compound.
What's next
Reading these five against your own organisation, the question is usually obvious: which of the five is the binding constraint right now? Most leadership teams can answer that within a few minutes. The harder question is what to do with the answer.
The next piece is about that: how to write an AI strategy, not the slide deck for the board, but the actual working document leaders use to make decisions about where AI fits, what to invest in, what to stop doing, and how to measure whether any of it is working. The five competencies above show up in that document. The strategy is the thing that turns them from a diagnostic into a plan.