I wrote the best brief of my career this spring. It took about two hours and it was addressed to a machine. Crucially, not one line of it had to survive a disagreement.

That last part took me longer to notice than it should have.

The brief was ordinary enough in its parts. Context: here is the situation, here is what has been tried, here is why the obvious answer is wrong. Principles: this is what good looks like here, here is what we never do and where the line to hold is even when it hurts. Then the operating instructions. When to stop and check in before going further.

I read it back and thought: I have never written this for a person.

Not in twenty-five years. Not for teams I trusted and rated and would have gone to the wall for.

The comfortable explanation arrived straight away. It goes like this: I had been carrying all of it in my head, my people deserved it written down, and the machine had finally forced me to do the work I should have done years ago. Pay the debt, give the team the brief.

That reading is flattering, it is half true, and I now think it is the less interesting half.

The reason it was easy

I could not have written that brief for my team. Not did not. Could not.

Put those same principles in front of six people who know the work and the meeting takes a day and a half. Someone says the third principle contradicts something we agreed in March. Someone else wants to know what happens when the line I say we hold costs us a launch. A third points out, correctly, that the thing I described as what we never do is something we did twice last year for good reasons.

I would have defended some of it and to be fair, I would have lost some of it. What came out the other end would have been harder to write down, yet much better.

The machine took the whole thing. It thanked me for the clarity.

So the completeness of that brief is not evidence that I had the good version all along. It is evidence that I was writing for a reader with no standing to object.

The tell

There is a line in my own brief I skipped past a dozen times before I saw what it was doing.

I told it where to push back on me.

I had to ask.

Nobody asks a good team to push back. Disagreement is the default condition of working with capable people, and most of a leader's energy goes on holding it in some useful shape rather than summoning it in the first place. With a machine it is a feature you remember to switch on, in the sections where you happen to suspect you might be wrong.

Which is exactly where you are not wrong. You already know where you are shaky. That is not where the damage lives.

The damage lives in the places you were so certain about that it never occurred to you to invite an argument.

What judgement is made of

Here is the thing I think the current conversation keeps stepping over.

Judgement is not the set of conclusions you hold. It is the record of what survived being contested.

That distinction sounds academic until you try to move judgement from one place to another, which is what every company is now attempting to do at speed. You can move conclusions easily. Why? Because they write down beautifully. What does not travel is the thing that made them trustworthy. Every time they were tested by someone who wanted a different answer and lost is what made them trustworthy.

Strip that out and you still have the sentences. They look the same on the page.

You can see the difference in how the two behave under pressure. A conclusion that has been argued with knows its own edges. The people holding it can tell you where it stops applying, what it costs, which cases nearly broke it, and what they would need to see to abandon it. That is not extra detail, it IS the judgement. A conclusion that has never been argued with has none of that, and it does not know it is missing anything.

Every experienced leader can name someone in their company who holds strong views they have never had to defend. They know the hard-won reasons behind the conclusions everyone has to apply. We are now building that person into the infrastructure and calling it institutional knowledge.

Three decimal places

Last month I wrote about a rule I worked under for most of my career. Connection tolerances held to three decimal places, taught to everyone who touched the product, old enough to outlast everyone applying it, and strong enough that good ideas lost arguments to it.

I described it then as a rule with teeth and left it there. Here is the part I did not say.

That rule did not have authority because it was written down. Plenty of things were written down. It had authority because it kept being argued with. Every year somebody arrived with a genuinely good reason to bend it: a cost saving, a new material, a design that would have been beautiful. The rule won those arguments on the merits, repeatedly, in front of people who badly wanted the answer to go the other way.

Decades of winning arguments is what a rule with teeth is actually made of. The three decimal places were only the notation.

Now load that same rule into a system on day one. Every decision downstream complies with it immediately. No cost saving ever gets to test it. Nobody has to defend it against a beautiful design. It reads identically and it is a completely different thing: a conclusion wearing the authority of something that earned it.

What the industry is building

This spring the World Federation of Advertisers (WFA) and BCG put a joint report in front of a room of global CMOs. Everyone is using AI yet very few are getting compounding value, and around seventy percent of the effort separating the leaders from the rest is people and change rather than technology. Their proposed fix is what they call an enterprise context layer. Encode the company's knowledge, principles and guardrails into the systems themselves, so that every AI-assisted piece of work draws on the institution's judgement by default.

Codify the thinking. Wire it in. Make judgement a property of the infrastructure instead of the people.

I understand the appeal, and I would rather a company did this than nothing, because writing your principles down well enough for a machine to use them is real work and most companies have never done it.

But look at what you are encoding.

You are not encoding the institution's judgement. You are encoding the version of it that was current on the day somebody sat down to write it out, produced under exactly the conditions I have just described: no room in the process for the six people who would have taken it apart. The context layer inherits the confidence of the original without inheriting the arguments that earned it.

Then it does something worse. It makes the thing unarguable going forward. A principle held by people can be tested on Tuesday by somebody with a good reason. A principle wired into the system that produces the work is not encountered as a claim at all. It arrives as the shape of the output. There is nothing there to disagree with.

The usual objection to codifying judgement is that it cannot notice when the world has moved. That objection is fair and it is too kind. The deeper problem is that it was never as sound as it looked, and now nothing will ever find out.

Why any sensible person would do it anyway

I want to be fair to the move, because I have made it myself and I will probably make it again.

Argument is expensive. It takes the time of your most capable people, which is the most costly thing you have. It is uneven, so the same question gets a different quality of challenge depending on who is in the room that week. It is slow at exactly the moments when speed feels like survival. And it produces nothing you can show a board. There is no artefact at the end of a good disagreement, only a decision that is quietly better than it would have been and no way to prove that to anyone who was not there.

Encoded judgement has none of those problems. It is fast, even, it applies at three in the morning, and it audits beautifully. You can show it to a regulator. You can hand it to a new starter on day one and they will produce compliant work by the afternoon.

So the choice companies are making is not stupid, and telling them it is will not get you anywhere. They are choosing something legible and cheap over something illegible and expensive, which is a choice organisations make correctly most of the time.

It is the wrong trade here for one reason. In almost every other case where you swap a slow human process for a fast encoded one, the thing you encoded stays true while you use it. A tolerance is a tolerance. A payment rule is a payment rule. Judgement is the one input that degrades precisely because you stopped arguing about it, and it degrades invisibly, and the system built on it goes on producing confident output the whole time.

You will not get a warning. That is the property that makes this different, and it is why the trade that looks prudent on the day looks reckless in the third year.

Every one of them agrees with me

I have spent the last few weeks building a set of agents to take over parts of my own working week. It has been the most interesting thing I have done in a while, and it has also been a slow lesson in the argument above.

Every one of them agrees with me.

Of course they do. I wrote them. They run on principles I set, in a context I supplied, with a tone I chose. When one of them produces something wrong, it produces it confidently and in my own register, which turns out to be an effective disguise. Twice now I have caught something on the second read that I would have caught instantly if a colleague had said it out loud in a meeting, because when a person says something slightly off, you hear it.

I am one person with a handful of agents. Scale that to a company where every team has a fleet, all of them drawing on the same encoded principles, and you do not have more capacity to think. You have one opinion, held many times, at speed.

Building the argument back in

So what do you do instead, if writing it all down is not the answer?

You build the contest rather than the codex.

The clearest example I know sits in Oslo. Norway's sovereign wealth fund has pushed AI into its work as hard as any institution I have watched. Alongside the automation they built something most companies would not think to build: a simulator in which their investment professionals make calls, see the consequences, and get structured feedback on the quality of their reasoning. A machine for being wrong in front of evidence, on purpose, before it costs anything.

Read it against everything above and notice what it actually is. It is not a system that holds the institution's judgement. It is a system that keeps putting the institution's judgement back into the argument it came from.

That is the design choice, and it is available to any company willing to make it. Ask which of your principles has been genuinely tested in the last two years, by someone with standing and a real reason to want a different answer. Ask what happened. If you cannot name the occasion, you do not have a principle. You have a habit that has not been challenged yet, and you are about to wire it into everything.

The practical version is smaller than it sounds. Before anything goes into the system that produces your work, make it survive a room. A room where someone is asked to take it apart and is thanked for succeeding.

What I still do not know

I have been careful in this piece to argue from things I have seen. Here is the part I have not resolved.

The systems I built will outlast me. I made sure of that, and it is the professional fact I am proudest of. They run in places I have never visited, operated by people I have never met, and they have not needed me for years.

What I have never fully tested is the judgement underneath them. That was never written down anywhere, for the reason this whole piece has been circling: it did not need to be, because it was alive in argument every day, and I was in the room for the argument.

I am not in the room forever. Nobody is. And there is only one way to find out whether what you built can keep winning the arguments without you, which is to stop being there and see.

It is not a document. It was never going to be a document.

Next month, a more personal piece. There is something I have been carrying through every one of these essays, and it is time to say it plainly.

Sources

Evidence

• WFA + BCG, AI Community — Global Marketer Week 2026 (Stockholm, April 2026): 100% of marketers using AI, 16% at advanced stages; ~70% of the effort separating leaders is people and change; the "Enterprise Context Layer" proposal engaged in the body. Link
• Norges Bank Investment Management, How we use AI in practice (AI Summit, 2026): the Investment Simulator as deliberately engineered judgement-building alongside aggressive automation. Link

Building on

• Michael J. Mauboussin, The Wisdom of Crowds (Morgan Stanley, Consilient Observer, 2026) — the conditions under which a group aggregates information rather than amplifying one error: diversity and independence. Remove either and the crowd stops working. The formal statement of what the agent-fleet passage argues informally. Link
• Jennifer Garvey Berger, "Disagree to Develop" (2026) — the move from disagreement as something a decision has to survive to disagreement as the thing that builds the people and the idea at once. Link
• Paul Willmott, Considered Machines (Substack, 2026) — the organisational rather than tooling read of AI that this piece extends. Link

In twenty-five years of changing one company, nobody ever handed me a list of the things I was not allowed to change.

I built things that had not existed before. New functions, new ways of reaching people, a whole channel where there had been a catalogue. Every one of them changed what the company was to somebody. Every one of them was approved by people who read the case and agreed with it.

Not once did anyone say: hold this, whatever else you do. I worked it out instead, the way everyone does. I got close enough to the people who already knew, and I stayed long enough to absorb what they would never have allowed. That worked, roughly, because I was there a very long time. It is a terrible way to run a company through a change.

Except in one place.

The one thing that was written down

The physical product had rules. Real ones, not a poster in a corridor. A body of encoded knowledge, taught, argued over, enforced, and older than almost everyone applying it.

How the parts connect, and the tolerance they connect at, held to three decimal places. Which shapes are allowed into the permanent vocabulary and which may only ever serve one purpose. What the design language does and does not do. What the name may sit next to, and what it may never sit next to.

