How a Non-Fiction Guidebook Develops Courage and Transforms Leadership

SHOW NOTES: 

WorkLife Stories from School of WorkLife Episode: How a Non-Fiction Guidebook Develops Courage and Transforms Leadership.

How a non-fiction guidebook develops courage and transforms leadership is rarely what managers expect — but for many, it becomes the insight that changes everything about how they show up during crisis.

Sid had been leading his compliance team for three years. He was managing the transition well on paper. But when formal complaints arrived from three of his own team members, he discovered that good intentions and actual impact are not the same thing. This is the story of the book that showed him the difference — and changed how he led.

RESOURCES MENTIONED

The Storytelling Newsletter (Free) Short, focused, and grounded in real WorkLife situations — how we communicate, lead, make decisions, and navigate challenges at work.  

Story Lesson How a Non-Fiction Guidebook Develops Courage and Transforms Leadership. Learn how a non-fiction guidebook that explores courage, vulnerability, and daring leadership can develop the capacity to lead effectively through difficulty and change.

Guided Programme The Power of Non-Fiction: Developing Connection Through Reading Discover how to develop community through kindness and literary exploration

This story was inspired by my book, WorkLife Book Club Volume One Shoreditch by Carmel O’ Reilly — following members of a London book club as they navigate WorkLife challenges through the wisdom found in the books they read together.

Commissioned learning resources, speaking engagements, and organisational partnerships: carmel@schoolofworklife.com

schoolofworklife.com

The stories I write are based on real WorkLife challenges, obstacles, failures and successes. Persons and companies portrayed in the stories are not based on real people or entities. Carmel O’ Reilly

Transcript

Speaker 0:08

