<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Matt Lacey — Writing</title>
    <link>https://mattlacey.co.uk/writing/</link>
    <atom:link href="https://mattlacey.co.uk/feed.xml" rel="self" type="application/rss+xml" />
    <description>Essays and notes on strategy and leadership, written for people doing the job rather than studying it.</description>
    <language>en-gb</language>
    <item>
      <title>The boardroom is the last waterfall</title>
      <link>https://mattlacey.co.uk/writing/the-boardroom-is-the-last-waterfall/</link>
      <guid isPermaLink="true">https://mattlacey.co.uk/writing/the-boardroom-is-the-last-waterfall/</guid>
      <pubDate>Tue, 06 Oct 2026 09:00:00 GMT</pubDate>
      <category>essay</category>
      <description>We taught delivery teams to work with uncertainty. Then we asked them to sprint towards a strategy written once a year, by a room that works nothing like theirs.</description>
      <content:encoded><![CDATA[<p>I was coaching a leader recently who felt stuck and couldn&#39;t say why.</p>
<p>Her CEO had been clear: slow down, take a breath, make sure we&#39;re stable before we go again. At the same time, her commercial director had asked her team for a 20% lift in results, with no additional budget.</p>
<p>She&#39;d been carrying both instructions, trying to honour each one. It took a retreat, away from the office, and probing questions, for the tension to become clear. “I hadn’t put those two things together, it seems obvious now.” The conflict wasn&#39;t hers to solve. It was a decision that needed to be made.</p>
<p>And nothing in how the business ran would have surfaced it. The plan was set for the year. There was no fortnightly moment where those two instructions had to sit on the same table in front of the same people.</p>
<p>I&#39;ve spent most of the last twenty years around product and tech teams, where agile became the default way to work with uncertainty.</p>
<p><strong>We made delivery agile. Why is strategy still waterfall?</strong></p>
<h2>Agile stopped at the boardroom door</h2>
<p>Think about what agile teams already believe. You can&#39;t predict what people will want, so you ship something small and learn. You plan, but you replan every couple of weeks. You treat the roadmap as a set of bets, and you expect some to lose.</p>
<p>No self-respecting product team would build for two years without talking to a customer. Yet plenty of leadership teams still write a strategy once a year, put it in a deck, and bring it out again at the next away day. In between there&#39;s no rhythm for testing it, no review of what&#39;s been learned, and no easy way to change course.</p>
<p>You get a strange picture: brilliant, adaptive teams, sprinting hard, in a direction nobody stress-tested.</p>
<p>Agile is a way of making decisions under uncertainty. So is strategy. They&#39;re the same problem at different altitudes. We just never took the method up the mountain.</p>
<h2>Who we put in the room</h2>
<p>Part of the answer is who ends up at the top table.</p>
<p>Simon Wardley describes three kinds of people an organisation needs. <em>Pioneers</em> explore the unknown and build the new thing. <em>Settlers</em> take the rough idea and make it real and repeatable. <em>Town planners</em> industrialise it and run it efficiently at scale. All three matter. The trouble is the order they arrive in.</p>
<p>Early on, pioneers run the show. As a business grows it rewards the people who make it predictable, and town planners rise. For roughly forty years management has prized operating excellence, so leadership teams fill up with excellent operators.</p>
<p>That isn&#39;t a criticism of operators — we need them badly. But Michael Porter drew the line years ago: operational effectiveness has a frontier your competitors can reach, while strategic positioning is much harder to copy. A top table built entirely from town planners is very good at running today&#39;s business, and often uneasy with the exploration that finds the next one.</p>
<p>Then we ask that table to set strategy in the most uncertain conditions any of us have known. People who are brilliant at <em>reducing</em> uncertainty, asked to decide <em>inside</em> it. No wonder the result looks like a plan.</p>
<h2>Deciding too fast</h2>
<p>When leaders are uncomfortable with uncertainty they rarely freeze. More often they do the opposite: grab the first credible option and move.</p>
<p>Paul Nutt spent years studying how organisations decide, and the Heath brothers popularised his work in <em>Decisive</em>. The finding, broadly, is that most decisions only ever weigh one real option — and the ones that weigh several tend to turn out better.</p>
<p>I see it most in boardrooms. A proposal lands. It&#39;s reasonable. Nobody wants to be the one slowing things down. So the first idea on the table becomes the plan, and the challenge that would have improved it never gets heard.</p>
<blockquote>
<p>Deciding too slowly is a real risk. Deciding too fast is the one I see more often.</p>
</blockquote>
<p>The better move is to hold the problem open a little longer. Generate a second and third option. Ask what you&#39;d need to believe for each one to be right.</p>
<p>The leader I was coaching had the mirror image: two decisions issued, neither reconciled. Deciding too fast and not deciding at all are the same failure. Both happen when a board has no rhythm for holding a question open and coming back to it with evidence.</p>
<h2>What an agile board would look like</h2>
<p>Two thinkers help here.</p>
<p>Nassim Taleb argues we should stop trying to predict the future and build things that gain from surprise. His barbell keeps most of what you have safe while placing many small bets where one good outcome pays back many times over.</p>
<p>Rita McGrath argues that lasting competitive advantage is largely a myth now. Winning organisations build a stream of temporary advantages, riding each one while it lasts and starting the next before it fades. Her discovery-driven planning treats a plan as a set of assumptions to test, cheaply and early.</p>
<p>Put them together and you get something any product team would recognise: strategy as a portfolio of bets, reviewed on a rhythm, with the riskiest assumptions tested first. In practice, an agile board might:</p>
<ul>
<li>review strategy every quarter as a live set of bets, with the evidence in front of them</li>
<li>fund a few small experiments alongside the big commitments</li>
<li>ask for two or three genuine options before any major decision</li>
<li>name the trade-offs out loud, including what it will stop doing</li>
<li>make room for a pioneer&#39;s voice at the table, even when the business is mostly settlers and planners</li>
</ul>
<p>None of that needs a new framework. It needs the board to hold its plan the way a good walker holds a map. You plot the route before you set off. Then, when you find a bog in the middle of the path, you go round it. Hold the map too tightly and it walks you straight in up to your knees.</p>
<h2>Back to the leader who felt stuck</h2>
<p>Once she saw that the two instructions couldn&#39;t both be true, she had something to take back to her leaders: a clear choice between stability and growth, with the cost of each. Trade-offs are the foundation of strategy.</p>
<p>A team that replans every fortnight would have caught that contradiction in weeks. It took a retreat and an outsider&#39;s questions to catch it at all.</p>
<p>That&#39;s the work. Better decisions, turned into action. Agile teams already know how to do it. The boardroom is the last place that hasn&#39;t caught up.</p>
<p>So here&#39;s the question to take into your next leadership meeting. If your delivery teams worked the way your board does, how long would it take you to notice?</p>
]]></content:encoded>
    </item>
    <item>
      <title>A target is not a strategy</title>
      <link>https://mattlacey.co.uk/writing/a-target-is-not-a-strategy/</link>
      <guid isPermaLink="true">https://mattlacey.co.uk/writing/a-target-is-not-a-strategy/</guid>
      <pubDate>Tue, 06 Oct 2026 09:00:00 GMT</pubDate>
      <category>note</category>
      
      <content:encoded><![CDATA[<p>The most dangerous sentence in budget season: &quot;We need 30% more — and we&#39;re cutting your budget.&quot;</p>
<p>A big number goes up on the wall. The resources to reach it go down. Everyone is expected to find the gap somewhere, usually through longer hours and quiet heroics. It might even work for a quarter. But the experiments stop, because nobody has time to try anything, and you buy this year&#39;s number with next year&#39;s future.</p>
<p>A target is a destination. Strategy is the route — and the route only exists once someone has done the hard thinking about what&#39;s possible, what has to change, and what you&#39;ll <em>stop doing</em> to make room. Without that, a goal is a wish. Put a few in a deck and you&#39;ve got a hope list.</p>
<p>The tell is one question: <em>what are we going to stop doing to get there?</em> A clear answer, and you might have a strategy. A pause, and you&#39;ve got a number plucked from the air.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Deciding too fast</title>
      <link>https://mattlacey.co.uk/writing/deciding-too-fast/</link>
      <guid isPermaLink="true">https://mattlacey.co.uk/writing/deciding-too-fast/</guid>
      <pubDate>Tue, 06 Oct 2026 09:00:00 GMT</pubDate>
      <category>note</category>
      
      <content:encoded><![CDATA[<p>We worry a lot about slow leaders — analysis paralysis, decisions kicked into next quarter. It happens. But in the rooms I sit in, the opposite is far more common.</p>
<p>A proposal lands. It&#39;s credible, it&#39;s been worked on, and nobody wants to be the one who slows things down. So the first reasonable option quietly becomes the plan. The challenge that would have sharpened it is never voiced; the second option that might have been better is never written.</p>
<p>Uncertainty makes this worse. When the future is unclear, grabbing the first credible answer <em>feels</em> like leadership. It relieves the discomfort. The leaders I rate do something harder: they keep the problem open a little longer, ask for a second and third option, and ask what they&#39;d need to believe for each to be right.</p>
<p>Speed matters. But a fast decision on the wrong option just gets you lost more quickly.</p>
]]></content:encoded>
    </item>
    <item>
      <title>Town planners at the top</title>
      <link>https://mattlacey.co.uk/writing/town-planners-at-the-top/</link>
      <guid isPermaLink="true">https://mattlacey.co.uk/writing/town-planners-at-the-top/</guid>
      <pubDate>Tue, 06 Oct 2026 09:00:00 GMT</pubDate>
      <category>note</category>
      
      <content:encoded><![CDATA[<p>Simon Wardley describes three kinds of people every organisation needs. <em>Pioneers</em> explore and come back with something new. <em>Settlers</em> make the rough discovery real and repeatable. <em>Town planners</em> industrialise it — efficient, reliable, ready for scale.</p>
<p>Watch what happens as a business grows. The early years belong to the pioneers. Then the organisation starts rewarding predictability, and the people who deliver it rise. Over time the top table fills with brilliant operators — which is fine, right up until you ask that table to set direction in deep uncertainty. People whose gift is removing uncertainty, asked to decide inside it.</p>
<p>The fix isn&#39;t to replace your operators. It&#39;s to make sure the explorers still have a seat, and that someone asks them what they can see ahead. Who on your leadership team is looking furthest out — and how often do they get the last word?</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