I watched good ideas lose those arguments. I watched people spend weeks on a case and get turned down over a decimal.

That is a continuity line, and it is the best one I have ever worked inside. It was written well enough that someone who had never met the people who wrote it could pick it up and make the call they would have made. It held for decades. It survived a near-collapse, a rebuild, and more reinvention than most companies attempt in a century. Everything else about that company changed, repeatedly: what it sold, who it sold to, how it reached them, what business it thought it was in. The line held through all of it, and the line is a large part of why all that change stayed recognisable.

It covered the product and the name.

Plenty got written after that. Five years into my time there I sat down with the chief executive to build a brand framework, because no such thing existed and the near-collapse had made the absence impossible to ignore. It was real work and it was needed. Policies have arrived in quantity ever since.

The problem was never that nothing was written down.

It is that almost none of it could turn anything down.

Where the rules get teeth

This happens in companies that care a great deal. It is a pattern, and once you see it you see it everywhere.

Rules get teeth where the loss would be fast, visible and expensive. Get a tolerance wrong and the parts do not fit, and you find out in a week. Put the name next to the wrong thing and a lawyer calls. Those failures have an owner and a date, so the rule that prevents them is allowed to cost something. It is allowed to be expensive.

Where the loss is slow and invisible, you get documents instead. How you say no to people. What you will not do to make a quarter. The thing you always give customers that costs money and that nobody ever asked for. The tone you take when you have got something wrong and have to say so. All of that gets described, at length, in frameworks and guides that everybody in the room agrees with. None of it gets a price. Each one can be traded away quietly, in a single meeting, by a capable person with a decent case, and nothing is technically broken.

So here is the shape most large companies are actually in. One domain where the rules bite. Everywhere else, documents you can hold for free.

Which is why the question feels answered when it is not. Ask a marketing leader whether she has continuity through her transformation and she will point at real things: a brand book, a design system, trademark rules, a tone-of-voice guide. She is not bluffing. Those documents exist, they took work, and some of them are enforced. The ones with teeth govern the marks. The rest describe who the company is without ever naming what being that costs.

The decision nobody owns

The first gets an owner, a budget, a steering group, a plan and a name on a slide. The second gets asked anyway. Not once, in a room, by people accountable for the answer. Several hundred times a week, in briefs and reviews and supplier calls and pricing decisions and service scripts, by whoever happens to be building that particular piece on that particular day.

They are not being careless. They have plenty of guidance and no line. So they do what I did, which is work it out from proximity: from whatever they have picked up about what would be allowed. Proximity produces different answers in different people. That is what proximity is for. It is a wonderful way to develop somebody and a hopeless way to hold a company together while you are pulling it apart.

Drift is the sum of those answers. It is not an emotional event, and it is not a measurement failure. It is a decision nobody owns, taken several hundred times, by default.

That is also why you cannot catch it. Every instance is defensible, because every instance was defended, in a meeting, successfully. There is no bad decision to find. You go looking for the moment it turned and there wasn't one.

The reaches were all sensible

I watched the slow version of this before the company I worked for came close to going under.

The business kept reaching into new things. Each reach had a case. There was growth to be had, the categories were adjacent, the logic held in the room. And with each reach the company became a little less the thing people had loved it for. The brand loosened its grip on them long before the accounts showed any strain.

When the crisis finally broke, it broke loudly, and the comeback is the part everyone remembers. The quiet part had been running for years by then. Nobody made a bad call. Every one of those decisions was made by capable people with a good argument and the authority to act. What was missing was anybody with the standing to say: not that one, because of this.

The numbers were fine for most of it. They usually are. The feeling goes first and the spending follows late, out of habit and contract and never quite getting round to switching, so the dashboard stays green.

Write the line for the decisions

The move here is not more brand guidelines. You have those, and they are not the problem. The move is to give the decisions the same treatment you already give the marks. Write down what does not change, before you publish what does.

Call it the continuity line. It is short. Five things, not fifty. And there are three tests for whether what you have written is a line or a poster.

• It has to be losable. If holding it never costs you anything, it is not a line. "We put the customer first" costs nothing, and nobody has ever had to turn down revenue to hold it. Name the thing you would say no to. If you cannot point at a deal, a saving or a launch you would give up rather than break it, you have written a description. Descriptions do not survive a bad quarter. This is the test almost everything in the drawer fails, including work I am proud of.
• It has to be encounterable. Something a customer actually meets. A rule about how you say no. A response you always give, even when it is expensive. A cost you eat instead of passing on. A constraint you never engineer around. The element rules worked because they were physical and could not be fudged. The rest of the business has to reach the same hardness through behaviour.
• It has to survive your absence. Take what you have written to somebody who was not in the room and has no history with you. Hand them three live decisions from this week. If they cannot make the call you would make, the line is still in your head rather than on the page, and it will not reach the people who are making those calls without you.

That third test is the one the element rules passed and almost nothing else did. It is why they held for over fifty years while everything around them moved. Written well enough to be applied by strangers, which is the only kind of rule that outlives the people who wrote it. There is a second reason to write it down, and it matters more the further you sit from the top.

If you need the argument in a finance director's language, it is this. Drift is not paid for in affection. It is paid for in re-acquisition. You spend next year's budget re-explaining yourself to people who already knew exactly who you were, and you book it as awareness. It shows up in her plan long before it shows up in a tracker.

What proximity used to cover

There is a reason companies got away with this for so long.

The whole unwritten part ran on proximity. I absorbed it by being near people who already had it, for years, and then other people absorbed it from me. That worked because change was slow, and because most of what mattered still passed through a small number of hands. The line did not have to be written down, because the people carrying it were in the room.

That enforcement is gone. Decisions are made now at a volume and a speed no small set of hands can sit across, by people who were never in that room, and increasingly by systems that never can be. An unwritten line was survivable when drift took five years. It is not survivable when it takes five months.

Which raises a harder version of the same question, one floor down, and it is the one I want to take up next month. The unwritten part was never only about the brand. It was the judgement itself.

I got twenty-five years of proximity. Most of the people making these calls in your company this week will get eighteen months and a handover document. Proximity is not coming back, and nothing has been built to replace it.

So write the line. Something shorter and harder than a values document. The short list of things that do not change, specific enough that a stranger could hold them for you.

The only line that holds is the one that can kill a good idea.

Next month: AI is taking over the work that used to build people's judgement. Your team is getting faster by the week. What's quietly not being built while they do.

Sources

Building on

• Donella H. Meadows, Dancing with Systems (2001) — wisdom #8, "pay attention to what is important, not just what is quantifiable." The green-dashboard beat rests on it: the loss that matters is the one no instrument is pointed at.
• Tony Fadell on manufactured constraints (2026) — when the constraints are not given to you, invent them; the argument that a hard limit is what makes range possible rather than what blocks it.
• Unowned Work Is the Real Startup Killer (2026) by Katie Barnes — the general case of the failure this piece diagnoses in one domain: work that matters, that nobody is accountable for, gets done badly by everyone at once.

Early in my career, a leader I respected told me I was too polite.

The specifics were small. When I asked my team to do things, I said "please." To me this was basic courtesy. I'm a Finn, but I'd spent enough time in the UK by then that "please" was automatic. To this leader, who was Nordic, it was something else. Saying "please" turned an instruction into a request. It opened the door to discussion. It signalled that the team could say no. And in their view, that was a failure of leadership before you'd even started.

I understood the logic. If your model of leadership is that the leader decides and the team executes, then "please" is noise. It muddies the authority. It slows things down.

But I kept saying it, more on instinct than principle. Something about the alternative felt wrong for the team I was working with. These were smart, experienced people. A directive approach wouldn't have energised them. It would have shrunk them. They'd have done what they were told and stopped bringing what they actually knew.

What I was reaching for, without having the language for it yet, was partnership. It wasn't a flat hierarchy; I was still the leader, still accountable. But the stance underneath said: I trust you to think, and I want that thinking. My job was to create the conditions where it actually mattered.

The result was a team that stepped up, because they didn't want to let each other down.

I've thought about that conversation for twenty years. It stung, and that faded. What stayed was the line it drew between two fundamentally different ideas about what leadership is for.

From Framework to Floor

Last month I wrote about what lasting transformation demands of leaders: four dimensions that aren't personality traits but structural requirements.

1. Discovery over direction.
2. Protecting space.
3. Staying in tune.
4. Never done.

I meant every word. But frameworks describe the architecture. They don't tell you what it feels like to live inside it.

This piece is the companion. Same four dimensions, but seen from the ground, in daily choices, where nobody's writing a case study about you. Discovery as a leadership stance. Protecting space when it costs you something. Staying open when your experience screams otherwise. And the quiet proof that it's working.

Discovery as Partnership

The "please" conversation was my first brush with what I'd later call discovery over direction, before I had any framework to put it in.

Discovery, as a leadership practice, sounds like it's about asking questions. It is. But behind the questions is a stance: I need your judgement as much as your output. That stance shapes everything the team is willing to bring.

I've watched this play out dozens of times with strategy rollouts. A strategy gets set. Clear objectives, sound logic, well-governed execution plan. It cascades through the company. People get their briefs, their deliverables, their KPIs. They execute.