Sid had been team leader of a compliance team for three years. Regulations understood, processes maintained, performance reviews that use words like reliable and dependable, and yet when the restructure came, something changed. The same approach that had always served him suddenly felt inadequate. He was being asked to lead twelve people through upheaval, remotely, through a screen, in a context where clear directives and structured check-ins couldn't reach the human reality of what his team was actually navigating. Sid was managing the transition well on paper, but he was beginning to suspect that managing and leading were not the same thing. Welcome to Work Life Stories from School of Work Life. I'm Carmel O'Reilly, and today's episode is how a nonfiction guidebook develops courage and transforms leadership. Rarely what managers expect, but for many it becomes the insight that changes everything about how they show up during crisis. This story is about Sid and about the call that forced him to lead differently, and the book you almost dismiss that showed him everything he had been missing about what leadership during crisis actually requires. The call that changed everything. The shift began with a phone call, his regional director, a hub model, remote working from most of the team. The physical footprint reduced by 70%. Sid had been leading through clarity, directives, structure, standards. It was how he'd built his team's reputation. Now he was being asked to maintain all of that through a screen. That evening, searching for resources on remote leadership, he came across repeated references to Dare to Lead by Brene Brown. The word vulnerability appeared in every review. His first instinct was skepticism. Vulnerability sounded like precisely the wrong approach during a crisis requiring decisive leadership. But Brown's research credentials caught his attention. This wasn't motivational speaking. It was grounded in data from organizations navigating real challenges. Curious, he ordered the book. The first risk A few weeks later, Sid faced his team for their first video call meeting, everyone now in their separate homes. He'd planned to present the restructure announcement with his usual approach, clear facts, outlined next steps, reassurance that he had everything under control. Instead, remembering Brown's research on vulnerability as courage rather than weakness, he opened differently. I want to start by acknowledging that this transition to remote work isn't something I've led before. I'm figuring out how to support you all effectively in this new context. I don't have all the answers yet, but I'm committed to working through this alongside you. The silence that followed felt eternal. Then Nisha, usually reserved in meetings, spoke. I really appreciate you saying that, Sid. I've been worried about how we'll maintain quality standards when we're all working separately, and I wasn't sure if I should raise concerns or just wait for you to tell us the plan. What followed was the most honest team conversation Sid had experienced in three years. What Sid realized afterwards, the more Sid thought about dare to lead, the more clearly he saw what the research had shown him. Brown's distinction between armored and daring leadership gave him a framework for understanding his own patterns. Armoured leadership uses perfectionism, emotional control, and the appearance of certainty to maintain an illusion of strength. It feels like competence, but it prevents the trust and honest communication that teams need during complexity and change. Sid had been armoured for three years without knowing it. His reluctance to admit uncertainty, his tendency to present polished plans rather than works in progress, his habit of identifying problems in his team's work rather than exploring the thinking behind their decisions. These hadn't felt like protection strategies. They had felt like professionalism. Brown's research showed him they were the same thing. What happened next? A few days later, one of his team members missed a deadline, something that hadn't happened before. Sid's instinct was to send a terse email about expectations. Instead, he asked a different question. Jordan, I've noticed these deadlines have slipped, which is unusual for you. I'm wondering what's happening that might be making work more challenging right now. What emerged was that Jordan's partner had lost their job in the same corporate restructure. Financial pressure, the pressure of being the sole income, the mental load of carrying that worry whilst trying to perform at work. Jordan had been trying to manage it all without burdening anyone. The missed deadline wasn't a performance issue. It was an impossible set of circumstances Jordan thought he had to handle silently. He and Jordan worked out a temporary adjustment to project allocation and identify resources Jordan could access for support, preventing a small struggle from escalating into a crisis of performance or trust. Brown's framework had a name for what Sid was learning to practice. Clear is kind, not avoiding difficult conversations, not sugarcoating feedback, but being honest about challenges whilst also being human about them. The shift. One insight changed how Sid approached leadership, from projecting certainty to naming uncertainty and staying present within it. Instead of asking, how do I show my team I have this under control? He started asking, What does this moment actually require from me as a leader? And the conversations changed almost immediately. When the complaints arrived, three months into leading his newly remote team, Sid faced something he hadn't anticipated. Three team members, including his most senior analyst, Aisha, submitted formal complaints about feeling excluded from decisions and undervalued in their roles. Sid's first instinct was defensive anger. He'd been working harder than ever. How could they claim he wasn't valuing them? But something made him pause before responding. He returned to Dare to Lead with different questions and found Brown's framework on the near enemies of daring leadership. Behaviors that look like courage but are actually protection strategies. He recognized himself. He'd been working hard to present and supportive, but entirely on his own terms, check-in scheduled when it suited his calendar. Decisions made with good intentions but without genuine input. A version of support that was on closer examination, a subtle form of control. Before replying to the complaints, he scheduled individual conversations with each person, not to defend his intentions, to listen. What he heard was painful but clarifying. Aisha told him his frequent check-ins felt like surveillance rather than support. Another team member described feeling infantilized by his tendency to offer solutions before she'd finished explaining challenges. A third said being praised for handling things well felt hollow when he was never involved in strategic decisions about the team's direction. They weren't describing malicious leadership. They were describing the gap between Sid's stated values and his actual behaviors. That gap, Brown's research made clearer, was one of the most damaging dynamics in any team. The teaching insight, Sid discovered that daring leadership wasn't about grand gestures of vulnerability. It was about the gap between the leader you believe yourself to be and the experience you're actually creating. When he stopped asking, how do I show my team I'm supportive? and started asking, What is my team's actual experience of my leadership? Two things changed. The complaint stopped being an accusation, and the team he'd been trying to support finally felt it. Why this matters, professional development often focuses on leadership techniques, how to give feedback, how to manage performance, how to communicate clearly. But leading people through genuine crises requires something harder to develop. The willingness to examine not just what you do, but what your behavior communicates, especially when your intentions and your impact are pointing in opposite directions. When we read research-based nonfiction, we gain access to frameworks that help us see those gaps. Not because the book tells us what to do, but because it shows us what we're doing all along and what it costs. Sid's story shows what happens when that recognition moves from the page into practice. And like the best guidebooks, it keeps revealing new things the longer you stay with it. That's today's story, how a nonfiction guidebook develops courage and transforms leadership. The complete lesson follows Sid's full journey, including how insights from Dare to Lead changed how he approached his team, his peers, and his own understanding of what vulnerability as courage actually requires, and what he discovered when he returned to the book several months later. It shows how you can apply the same perspective in your own work, learning to recognize the gap between your stated values and your actual behaviors, and developing the courage to close it. And if you want to go deeper, the companion guided program, The Power of Nonfiction, Developing Connection Through Reading is there when you're ready. This story was inspired by my book, Work Life Book Club, Volume 1, Shoreditch by Carmel O'Reilly. All the details and links are in the show notes, or you can find everything at schoolofworklife.com. Subscribe to the podcast for weekly audio stories, or visit the newsletter, storytelling newsletter for the written versions, or both. Next time we'll be exploring how leaving security behind reveals your origin story. A story about how Jed discovered that his growing dissatisfaction with a prestigious legal career wasn't in gratitude for what he'd achieved, but a signal that he'd spent nine years using his capabilities to protect the powerful from the consequences of harming the vulnerable. And what he was willing to sacrifice when he finally chose differently. Until then, remember the novels that move you most deeply often contain the keys to understanding the people and challenges you encounter in your professional life. Thank you for listening.