The Soft Edge of AI Transformation
Why the organisations winning with AI are getting good at precisely what traditional management is worst at
A pattern is becoming visible across the organisations making real progress with AI. It’s not what most transformation programmes are designed to produce, and it’s not what most leadership teams are being shown.
These organisations have not necessarily moved fastest on technology. They do not always have the clearest AI strategy, the most advanced tools, or the highest rates of individual adoption. What they tend to have is something harder to name and harder to copy: the right conditions for capability to accumulate, for intent to travel without distortion, and for gains at the edge of the organisation to become gains at the centre.
This sits awkwardly with the dominant approach to AI transformation, which is built on hard edges - clear use cases, measurable adoption rates, defined ROI, governance frameworks, structured rollout plans. None of these things are wrong in themselves. But together they reflect a mental model of how transformation should work that is increasingly at odds with how AI actually creates organisational value.
That model is Pipeline Thinking. Strategy enters at one end, capability is built in the middle, performance emerges at the other end. Each stage is legible, sequential, and - in principle - controllable. It is the model that has shaped most large-scale change efforts for decades, and it feels rigorous precisely because it has hard edges.
But organisations do not behave like pipelines. And in the age of AI, the cost of assuming they do is rising fast.
Pipeline Thinking and Its Limits
Pipeline Thinking has a seductive logic. Define the strategy clearly enough, build the right capabilities, communicate intent effectively, and execution should follow. If it does not, the diagnosis is usually the same: the strategy was unclear, the capabilities were insufficient, or the communication failed. The solution is more of the same, but better.
This assumption shapes what gets counted as a legitimate intervention, e.g. hard skills, certified training, platform adoption, defined processes. These are the things that Pipeline Thinking can see and measure. What it systematically underweights is the more complex layer in between: the conditions that determine whether strategy actually takes hold, whether new capabilities spread and reinforce one another, and whether individual gains accumulate into organisational performance.
In stable environments, organisations could compensate with informal structures that absorbed variation, experience and familiarity that held things together, and managers stepping in to reconnect fragmented work.
The pipeline worked, more or less, because the gaps were filled by things no one had explicitly designed - but AI removes the sequential stability that allowed this to function. Individuals and teams can now experiment more rapidly, develop new ways of working more quickly, and generate outputs at a speed that was not previously possible. Capability accumulates fast, but so does inconsistency. Different interpretations of the same objective become embedded simultaneously. Local optimisation becomes easy, while coherence becomes harder.
The challenge is not that organisations become less capable. The challenge is that capability can now evolve faster than the conditions required to integrate it. Pipeline Thinking has no good answer to this challenge. It can accelerate the inputs, but it cannot address what happens in between.
Conditions Thinking: The Alternative Frame
The alternative is not to abandon rigour, but to apply it to the right things.
Conditions Thinking starts from a different premise: that performance is not the output of a pipeline, but an emergent property of the environment in which people and teams operate.
It does not flow directly from strategy or capability. It emerges from how those things interact, how intent travels through the organisation without distorting, how new capabilities spread and reinforce one another, how individual gains accumulate rather than remain isolated.
This reframe matters because it changes what leaders need to attend to:
Pipeline Thinking asks: have we communicated the strategy clearly? Have we built the capability? Are adoption rates on track?
Conditions Thinking asks: what allows intent to propagate without becoming distorted? What determines whether new capabilities spread or remain isolated? What is preventing individual gains from compounding into organisational performance?
These are softer questions, which help identify the conditions for success, but are often dismissed in traditional change thinking. They do not submit easily to the hard-edged measurement and control that Pipeline Thinking prefers. But soft, here, does not mean vague or secondary. It means distributed rather than centralised, relational rather than procedural, and accumulative rather than instantaneous.
Importantly, Conditions Thinking describes precisely the terrain where AI transformation is most likely to create (or fail to create) durable and sustainable organisational value.
What the Conditions Actually Are
Some of the conditions that matter are structural:
The shared artefacts that carry context across boundaries
The decision processes that make local choices visible to others
The feedback mechanisms that allow the organisation to understand whether it is moving coherently
Others are cultural:
The norms that determine whether new practices spread or remain isolated
The shared language that shapes how problems are understood
The habits that determine whether learning accumulates or dissipates
And some are coordinative:
The specific points where work connects across roles, teams, and functions
In an earlier edition, I wrote about the coordination layer: the part of the organisation where work is connected rather than created, and where most current AI initiatives are not yet operating. In that edition, we looked at agentic process surrounds, narrow AI interventions placed at points of high coordination leverage, as one practical response to this. Not broad agents that manage entire processes, but small ones that carry context across handovers, prepare inputs for recurring decisions, or surface divergence before it becomes a problem.
Consider what happens to a recurring decision-making process when three people on the same team are each using AI differently - different prompts, different tools, different assumptions about what a good output looks like. The decision still gets made, the output still arrives on time, but the criteria have quietly diverged. Context doesn’t transfer cleanly from one cycle to the next. The manager becomes the integration point by default, spending significant time reconciling outputs that were never designed to be reconciled. Nobody names this as a conditions failure. It looks like a coordination problem, or a communication problem, or simply a busy week. But what it reveals is an environment where individual capability has advanced faster than the shared frame of reference required to make that capability compound.
These conditions do not execute strategy. They determine whether execution remains coherent as strategy moves through the organisation. Strategy survives through systems of reinforcement more often than through systems of instruction.
Which Thinking Are You Actually Using?
The distinction between Pipeline Thinking and Conditions Thinking rarely shows up in strategy decks. Both can produce the same language: capability building, adoption, transformation, impact. The difference shows up in what leaders choose to attend to, and what they leave implicit.
The difficulty is that Pipeline Thinking is not just a structural habit. It is a comfort habit. It offers legibility: visible inputs, measurable outputs, defensible decisions. Conditions Thinking requires tolerating a degree of ambiguity that feels uncomfortable when boards want hard numbers and leadership teams are under pressure to show progress. Asking “what conditions are preventing intent from propagating?” is a harder conversation to have than “are adoption rates on track?”, even when it is the more important one. The diagnostic questions below are useful partly because they make that discomfort productive.
