This week’s episode is about what’s still standing after the people who built something have gone. If you’ve watched or listened, you have the argument and the 8:59 story so I won’t repeat them here. This issue does two things the episode doesn’t. It takes on the best objection to the argument. And it gives you a test for your own rhythms that you can run this week, without waiting for anyone to leave. The objection The fair challenge goes like this. Organisations aren’t short of meetings that outlive the people who started them. They’re drowning in them. A ritual that survives its sponsor isn’t always a win. Sometimes it’s just a habit nobody has the authority to stop. That’s true, and it’s worth taking seriously. Survival on its own proves nothing. Most diaries are full of meetings that keep running long after anyone can say why. They survived the handover too. Nobody would call them a capability. So the test isn’t whether a rhythm keeps running. It’s whether it still forces a decision. The meeting in the episode survived because it did one thing every week. It put what was off track on a wall and made someone own the fix by Friday. Take that away and it would have deserved to die, whoever was in the chair. That’s why a rhythm needs a written reason, not just a calendar slot. What it’s for. What decision it forces. What breaks the day it stops. And the line most people leave out: what would tell you it’s time to stop it. A reason that includes its own exit is what separates a capability from a ritual. A rhythm with a reason survives the handover. A rhythm without one either dies with its sponsor or lives on as a ritual. Neither is a capability. The test: five rhythms, four lines each List the five recurring meetings your results depend on most. The weekly performance review, the monthly pipeline call, whatever actually moves things in your part of the organisation. For each one, write four lines. * Who calls it. * The decision it exists to force, in one sentence. * What would break if it stopped. * The last time it ran without the person who started it. Then sort them into three groups. * Runs itself. Someone else has chaired it, it went ahead anyway, and anyone in the room could give you the one-sentence reason. That’s a capability. * Runs on a person. It only happens when one name calls it. That’s a habit, and it leaves when they do. * Runs on memory. It happens every week, but nobody can say what decision it forces. That one won’t survive a new leader, and maybe it shouldn’t. Now take the one that matters most and write its reason down. Half a page is plenty. What it’s for, what it decides, what breaks without it, and what would tell you it’s time to stop. Put it where the next person will find it before they find the cancel button. Then hand the chair to someone else for a month, while the person who started it is still around to watch. That’s the cheapest handover you’ll ever run, because you get to see it fail while there’s still someone in the building who can fix it. And take a hard look at anything in the third group. Some of those meetings should be rewritten. Some should be stopped, on purpose, with a sentence saying why. The line to remember The test of the work was never how it launched. It’s what’s still standing the year after you’ve gone. Watch or listen The full episode is at the top of this post. It’s the quietest one of the season, built around a Monday meeting I walked past at 8:59 one morning, months after I’d left, and found still running without me. You can also listen on Apple Podcasts or Spotify, or watch on YouTube. If you run the test, reply and tell me how many of your five ran on memory. Built to Absorb. One problem, one fix, every week. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.builttoabsorb.com