But nobody below the room where the strategy was made understands why it looks the way it does. They know what they're delivering. They don't know what was debated, traded off, weighed and rejected. So when something changes (the market shifts, a new constraint appears, an opportunity arrives that doesn't fit the brief), they escalate. They can execute the plan. They can't think with it.

Now compare what happens when the same team is involved in building the strategy. When they've wrestled with the trade-offs, heard the reasoning, tested it. Those people adapt without waiting for permission, because they understand the logic well enough to know what bending is acceptable and what would break something important.

The signal it's working? Someone disagrees with you because they've grasped the thinking well enough to see a flaw you missed. That's capability showing up as disagreement.

And the cost when it's missing isn't just frustration. A team that complies but doesn't think is a team that can't adapt when the world changes faster than the plan. At scale, that's a company that needs permission from the top to respond to what's happening on the ground. I've watched organisations lose months to that gap.

Different situations demand different approaches. Crisis needs direction, ambiguity needs exploration. But the default matters enormously.

What Protecting Space Actually Costs

If discovery is the stance, protecting space is what sustains it. And it's the dimension most likely to go wrong.

I once watched a leader try to protect their team the wrong way. They absorbed pressure from above. They deflected organisational noise, the politics, the posturing, the meeting about the meeting. The team operated in what felt like a bubble of calm.

But absorbing everything comes at a cost. Over time, the weight turned inward. The leader became resentful, and the target was the team, not the company above them. When progress was slower than expected, the frustration leaked out. Small comments. Implications that the team didn't understand how much pressure existed above them. Snipes at individual work that felt disproportionate.

The trust collapsed quickly. Team members started second-guessing themselves, presenting work with caveats and apologies before anyone had said a word. Two years of confidence, dismantled in a few months of doubt.

That collapse had a cost beyond the human toll. The team's best people started leaving, quietly updating their profiles and taking calls. The ones who stayed became risk-averse, checking everything with the leader they no longer trusted. Decisions that used to take a day took three weeks. A transformation that had been running ahead of schedule stalled, then slipped, then got quietly downgraded in the next board review. The budget wasn't cut. The ambition was, which is worse.

The leaders I've watched do this well make a different move. They sort the pressure instead of swallowing all of it. The politics and interference get filtered out. But the real challenges, the hard decisions, the problems the team actually needs to work through — those get let in. Deliberately. Because that's where judgement develops.

And then comes the part that's hardest to teach: not stepping in when you could. Watching someone head toward a mistake and holding your nerve. Not because you don't care. Because you care about what they'll be able to do next time, when you're not there.

The systems thinker Donella Meadows spent her life mapping how complex things work, and closed her best-known book on a quieter note: you can't control a system like that. You can only learn its rhythm and stop fighting it. She warned against being an unthinking intervenor. She isn't telling leaders to do nothing. The point is subtler: the urge to fix is often the thing that breaks.

Nicolai Tangen, who runs Norway's sovereign wealth fund, set his teams a hard mandate, then did the harder thing. He left them to find their own way there. That took more nerve than stepping in. Restraint with a spine. The direction was fixed. The route was theirs, and so was the learning.

When Experience Works Against Staying in Tune

Discovery and protected space create the conditions for thinking. But there's a trap that waits for leaders who've been sustaining those conditions for a long time, and it strikes at the third dimension, staying in tune.

You've seen a lot. You've been right often enough that your pattern recognition is fast and usually accurate. Someone brings you a problem and you can see the answer before they've finished describing it. Three times out of four, you're right.

So you stop listening early. You jump to the answer. You save everyone time by cutting to what you already know.

Here's the problem: the three times you're right, you've saved twenty minutes. The one time you're wrong, you've missed something that mattered, and nobody tells you, because you didn't create space for it. Your speed signals that the conversation is over before it started.

I've caught myself doing this. It's the moment when experience flips from asset to liability, when the thing that made you effective starts preventing you from seeing what's actually in front of you.

Last month I described staying in tune as building a self-correcting system: an organisation that calibrates whether or not a particular leader is asking. That's the structural goal.

The cost of getting this wrong goes beyond bad decisions. When the most experienced person in the room stops genuinely listening, the organisation loses its early warning system. The meetings still happen. The updates still flow. But the thinking moves out of the room, and the signals that something is changing reach the top last, not first.

The Quiet Proof

The fourth dimension, never done, is the hardest to write about, because when it's working you barely notice.

It doesn't look like a transformation. It looks unremarkable. That's the point.

A meeting where you haven't spoken in twenty minutes, and the conversation is sharper than anything you would have steered. Someone making a call you wouldn't have made, well-reasoned, and you leave it alone. A team member coaching a newer colleague not just on the task but on the thinking behind it: why we do it this way, what "good" looks like here.

The biggest signal? When you're not needed for something you used to be needed for. When a decision gets made in your absence and it's sound. When the principles you've spent years making explicit show up in someone's work who you've never directly managed.

That's proof of transfer, not lost control.

It happens gradually. There isn't a moment when you hand over the keys. There's a slow realisation that the capability isn't attached to you anymore. It's embedded in how they work.

That's the "never done" dimension made visible. The team absorbed it, and kept going. The leader never announced it.

If someone asked you "what is your team becoming?" this is what the answer looks like when it's working. Not a strategy document. Not a capability matrix. A room full of people making good calls without you in it.

What "Too Polite" Was Really About

The leader who told me I was too polite was solving for speed: a clean line between decision and execution. In contexts where that matters, they were right.

But I was solving for something else, even if I couldn't have said it then. A team that would still be working well after any one of us left. People who would think with me and own the reasoning. Capability that would compound rather than deplete.

That's the hardest thing leadership asks. And it's the only thing that lasts.

Last month I explored what transformation demands of leaders. This month I've tried to get closer to the ground. Next month, I turn the question outward: how a brand can hit every number and still lose the people who used to care, long before anything shows up on a dashboard.

Sources

• Donella Meadows, Thinking in Systems (2008): the closing "Living in A World of Systems" chapter, on why a complex system can't be controlled, only tuned. The root of the restraint argument here. (link)
• Amy Edmondson, The Fearless Organization: the conditions for honest challenge this piece treats as necessary but not sufficient. (link)
• Aswath Damodaran, "An Ode to Restraint: Lessons from the Tim Cook Legacy at Apple." (link)
• Tony Fadell on manufactured constraints (General Magic). (link)
• Nicolai Tangen, Norges Bank Investment Management: a fixed mandate, then autonomous teams left to deliver it. (link)

I sat in on a team meeting eighteen months after a leader I admired had left.

The weekly check-in still ran at the same time, same room, same agenda. People showed up. Updates were shared. But something had gone. The meetings used to crackle: challenges got raised, assumptions got tested, someone would push back and the whole room would lean in. Now it was a status report. Smooth, polite and – empty.

Afterwards I asked a new hire why they did things a certain way. She shrugged. "That's just how it was set up."

She didn't say by whom. She didn't know. The rituals were still running but the thinking behind them had gone. Nobody on that team could feel the difference. They thought this was what the leader had built. They had no idea what they'd lost.

The leader who'd left was brilliant. Trusted. Self-aware. She'd read the research on psychological safety and lived it. People had spoken up in her meetings. They'd challenged each other. They'd brought bad news early. By every measure the transformation was working while she was there. Engagement scores were up and the Board was pleased.

I've watched this happen four times. Different companies, different sectors. Always the same arc: a leader does everything the books say. Builds trust. Creates safety. Delivers results. Leaves. And within eighteen months, the whole thing quietly unravels.

Not because they failed at leadership. Because leadership alone was never going to be enough.

Three Camps, One Missing Question

When transformation fails, the post-mortem usually falls into one of three camps.

• Camp 1: The strategy was wrong, or the execution was. Get the strategy right, govern it tightly, and change will follow. There's real substance here. I've watched transformations collapse because nobody could articulate what they were actually trying to achieve.
• Camp 2: The leaders weren't ready. This is where most energy has gone in the past decade. Amy Edmondson's work on psychological safety. Trust, vulnerability, emotional intelligence. I've watched transformations fail because leaders couldn't create the conditions for honest conversation.
• Camp 3: Nothing was built to last. No infrastructure. No transferable principles. No systems that work without their creators. This is the territory I've been writing about for the past five months: the departure test, the difference between rented and built capability.

Each camp is right about what it diagnoses. But each tends to treat its answer as the answer. Fix the strategy. Develop the leaders. Build the systems. As if the problem were a single missing ingredient.

The question that matters: how do these building blocks fit together in a way that creates lasting capability?

Good strategy doesn't remove the need for good leadership. Good leadership doesn't remove the need for good infrastructure. And infrastructure doesn't replace either, it's what connects them and makes them persist beyond the people and the moment.

If you're leading a marketing function through AI adoption, you're living all three camps at once. Your board wants the strategy. Your team needs the leadership. And the infrastructure question: can your people make good judgement calls at scale, without you in the room, is the one nobody's asking. I wrote earlier this year about what happens when teams lose the work that taught them to think. People freeze. Not because they lack ability, but because nobody built the infrastructure for the decisions that remain when the intelligence layer is automated. That freeze is a leadership problem as much as a structural one.

This piece turns to leadership because leadership is where the three camps either connect or fall apart.

Two Questions About Leadership

Within the leadership conversation, there are two questions. Most of the books, programmes, and keynotes address only the first.

• Question 1: Can you lead people through change? Build trust. Create safety. Model vulnerability. And develop your people.
• Question 2: Can you build something that works without you? This is the question that determines whether your transformation was a moment or a capability. Whether you led people through change, or built something that keeps changing after you've gone.

Question 1 without Question 2 produces heroic transformation. Change that depends on the presence of exceptional leaders. It looks like success right up until those leaders are no longer there.

Question 2 without Question 1 doesn't work either. Infrastructure built without trust is just machinery. People comply with it rather than own it. It becomes bureaucracy, not capability.

The leadership that builds lasting capability addresses both questions together. Both at once. Two sides of the same practice.

What Lasting Transformation Demands

After 25 years watching change efforts succeed and fail, I've come to see four things that lasting transformation demands of leaders. Requirements, as structural as anything in the methodology I've written about earlier in this series.

Each one operates at two levels, human and structural. Neither works without the other. The human dimension without the structural creates dependency on exceptional leaders. The structural without the human creates systems nobody believes in.

1. Discovery Over Direction

Leaders who ask questions rather than pronounce answers build trust. They signal that other people's knowledge matters. They create the conditions Edmondson describes where people can contribute without fear.

But discovery does something else. Principles that emerge through collective exploration are owned by the people who surfaced them. They're not the leader's vision, handed down. They're shared understanding, built up. When that leader leaves, the principles stay, because they were never "theirs" to begin with.

I watched it most clearly during the LEGO turnaround in the early 2000s. The new CEO, Jørgen Vig Knudstorp, later reflected: "I wasn't competent for the role, so instead of telling people what to do, I asked questions and focused on getting to the source of truth." That sounds like weakness. But the principles that emerged from those questions still guide it two decades later. They lasted because they were discovered, not decreed.

Most leadership development trains people to be better at giving direction: clearer vision, stronger communication, more compelling storytelling. All valuable. But without the infrastructure to capture and embed what discovery surfaces, even brilliant discovery fades when the leader who facilitated it moves on.

What transformation demands isn't direction or discovery. It's discovery that feeds into systems explicit enough to outlast whoever did the discovering.

2. Protecting Space

This one is easy to misread. It's easy to hear "protecting space" and picture a leader who shields their team from hard questions, absorbing pressure from above, deflecting organisational noise, keeping people comfortable so they can focus.

That's not what I mean. Or rather, that's only half of it, and the half that doesn't build capability on its own.

The leaders I've watched do this well make a distinction. They remove the wrong pressures: the politics, the interference, the meeting about the meeting, the noise that burns energy without building anything. But they don't remove pressure altogether. They make room for the right pressures, i. e., real decisions with real stakes, problems their people need to work through, consequences they have to own.

And then comes the harder part: not stepping in.

Jørgen described this as: "Many of the things happened because I didn't stop them." Not delegation, but something subtler. The restraint of not intervening when you could. Trusting that the person heading toward a mistake might learn more from the stumble than from your correction.

This is the opposite of mollycoddling. The leader clears the path so their team faces genuine challenges and then resists the urge to solve those challenges for them. That's what develops distributed judgement. Not comfort. Exposure to the right kind of difficulty, with the space to work through it.

The structural question is whether those conditions hold when the leader who created them is gone. Does the team keep wrestling with hard decisions? Or does it wait for someone to either shield them or tell them what to do?

3. In Tune, Not Right

Leaders who seek feedback, who model vulnerability, who admit when they're wrong, create conditions for learning. Edmondson's research shows teams where the leader says "I might be wrong" outperform teams where the leader needs to be right.

But "in tune, not right" does something beyond creating a learning culture. It's the only honest response to the kind of system you're actually leading. Every decision you make changes the system you're deciding in. Restructure a team and the culture shifts. Introduce a process and people adapt around it. The ground shifts underneath you, partly because of what you built on it last quarter. In a system like that, "right" is always temporary. The only sustainable posture is continuous calibration.

A leader who says "tell me when I'm out of tune" is building a culture of continuous adjustment, what I've called Type 0 calibration in earlier pieces. The human dimension creates safety to speak up. The structural dimension turns that into a self-correcting system that keeps calibrating whether or not a particular leader is asking.

Jørgen, reflecting on his own leadership: "I don't want to be right, but I want to be in tune. What I want is for people to tell me when I'm out of tune, unfiltered."

Self-awareness is a personal quality. It leaves with the person. The structural question is whether you've built an organisation that self-corrects, not because one leader is unusually open to feedback, but because the system expects and enables continuous adjustment. Build the second while you still have the first.

4. Never Done

Leaders who stay open to learning, who resist the temptation of "we've figured this out", help their teams adapt. Growth mindset, in the popular framing.

But "never done" has a structural implication that goes beyond any one leader's posture. A leader who embodies this builds an organisation that expects and welcomes ongoing tuning, rather than waiting for the next transformation programme.

"There was never a moment when everything worked." That's not a confession of failure. It's a design specification. The system is never finished. Calibration is the permanent state, not the gap between one stable period and the next.

Most organisations treat change as episodic: a disruption to be survived, then a return to normal. Leaders who live "never done" build something different: teams that treat adjustment as the normal state. Good programme management keeps the discipline of that adjustment going: tracking, reviewing, course-correcting. Leadership sets the expectation. Infrastructure and execution make it real.

What transformation demands isn't just a leader who keeps learning. It's connecting that learning orientation to systems and disciplines that keep the organisation learning, with or without any particular leader in the room.

What Creates These Leaders

Jørgen didn't choose intellectual humility as a leadership style. He was forced into it. He genuinely didn't have the answers. The discovery orientation that built lasting capability wasn't a technique: it was the only honest option available.

The pattern holds across 25 years. A crisis that stripped away the option of pretending to know. A role they weren't qualified for. A situation where the old playbook didn't work.

So if these capabilities are often produced by circumstances most leaders don't experience, what fills the gap?

One answer: the methodology can create the conditions the crisis created by accident. When the 4Es requires leaders to explore before prescribing, they practise intellectual humility whether it comes naturally or not. When experimentation demands comfort with real ambiguity, where some hypotheses don't survive, leaders develop that comfort through doing, not training. The methodology doesn't wait for the right leaders to arrive. It creates the conditions that develop the capabilities it requires.

That doesn't mean it's easy. There's another condition that rarely gets discussed: tenure.

Game theorists call it the shadow of the future.

Short-tenure leaders, the ones who know they'll move on in two or three years, can afford heroic transformation. The gains show up on their watch; the depreciation shows up on someone else's.

Long-tenure leaders can't do this. Every shortcut catches up with them. Every dependency they create becomes their problem. Every capability they fail to transfer means they're still the bottleneck in year five, year ten, year fifteen.

Jørgen mentored me for six years. The line he gave me was: "Never take shortcuts. Even if you get away with it, you'll know." That's the shadow of the future made personal. Not just strategic calculation — integrity. The refusal to build something that works only while you're watching.

This isn't an argument against mobility. It has implications for how boards think about leadership continuity during transformation. But that's a conversation most governance structures aren't designed to have.

The Departure Test, Applied to Leadership

Here's what I've come to see, and it's not easy to say: the leadership qualities that make transformation feel successful in the moment can actually prevent lasting capability if the leader doesn't deliberately build for their own absence.

A deeply trusted, emotionally intelligent leader who personally holds the system together is, structurally speaking, a single point of failure. The better they are at Question 1, the more invisible the Question 2 gap becomes. Everyone feels the transformation is working. Nobody notices it's working because of one person.

When you leave, not if, but when, what principles did you make explicit enough that someone who never met you could apply them? What capability did you transfer so thoroughly that your team can teach it to people who haven't joined yet?

But there's a harder version of the test. It's not enough to lead this way yourself. The question is whether your direct reports lead this way with their teams. Whether the person two levels down experiences the same discovery, the same space to wrestle with real decisions, even though they've never met you. Because the leader between you and them absorbed these practices as their own.

That's the real departure test. The capability doesn't just survive your absence. It reproduces.

This requires you to systematically reduce your own importance. Every principle you make explicit is one less thing that depends on your judgement. Every capability you transfer is one more step toward making yourself unnecessary. This runs against everything leaders are trained and rewarded for. Organisations promote people who are indispensable.

The departure test doesn't care how brilliant you were. It only asks what you left behind.

Over the past six months, I've built a framework for understanding what makes change last: the diagnostic, the methodology, and now the leadership dimension. Next month, I want to get closer to the ground: what it actually looks like when leaders do this well. Not the theory. The practice.

Every transformation kickoff I've sat through has the same shape. A sharp diagnosis on screen, a compelling case for change, senior people nodding, the board behind it, the budget approved. The mood is serious but settled — everyone knows what we're solving for.

Then comes the question that lets the air out: what do we actually build?

The silence isn't because people lack ideas. It's because the ideas are all tactical. A new process to follow, a specialist to bring in, a platform to stand up. Each one sounds right. None of them answer the question underneath: what infrastructure would let this company make good decisions at scale, without depending on any specific person, tool, or platform to hold it together?

There's no shortage of thinking about what's wrong with transformation. There's a near-total absence of a process for what to build instead.

Here's mine: the 4Es. Explore, Experiment, Envision, Enable. Refined through failure, proven by what lasted after I left.

It works for building any capability that needs to last: AI adoption, brand coherence across thirty markets, post-merger integration, innovation infrastructure. The domain changes. The process doesn't.

Why Most Methodologies Fail

Most transformation methodologies assume you already know what to build. The methodology is the project plan.

That's fine for problems where the rules don't change as you work on them. Building capability that lasts is a different class of problem. The people inside the system learn, adapt, and respond to what you build. Infrastructure that enabled capability at 500 people might create bureaucracy at 5,000. The principles that guide a design-led company won't transfer to an engineering-led one.

The process is rigorous and transferable. The outputs (the specific principles and infrastructure) are context-specific. That's not vagueness. Importing someone else's answers is precisely why most transformation fails.

There's another reason. Three assumptions the old transformation proposition rested on are under pressure at once.

• The first is that you can diagnose from what gets reported up. In any organisation at scale, the information reaching leadership has been filtered, translated, and shaped for consumption. What people say they do has drifted from what they actually do, and the drift widens with every layer between you and the work. Shared ground has to be seen, not reported.
• The second is that intelligence, properly applied, produces sound judgement. Research on how smart people actually reason keeps finding the opposite: cognitive ability and judgement are decoupled. Clever people aren't reasoning their way to better answers. They're building better arguments for the answers they already had. Intelligence dresses up the instinct. It doesn't override it. Judgement comes from somewhere else: structured feedback under consequence, applied repeatedly, until pattern recognition stops being theoretical. That can't be hired in. Though that's rarely why expertise gets hired anyway. Boards prefer to hear bad news from a stranger, not from the people who've been delivering it for two years.
• The third is that good people can overcome a mediocre system. What Moneyball did to baseball, Google's Project Aristotle did to this one. Across 180 teams, the strongest predictor of performance was how the team was structured and how it operated. Systems dominate talent at scale. A good system makes average people capable. A bad one wastes exceptional ones.

Methodologies built on those three assumptions (gather the facts, apply rigorous logic, deploy the best talent) can't keep up.

Why these four

This is what the 4Es is built for.

Explore has to get close enough to actual work to see what's true, because what people report about how they work is no longer a safe starting point. Experiment tests under real consequence, which is how judgement gets built when it can no longer be hired in. Envision designs the system: principles, scaffolding, finite rules for infinite expression. Capability at scale is a property of systems, not of the brilliant people staffed into them. And Enable transfers what you've built, so the capability outlives the people who built it. Without that transfer, the other three revert the moment attention shifts.

Explore: Discovering the Context

Exploration means understanding what principles actually guide decisions versus what's written on walls. Observing how people operate under pressure, not in workshops. Mapping where capability already exists but can't be used, and what blocks it. Noticing workarounds, because workarounds are where the infrastructure gaps live.

The principles you need to scale are usually already in the building. They're just locked in people's heads. Exploration makes them explicit.

It also surfaces something at risk of being lost: what the company already knows about its customers, its market, its craft. Knowledge that's tacit, distributed, and in danger of disappearing as AI handles the work that used to generate it. Exploration captures that knowledge before the accidental learning path goes away.

When we built a marketing experimentation capability, I spent five weeks watching how decisions actually got made. Not the process on paper, the real one. Where did intuition override evidence? Where was evidence ignored because the political cost of being wrong was too high? Two things surprised me. The appetite for experimentation was higher than leadership assumed. People were quietly running their own tests, but without shared language, the learning stayed local. And the biggest barrier wasn't resistance. It was that nobody had asked these people what they already knew about what worked.

For leaders, this phase demands intellectual humility. Genuinely not knowing. A turnaround I witnessed started this way. The new leader later said: "I wasn't competent for the role, so instead of telling people what to do, I asked questions." The principles that emerged still guide that company two decades later. They lasted because they were discovered, not decreed.

Experiment: Trying What Might Work

Exploration produces hypotheses about what infrastructure might work in this context. Hypotheses need testing, not in theory but on real work with real stakes.

This phase tries approaches and keeps only the ones that produce the intended outcome. Not "does this tool work?" but "does this approach build capability that transfers?" That question changes what you measure. Effectiveness matters. But so does whether the people involved are becoming more capable or more dependent.

A distinction matters here that most companies miss. Experimentation is not piloting. Pilots are open-ended. They run until someone decides they've proved the concept, or until attention shifts. The learning is incidental. Real experimentation is designed to end. It has a thesis, a timeframe, and a clear definition of what success looks like. If the experiment can't tell you what the wider company should do differently, it was never an experiment. It was a demo.

In the experimentation build, we tested three infrastructure designs with pilot teams on live campaigns. Real budgets, real stakes. Two failed. The first was too heavy: people spent more time on the process than the thinking. The second was too threatening: it surfaced decisions senior people had been making on gut feel, and the transparency felt like exposure. Those failures taught us more than the success. The pilot that worked was the one where the team said "this is just how we should be working." A way of thinking embedded in what they already did.

Envision: Designing What Scales

With evidence from exploration and experimentation, you can design the infrastructure that enables capability at scale. Not before. Designing before you've explored and tested is how you get 200-page playbooks nobody opens.

This phase creates what I call "finite rules for infinite expression": infrastructure that bakes in principles while preserving flexibility. Think about grammar. Finite rules, infinite expression. Grammar doesn't constrain language; it enables it.

The design question is always: what's the minimum structure that enables the most distributed judgement? Governance that's simpler than the problem it governs doesn't produce control. It produces friction. Over-specification doesn't help either. Every additional rule is a bet that you can predict the future. Principles are the opposite bet: that you can't predict the future, so you build the capacity to respond to whatever arrives.

This is where most capability work goes wrong. A three-level structure helps:

• Purpose principles: why we exist. Change rarely. These are the stable ground everything else stands on. Also useful for specific functions, not only at company level.
• Operating principles: how we work. Guide daily decisions. Most companies and functions skip this level entirely, which is why people escalate decisions they should be making themselves.
• Craft principles: what good looks like in specific work. The layer almost no company has spelled out clearly enough to scale. It's where onboarding breaks down and quality becomes inconsistent. And it's the layer that determines whether AI helps or hollows out your team. When a marketer uses AI to generate a brief, what tells them the output is good enough? Not the tool. The principles they've absorbed about what a good brief looks like. Without craft principles, AI produces faster mediocrity.

In the experimentation build, we designed the lightest possible infrastructure. Principles for what makes a good experiment: a way of thinking. Templates that guided without constraining. A peer review mechanism where marketers challenged each other's test designs, which did something no training could: it built shared judgement through practice. Purpose principle: "we test because learning compounds and guessing doesn't." Operating principle: "every test has a hypothesis written before it runs." Craft principle: "a good experiment tests one variable; the control must be real, not assumed."

Would a smart person joining the team six months from now be able to use this infrastructure to make good decisions without asking the people who designed it?

Enable: Where Half-Life Gets Built

The final phase is transfer.

Training teaches people what to do. Transfer builds their ability to figure out what to do when nobody's told them. The distinction matters because most transformation fails right here: the consultants leave, the project team disbands, and everything slowly reverts.

What makes reversion harder is capability that's been genuinely absorbed, not enforcement. The people closest to the work don't just use the infrastructure. They own it, adapt it and teach it to people who arrive after the builders have gone.

In that build, transfer took eighteen months. Early adopters became teachers, not because we asked them to, but because the methodology let them. The central team shrank deliberately. We measured one thing: how often teams consulted us. When we went two weeks without a question, that was progress. But that wasn't the moment I knew transfer was real.

The moment was a phone call. A marketer in a market our programme had never reached asked me about our test design principles. Not because anyone had told her to, but because a colleague in another team had taught her. That colleague had learned from someone who'd been in one of the original pilots. The knowledge was three handshakes from anyone on the original team. Nobody in the chain had been asked to spread it. The infrastructure had created the conditions, and the capability travelled on its own.

I've written before about the business results this build produced: 16 million DKK invested, 300 million DKK in incremental sales in year one. That ratio won't transfer to every context. It's shaped by the operating base it sat on top of and the category reach already in place. What does transfer is the pattern: a small, disciplined capability investment unlocking compounding value across a much larger operating base. In this case, the programme was killed in a restructure. The capability didn't notice.

This phase demands something most leaders resist: letting go. Making yourself unnecessary.

How long should you expect the whole thing to take? Longer than you'd like. It varies with the size and complexity of what you're building into. The signal is always the same: a team that keeps moving after the builders are gone.

When the 4Es Fails

The methodology can fail. Five ways:

• Performative exploration: discovery motions that validate what leadership already decided.
• Rigged experimentation: pilots designed to succeed rather than learn.
• Over-engineered envisioning: writing process where principle was needed. Infrastructure so detailed nobody uses it.
• Rushed enabling: launching before capability transfers.
• And the subtlest: leadership that can't let go. Everything else works, but the builders can't stop being needed. The system works as long as they're there. Which means it doesn't work.

Each failure mode maps to a leadership capability: intellectual humility (Explore), comfort with ambiguity (Experiment), principle-based thinking (Envision), letting go (Enable). These aren't personality traits you either have or you don't. They're practices that develop through doing the work. The 4Es creates the conditions for leaders to develop the capabilities it requires, rather than waiting for the right leaders to arrive.

The Evidence Question

Norway's sovereign wealth fund offers a public proof point. Their April AI summit showed the 4Es playing out live at $1.8 trillion scale. They explored first: insourcing their data and building a single data foundation before touching AI. They experimented with small autonomous teams of two developers and one business person, no ceremonies. They envisioned infrastructure, not tools: a governance framework that translates principles into daily practice, and an Investment Simulator that surfaces portfolio managers' behavioural blind spots rather than telling them what to trade. And they enabled by training everyone in AI and through a volunteer Ambassador Network working with each team to find the specific pain point, where AI could help them and hold the work inside the governance principles already set. The CEO's mandate was non-negotiable. The ambassadors made it real. Over half the organisation now writes its own code. If the people who built this left, would it keep working? The structure says yes. Time will test it.

I don't have a controlled study across dozens of companies. What I do have is a 25-year pattern inside one large company across six radically different domains: physical product, consumer experience, digital transformation, sustainability, diversity and inclusion, and marketing experimentation. I've detailed the results and the structural reasons they lasted in earlier pieces. Apply the departure test to your own past investments. Look at transformation budgets from the past five years. How many built capability that persists today?

If the answer is "not many," something different is needed. The 4Es is my take.

Continuous Calibration

The 4Es isn't linear. Exploration shapes experimentation. Experimentation sends you back to explore. Enabling exposes the next thing to envision.

Beneath all four phases runs continuous calibration: the ongoing micro-adjustments that keep infrastructure alive. There's never a moment when everything works.

Regenerative transformation isn't "build then done." It's "build capability for continuous calibration."

Build what doesn't need you.

Next month: what this methodology demands of leaders — and why the qualities that make transformation succeed are often produced by circumstances most leaders don't experience.

I had dinner recently with a room full of senior marketers. Smart people. Big brands. The conversation was sharp, fast, and almost entirely about tactics.

Which platforms. What formats. How to win the algorithm. Who to hire. How to outsource faster.

Nobody asked the question underneath: what happens when the platform changes again? What have you actually built?

It wasn't a bad conversation. These are real problems, and the people in that room were solving them well. But there was a gap between the quality of the diagnosis and the depth of the response. I keep seeing it in how large companies respond to structural shifts. They see the change clearly. They respond to it intelligently. And the response never quite reaches the level the problem demands.

That gap matters. Because right now, three forces are converging that change the shape of the problem entirely.

Three shifts, one pattern

Social collapsed the funnel first. Someone sees a product in a TikTok comment, checks the brand on Instagram, reads three reviews on Reddit, and buys through a link in someone else's story, all before the brand team knows it happened. Discovery, research, service, and purchase happen in a single interaction. The model where brand lives with a creative agency, performance with a media agency, and social with the digital team no longer maps to how people actually experience you.

AI is collapsing it further. Conversational AI sits in the middle of this blurred funnel. When someone asks ChatGPT or Gemini for a recommendation, they skip the awareness stage entirely. They don't visit your website. They don't see your ads. They get an answer, and if your brand isn't part of that answer, you don't exist.

After ChatGPT launched, Stack Overflow traffic plunged. AI could replace pure information-seeking. Reddit held steady. Community and lived experience can't be replicated. The same logic applies to brands. Anything purely informational is vulnerable. Anything built on judgement, relationship, or genuine experience is defensible.

And the horizon that makes both of these shifts urgent rather than gradual: the customer may not be human. AI agents are beginning to make purchasing decisions, not just recommendations but actual transactions. When the customer is a machine, the rules change entirely. Your content, your product information, your brand presence all now serve two audiences. One human, one machine. Built for different logics. Evaluated by different criteria.

"Bot psychology" is already a field. This isn't guesswork anymore.

The tactical trap

The diagnosis behind these shifts is excellent. Senior marketers understand that social has changed the game. They can feel that AI is shifting how people find brands. The smarter ones are already thinking about AI agents. Stefano Puntoni (HBR) published a sharp analysis recently of how conversational AI and AI agents are reshaping marketing, then closed with the most important line in the piece: "Treat this as a leadership issue, not a marketing-department problem." The diagnosis was right. Every recommendation that preceded it was tactical.

A separate HBR study of 35 senior leaders found that 93% identified "human factors" as the primary barrier to AI adoption. That framing tells you where the thinking stops. "Human factors" is what people say when they can see the problem is about people but can't name the structural gap underneath. The issue isn't the humans. It's that nobody has built the infrastructure for humans to operate in.

And that's the pattern. In every case, the response is the same.

• Social collapsed the funnel? Hire a social agency. Build a content studio. Outsource to someone who knows TikTok.
• AI is displacing search? Build Generative Engine Optimisation (GEO) capability. Hire an AI consultant. Optimise your structured data.
• AI agents are becoming customers? Study bot psychology. Restructure your metadata. Prepare for machine-readable commerce.

None of these responses is wrong. You probably do need a data scientist. You probably do need someone who understands GEO. The problem is what happens after the hire. In most companies, the specialist delivers. They run the analyses, build the models, handle the work that nobody else can do. The capability stays in their head.

There's a useful way to see why these responses keep falling short. Sequoia Capital published an analysis recently that splits professional work into two types: intelligence and judgement.

• Intelligence work is rule-based. Complex, skilled, but the rules are rules. Campaign setup. Performance reporting. Audience segmentation. Media buying.
• Judgement work is what sits above the rules: deciding what to test, reading what the data means, knowing when to hold a brand position and when to shift.

Every one of those tactical responses is an intelligence-layer fix. Hire someone who knows the rules of TikTok. Buy a tool that handles the rules of GEO. Outsource the rules of machine-readable commerce.

The problem is that AI is coming for the intelligence layer faster than most marketing leaders have grasped. Software engineering crossed the threshold first. Over half of all AI tool usage across professions sits in that one field. Every other field is catching up. Within the next year or two — faster in some categories, slower in others — most of the intelligence work a marketing team does today will be handled by tools that are faster, cheaper, and more consistent than any team. Campaign optimisation, content production, performance analytics, media buying within set parameters. The tools already exist. Adoption is the only variable.

So here is the question nobody at that dinner was asking: when the tools handle the intelligence work, what happens to the judgement?

The gap that opens

Most marketing teams have never had to answer that question, because the intelligence work and the judgement work were tangled together. When your team spends weeks building a campaign, they learn things along the way. What the audience responds to. How the creative lands. What the data suggests about the next move. The doing teaches the thinking. Slowly, unevenly, but it happens.

When AI handles the doing, that accidental learning path disappears. The team gets the output without the process. They get the answer without the working. And working is where judgement develops.

Ask a CMO what their team will do with the time AI frees up and the answer is always the same: strategic thinking, creative experimentation, brand building. The reality, in most companies I've watched adopt new technology, is different. People freeze. Not because they lack ability, but because their professional identity was built on being excellent at things machines now handle. Or they fill the time with more of the same work at lower resolution. Or they defer to whoever is loudest in the room, because nobody has built the infrastructure for making strategic calls at scale.

This is the part that should worry CMOs more than any platform shift.

Not because the people are worse, but because the thing that taught them to think has been automated out of their day.

I watched it happen when marketing automation arrived. A team I worked with got a system that could test and optimise at a speed they'd never had before. Within a year, they were running more tests than ever and learning less from each one, because nobody had built the thinking infrastructure around what to test or what the results meant. The tools got better. The decisions didn't.

The cost of that gap doesn't show up in any quarterly report. It shows up as teams that are efficient but directionless. Marketing functions that produce more content than ever and build less brand equity than ever. Decisions that get made by default rather than by design, because the people closest to the work have the tools to execute but not the infrastructure to decide.

And here's the competitive version of the problem: the company that builds judgement infrastructure will compound what it learns from every AI tool it deploys. The company that doesn't will buy the same tools, run the same campaigns, and wonder why nothing accumulates. Same spend. Widening gap.

What this actually demands

Small companies and social-native brands don't have this problem. When you're twenty people, everyone already operates across the full funnel. There's no gap between brand and performance because the same person does both. There's no handoff between social and customer service because they sit at the next desk. And there's no shortage of judgement because everyone is close enough to the work to develop it naturally.

But as companies grow, they specialise. They fragment into departments. They build depth (which is valuable) but lose the horizontal integration that made them agile when they were small. By the time you're a thousand people, brand, performance, service, and commerce live in different teams, different agencies, different reporting lines. The ability to hold it all together doesn't exist in any one place.

The convergence exposes this fragmentation. It demands the agility of a startup at the scale of a multinational. No amount of tactical hiring or outsourcing solves that, because the gap isn't in any single function. It's between all of them.

You can't workshop your way to distributed judgement. It has to be built as infrastructure: principles clear enough that people across the company can make good calls without waiting for the expert to weigh in. I wrote last month about why most approaches to this don't scale – and what the ones that do have in common.

That's what "treat this as a leadership issue" actually means. Not that the CMO should pay more attention to AI, or that the board should add a digital agenda item. It means building the judgement infrastructure that lets a thousand people make good decisions in situations nobody designed for, and keep making them as the ground shifts again.

The uncomfortable question

There's a test I keep coming back to: does what you've built keep working when the builders leave? Here, it applies with a twist. The question isn't just whether the capability survives the departure of the people who built it. It's whether it survives the departure of the platform it was built for.

Most tactical investments fail that test. What was built for social doesn't hold for AI. What was built for AI won't hold for whatever comes after. If the capability can't flex, it was never infrastructure. It was a workaround with a shelf life.

These aren't three separate challenges. They're three symptoms of one structural shift: the marketing operating model that most large companies have run for twenty years no longer maps to how value is created. The temptation is to respond to each one individually, a social strategy, an AI strategy, a GEO strategy, each with its own team, agency, or consultant.

That's rebuilding. Starting from scratch each time the ground shifts, because nothing from the last round was designed to flex. The alternative is calibration: infrastructure that adjusts rather than breaks when the context changes. The point isn't whether you'll keep transforming. It's whether you're building something that calibrates or something you'll have to replace in three years.

If you're on a board or running a marketing function, there's a version of this you can test on Monday morning: ask your team what they'd do differently if every piece of intelligence work they do today were automated by September. If the answer is "more strategic work" but nobody can name what that means in practice, you've found the gap.

And if you get different answers from your board, your executive team, and your marketers, you've found the gap before the gap.

The tools are about to get very good at the intelligence work. The question is what your team is becoming.

There's a powerful case for treating tactics as strategy.

Move fast. Be native to every platform. Produce at volume. Win the algorithm. Some of the most influential voices in marketing argue that this is the work, that speed and platform fluency matter more than grand strategic frameworks. And for some companies, they're right. Social-native brands, lean startups, small teams where everyone holds the whole brand in their heads can operate this way and win.

The problem is what happens when you try to run that playbook at scale.

A few weeks ago, I was talking with the CEO of a creative agency that's increasingly moving into strategy work. She mentioned something that stopped me: many of the companies she works with have absorbed the tactics-first mindset completely. They're not unsophisticated. They're executing well, fast content, sharp creative, native to every platform. But there's no accumulation from one effort to the next. No principles guiding what it all should express. No foundation underneath the speed.

When you're twenty people, you don't need that foundation. Everyone already knows what the brand stands for. The founder is in the room. Coherence is automatic.

When you're a thousand people across thirty markets, it isn't. You fragment. The tactics stay sharp but they disconnect from each other. Speed without coherence. Volume without accumulation. And then surprise when the brand doesn't compound.

That's the first version of a pattern I keep seeing, but it's not the only one. More sophisticated companies fall into more sophisticated traps. And all of them share the same underlying flaw. I'm using marketing as the lens here because it's where the pressure is most acute right now (the agency restructurings, the arrival of AI, the collapse of old models). But the pattern runs deeper than marketing.

Four Approaches That Don't Scale

Execution without architecture. In marketing, this looks like the tactics-first mindset: fast, native, high-volume execution. Works brilliantly at small scale. Breaks at large scale, because coherence can't be maintained through proximity when the team spans continents and the brand touches a thousand different contexts every day. There's nothing to build on.

The false trade-off. More sophisticated. In marketing, it shows up as the brand-versus-performance debate: recognition that brand building and performance marketing serve different purposes, one creating demand and the other harvesting it. But the pressure to prove ROI pushes budgets toward what's measurable. Short-term activation wins; long-term brand gets starved. You're perpetually harvesting demand you never built, and eventually the field runs dry.

The tool trap. New martech stack, new data platform, new AI tools. It feels like progress. But this is where the most money gets spent and the least value gets built. Early adopters figure out how to make the tools work. Results improve, for a while. Then those people move on, the consultants finish their engagement, and the gains erode. Training doesn't fix it. It just moves the dependency from the vendors to the people who got trained. When they leave, the capability leaves with them.

Rented expertise. The most sophisticated of all, and the hardest to see. You diagnose a capability gap correctly. You hire the right agency, bring in the right consultant, build the right specialist team. The response is smart, targeted, effective. But the capability concentrates in the specialist rather than spreading across the company. When the engagement ends or the team disbands, the ability to operate goes with them. The company felt modern and proactive. It never learned to do it itself.

Four approaches. Each more advanced than the last. None of them scale.

If you're not in marketing, you've still seen this pattern. Swap "brand" for "sustainability" or "AI adoption" and the four approaches look exactly the same. The ingredients change. The trap doesn't.

This is the pattern I named last month: most strategic investments depreciate. The investment was real; the return was rented, not built.

What Scales Instead

None of the four approaches are wrong. You need execution speed. You need to navigate the trade-offs. You need good tools and specialist knowledge. The problem isn't any single ingredient — it's treating each one as sufficient, or pursuing them in isolation. Without principles connecting them, every investment depreciates on its own.

I learned this the hard way. Years ago, I led work on how sustainability shows up in our brand — the communications, product design, packaging, retail experience, the whole system. The easy path would have been training. Workshops for designers. Sessions for retail teams. It would have worked locally, but it wouldn't have scaled. Every new hire, every new market would need the same training. And when trained people moved on, the understanding would leave with them.

Instead, we built principles specific enough to guide choices: what sustainability means for a product designer making material decisions, for a retail team designing store experiences, for a customer service rep answering environmental questions. Not "here's what sustainability means" but "here's how to make sustainability-consistent decisions in your context."

Training would have created 500 people who understood sustainability. Infrastructure created a company that makes good sustainability decisions, including people who joined years after the work was done and never attended a single workshop. If you've led transformation at any scale, you've seen both versions. The second is rarer. And you can feel the difference the moment you walk into the room.

A caveat: infrastructure isn't automatically good. The wrong infrastructure (rigid processes, outdated principles, systems that encode yesterday's thinking) can prevent transformation rather than enable it. "We've always done it this way" is often infrastructure speaking. The question isn't whether you have infrastructure. It's whether it enables judgment or boxes it in. Rules that box people in go stale the moment the context changes. Principles that enable judgment flex across situations they were never designed for.

