top of page
Search

The Rest You Cannot Take. THE HEARTWRIGHT · ISSUE NO. 07

July 28, 2026

Where resilience meets trust — and rest only works when both hold.

Published Tuesday, July 28, 2026  ·  Bi-weekly  · www.heartledleadership.org

EDITOR'S NOTE

Issue No. 06 opened the synthesis series with alignment × environment — the seam where stated values meet the room, and the room wins. This issue picks up the next pair: resilience × trust. Rest that is designed but cannot be taken. Trust that is stated but not operational. The two failure modes almost always show up together.

If you have ever been on a team where the PTO policy is generous and no one uses it, you have already met the seam this issue is on.

A quiet piece of news, tucked at the bottom of this issue: the Heart Led shop is now open — a primary storefront on the site and a curated selection on Etsy. More below.

— Lauren

THE LEAD  ·  THE REST YOU CANNOT TAKE

Designed rest and trust are the two halves of capacity. When either fails, the other cannot compensate.

Issue No. 04 argued that rest is infrastructure — a designed feature of the architecture, not a habit an individual is responsible for. Issue No. 05 argued that trust is operational consistency — the predictability the system provides so people can hold to decisions without re-litigation. Both are correct. Neither, on its own, produces the outcome the pillar was designed for.

A generous PTO policy that no one uses is not a resilience feature. It is a trust failure that is quietly draining the resilience feature the leader thought they were providing.

Rest that is designed but not trusted does not happen. The vacation the calendar allows, but the culture does not. The day off that a manager blesses in the 1:1, but audits on Slack (or via email) the next morning. The sabbatical outlined in the handbook, but has never been taken by anyone above a certain level. In each case, the system has designed rest at the policy layer and defeated it at the trust layer — because no one on the team trusts that stepping away will hold without cost.

Trust that is stated but not built is the mirror failure. The team is told to trust each other. The system is told to trust the team. The vocabulary is present. The operational consistency is not. Every message carries insurance language. Every decision gets a verification meeting. The rest that was supposed to come from trust (trust that the decision will hold, trust that the document is enough, trust that the coverage while you're out will actually work), never arrives. What arrives instead is a team that is technically resourced for rest and structurally unable to take it.

Three shapes the seam takes:


  • PTO with no coverage design. The vacation policy is generous. The system for who covers what while a person is out is unwritten. The rest exists on paper. The trust required to take it does not.

  • On-call with no downbeat. The rotation is designed. The recovery day after being paged at 3 a.m. is not. The team trusts each other to trade shifts. They do not trust the system to give the shift back.

  • Sabbaticals no one senior has taken. The policy exists. The signal that senior leaders will not take it — because the trust that the org can hold in their absence has not been earned — means no one below them takes it either. Policy without example is a design without a switch.


The fix, in each case, is not a bigger rest program. It is trust redesigned at the layer where rest actually happens: coverage, consistency, and the demonstrated willingness of leadership to step away and let the system hold.

Rest runs on trust. Trust makes rest possible. Neither pillar holds alone.

THE PILLARS  ·  RESILIENCE × TRUST

A quick reminder of how these two sit in the HEART framework, and why their seam is so productive:


  • Resilience (Issue No. 04) is the system's designed capacity to sustain performance under load. Rest is its infrastructure.

  • Trust (Issue No. 05) is operational consistency — the predictability that lets people commit to decisions and step away from work without a verification cost when they return.


The seam question for this week: is there a rest feature in your team — PTO, on-call recovery, a project downbeat, a sabbatical policy — that is designed on paper and undertaken by almost no one? That gap is not a communication problem. It is the trust layer refusing to hold what the resilience layer designed.

NOW AVAILABLE  ·  THE HEART LED LEADERSHOP

A quiet announcement, and a natural next step in the work. Heart Led Leadership now has a shop — actually two, a primary storefront on the website and a curated selection on Etsy.



Each item in the shop is designed to sit next to the framework, not replace it; a tool is only as useful as the practice it serves. If you have used any of the resources with your team, replies about what worked (and what did not) go directly into how the next batch is designed.

FROM YOUR REPLIES  ·  OPEN QUESTIONS STILL LANDING

Reader replies to Issues No. 02 through No. 06 continue to land. A curated synthesis pass is underway. The most useful will show up, anonymized, in a coming issue once I can do the answers justice.

All invitations remain open. The threshold for inclusion here is signal, not volume.

FIELD NOTES  ·  WHERE I'VE BEEN, AND WHAT'S NEXT


  • Podcast  ·  "How to Market Your Nonprofit" @Counterintuity Thanks to the team for having me. Just taped an episode on leadership systems for mission-driven organizations. As nonprofits adopt AI and new technologies to expand their impact, they're also navigating new questions around trust, data stewardship, governance, and risk. These conversations don't have to be driven by fear; they're an opportunity to build stronger organizations that protect the people and communities they serve. 🎧 Listen here:• Podcast home: https://lnkd.in/g6yAnvhg• Spotify: https://lnkd.in/gzwzJ4ez• Apple Podcasts: https://lnkd.in/guNHJP4b

  • Speaking  ·  Girls Who Print Summit ·  Thursday, July 30. A community of women in the printing industry. I'm honored to be joining the Girls Who Print Global Summer Summit on July 29–30 as part of the Water theme, where I'll be speaking about "Navigating Stormy Seas". It's about learning to navigate one without losing yourself. The Girls Who Print Summer Summit is free, fully online, and one registration gives you access to every session, with replays delivered afterward. If you're looking for thoughtful conversations about leadership, career growth, and the future of our industry, I'd love for you to join us. https://lnkd.in/gKPZshWh

  • Advocacy · Surveillance Technology Oversight Project (S.T.O.P.) at the Valkyries Game on Sunday, August 2. Event details and registration at secure.qgiv.com/for/pdsfcp/event/pdsfcp/. Full Court Press, our fundraiser. Grab your all-inclusive suite ticket ($325 — suite access, food, and drinks) and you're in. Come help us fight for privacy and civil rights as the Golden State Valkyries take on the Toronto Tempo.

  • Book  ·  GarWu Publications. Still waiting to hear from our editor and publisher, Transcend Studios. But things are progressing nicely.

  • Next synthesis pair  ·  Issue No. 08 will continue the seam series — Humanity × Environment (design defaults built for a fictional employee) or Alignment × Trust (stated values held with operational consistency, or not). Reader vote welcome.


ONE QUESTION

This week, name one rest feature in your team — PTO, coverage design, a designed recovery day, a sabbatical policy — that exists on paper and that almost no one takes. Do not fix it yet. Just name what would have to be true, in the trust layer, for it to actually get taken. 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

bottom of page