The One Who Can Carry It · T H E H E A R T W R I G H T · I S S U E N O. 1 0
Where humanity meets resilience — and the system routes its hardest work to whoever has proven they can absorb it.
Published Tuesday, September 8, 2026 · Bi-weekly · www.heartledleadership.org
EDITOR’S NOTE
I hope you had an amazing long weekend!
Issue No. 09 asked which of your stated values had actually survived a hard moment. The replies were specific in a way that a question rarely produces. Not “we say one thing and do another,” but the exact meeting, the exact trade-off, the exact quiet cost. Several of you named the moment and then named what it changed. That is the work. Thank you.
One piece of news before the essay: "The HEART Advantage" has a publication date. January 26, 2027. Alongside the waitlist, I am building the ARC list now — if you would read an advance copy and say something honest about it at launch, book.heartledleadership.org or a DM will get you on it.
Two smaller notes: the Girls Who Print recordings are live, both links below, and Speaker of the Year voting is open.
Also new, and useful alongside this issue: the HEART Self-Audit is live. It is a short, structured pass across the five pillars — Humanity, Environment, Alignment, Resilience, Trust — built to show you where your leadership is already strong and which pillar is quietly carrying the most load. Most people are surprised less by their weakest pillar than by their strongest one, which tends to be the thing they have stopped noticing they do well. www.heartledleadership.org/heartselfaudit
— Lauren
THE LEAD · The one who can carry it
The message came in at 6:40pm on a Friday night. “Can you take this one? You’re the only one who can.”
I said yes. I always said yes. I was proud of it, in the way you are proud of something you have not examined.
It took me years to hear that sentence correctly. Being the only one who could was not a compliment. It was a design flaw, and I was the workaround.
Every system routes load somewhere, and it routes it toward whoever has proven they can carry it. That is not malice. It is efficiency. Under pressure, the fastest safe path is the person who has absorbed pressure before. The leader reaching for that person is not exploiting anyone. They are solving tonight’s problem with the lowest-variance option in the room.
Run that logic for four quarters, and you have designed something specific: A system whose failure mode is the steady depletion of its most capable people. The reward for absorbing load is more load. The reward for recovering quickly is being asked to recover again sooner.
Humanity says people are not interchangeable units of capacity. Resilience says the system should absorb its own shocks. The seam between them is a question almost no one asks out loud: What does your system do with the person who can take it?
This is not a story about bad managers. It is a story about a default. Three shapes it keeps taking:
The glue person. They hold the context nobody wrote down, so work moves faster when it moves through them. Which means it always moves through them. Which means they cannot be moved. This reads as being indispensable. It functions as a ceiling.
The unofficial escalation path. On paper, hard problems route through a process. In practice, they route through a name. Nothing about this appears on a capacity plan, a headcount request, or a performance review, because it never took the form of a decision. It took the form of a habit.
The person who never says no. Their capacity gets estimated from the last thing they absorbed, never from what absorbing it cost. The cost is invisible, so the estimate is always wrong, and always wrong in the same direction.
In none of these is anyone being punished. They are being trusted. That is exactly what makes it hard to see and harder to name. “I knew I could count on you” is warm, sincere, and doing the work of a staffing decision nobody made on purpose.
There is a second cost, and it lands on everyone else. When one person absorbs the hard things, no one else gets to practice. The gap between the reliable person and the rest of the team widens every quarter, which makes the routing decision more correct each time, which widens the gap further. The system is not just depleting one person. It is deskilling the others.
The design work is to make load visible where it actually lands, not where the org chart says it lands. Capacity counted per person, not averaged across a team. Escalation paths with a second name on them that has been tested, not just written down. A standing rule that whoever absorbed the last one is not eligible for the next one. Promotion criteria that do not quietly punish the person holding a team together in place.
A system that runs on one person’s reliability is not resilient. It has a single point of failure, and it has handed that point of failure a compliment instead of a backup.
The Pillars · Humanity × Resilience
This seam sits underneath two issues that came before it, and it is worth being precise about the order:
Issue No. 04 argued that rest is infrastructure. Recovery is a designed feature of the architecture, not a habit an individual is responsible for.
Issue No. 07 argued that designed rest still fails when trust is not operational, because people will not take recovery they believe will be counted against them.
Both of those assumed something I never examined: That the load was distributed in the first place. It often is not. And a recovery system cannot fix an allocation problem. If the hard work keeps finding the same person, no amount of designed rest will reach them, because they will be the one covering while everyone else takes it.
Humanity (Issue No. 01) is the recognition that people are not interchangeable capacity. Two people with the same title do not have the same reserve, and that difference is not a performance rating. Resilience (Issue No. 04) is the system’s ability to absorb load. A system that absorbs load by concentrating it has not absorbed anything. It has relocated it onto a person.
The seam question for this week: Look at the last three things that went sideways on your team and write down who actually carried each one. If a name repeats, you have found your capacity plan, and it is a human being.
Field Notes · Where I've been, and what's next
Book 1 · The HEART Advantage — we have a date. The HEART Advantage publishes January 26, 2027. Two ways in ahead of that: the waitlist at book.heartledleadership.org, where news lands before anywhere else, and the ARC list. If you would read an advance copy and say something honest about it at launch, that is exactly who I am looking for — book.heartledleadership.org, or DM me directly.
Book 2 · Burning Out on Your Success. Now in the manuscript and design cycle with Page Two. The book is the structural companion to the AI Summit keynote and to much of what The Heartwright has been building toward. More as the chapters settle.
Book (Picture Book) · GarWu Publications (children's privacy book with Alea Garbagnati). Still targeting Spring 2027. The most recent editor pass landed the way we hoped it would.
New · The HEART Self-Audit. A short structured pass across all five pillars, built to surface where your leadership is already strong and which pillar is carrying the most weight: www.heartledleadership.org/heartselfaudit
Recap · Girls Who Print — recordings now live. My session, “Navigating Stormy Seas”: https://lnkd.in/g2GPWtyy. The Water track panel: https://lnkd.in/gMe2YtMZ. If you only have time for one, the session is the tighter argument; the panel is where the disagreement got interesting.
Nomination · Speaker of the Year. Voting is open: https://lnkd.in/gVdFDGci. If the work has been useful to you this year, this is where a vote or a reshare meaningfully moves the needle. Vote if you're able. Reshare if you're willing. Thank you.
Shop update · Two storefronts, each pointed at a different room. On Etsy, HeartLedLeaderShop (etsy.com/shop/HeartLedLeaderShop) carries the leadership retreat tools and AI prompt packs. HeartLedStudio (heartledstudio.etsy.com) carries cards, invites, and wedding stationery. Different tools for different tables.
One Question
This week, list the last three unplanned things your team absorbed, and name who actually absorbed each one. Not who owned it on paper. Who carried it. If one name repeats, ask two things: What would have happened if that person had been unavailable, and what the system has given back to them. Reply with what you find. The most useful answers will show up, anonymized, in a future issue.
—
The Heartwright is written by Lauren Wu and published by Heart Led Leadership.
Comments