This is where the departure test — which I explored in depth last month — becomes practical. If the people who built it left tomorrow, would it keep working? If it's enabling judgment, it'll survive the departure. If it's boxing people in, it was never really infrastructure. It was someone else's decisions disguised as a system.

From Sitting Up to Running

It starts with sitting up. The basics are documented. Rules exist. Without them, chaos. But rules don't scale because every new context needs someone at the centre to translate. Tools are present but disconnected from any shared logic. Specialist knowledge concentrates in a few heads. Speed exists, but it's directionless, fast without being coherent. And the big trade-offs (in marketing: brand versus performance; in sustainability: compliance versus value creation) sit unresolved, usually fought over in budget cycles.

Then crawling. Principles get spelled out — how to think, not just what to do. People start to get it, but it's patchy. The trade-offs are being named, people can see they're connected rather than opposed, but they haven't been resolved through shared principles yet. Tools are starting to serve the principles rather than operating on their own. Specialist knowledge is beginning to transfer, inconsistently. You've got understanding without confidence.

Walking changes the feel of a company. Principles are embedded and practised. People make decisions without checking with the centre. The trade-offs that paralysed earlier stages are now navigated through principles: people know which way to lean and why. Specialists coach rather than own. Their job shifts from doing the work to building others' ability to do it. Tools are used through the lens of principles. New hires pick it up from colleagues, not documentation. You're moving, but stretch too fast and you'll stumble.

