How Reading Fiction Develops Resilience and Strengthens Leadership

SHOW NOTES: 

WorkLife Stories from School of WorkLife Episode: How Reading Fiction Develops Resilience and Strengthens Leadership 

Discovering how reading fiction develops resilience and strengthens leadership is rarely what managers expect — but for many, it becomes the insight that transforms how they respond when careful planning meets an unpredictable world.

Sophie had built her reputation on delivering results. She had always believed that good planning prevented problems. But lately it felt as though the problems kept multiplying. This is the story of the moment a novel about survival showed her that resilience isn't about controlling every variable — it's about learning to adapt when control disappears.

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 Reading Fiction Develops Resilience and Strengthens Leadership  Discover how stories about survival, uncertainty, and adaptation can strengthen resilience and transform how leaders respond to challenge. 

Guided Programme The Power of Fiction: Developing Character Traits Through Reading — Discover how literature strengthens empathy, perspective, and moral judgement — essential traits for thoughtful leadership. 

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_00 0:08

Sophie had built her reputation on delivering results. As a senior project manager at a growing consultancy, she was known for careful planning, clear timelines, and the ability to keep complex projects moving. Her team respected her systematic approach. Clients trusted her organization and attention to detail. But recently something had begun to unravel. The same pattern kept repeating. Careful planning followed by unexpected obstacles, revised schedules that immediately became obsolete, team members becoming increasingly overwhelmed despite the detailed systems she had created to support them. Her most recent project, a digital transformation for a major client, was already three weeks behind schedule with no clear path forward. Sophie had always believed that good planning prevented problems, but lately it felt as though the problems kept multiplying. Welcome to Work Life Stories from School of Work Life. I'm Carmel O'Reilly, and today's episode is how reading fiction develops resilience and strengthens leadership. Rarely what managers expect, but for many it becomes the insight that transforms how they respond when careful planning meets an unpredictable world. This story is about Sophie and about the night, a novel about a boy stranded with a tiger showed her that resilience isn't about preventing problems. It's about learning to navigate them. The night she picked up a book. The shift began late one evening. After another long day trying to stabilize the project, Sophie sat staring at her dashboard. The same red indicators that had been flashing for weeks were still there. A developer had resigned without warning. The client had introduced new requirements that affected every work stream. Testing had uncovered deeper architectural problems that would take weeks to resolve. Each attempt to fix the situation seemed to reveal another issue beneath it. At 11 30 p.m., knowing sleep was unlikely to come easily, Sophie reached for the novel she had been carrying in her bag for months, Life of Pi by Jan Martell. Her sister had given it to her, describing it as a story that changed how people thought about survival. That night she began reading simply to quiet her mind. Instead she found herself absorbed in Pai's extraordinary situation, stranded on a lifeboat in the Pacific Ocean with a Bengal tiger. But what stayed with Sophie wasn't the danger, it was the way Pai responded to it. He didn't try to control the ocean, he observed it. He adapted to it. Each day he adjusted his thinking, his routines, and his strategy based on what the situation required. By dawn, Sophie realized something unexpected. Pai wasn't surviving because conditions improved. He was surviving because he kept adapting. And Sophie realized she rarely approached professional challenges that way. The Monday morning experiment. On Monday morning the testing lead delivered more difficult news. Another critical bug had appeared during testing, one that would delay the system launch by at least another week. Sophie's usual response began forming automatically. Escalate the issue, redistribute resources, increase oversight to prevent further errors. Instead, she paused and asked a different question. What is this bug showing us about how the system actually works? The discussion that followed surprised the whole team. The bug wasn't just an isolated problem. It revealed a deeper misalignment between how the system had been designed and how your users would actually interact with it. What the team had been treating as a failure was actually information. Once they understood that, they could redesign the functionality more effectively than before. Two weeks later, the revised solution was working, better than the original design, and the project was only one week behind schedule. More importantly, the team felt energized rather than defeated. What Sophie realized afterwards? The more Sophie reflected on life of Pai, the clearer the lesson became. Pai didn't survive by forcing his situation to match his expectations. He survived by adapting his expectations to match reality. And Sophie realized she had been trying to do the opposite. She had been trying to force projects to follow the plan. What happened next? Over the following week, Sophie began noticing moments where Pai's approach applied directly to her work. In life of Pai, survival deepened on treating every situation as information. Pai constantly adjusted his routines based on what the ocean, the weather, and even the behavior of Richard Parker revealed to him. Sophie began applying the same principle to her projects. When a client introduced new requirements that disrupted the delivery schedule, she stopped treating the change as a failure of planning. Instead, she asked the team what the new information revealed about the client's evolving priorities and how the project could adapt to serve them more effectively. When technical constraints surfaced during development, she resisted the instinct to push the team harder against the original timeline. Instead, she asked what those constraints revealed about how the system actually needed to work. Like Pai, adapting his survival strategies day by day, Sophie began helping her team adjust their approach as new information emerged, treating setbacks as signals that the work needed to evolve rather than proof that the project was failing. Gradually she redesigned her project frameworks to allow both stability and adaptation, clear goals but structured points where the team could reassess direction based on what they were learning. The shift won insight change how Sophie's approach leadership, from trying to prevent disruption to learning how to adapt when disruption appears. Instead of asking, how do we stop this happening? She began asking, What is this situation showing us about what we need to change? The ripple effect. As Sophie began working this way, something else began to change. In life of Pai, Pai survived not only by adapting his strategies, but by accepting the reality of his situation without losing hope that survival is possible. He holds both roots at the same time. The ocean is dangerous, and he still has a chance. Sophie began approaching difficult moments in her projects the same way. When a major integration problem revealed deeper architectural issues, she didn't minimize the difficulty. She acknowledged it clearly with the team. This is a real problem, she told them, but is also telling us something important about how the system needs to work. Instead of exhausting themselves trying to defend the original plan, the team began exploring better solutions. Developers brought problems forward earlier. Conversations shifted from blame to curiosity, and challenges that once triggered crisis meetings became opportunities for creative redesign. Like Pi, learning to live with the ocean rather than fight it, Sophie's team began navigating uncertainty instead of trying to eliminate it. But Sophie also discovered something Life of Pi had shown her without her fully seeing it yet. Adaptive thinking without structure creates a different kind of problem. That lesson came from a harder moment when she applied Pi's approach too freely and the project began to drift. She had to return to the novel with new questions, and what she found there changed how she understood resilience entirely. The teaching insight. Sophie discovered that resilience is not about controlling every variable, it's about learning how to respond when control disappears. Life of Pi shows that survival depends on constant adaptation, observing what is happening, adjusting strategy, and continuing to move forward despite uncertainty. When Sophie began approaching her projects this way, two things changed. Her team became more willing to surface problems early, and setbacks that once caused panic became information that helped them make better decisions. Instead of trying to force reality to match the plan, Sophie learned to adjust the plan to match reality. That shift turned uncertainty from a threat into something her team could work with and ultimately learn from. Why this matters? Professional life rarely unfolds exactly as planned. Projects shift, conditions change, unexpected obstacles appear. Sophie's story shows why fiction can help develop resilience. Stories like Life of Pi explore how people respond when certainty disappears and survival depends on adaptation. And those insights can transform how we approach the challenges we face in our own work. When we read fiction that follows characters navigating sustain adversity, we practice a specific kind of thinking, learning to treat setbacks as information rather than evidence of failure, and to hold both the difficulty of a situation and the possibility of moving through it at the same time. Sophie's story shows what happens when that habit of thinking moves from the page into the room. And like the best novels, the practice keeps revealing new things the longer you stay with them. That's today's story: how reading fiction develops resilience and strengthens leadership. The complete lesson follows Sophie's full journey, including how insights from life of Pi changed how she approached uncertainty, adaptation, and leadership under pressure. The moment she applied Pi's approach too freely and had to return to the novel to understand what she had missed and what she discovered when she reread it six months later, and shows how the same practice of reading with genuine curiosity about how people navigate uncertainty can strengthen your own resilience as a leader. And if you want to go deeper, the companion guided program, the power of fiction, developing character traits through reading is there when you're ready. This story was inspired by my book, Work Life Book Club, Volume 1 Shortage 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 storytelling newsletter for the written versions or both. Next time we'll be exploring how strategic opening lines transform business proposals into competitive advantage. A story about Donna with comprehensive proposals kept losing to competitors until she discovered that the first few sentences weren't just introductions. They were the difference between commodity vendor and strategic partner. Until then, remember resilience isn't about preventing problems. It's about learning how to navigate them with creativity and grace. Thank you for listening.