Built to Absorb

About Built to Absorb

Where large programmes lose the value they were funded to deliver, and how the best operators capture it. One problem, one fix, every week. www.builttoabsorb.com (https://www.builttoabsorb.com?utm_medium=podcast)

Publisher

Ricky Asemota

Category

business · technology

Language

en

Explicit

No

First episode

29 Sept 2026

Latest episode

11 Nov 2026

Latest episodes

7 episodes in the feed.

1. 

   11 Nov 2026

   The Next Decade

   This week’s episode is the halfway mark of the season, and it turns on one line. If you’ve watched or listened, you have the read and the four things I’d watch for. I won’t repeat them here. This issue does two things the episode doesn’t. It takes on the best objection to that line. And it gives you a ledger you can build in about an hour, to see whether your own organisation’s announcements are turning into delivery. The objection The fair challenge goes like this. Announcements matter. They commit leaders in public. They attract the people you need. They release the money. Without the launch, there’s nothing to absorb in the first place. I agree. An announcement is a commitment, and commitment is useful. I’ve stood at the back of those rooms, and the ambition in them was real. Nothing in this season argues against ambition. The problem isn’t announcing. It’s scoring the announcement as the result. Once the launch is what gets rewarded, attention leaves with the audience. The work of absorbing it, the ordinary weeks where the new way either shows up or doesn’t, gets less of everything. Less time, less money, less senior attention. Not because anyone decided to starve it. Because nobody claps for it. So keep the announcement. Just stop counting it. Count what it changed a year later, in a normal week, with nobody watching. An announcement is the start of the evidence. It isn’t the evidence. The ledger: an hour with your last eighteen months List everything your organisation announced in the last eighteen months. Programmes, platforms, reorganisations, targets. Anything that got a launch. For each one, write three lines. * What was promised. * Where it would show up in an ordinary week if it had landed. A decision made differently. A meeting that now exists. A number that moved. A task nobody does any more. * What you can actually point to today. Then sort them. * Absorbed. You can point to the ordinary-week evidence, and it would still be there if the sponsor left. * Adopted on paper. The structure exists. The org chart, the licences, the steering group. The work underneath still runs the old way. * Announced only. The launch happened. Nothing since. Be fair about timing. Some programmes are built to land over years, and it would be easy to score them all as failures. Score each one against what should be visible by now, not against the finish line. Then take the announced-only list to the people who launched them, one at a time. For each one, either put a name and a date on the first ordinary-week change, or say out loud that it’s been dropped. Dropping it honestly costs less than carrying it as a promise. Every unkept announcement makes the next one easier to ignore. The adopted-on-paper column is where the second half of this season lives. Those are the failures you can’t point at, and next week starts with the first of them: the load nobody budgets for. The line to remember An announcement is not evidence of absorption. Watch or listen The full episode is at the top of this post. It opens on a launch, the good kind, with the stage and the countdown, and then on the morning after, when the real work either absorbs what was announced or doesn’t. You can also listen on Apple Podcasts (https://podcasts.apple.com/us/podcast/built-to-absorb/id6806991972) or Spotify (https://open.spotify.com/show/7nwgw6S59jbshSNyLYsUeF), or watch on YouTube (https://youtu.be/QwAAUBrS-R0). If you build the ledger, reply and tell me which column was longest. 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

2. 

   4 Nov 2026

   Institutions That Outlast

   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 (https://podcasts.apple.com/us/podcast/built-to-absorb/id6806991972) or Spotify (https://open.spotify.com/show/7nwgw6S59jbshSNyLYsUeF), or watch on YouTube (https://youtu.be/HAXCnAI893o). 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

3. 

   28 Oct 2026

   The Foundations Problem

   Last week’s question was whether the work was being delivered. This week’s episode asks the harder one underneath it: “Could you even tell?” If you’ve watched or listened, you have the argument and the night I learned it. I won’t repeat them here. This issue does two things the episode doesn’t. It takes on the objection I hear most often. And it gives you a test you can run on your own foundations this week without touching a single system. The objection The fair challenge goes like this: Data is never clean. If you wait for one perfect source of truth before you launch, you’ll never launch anything. Fix it in flight. I agree with the first half. If the test were clean data, nothing would ever go live. But the episode isn’t asking for clean data. It’s asking for an agreed number, and those are two different things. Clean means right. Agreed means everyone in the room will act on it, flaws and all. You can launch on an imperfect number that everyone trusts, and improve it as you go. You can’t launch on two good numbers that disagree, because the first meeting after go-live stops being about what to do and becomes an argument about whose figure is real. And it doesn’t have to be every number. Just the handful your launch will be judged on. If those don’t match, launching doesn’t save time. It schedules the argument for later, in public, when it’s more expensive to have. “Fix it in flight” works for most things. It doesn’t work for the instrument you’re steering by. The test: three numbers, three people Pick the three numbers your next big decision will depend on. Revenue at risk. Active users. Cost to serve. Whatever your board will actually act on. Ask three people, separately, for each number. Use the same wording, ask in writing, and ask where they got it. Then compare. * Same number, same source. That’s a foundation. * Same number, different sources. That’s luck. It will come apart the first time something changes. * Different numbers. There’s no foundation yet, whatever the dashboard looks like. Ask the same three people two more questions. If this number moved the wrong way tomorrow, whose phone would you pick up? Three different names means nobody owns it. And in your last review, how much of the hour went into reconciling figures instead of deciding? That’s what a missing foundation costs, every week, and it never shows up in a budget. Then fix one number before the next meeting. Choose the source everyone will accept, not the best one. Agreement doesn’t make a number right. It makes it something you can fix together. Put one name against it, and write its definition in a single sentence nobody can read two ways. The line to remember: “You can buy the technology. You cannot buy the trust.” Watch or listen The full episode is at the top of this post. It opens on the night before a go-live I stopped, because two of my own people pulled the same core number from two systems and it didn’t match. You can also listen on Apple Podcasts (https://podcasts.apple.com/us/podcast/built-to-absorb/id6806991972) or Spotify (https://open.spotify.com/show/7nwgw6S59jbshSNyLYsUeF), or watch on YouTube (https://youtu.be/Ru033Srze-E). If you run the test, reply and tell me how many of your three numbers matched. 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

4. 

   21 Oct 2026

   The Delivery Gap

   The most dangerous colour in a transformation isn't red. It's green. A board that's all green is not a board that's on track. It's a board that's stopped telling you the truth. Years ago I sat in a status review where every line was green. On track, on budget, on plan. I believed it, moved my attention to the fires that were actually burning, and looked away. Under one of those green lines sat a decision nobody had made. Only deferred. Someone had dressed up "we haven't decided this yet" as "this is handled", and the colour let everyone stop looking. By the time it broke into the open, months later, it had grown teeth. I'd taken green to mean done. It doesn't mean done. The programmes that actually deliver aren't the ones with the most green. They're the ones willing to show red early, and to cancel almost nothing late. What you'll take away The line. Green isn't the colour of progress. It's the colour of a deferred decision. The tell. Every line on the dashboard green, and everyone around the table talking in anecdotes rather than decisions. The question. If you stopped announcing for one quarter, what would you actually finish? And on your greenest programme, when did someone last show red? 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

5. 

   14 Oct 2026

   The Suitcase Problem

   Think of the one person in your organisation you genuinely couldn't afford to lose. Now the harder question. Why is that true? There are two very different answers, and from the outside they look identical. One is real strength: a person who's made everyone around them better. The other is the most expensive kind of fragility there is, and almost nobody sees it until the person has gone. WHAT YOU'LL TAKE AWAY The line: If a capability lives in one person, you don't own it. You're renting it, until the day they leave. The tell: When your best person leaves, does the capability stay, or does it walk out with them? The question: If your three best people left this quarter, what would still be standing on Monday? Name it, or admit you were renting it. Years ago I joined a business and did the sensible thing. I put my attention where the numbers were red, and left alone the one part that was working. What I didn't weigh was whose results those were. They were his, run out of his own head, never once built into the team around him. Then he left, and the whole function fell off a cliff. The capability I'd trusted had his name on it, not the company's. It walked out in his suitcase, because it had never lived anywhere but in him. Nobody decides to become dependent. You wake up one day and a whole function is one person. The single-point-of-failure audit from this episode is in the written version: https://www.builttoabsorb.com/p/the-suitcase-problem (https://www.builttoabsorb.com/p/the-suitcase-problem) New episode every Wednesday. 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

6. 

   7 Oct 2026

   The Phase 2 Problem

   Money buys motion. It doesn't buy capability. I ran a reorganisation once that worked perfectly on paper. New teams in six weeks, new structure, new names on the chart, a launch everyone applauded. Then I sat in with one of those teams a few weeks later and watched them push every real decision straight back up the old chain. WHAT YOU'LL TAKE AWAY The line: Money moved at the speed of a memo. Capability moves at the speed of learning. The tell: More capital approved than people who can land it. If that sentence is true of an organisation, it's living the problem, and the strategy deck doesn't get a vote. The question: Are you staffing for the phase you're actually in? Or still paying for the one you just left? I'd changed the drawing. I hadn't changed the company. The boxes had moved. The power hadn't. The incentives hadn't. The habits hadn't. The new structure was running on the old logic. I'd moved the structure at the speed of a memo, and capability moves at the speed of learning. I hadn't waited for it. That mistake scales. For a long time transformation has been told as a story about money: who's funding what, how big the number is, which sector's next. Then the easy money tightens, and it stops being about deploying more and starts being about using what you already bought. Phase one asked whether we could fund it. Phase two asks the harder, quieter question. Can we absorb it. Most of the market is still answering the first question while standing in the second. The written version of this episode is on Substack: [PASTE EP1 POST URL] New episode every Wednesday. 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

7. 

   29 Sept 2026

   Start Here

   A company I worked with spent a fortune on a new system. A year later I asked to see the usage data. Most people had logged in exactly once, on the day of the training. They’d bought the capability. They just never absorbed it. That gap is what this show is about. One problem, one fix, every week. Nobody had been lazy. The money hadn’t been short. The thing worked. And a year in, a fortune in tools sat in the building like gym equipment nobody’s touched since January. That’s the pattern that bothered me more than any other. Not talent, not capital, and most of the time not even the strategy. An organisation can buy almost anything. It can absorb almost none of it. This is the orientation episode. Who I am, what that word “ABSORB” actually means, and what you can expect this season. Then we get to work. WHAT YOU’LL TAKE AWAY The line: “Capability moves at the speed of learning, not the speed of money”. The question, to take into a real meeting this week: “If this were true here, where would we see it?” The deal, every episode after this one: one tell you can look for in your own organisation, one question you can ask your team, and one line sharp enough to repeat without me in the room. Give you none of those and I’ve wasted your commute. Ep0 is the orientation, so it gives you the line and the question but not a tell. The tells start next week. 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 (https://www.builttoabsorb.com?utm_medium=podcast&utm_campaign=CTA_1)

Reach and audience

Public platform figures. Ratings count people who left a rating, not total listeners.

Spotify

5.0 / 5

1 ratings

Contact Built to Absorb

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.