Running is where infrastructure starts to sustain itself. Capability builds across every team, every market. Speed and coherence reinforce each other: fast execution strengthens the brand rather than fragmenting it. Trade-offs are navigated instinctively. Tools strengthen the whole system rather than adding isolated capabilities. Specialist knowledge has spread. The company no longer depends on the people who brought it in. People who joined years after the work was done operate with the same judgment as those who built it.

In brand, this progression is concrete. A company sitting up has brand guidelines and a brand team everyone depends on, and the brand-versus-performance debate runs unresolved underneath every budget meeting. Crawling, it has principles like "local relevance strengthens global brand" but people aren't sure how far they can push. Walking, teams develop campaigns and share them with the brand team for feedback, not approval. Running, a team in Singapore develops a Lunar New Year campaign, launches it, and shares learnings with the team in Brazil planning for Carnival. The brand team isn't involved in either, and no one's arguing about brand versus performance because the infrastructure makes it one conversation.

Most transformations invest in helping companies sit up better. Nicer documentation. Clearer templates. Fancier tools. More training. Each of those matters. You can't skip from sitting up to running without them. But they only drive the progression when connected by principles. Without that connective tissue, you get better-equipped people still waiting for someone at the centre to approve their work.

Building this isn't a quarter's work. For most companies, moving from sitting up to walking takes 12–18 months. Reaching running, where infrastructure is truly self-sustaining, often takes 2–3 years. The investment is front-loaded; the returns compound over time. But the early signs show up much sooner. Within a few months, you'll notice the questions changing. Fewer people asking "can I do this?" and more asking "here's what I'm thinking, does this hold?" The volume of escalations drops. Local teams start making decisions they previously would have referred upward. The quality of mistakes shifts: from random guesses to principled attempts that miss intelligently.

None of these show up in a dashboard. All of them tell you something is shifting.

The Path Forward

Consider what rented capability actually costs. Every time capability walks out the door, you're not starting from zero. You're starting from zero having already spent the budget to get somewhere. A company that restarts its transformation every three years doesn't spend 1x. It spends 3x for 1x of value. The board paper never frames it that way, but the pattern is stark.

The four approaches aren't wrong. They're incomplete. They don't add up on their own. They compound only when connected by principles that guide how they're used, and embedded in infrastructure that doesn't depend on the people who built it.

In marketing, this means brand can't be built by the marketing team alone. Customers don't experience your brand in silos. They don't separate your ad from your pricing from your call centre from your checkout. Everyone who touches the customer builds brand, whether they know it or not. And they need infrastructure: shared principles that enable good decisions without anyone else being in the room. That's an enterprise problem, not a marketing problem.

If you're leading marketing transformation, the question isn't "how do we improve our brand marketing?" It's "what infrastructure would let a thousand people make brand-building decisions without checking with us first?" Are we helping people sit up better, or building what helps them run?

If you're on a board approving transformation budgets, ask a question that rarely appears in business cases: what's the half-life of this investment? Not the projected ROI. The structural durability. Will this capability be worth more in three years or less? If the honest answer is "less," you're not approving an investment. You're approving an expense with a transformation label.

And if you're a CEO, ask yourself: where am I the human switchboard? Where does quality depend on my judgment rather than on systems others can use? Every place you find one is a place where capability is concentrating rather than spreading, and where the company is more fragile than it looks.

These questions apply whether your transformation is about brand, sustainability, AI, or any other capability you need at scale. The ingredients change. The trap doesn't. And the way out is always the same — principles that enable judgment, embedded in how decisions get made, spreading without depending on the people who built them.

The ingredients you can buy. The connective tissue you have to build.

Next month: why the landscape shifting around you makes this more urgent than you think.

Last month I named an uncomfortable pattern: most change efforts depreciate. Billions invested. Returns temporary.

The organisations commissioning transformation know it. The consultants delivering it know it. The boards approving the budgets suspect it. Everyone keeps doing it anyway. The business press is full of articles diagnosing the "transformation treadmill" — the exhausting cycle of change programmes that never quite stick. The pattern is finally getting attention. What's missing is the structural explanation — and a test for whether you're actually escaping it.

This month I want to go deeper. Not just what happens, but why. Because the structural reasons matter — they determine whether anyone can do anything about it.

Here's the uncomfortable truth: depreciation isn't a failure of execution. It's a failure of architecture. The way most transformation gets built guarantees it won't last.

Part 1: The Problem

The Depreciation Pattern

Watch any large organisation long enough and you'll see it.

A transformation launches. Significant investment — consultants, technology, internal resources. Early wins generate excitement. Case studies get written. People get promoted.

Then time passes. The project team moves on. The consultants finish their engagement. Attention shifts to the next priority.

Two years later, you'd hardly know it happened. The gains have eroded. The capability has dispersed. The organisation is starting over — often on the same problem.

This isn't rare. It's the default.

I've watched it happen with digital transformations, culture programmes, innovation initiatives, operating model redesigns. Different labels, same pattern. Activity that felt like progress but didn't leave anything behind.

The question isn't whether you've seen this. The question is why it keeps happening — and whether it has to.

Part 2: Why It Happens

Four Structural Reasons

Depreciation isn't random. It follows predictable structural patterns.

1. Capability Concentrates

Most transformations create pockets of excellence rather than distributed capability. The project team becomes expert. The consultants hold the methodology. A few key people "get it" while everyone else watches.

This feels like progress — you can point to the capable people. But capability that concentrates is capability that's fragile. When those people move on, the capability moves with them.

2. Knowledge Stays Tacit

Ask the people running a successful transformation what makes it work, and they'll struggle to explain. They know it when they see it. They make dozens of judgment calls that produce quality. But they can't articulate it clearly enough for someone else to follow.

This is normal — most expertise is tacit. But tacit knowledge doesn't transfer. It doesn't scale. It doesn't survive the departure of the people who hold it.

3. Dependency Forms

Successful transformations create heroes — the people who make it work through sheer force of will. They coordinate across silos. They translate between groups. They hold the whole thing together.

This heroic coordination isn't wrong — exceptional people doing exceptional things is often how breakthroughs happen. Linda Hill and her colleagues call them "bridgers" – and they are right that these people are essential to getting innovation across the finish line. But it's not scalable. And it's not transferable. What looks like leadership is actually a symptom: it signals that the underlying infrastructure doesn't exist. The principles aren't clear enough. The systems don't enable distributed judgment. So everything flows through human switchboards.

The problem isn't the heroes. It's building as if you'll always have them.

4. Key People Leave

This is the obvious one, but it's worth stating plainly. People move. They get promoted. They take other jobs. They retire.

If the transformation depends on specific people, their departure is a countdown to depreciation. Not because they were bad at their jobs — because of how the thing was built.

The Four Types of Change

Part of why depreciation persists is that we use one word for very different things.

Type 0: Continuous Calibration. Micro-adjustments, course corrections. This should be constant and expected. There was never a moment when everything worked.

Type 1: Surface Change. Products, campaigns, processes. These change constantly — monthly, quarterly. They should be agile and experimental.

Type 2: Capability Change. Systems that enable the generation of Type 1 solutions. These change periodically — every few years. The infrastructure should last; the agility it enables should flex.

Type 3: Principles Change. Core truths that guide everything. These change rarely — once a decade, if ever.

Most transformation confusion comes from mixing these up. Treating Type 1 solutions as if they need Type 3 permanence. Treating Type 3 principles as if they need Type 1 flexibility.

The real gap is Type 2. Most organisations have a purpose statement (Type 3) and constantly change their products and processes (Type 1). What they lack is the infrastructure in between — the capability layer that makes good decisions possible at scale.

What does Type 2 infrastructure actually look like? It's not a platform or a process. It's the layer that tells people how to make good decisions when no one's watching.

Think: principles clear enough that a new hire can apply them without asking permission. Systems that surface quality problems before they reach customers. Ways of working that spread through use rather than training programmes. The scaffolding that makes distributed judgment possible.

Next month I'll go deeper into what this architecture looks like. For now, the key point: most transformation investment goes to Type 1 (new solutions) or Type 3 (purpose statements). The infrastructure that would make either of them stick gets skipped.

Why Good Strategy Isn't Enough

Here's something I've learned that might be uncomfortable for strategists to hear: strategy alone can't solve this.

I've watched brilliant strategies depreciate. Not because the thinking was flawed — because no one built the infrastructure for distributed execution. The direction was clear. The capability to sustain it wasn't.

Strategy sets the destination. It doesn't build the vehicle that gets you there and keeps running after the driver changes.

This isn't an argument against strategy. Good strategy is necessary. It's just not sufficient. The gap between strategy and lasting execution is where most transformation investment goes to die.

Filling that gap requires something most strategy work doesn't touch: building the infrastructure that enables people throughout the organisation to make good decisions without checking upstairs. And developing the leadership capabilities to let them.

Why the Incentives Push Toward Depreciation

Understanding the structural reasons isn't enough. You also need to understand why they persist — why smart people in well-run organisations keep building things that depreciate.

Quick wins over lasting capability. Boards want results. Executives want to show progress. Consultants want to demonstrate value. All of these push toward visible short-term wins rather than invisible long-term capability.

Clear credit over distributed ownership. When capability concentrates, credit is clear. When capability spreads, credit diffuses. Career advancement rewards the former.

Being indispensable over becoming unnecessary. Consultants who make themselves unnecessary lose their contracts. Internal experts who distribute their expertise lose their unique value. The incentive is to stay needed.

Moving fast over building deep. Exploration takes time. Experimentation requires patience. Building infrastructure is slower than delivering solutions. Every timeline pressure pushes toward the faster option.

None of this is malicious. It's structural. The default path leads to depreciation because that's where the incentives point.

Overcoming it requires building differently from the start — and reshaping the incentives for the people involved.

What might that look like? Consultants whose contracts include a "departure test" milestone — paid in part on whether capability transfers, not just whether the solution launches. Internal teams measured on how many people they've made capable, not just what they've delivered. Leaders evaluated on what still works a year after they've moved on, not just what they achieved while in role.

These aren't fantasy. I've seen versions of each. But they require commissioners who ask for them and providers willing to be held to them. That's rare — which is why depreciation remains the default.

Part 3: The Reframe

Rented vs Built

Here's a useful distinction: are you renting capability or building it?

Rented capability looks like:

• Consultants who deliver solutions but not the ability to generate them
• Project teams who hold the expertise rather than spreading it
• Centres of excellence everyone depends on rather than learns from
• Key people who "just know" how things work but can't explain it

When any of these leave, capability leaves with them.

Built capability looks like:

• Principles anyone can apply
• Infrastructure that enables judgment
• Know-how that spreads through use
• Systems that improve without their designers

When people leave, the capability stays.

To be clear: the issue isn't whether you use consultants or project teams. It's the model of engagement. The same consultancy can either extract value or build capability — it depends on what they're asked to do and how success is measured. Most are asked to deliver solutions. Few are asked to leave capability behind.

Renting is faster to start. It's easier to justify — you can point to clear deliverables and expert resources. It feels like you're buying competence.

But rented capability depreciates. Built capability compounds.

Most organisations don't choose renting consciously. They fall into it because the structural reasons and incentives push that way. Now you can see why.

Building takes longer upfront. The payoff is less visible. Success means becoming unnecessary — which doesn't feature in most performance reviews.

Not everyone wants that trade. But it's the only one that lasts.

The Departure Test

Once you understand the distinction between renting and building, you need a way to test which one you're doing.

I've started applying a simple diagnostic: if everyone who built this left tomorrow, would it keep working?

It's a brutal test. Most initiatives fail it.

Not because the people were lazy. Not because the strategy was wrong. Because the capability was never designed to outlive its creators.

This test should be applied at the board level. Before approving transformation budgets, ask: what will remain when the project team disbands? What capability will the organisation own independently? How will we know if we're building an asset or renting an outcome?

Most boards don't ask these questions. They approve investments based on projected returns without examining whether those returns are structurally durable.

Here's the question that changes the conversation:

If the key people left tomorrow, would this keep working?

Once you're asking that, others follow:

• What will remain when the project team disbands?
• How will we know if capability is concentrating or spreading?
• Are we building Type 2 infrastructure or just funding Type 1 activity?
• What's the half-life of this investment?

These questions surface whether you're making a strategic investment — or funding sophisticated activity that will depreciate like any other expense.

Part 4: The Path Forward

What Compounding Looks Like

If depreciation is the default, what does the alternative look like?

I built a marketing experimentation capability a few years ago. In its first year, it generated 300 million DKK in incremental revenue. The formal infrastructure is gone now — reorganisation and shifting priorities claimed it.

But something survived. Eighty marketers who learned a different way of working. The structure didn't last. The capability did. I've since watched some of them build experimentation into their own teams. Others have applied the thinking in contexts the programme never touched — different markets, different channels, problems we never anticipated.

Here's what I've noticed about capability that compounds:

It spreads. People teach each other. The knowledge doesn't stay locked in a few heads — it propagates through the organisation. Five years later, it's not a "programme" anymore. It's just how work gets done.

It improves through use. Each application makes it stronger, not weaker. People discover new ways to apply it. Edge cases get incorporated.

It works without its creators. The people who built it can leave, and it keeps functioning. Not because it's frozen in place — because the capability transferred.

It survives structure changes. Reorganisations happen. Priorities shift. Budgets get cut. Capability that compounds persists through these disruptions because it lives in people and principles, not in org charts and programme offices.

Where to Start

If you're reading this and recognising the pattern in your own organisation, here's where to start:

Before your next transformation investment, ask the investment committee to answer the departure test explicitly in the board paper. Not as a throwaway line — as a section that explains what capability the organisation will own independently when the project ends.

For transformations already underway, ask the programme lead: if your team disbanded tomorrow, what would keep working? If the honest answer is "not much," you're renting. That doesn't mean stop — it means change what you're building toward.

For your own leadership, notice where you're the human switchboard. Where does quality depend on your judgment rather than systems others can use? That's where capability is concentrating rather than spreading.

The Alternative Is Possible

Depreciation isn't inevitable. Some transformations build capability that compounds. The organisations that achieve this aren't luckier or better resourced. They build differently.

What that architecture looks like — the principles, the levels, and what it demands of leaders — is what I'll explore next month.

This is part of an ongoing exploration of what makes change last — the gap between strategy and execution, and what actually bridges it.

I kept seeing the same thing.

A team would build something good. Real progress. Energy, focus, results. Then time would pass. Key people would move on. Attention would shift. And slowly — sometimes quickly — the thing would fade. Two years later, you’d hardly know it happened.

I’ve watched this pattern dozens of times across 25 years inside one company. Change efforts that launched with fanfare and dissolved without a trace. Capabilities that lived in a few people’s heads and walked out the door when they left. Initiatives that worked brilliantly — until they didn’t.

But I’ve also seen the opposite.

Some things last. They spread. They get better through use. People teach each other. Five years later, it isn’t a “programme” anymore — it’s just how work gets done.

Same company. Same leaders. Same budgets. Different outcomes.

For a long time, I assumed the difference was commitment. Or executive sponsorship. Or picking the right problem.

Those things matter. But they’re not the thing.

The difference is whether you build something that depends on you — or something that works without you.

Why This Matters

This isn’t just about project management or change fatigue. It’s about strategic investment.

Boards approve transformation budgets expecting durable capability. What they typically get is temporary improvement — gains that erode the moment attention shifts elsewhere. The investment was real. The return was rented, not built.

I’ve started applying a simple test: If everyone who built this left tomorrow, would it keep working?

It’s a brutal test. Most initiatives fail it. Not because the people were lazy or the strategy was wrong — because of how the thing was built.

This pattern isn’t unique to where I’ve worked. It shows up in AI implementations that stall after the pilot. In post-acquisition integrations that destroy value instead of creating it. In scaling companies that lose what made them great the moment they outgrow the founders’ direct attention.

The context varies. The pattern is remarkably consistent.

How I Came to See It

I didn’t arrive at this by accident.

Before I joined the company where I’ve spent my career, I worked for eight years in the UN system — empowering young people to create change in their communities. I lobbied governments. I designed programmes. I learned what it takes to make things stick when you have no power to force them.

Then I made what my colleagues thought was a bizarre choice: I went to design school. Product design. “The most unsustainable profession in the world,” I joked. But I meant it. I wanted to understand what it takes to create change from the inside — to work on things that matter, within systems that resist.

That path led me to a company I’d loved since childhood. I joined as a product designer, developing new products from concept through production. I thought I was joining a stable, thriving business.

I wasn’t.

Within a few years, the company was facing collapse. The crisis came from overreach — chasing growth in the wrong directions, losing touch with what made it strong. I watched from the middle of the organisation, where strategy meets reality.

What happened next became a business school case study. New leadership. A return to fundamentals. A rebuild that took the company from near-bankruptcy to 74 billion DKK in revenue, from 3,000 people to over 31,000. I've been there through that growth — and five subsequent step-changes in scale.

I was there for that. Not in the executive suite — but in the rooms where it got real. Working on what the brand meant, what the values actually required, how to translate strategy into practice.

And I stayed. For 25 years now. Long enough to see what lasted from that turnaround — and what faded. Long enough to test my own ideas about what makes change stick.

What I’ve Tested

I’ve built things. Repeatedly. Not products, after those early years. Capabilities. Functions. Ways of working.

I’ve set up how a brand shows up beyond physical products — online, on the phone, in stores. I’ve inherited decimated functions and rebuilt them into something that shaped how the organisation thought. I’ve led consumer insights. I’ve transformed a broken digital platform into something that actually worked — piece by piece, over three years, with a team I had to rebuild from dysfunction.

Later: sustainability communications. Diversity and inclusion foundations. A marketing experimentation capability designed to spread through the organisation.

Each time, I’ve followed the same instinct: build it so it works without me.

One capability I built — a marketing experimentation infrastructure — generated 300 million DKK in incremental revenue in its first year. Three years later, the formal infrastructure is gone — reorganisation and shifting priorities claimed it. But something survived: eighty marketers who learned a different way of working. The structure didn’t last. The capability did. The skills outlasted the structure.

That’s when I started to understand: this isn’t just good project management. It’s a different kind of change entirely.

What It’s Cost

I should be honest about something.

Not all success is worth the cost.

There was a stretch — successful by external measures — where I lost my voice. Roles that looked good on paper but took more than they gave. I couldn’t measure my real impact, so I started looking for validation from the wrong people. For a while, I felt like a stranger to myself.

Getting it back took years, and taught me things the successful years couldn’t. But that’s a story for another time.

The Pattern Named

So what’s the difference? What separates change that fades from change that lasts?

I’ve started calling it the difference between change that depreciates and change that compounds.

Change that depreciates generates activity, maybe even early wins — but capability concentrates in a few people. When they leave, the gains leave with them. The organisation invested real money and effort. The return was temporary. Two years later, they’re starting over.

Change that compounds builds capability that grows over time. Know-how spreads — people teach each other. The thing works without its creators. It improves through use. Five years later, it’s still running, still evolving, still generating value.

Most change depreciates by default. Not because anyone chooses that. Because the incentives push that way. Quick wins. Clear credit. Being indispensable.

Change that compounds requires giving things up: speed at the start, credit clarity, being needed. Not everyone wants that trade.

But if you want change that lasts — that’s the only trade that works.

There’s a deeper distinction here — between what I’ve come to call extractive and regenerative approaches. Extractive change pulls value out without building capacity back in. Regenerative change builds capacity that outlasts the effort. I’ll explore this more in future pieces. For now, the key point is simpler: most strategic investment depreciates. It doesn’t have to.

The difference is whether you build something that depends on you - or something that works without you

The Gap This Fills

There’s no shortage of frameworks for strategy. No shortage of advice on change management. Brilliant thinkers have mapped out what makes companies last, how to make strategic choices, why competitive advantage erodes.

What’s missing is honest examination of what happens in the space between strategy and reality — where strategic intent either becomes lasting capability, or quietly dies while everyone pretends it’s working.

I’ve started calling this the messy middle. Post-strategy, pre-value. The territory where transformation budgets get spent and strategic plans get tested. Where most initiatives fail — not from bad strategy, but from architecture that guarantees depreciation.

That’s the territory I want to explore. Not from theory — from 25 years of building it, breaking it, and watching what survived.

What’s Coming

After 25 years inside, I'm starting to write publicly about what I've learned — while I'm still close enough to remember how it actually felt.

This newsletter is called The Tenon. A tenon is a woodworking joint — the part that fits into the mortise so two pieces become one load-bearing structure. I’m interested in the joint between strategy and reality. The place where vision either becomes lasting advantage — or gets lost in the messy middle.

I’ll be writing about:

Why strategic investments depreciate. The structural reasons most transformation spending doesn’t build lasting capability — and what boards should ask but rarely do.

What compounds instead. The architecture of advantage that lasts. What to embed, how to design for durability, why principles matter more than processes.

What it demands of leaders. The specific capabilities required to bridge strategy to reality — and why they’re different from the skills that get you to the top.

Where it shows up now. AI implementation, post-acquisition integration, scaling culture — the places where these patterns are most visible and most urgent.

I’ll draw on what I’ve seen inside — not as a case study to admire, but as a source of patterns that apply more broadly. And I’ll bring in what I’m seeing elsewhere, because this pattern isn’t unique to any one company or industry.

Who This Is For

If you’re tired of transformation that doesn’t stick.

If you’ve ever watched a strategic initiative launch with confidence and fade with a whimper.

If you’re responsible for making strategy real — inside an organisation, as an advisor, as a board member.

If you suspect there’s a pattern to what lasts and what doesn’t, and you want to understand it.

This is for you.

An Invitation

I’m not presenting this as a finished system. It’s still forming. I’m a practitioner sharing what I’ve learned, in public, as I refine it.

If any of this resonates — if you’ve seen these patterns too, or you’re wrestling with them now — I’d love to hear from you. Reply to this post. Find me on LinkedIn. The best ideas come from conversation, not isolation.

Subscribe if you want to follow along.

Here’s to what lasts.

—Cecilia