The Art of WorkLife Storytelling at Work

Helping People Turn What Happened Into Stories That Build Trust, Share Learning and Show What Their Work Means

The Art of WorkLife Storytelling at Work. Helping People Turn What Happened Into Stories That Build Trust, Share Learning and Show What Their Work Means. A man on the phone, beside scenes at a rainy station, a call centre and a team meeting.

The Art of WorkLife Storytelling at Work is the second of five resources in Story-Based Learning for Organisations. Here you can read Cillian’s full story, with its Reflection Points, Learning Questions and Self-Coaching Exercises, and the five practices for sustaining your learning. Work through it at your own pace, pausing at each exercise and coming back when you’re ready.

The complete resource, free to download, also includes the Workbook, which gathers every tool from the story into one place with worked examples, a Facilitator Guide with three 90-minute session plans for group sessions, and a Manager’s Guide that explores the same story from the other side of the table.

Download the complete resource for free → THE ART OF WORKLIFE STORYTELLING AT WORK

The Art of WorkLife Storytelling at Work

Helping People Turn What Happened Into Stories That Build Trust, Share Learning and Show What Their Work Means

Every working day holds stories worth telling, and the ones that matter most are often the ones you would rather not tell, until you tell them completely: what went wrong, what went right and why it mattered.

The Art of WorkLife Storytelling at Work begins with a question Cillian Walsh can’t answer.

A Story-Based Learning Resource: Cillian’s Story — From the Timeline to the Story

Cillian is a product lead at a company that builds the ticketing app for a regional rail operator. On a Tuesday morning, a major update went live, and for three hours at the height of the morning rush, thousands of passengers couldn’t buy a ticket. By lunchtime it was fixed. Three weeks from now, he will present what happened to the leadership team.

The obvious answer is a timeline and a list of fixes. He has written plenty of those before, and he knows how to make one look thorough.

What he hasn’t yet examined is the story underneath it: what each person on his team saw that morning, what was missed and why, what the team did well under pressure, and why any of it matters to the people the app was built for.

The Art of WorkLife Storytelling at Work follows Cillian through the three weeks before that review. Through a question from his grandmother, five versions of the same morning, a warning nobody heard and a director who wants more than a timeline, he discovers that the account he was expected to give and the story that needs telling are very different, and that the second one has far more to offer his organisation.

Blending storytelling with Reflection Points, Learning Questions, Self-Coaching Exercises and The Art of WorkLife Storytelling at Work Workbook, the resource guides each of your people through the same journey Cillian takes. It is designed for independent learning and for facilitator-supported group sessions, with a full Facilitator Guide and a Manager’s Guide that explores the same story from the other side of the table.

The Art of WorkLife Storytelling explores how to find, shape and share the stories that communicate who you are, what you have learned and why your work matters. Here, the craft of powerful beginnings, engaging middles and memorable endings comes together in three complete stories, a Failure Story, a Success Story and a Passion Story, and they are brought to one of the moments organisations know best: the review of what happened.

For Your Organisation

The Challenge

Your organisation holds reviews. Project reviews, lessons learned sessions, updates to the leadership team and the conversations that follow when something hasn’t gone to plan. They are one of the most valuable ways an organisation learns from its own experience, a chance to understand what happened and carry that understanding forward.

The review is only as rich as the story told in it. When something has gone wrong, people under pressure tend to reach for a timeline and a list of fixes. Each fact is accurate, and the account is thorough. Yet the people who were there each carry a different version of events, and the most important parts, the warning that went unheard, the choices made under pressure and the people the work is for, are left out.

When that happens, the learning stays with the few people who were in the room. Reviews become something to get through rather than something to learn from. The same lessons are learned again, at greater cost. And the story an organisation tells itself about its own work becomes thinner each time.

The Art of WorkLife Storytelling at Work helps each person find the real story beneath the timeline, shape it so others can hear it, and tell it completely: what went wrong, what went right and why it mattered. And it helps managers and leaders ask for that story, so that reviews become the start of learning that reaches everyone in the organisation, whatever their stage.

Who This Is For

People preparing a project review, a lessons learned session, an update to leadership or any moment when they need to explain what happened to people who weren’t there.

Perhaps they are capable and well prepared, and still find their account sounds defensive. Perhaps they have presented a thorough review and watched the room lose interest halfway through. Perhaps they know there is a better story to tell and can’t yet find the shape of it.

It is also for the managers and leaders who ask for those reviews, and for the learning and development teams who design the programmes around them.

What Your People Will Learn

  • How to recognise when a timeline is hiding the story that needs telling
  • How to gather different versions of the same events, and find what each one reveals
  • How to find the story beneath the facts, including the parts nobody wants to tell
  • How to write a powerful beginning that draws people in from the first line
  • How to build an engaging middle that holds attention through tension, turning points and the people involved
  • How to create a memorable ending that carries the learning forward
  • How to tell the same story to different audiences, from the leadership team to colleagues and customers
  • How to tell a Failure Story, a Success Story and a Passion Story completely, so that together they build trust rather than defend a position

What Your Managers Will Learn

  • How to ask for the story behind a review, as well as the facts
  • How to make it safe for people to tell the parts that went wrong
  • How to listen for the voices that went unheard
  • How to turn one team’s story into learning for the whole organisation

What’s Included

  • Cillian’s complete story, told in three parts
  • Reflection Points, Learning Questions and Self-Coaching Exercises at every stage
  • The five School of WorkLife practices for sustaining your storytelling: Self-Awareness, Observation, Effective Self-Feedback, Insightful Self-Questions and Writing Your WorkLife Stories
  • The Art of WorkLife Storytelling at Work Workbook, including the Story Gathering Sheet, the Beginnings, Middles and Endings Worksheet, the Audience Map and the Three Complete Stories Worksheet
  • A Facilitator Guide with three 90-minute session plans, facilitator questions and guidance on feedback in the group
  • A Manager’s Guide, exploring the story from the director’s side of the table

How This Resource Works

The Art of WorkLife Storytelling at Work is built in three parts and nine stages.

Part One — Discover the Stories Already Being Told

  • Stage 1 — The Request
  • Stage 2 — Five Versions of the Same Morning
  • Stage 3 — The Story Beneath the Timeline

Part Two — Develop the Story

  • Stage 4 — Powerful Beginnings
  • Stage 5 — Engaging Middles
  • Stage 6 — Memorable Endings

Part Three — Direct the Telling

  • Stage 7 — Knowing Your Audience
  • Stage 8 — The Rehearsal
  • Stage 9 — The Telling

Each stage follows Cillian through a moment in his three weeks, then turns to the experience of each of your people with a Reflection Point, Learning Questions and a Self-Coaching Exercise, and closes with time to write. By the final stage, each of your people has gathered the different versions of a story from their own working life, shaped it with a powerful beginning, an engaging middle and a memorable ending, and told it completely as a Failure Story, a Success Story and a Passion Story.

The Art of WorkLife Storytelling at Work

Helping People Turn What Happened Into Stories That Build Trust, Share Learning and Show What Their Work Means

The Characters

Cillian Walsh is 34, from the west of Ireland, and a product lead at a company that builds the ticketing app for a regional rail operator. He leads a small team of developers, designers and testers, and he is known for staying calm when things go wrong. He has presented reviews before, and they have always been thorough.

Rachel is the company’s Director of Product and Cillian’s manager. She has asked him to present a review of the launch morning to the leadership team in three weeks, and she has told him she wants to understand what happened, not only when.

Nora is Cillian’s grandmother, a retired headteacher who still lives in the house where he spent his summers as a boy. He rings her every Sunday evening, and she has asked the same question of every story he has ever told her: “And what happened next, and why does it matter?”

Priya, Marek, Grace and Sam are members of Cillian’s team. Priya is a tester, Marek a developer, Grace leads the customer support team, and Sam designs what passengers see on their screens. Each of them was there on the launch morning, and each remembers it differently.

Part One — Discover the Stories Already Being Told

When something goes wrong at work, the first account arrives quickly. It comes from the system logs, the incident report and the order in which things happened. Part One slows it down, long enough to hear the other accounts: what each person saw, what each person did and what nobody has said yet.

The path runs through three stages, drawn from the first week of Cillian’s three weeks:

  • Stage 1 — the expected timeline meets a question it can’t answer.
  • Stage 2 — five people describe the same morning, and each version reveals something the others leave out.
  • Stage 3 — the versions, read together, reveal the story beneath the timeline.

Cillian’s story runs alongside yours at each stage as the example. His morning and his team are his own. What you share with him is the movement, from an account you were expected to give towards the story that needs telling.

Stage 1 — The Request

The message from Rachel arrived on the Wednesday after the launch, between a thank-you note from the rail operator and a request for a meeting about the next release.

“Thank you for everything on Tuesday,” it read. “I’d like you to present a review of the launch morning to the leadership team on the 28th. I want to understand what happened, not only when.”

Cillian read it twice and opened a new document. He knew what a review looked like. He had presented four of them in the past two years, and the leadership team had always thanked him for his thoroughness.

The Timeline

He began with the facts.

05:45 — Update released.

06:50 — First failed ticket purchases reported.

07:05 — Incident declared.

07:40 — Cause identified in the new payment service.

08:00 — Rail operator agrees that passengers can board and buy on the train.

10:00 — Temporary fix in place. Ticket purchases restored.

12:30 — Full fix confirmed.

Beneath it, he listed six actions: more testing at peak volumes, a new alert for failed payments, an earlier release time and three more. By Friday evening, the document was eleven pages long, and every fact in it was accurate.

It was the kind of review he had always written. He couldn’t explain why this one felt so thin.

The Sunday Call

On Sunday evening, he rang his grandmother, as he always did.

Nora asked about his week, and he told her about the launch. He told it the way he had written it: the update, the failures, the fix, the actions. It took about two minutes.

There was a pause on the line. Then she asked the question she had asked of every story he had told her since he was seven years old.

“And what happened next, and why does it matter?”

“We fixed it by lunchtime,” said Cillian.

“That’s what happened next,” said Nora. “Why does it matter?”

He opened his mouth to answer, then closed it again. He thought about the eleven pages. Not one of them answered her question.

“I’ll ring you next Sunday,” he said, “and tell you.”

“I’ll be here,” said Nora.

Reflection Point

A timeline can be complete and still leave the story untold. It records when things happened, in the order they happened, and it can be accurate in every detail. What it rarely holds is why things happened, what people did and felt, and why any of it matters to the people the work is for. Cillian’s eleven pages and his two-minute account to Nora were early signals, worth noticing well before he understood what was missing.

Learning Questions

  1. Cillian’s review was accurate in every detail, yet it felt thin. When have you presented an account of your work that was complete and still left something out?
  2. Rachel asked to understand what happened, not only when. What would change in your own reviews if someone asked you the same?
  3. Cillian told the whole launch in two minutes. Which recent event at work have you told so briefly that the most important part went unsaid?
  4. Nora asked why it mattered, and Cillian had no answer. Why does a recent piece of your work matter, and to whom?

Self-Coaching Exercise — The Timeline

Choose an event from your own working life that you have had to explain to others: a project, a problem, a change or a moment that didn’t go to plan. Write it as a timeline, in the order things happened, as quickly as you can.

Then read it back and ask yourself:

  • What does this timeline tell people about when things happened?
  • What does it leave out about why they happened?
  • Who was there, and what did they see that isn’t written here?

Now write one sentence answering Nora’s question: why does it matter?

Keep both. They are the starting point for everything that follows.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 2 — Five Versions of the Same Morning

On Monday morning, Cillian booked half an hour with each member of his team. He told them he wasn’t looking for what went wrong. He wanted to know what the morning had been like for them.

He kept notes of each conversation in the same way, so he could read them side by side afterwards.

Marek’s Version

Where he was: at his desk from 06:55, with three screens and a cold coffee. What he saw: the new payment service failing every time the number of passengers rose. What he did: traced it, found it and built a temporary fix in under three hours. What he said: “Once we knew where to look, it took forty minutes to find. It was the hour before that which felt like a week.”

Priya’s Version

Where she was: in the office by 07:15. What she saw: the problem she had flagged on the Friday before the release. What she did: logged a note that the payment change hadn’t been tested at rush-hour volumes. It was marked low priority in the final rush to release. What she said, very quietly: “I said it once. I should have said it again.”

Cillian stopped writing. He hadn’t known.

Grace’s Version

Where she was: in the support room with her team of six, phones ringing from 06:55. What she saw: one thousand four hundred calls in three hours. What she did: stayed on the line with an older man standing on a platform in the rain, about to miss a hospital appointment, until the station staff let him board. That afternoon, she rang him back to make sure he had made it. He had. What she said: “He kept apologising to me. As though it was his fault.”

Sam’s Version

Where he was: on the train into work, watching passengers around him tap their screens again and again. What he saw: the message on every screen, Something went wrong. Please try again later. What he did: as soon as the rail operator agreed passengers could board and buy on the train, he rewrote the message to tell them so, and had it live by 08:10. What he said: “We were telling people to try again when trying again was the one thing that wouldn’t work.”

Cillian’s Own Version

Where he was: on a call from 07:05, managing the incident, the rail operator and the leadership team. What he saw: numbers on a dashboard. What he did: made decisions, kept everyone informed and kept the team calm. What he realised, writing it: he had spent the whole morning looking at the problem, and almost none of it looking at the people.

Reflection Point

Every person who was there carries a version of events, and each version is true. Marek saw the technical problem. Priya saw the warning that went unheard. Grace saw the passengers. Sam saw what the passengers saw. Cillian saw the dashboard. None of them saw the whole morning, and a review built from only one version leaves out what the others knew. Listening to every version, without judging any of them, is where the real story begins.

Learning Questions

  1. Cillian told his team he wasn’t looking for what went wrong. How would people describe an event to you if they knew you weren’t looking for blame?
  2. Priya had raised a warning that nobody heard. Whose voice has gone unheard in an event you have been part of?
  3. Grace remembered an older man on a platform in the rain. Which person affected by your work would remember an event very differently from you?
  4. Cillian realised he had spent the morning looking at the problem and not the people. Where have you been closest to the facts and furthest from the people?

Self-Coaching Exercise — Gathering the Versions

Return to the event you chose in Stage 1. Make a list of everyone who was there or was affected by it, including the people your work is for.

For each person you can speak to, ask them what the event was like for them. For those you can’t speak to, write what you know or can imagine of their experience. For each version, note:

  • Where they were
  • What they saw
  • What they did
  • What they said, or would say

Write your own version last, in the same way.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 3 — The Story Beneath the Timeline

On Thursday evening, Cillian laid the five versions out on his kitchen table and read them together for the first time.

Read one at a time, each had seemed like a small part of the morning. Read together, they told a story his timeline had missed entirely.

What the Timeline Left Out

His timeline began at 05:45 on Tuesday. The story began on the Friday before, with Priya’s note.

His timeline recorded that the fix was in place by 10:00. It said nothing about Marek’s hour of searching, Grace’s team answering one thousand four hundred calls, or Sam rewriting a message on a crowded train.

His timeline listed six actions. Not one of them would make it easier for the next person in Priya’s place to be heard.

And nowhere in eleven pages was there a single passenger.

Three Threads

Cillian turned to a clean page and wrote down what he could now see. There was what went wrong: a warning raised, marked low priority and lost in the rush to release. There was what went right: a team that pulled together under pressure and fixed a serious problem in a morning. And there was why it mattered: an older man on a platform in the rain, apologising for something that wasn’t his fault.

He looked at the three threads for a long time. The first was the part he would rather not tell. The second was the part he was proud of. The third was the part he had forgotten.

He thought of Nora’s question. For the first time, he had the beginning of an answer.

Reflection Point

The story beneath a timeline rarely begins where the timeline begins. It begins with the choices that came before, and it includes the people who acted and the people who were affected, as well as the facts. Finding it means reading every version together and asking what none of them shows alone. Cillian’s three threads, what went wrong, what went right and why it mattered, gave him the first clear outline of the story that needed telling.

Learning Questions

  1. Cillian’s timeline began on Tuesday, and the story began on the Friday before. Where does the story of your own event really begin?
  2. The team’s best work wasn’t on the timeline at all. What did people do during your event that no record shows?
  3. There wasn’t a single passenger in eleven pages. Who is missing from your own account?
  4. Cillian could see what went wrong, what went right and why it mattered. Which of the three is hardest for you to tell about your own event, and why?

Self-Coaching Exercise — The Story Beneath

Read every version you gathered in Stage 2 together, including your own. Then write three short notes:

  • What went wrong, including the part you would rather not tell
  • What went right, including what people did that no record shows
  • Why it mattered, and to whom

Finally, write one sentence about where the story really begins. Leave these notes here for now. Part Two will give them their shape.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Where You’ve Arrived

You came into Part One with an account you were expected to give. You leave with every version of the same event, gathered and read together, and the outline of the story beneath it: what went wrong, what went right and why it mattered.

Cillian began with eleven accurate pages and a question from Nora he couldn’t answer. Five conversations, four with his team and one with himself, showed him five different mornings, and reading them together showed him the story his timeline had missed.

In Part Two, that outline becomes a story others can hear, through powerful beginnings, engaging middles and memorable endings.

Part Two — Develop the Story

The outline of a story needs shape before others can hear it. Part Two gives it shape through the three parts every story needs: a powerful beginning that draws people in, an engaging middle that holds their attention, and a memorable ending that stays with them.

The path runs through three stages, drawn from Cillian’s second week:

  • Stage 4 — Powerful Beginnings, written first as a summary, then rewritten to draw people in.
  • Stage 5 — Engaging Middles, written first as a list, then rewritten to hold attention.
  • Stage 6 — Memorable Endings, written first as actions, then rewritten to carry the learning forward.

The first version of each part rarely does its job. Cillian writes each one, questions it and rewrites it, and you’ll do the same.

Stage 4 — Powerful Beginnings

On Monday morning, Cillian set the eleven pages aside and opened a blank document. Before he could tell the story, he needed to know how it would begin.

The First Version

He wrote the opening he had used for every review before.

“This review covers the incident on the morning of Tuesday the 14th, in which a failure in the new payment service prevented ticket purchases between 06:50 and 10:00. It sets out the timeline, the cause and the actions agreed.”

He read it back. It was clear, and it told the leadership team exactly what to expect. That was the problem. Nobody hearing it would lean forward.

Questioning the Beginning

He asked himself where the story really began. Not at 06:50. On the Friday before, with Priya’s note.

Then he asked who the story was really about. Not the payment service. The people: the team who had worked through the morning, and the passengers who had stood on platforms tapping their screens.

And he asked what would make the leadership team want to hear the rest. A summary told them what they were about to hear. A beginning needed to give them a reason to listen.

The Rewritten Beginning

“On the Friday before the launch, one of our testers raised a warning that nobody heard. Four days later, an older man stood on a station platform in the rain, about to miss a hospital appointment, apologising to our support team for something that wasn’t his fault. This is the story of what happened in between, and what we learned from it.”

Cillian read it aloud in the empty office. He wanted to know what happened next. That was the test.

Reflection Point

A powerful beginning gives people a reason to keep listening. It tends to start where the story truly starts, with a person or a moment rather than a summary, and it raises a question the listener wants answered. Cillian’s first opening told the leadership team what they were about to hear. His rewritten opening made them want to hear it. The facts stayed the same. The beginning changed everything about how they would be received.

Learning Questions

  1. Cillian’s first opening was clear and told people what to expect, and nobody would lean forward. How do your own reviews and updates usually begin?
  2. The story began on the Friday before, not at 06:50. Where does your own story truly start?
  3. Cillian chose to begin with two people: Priya and the older man on the platform. Which person could your story begin with?
  4. Cillian’s test was whether he wanted to know what happened next. Would your opening pass that test?

Self-Coaching Exercise — Your Powerful Beginning

Using the notes from Part One, write the first version of the opening to your story, the way you would usually begin. Then question it:

  • Does it start where the story truly starts?
  • Does it begin with a person or a moment, or with a summary?
  • Does it raise a question the listener wants answered?

Rewrite it until it passes all three. Then read it aloud and ask yourself whether you want to know what happens next.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 5 — Engaging Middles

On Wednesday, Cillian turned to the middle of the story. This was where his eleven pages had always lived: the timeline, the cause and the fix, set out in order.

The First Version

He began by drafting the middle in the usual way.

“At 06:50, the first failed purchases were reported. An incident was declared at 07:05. The cause was identified at 07:40 as a change to the payment service that had not been tested at peak volumes. At 08:00, the rail operator agreed that passengers could board and buy on the train. A temporary fix was in place at 10:00, and the full fix was confirmed at 12:30.”

It read like a train timetable. Every stop was in the right place, and there was no reason to stay on board.

Questioning the Middle

He asked himself what had made the morning hard. It was the hour between 06:50 and 07:40, when nobody knew what was wrong.

He asked where the turning points had been. Marek finding the cause. The rail operator agreeing to let passengers board. Sam’s message going live.

And he asked who had made the choices that mattered. Every one of them had a name, and none of those names appeared in his draft.

The Rewritten Middle

“For the first hour, nobody knew what was wrong. Grace’s team was answering a call every few seconds. Marek was searching through a system that looked perfectly healthy until the number of passengers rose. I was on a call with the rail operator, watching a dashboard turn red.

At 07:40, Marek found it: the payment change from Priya’s note. Twenty minutes later, the rail operator agreed that passengers could board without a ticket and buy on the train. By 08:10, Sam had rewritten the message on every passenger’s screen. Until then, it had told them to try again later, when trying again was the one thing that wouldn’t work.

By 10:00, passengers could buy tickets again. Grace’s team had taken one thousand four hundred calls. And the older man on the platform made his hospital appointment, because Grace stayed on the line until the station staff let him board, and rang him back that afternoon to make sure he had.”

Cillian read it back. It had the same facts as the first version. This time, he could see the morning.

Reflection Point

An engaging middle holds attention through tension, turning points and the people who made the choices. A list of facts in order tells listeners what happened. A middle built around the moment nobody knew what was wrong, the moments things changed and the people who changed them helps listeners understand what it was like and why each choice mattered. Cillian kept every fact from his first version. He gave them back their people.

Learning Questions

  1. Cillian’s first middle read like a train timetable. Where does your own account read like a list rather than a story?
  2. The hour when nobody knew what was wrong was the hardest part of the morning. What was the moment of greatest tension in your story?
  3. Marek finding the cause, the operator’s agreement and Sam’s message were the turning points. What were the turning points in yours?
  4. Every choice that mattered had a name, and none appeared in the first draft. Whose names belong in your story?

Self-Coaching Exercise — Your Engaging Middle

Write the first version of the middle of your story, the way you usually would. Then question it:

  • Where is the moment of greatest tension?
  • What were the turning points?
  • Who made the choices that mattered, and are they named?

Rewrite it until a listener could see the event as well as know what happened.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 6 — Memorable Endings

On Friday, Cillian came to the ending. In every review he had ever written, the ending had been the same: a numbered list of actions.

The First Version

“Actions agreed: one, introduce testing at peak volumes for all payment changes. Two, add an alert for failed payments. Three, move releases to a quieter time of day. Four, review the process for prioritising test findings. Five, update the passenger error messages. Six, hold a follow-up review in three months.”

Every action was sensible. He tried to imagine any member of the leadership team remembering one of them a week later, and couldn’t.

Questioning the Ending

He asked himself what he wanted people to remember. Not six actions. One thing.

He went back to his notes from the five conversations, and stopped at Priya’s words. I said it once. I should have said it again. Every action on his list fixed the morning. None of them would make it easier for the next Priya to be heard.

And he asked himself how the story should end: with what the team would do differently, or with why it mattered. He realised it needed both.

The Rewritten Ending

“We have six actions, and you’ll find them in the appendix. But there is one change that matters more than all of them. From the next release, every launch meeting will begin with the same question: what warning haven’t we heard yet? Priya has agreed to ask it first.

Because somewhere on a platform, there is always someone like the man in the rain, trusting that the app in his hand will work. That trust is what we build. And it depends on hearing the quietest voice in the room.”

Cillian sat back. He could imagine the leadership team remembering that.

Ready to Be Heard

That evening, he read the whole story through from beginning to end. The beginning drew him in. The middle held him. The ending stayed with him. It was the best review he had ever written.

Yet he had only told it to himself. He wouldn’t know whether it worked until he told it to others.

Reflection Point

A memorable ending carries the learning forward. Lists of actions are useful, and they rarely stay with anyone. An ending that gathers the story into one clear change, one image or one question gives listeners something to take with them. Cillian’s rewritten ending kept the actions and added what he wanted people to remember: a question that would help the next quiet warning be heard, and the reason it mattered.

Learning Questions

  1. Cillian couldn’t imagine anyone remembering his six actions a week later. What do people remember from the endings of your own reviews?
  2. He realised none of his actions would help the next Priya be heard. What does your list of actions leave unaddressed?
  3. Cillian’s ending came back to the man on the platform. Which image or person could your ending return to?
  4. Cillian wouldn’t know whether his story worked until he told it to others. Who could you tell your story to first?

Self-Coaching Exercise — Your Memorable Ending

Write the first version of the ending to your story, the way you usually would. Then question it:

  • What do you want people to remember a week from now?
  • Is there one change, one image or one question that gathers the story together?
  • Does the ending say why it mattered?

Rewrite it until it would stay with a listener. Then tell your whole story aloud, from beginning to end, to someone who can listen as your audience would.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Where You’ve Arrived

You came into Part Two with the outline of a story. You leave with a powerful beginning, an engaging middle and a memorable ending, each written, questioned and rewritten.

Cillian began the week with the same opening, timeline and list of actions he had always used. A beginning that started with two people, a middle that gave the facts back their people and an ending built around one question turned eleven pages into a story.

In Part Three, the story meets its audiences, is tested aloud and discovers how far it can travel.

Part Three — Direct the Telling

A story takes its final shape when it meets the people who will hear it. Part Three brings Cillian’s story to its audiences, tests it aloud and carries it into the review that began this journey, and beyond.

The path runs through three stages, drawn from the final week before Cillian’s review and the months that followed:

  • Stage 7 — Knowing Your Audience: the same morning, told differently to the leadership team, the team and passengers.
  • Stage 8 — The Rehearsal: the story is tested aloud, and Cillian discovers three stories inside it.
  • Stage 9 — The Telling, and what the organisation does with the story afterwards: developed into three complete stories, it becomes part of how everyone learns, whatever their stage.

Stage 7 — Knowing Your Audience

On Monday, Cillian showed Rachel his draft. She read it twice without speaking.

“This is the review I hoped for,” she said. “And I think it needs telling more than once. The team should hear it. And the rail operator wants to update its passengers about what happened. Can you help them with that too?”

Three Audiences, One Morning

That afternoon, Cillian took a sheet of paper and drew three columns: the leadership team, the team and the passengers.

Under each, he wrote what they already knew, what they needed to understand and what they would want to hear most.

The leadership team knew the headline. They needed to understand how a warning could be lost, and they would want to hear what would stop it happening again.

The team knew the morning better than anyone. They needed to understand what each of them had seen that the others hadn’t, and they would want to hear that their work had been noticed, Priya’s warning most of all.

The passengers knew only what had happened to them. They needed an apology without excuses, and they would want to hear what would be different next time.

The Same Facts, Told Differently

Cillian realised the facts would stay the same for all three. What changed was where each telling began, what it dwelt on and how it ended.

For the leadership team, the story would begin with Priya’s note. For the team, it would begin with the five versions of the morning, because each of them had only seen their own. For the passengers, it would begin with the platform, because that was where they had been.

He wrote a short version for the rail operator’s passenger update and sent it to Grace to read first. She sent it back with one change. “They don’t need the technical detail,” she wrote. “One sentence on what failed is enough. What they need to know is what we’ve learned, and the steps we’re taking because of it.”

Reflection Point

The same story can be told to different audiences without changing a single fact. What changes is where it begins, what it dwells on and how it ends, shaped by what each audience already knows, what they need to understand and what they want to hear. Cillian’s three columns turned one story into three tellings, each true to the morning and each written for the people who would hear it. Grace’s one change showed him how much the passengers’ telling depended on choosing the right details, and on giving them what had been learned.

Learning Questions

  1. Rachel saw that the story needed telling more than once. Who else needs to hear the story of your own event?
  2. Cillian asked what each audience already knew, needed to understand and wanted to hear. How would you answer those three questions for your most important audience?
  3. Each telling began in a different place. Where would your story begin for each of your audiences?
  4. Grace’s change removed something the passengers didn’t need. What could you leave out for one of your audiences?

Self-Coaching Exercise — Your Audience Map

List everyone who needs to hear your story. Choose up to three audiences, and for each one write:

  • What they already know
  • What they need to understand
  • What they want to hear most
  • Where your story will begin for them

Then write a short version for the audience furthest from the event, and ask someone close to that audience to read it first.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 8 — The Rehearsal

On Wednesday, Cillian booked a meeting room and asked Priya, Marek, Grace and Sam to listen to the review from beginning to end, as the leadership team would hear it.

He stood at the front and told it. It took eleven minutes. When he finished, nobody spoke for a moment.

What They Heard

“The beginning made me want to listen,” said Grace. “But the man on the platform gets lost. He’s at the start and the end, and in the middle he disappears under everything else.”

Marek nodded. “And it sounds as though I found the problem on my own. Grace’s team were passing me the error patterns from the calls. That’s how I knew where to look.”

“Read the message out loud,” said Sam. “The one on the screens. The leadership team needs to hear what passengers saw.”

Priya looked down at her notes. “When you go straight from my note to how well everyone worked that morning,” she said carefully, “it sounds as though the good part cancels out the mistake. Could you give it a moment before you move on?”

Cillian thanked them all and made every change. Telling it again that evening, he could hear how much stronger it had become.

The Sunday Call

On Sunday evening, he rang Nora and told her the whole story.

She listened without interrupting. When he finished, she was quiet for a moment.

“That’s a much better story than last time,” she said. “And do you know, there are three stories in it. One about what went wrong. One about what went right. And one about why you do the work at all. Any one of them could be told on its own, and teach something the others can’t.”

Three Stories in One

After the call, Cillian sat at the kitchen table and read the story again. It was the story the leadership team needed: what happened, told completely, from Priya’s note to the man on the platform.

But Nora was right. Inside it were three stories, each worth telling on its own. The story of what went wrong could teach every new tester and developer why a warning needs to be heard. The story of what went right could show every team what working together under pressure looks like. And the story of why they did the work at all could remind everyone in the company who it was for.

Told as one, the story would serve the review. Developed into three complete stories, a Failure Story, a Success Story and a Passion Story, each with its own powerful beginning, engaging middle and memorable ending, it could keep teaching long after the review was over.

He made a note of the three, and went back to rehearsing the one.

Reflection Point

A story tested aloud reveals what a story read silently can hide. Listeners hear where attention drifts, where credit is missing and where meaning blurs. Each member of Cillian’s team heard something he couldn’t hear alone, and their changes made the story stronger. Nora heard something more: that one well-told story can hold several others inside it, each able to stand on its own and teach something different to different people.

Learning Questions

  1. Cillian asked his whole team to listen as the leadership team would. Who could listen to your story as your audience would?
  2. Each member of the team heard something different. What would the people in your story hear that you can’t?
  3. Nora heard three stories inside one. Which stories are held inside yours?
  4. Each of the three could teach something different to different people. Who in your organisation could learn from each of the stories inside yours?

Self-Coaching Exercise — Your Rehearsal

Tell your story aloud, from beginning to end, to one or two people who can listen as your audience would. Ask them:

  • Where did your attention drift?
  • Where did the meaning blur?
  • Did any part of the story undo another?

Then look at your story again. Write three headings, What Went Wrong, What Went Right and Why It Mattered, and note which parts of your story belong under each one.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Stage 9 — The Telling

On the 28th, Cillian stood in front of the leadership team in the boardroom on the top floor. Rachel sat near the end of the table. He had printed the timeline and the six actions as an appendix. He didn’t refer to them once.

He told the story as he had shaped and rehearsed it, from Priya’s warning on the Friday to the man on the platform, with his team’s changes in every part of it.

After the Telling

When Cillian finished, the room was quiet. Then the chief executive asked a question Cillian hadn’t prepared for.

“How many other warnings are sitting in our systems right now, marked low priority?”

Nobody knew. By the end of the meeting, the leadership team had agreed to find out, across every team in the company.

Afterwards, Rachel caught him in the corridor. “I’d like this story to become part of how we all learn here,” she said. “Could you develop it so that others can tell it too?”

Cillian thought of Nora, and of the note he had made on Sunday evening.

Three Complete Stories

Over the following fortnight, Cillian developed the story into the three Nora had heard inside it, each one complete, with its own powerful beginning, engaging middle and memorable ending.

The Failure Story

“On the Friday before the launch, Priya, one of our testers, wrote a note. The new payment change hadn’t been tested at rush-hour volumes. She logged it, it was marked low priority, and in the final rush to release, nobody read it again. Including me.

On Tuesday morning, the payment service failed exactly where Priya had said it could. For three hours, at the busiest time of day, passengers couldn’t buy tickets. The note that could have prevented it was sitting in our system the whole time.

When I asked Priya about it, she said, ‘I said it once. I should have said it again.’ She shouldn’t have needed to. That’s what went wrong. The warning was there. We didn’t make room to hear it.”

The Success Story

“At five to seven on Tuesday morning, the phones in Grace’s support room started ringing, and they didn’t stop for three hours.

For the first hour, nobody knew what was wrong. Marek was searching through a system that looked perfectly healthy until the number of passengers rose. At 07:40, he found it. Twenty minutes later, the rail operator agreed that passengers could board and buy on the train. By 08:10, Sam had rewritten the message on every passenger’s screen, which until then had been telling them to try again when trying again was the one thing that wouldn’t work. Grace’s team took one thousand four hundred calls, and not one of them was cut short.

By 10:00, passengers could buy tickets again. By lunchtime, the full fix was in place. Nobody on the team was asked to stay. Everyone did. That’s what went right.”

The Passion Story

“Two years ago, we built this app because half the stations on the line have no ticket office. Before the app, passengers at those stations queued at a single machine, in all weathers, hoping it worked.

On Tuesday morning, an older man stood on one of those platforms in the rain, about to miss a hospital appointment. He rang Grace’s team, and he kept apologising, as though it was his fault. Grace stayed on the line with him until the station staff let him board. That afternoon, she rang him back. He had made his appointment.

That’s why it matters. Every passenger with our app in their hand is trusting it to work. That trust is what we build. From the next release, every launch meeting will begin with one question: what warning haven’t we heard yet? Priya has agreed to ask it first.”

Six Months Later

The three stories had travelled further than Cillian had imagined. People in their first week heard them at their induction. The leadership team told them at their own away day. Experienced engineers who had been with the company for decades heard them at the all-staff meeting, and two of them came to find Cillian afterwards with warnings of their own that had never been heard.

Every launch meeting now began with Priya’s question. At the third one, a new developer answered it with a problem nobody else had spotted. The release was delayed by a day. Nobody on a platform ever knew.

Priya had started telling the Failure Story herself, to every new tester who joined. Grace told the Passion Story to her support team. Marek and Sam told the Success Story together, finishing each other’s sentences.

Nothing about the work had become easy. There were still difficult mornings. But the company had begun to learn from its own stories, and to tell them completely.

On Sunday evening, Cillian rang Nora and told her what had happened next.

“And why does it matter?” she asked.

This time, he didn’t need to think.

“Because a story told completely,” he said, “keeps teaching long after the morning it’s about.”

There was a pause on the line. “Now that,” said Nora, “is a story.”

Reflection Point

A story told completely builds trust, because it tells what went wrong without defending it, what went right without spinning it and why it mattered without losing sight of the people the work is for. Cillian’s one story served the review. Developed into three complete stories, it kept teaching, because others could retell each one. The stories travelled from a single review to every part of his organisation, reaching people in their first week and those who had been there for decades, and each telling carried the learning a little further.

Learning Questions

  1. Cillian’s story included his own part in what went wrong. What would it take for you to tell what went wrong, including your own part, without defending it?
  2. Rachel asked Cillian to develop the story so that others could tell it too. Which of your stories could others learn to tell?
  3. The Passion Story began with why the team built the app at all. Why does your work exist, and who is it for?
  4. Six months later, the stories were being retold by people across the organisation. Who could retell each of your three stories, and to whom?

Self-Coaching Exercise — Your Three Complete Stories

Using everything you have written so far, tell your event as three complete stories:

  • The Failure Story: what went wrong, including your own part in it
  • The Success Story: how people responded, and who made the difference
  • The Passion Story: why the work matters, and to whom

Give each story its own powerful beginning, engaging middle and memorable ending. Then read all three aloud, in that order, and notice how they work together.

Pause here to complete this exercise in your journal or preferred note-taking system.

Your Responses and Notes:

Where You’ve Arrived

You came into Part Three with a story shaped from beginning to end. You leave with an audience map, a story tested aloud and three complete stories, a Failure Story, a Success Story and a Passion Story, ready to tell and retell.

Cillian began three weeks earlier with eleven accurate pages and a question from Nora he couldn’t answer. He finished with one story that served the review, and three that became part of how his whole organisation learned.

Your Story, Told Completely

You began with an account you were expected to give.

You finish with:

  • Every version of an event from your own working life, gathered and read together
  • The story beneath the timeline: what went wrong, what went right and why it mattered
  • A powerful beginning, an engaging middle and a memorable ending, each written, questioned and rewritten
  • An audience map, with a telling shaped for each of the people who need to hear it
  • A story tested aloud, with what your listeners heard
  • A Failure Story, a Success Story and a Passion Story, each told completely

Cillian never stopped writing accurate timelines. He discovered the story beneath them, and found the craft to tell it in a way that his whole organisation could learn from.

Sustaining Your Storytelling Through Five Practices

Cillian’s three weeks were a beginning. What he learned about finding, shaping and telling stories kept deepening in the months that followed, because he kept practising. Five practices sit at the heart of every School of WorkLife resource, and each one helps you keep your own storytelling alive long after the review has passed.

For each practice, take time to reflect on the questions and write your responses.

1. Develop a Practice of Self-Awareness

Self-awareness begins with noticing your own responses as you tell a story: the parts you rush, the parts you avoid and the moment your voice changes. Cillian felt his first review was thin before he could say why, and he sensed there was more in his story long before Nora named the three stories inside it. Noticing those feelings, and taking them seriously, shows you where the real story lies.

Self-Awareness Questions:

  • Which part of my story do I rush, or leave out altogether?
  • Where do I feel defensive when I tell it?
  • Which part of my story do I most enjoy telling, and why?

Pause here to complete this practice in your journal or preferred note-taking system.

Your Responses and Notes:

2. Develop a Practice of Observation

Observation turns your attention outwards, to the people who were there and the people who are listening. Cillian’s five conversations showed him five different mornings, and his rehearsal showed him what his listeners heard that he couldn’t. Observing how others experienced an event, and how they receive your telling of it, reveals the story you would otherwise miss.

Observation Questions:

  • Who saw this event differently from me, and what did they see?
  • When I tell a story, where does my listeners’ attention drift?
  • Which voices are missing from the stories my team tells?

Pause here to complete this practice in your journal or preferred note-taking system.

Your Responses and Notes:

3. Develop a Practice of Effective Self-Feedback

Effective self-feedback means looking at your own stories clearly and kindly, so that you learn from them rather than defend them. Cillian’s first versions of his beginning, middle and ending were accurate and safe. His rewritten versions told the truth more fully, including his own part in what went wrong. Writing regularly about what worked in a telling and what didn’t gives you the same chance to improve.

Effective Self-Feedback Questions:

  • What worked in the last story I told at work, and what would I change?
  • Where did I protect myself rather than tell the whole story?
  • What did my listeners need that I didn’t give them?

Pause here to complete this practice in your journal or preferred note-taking system.

Your Responses and Notes:

4. Develop a Practice of Insightful Self-Questions

The right question can open a story that months of reporting leave closed. Nora’s question, “And what happened next, and why does it matter?”, changed everything about how Cillian saw the launch morning. Priya’s question, “What warning haven’t we heard yet?”, changed how his whole organisation worked. Asking yourself insightful questions, regularly, bridges the gap between reporting and storytelling.

Insightful Self-Questions:

  • What happened next, and why does it matter?
  • Where does this story really begin?
  • What warning haven’t I heard yet?

Pause here to complete this practice in your journal or preferred note-taking system.

Your Responses and Notes:

5. Develop a Practice of Writing Your WorkLife Stories

Your Failure, Success and Passion Stories are a beginning. Every working year brings new events worth telling, and each new story strengthens your craft. Cillian’s three stories became part of how his organisation learned, retold by others long after the review. Well-crafted stories help you communicate what happened, what you learned and why your work matters, in a review, a team meeting, an induction or a conversation with someone facing what you once faced.

Story Development Questions:

  • Which recent event would make a new Failure, Success or Passion Story?
  • Who in my organisation could learn from a story I haven’t yet told?
  • Which of my stories could someone else retell, and what would they need to tell it well?

Pause here to complete this practice in your journal or preferred note-taking system.

Your Responses and Notes:

Remember: These five practices work together. Self-awareness notices what you avoid, observation hears what others saw, effective self-feedback learns from each telling, insightful self-questions find the story beneath the facts, and writing your WorkLife stories gives them a shape others can hear.

Continue With the Complete Resource

The Workbook gathers every tool from the story into one place with Cillian’s worked examples, the Facilitator Guide brings it into group sessions, and the Manager’s Guide explores the same story from the other side of the table.

Download the complete resource for free → THE ART OF WORKLIFE STORYTELLING AT WORK

© School of WorkLife 2026. All rights reserved.

Share Your Reflections

After you’ve worked through the learning resource, I’d appreciate it if you could take a moment to answer three short questions. It really helps me to keep creating resources that are useful to you and your organisation:

Answer the three questions

Listen to the audio version here:

Connect and Continue

Work With Me: Individual WorkLife Coaching, Commissioned Learning Resources, Speaking Engagements and Organisational Partnerships.

Support This Work: Your support makes a difference and helps me to continue creating resources that are accessible to everyone. Thank you. Carmel

Explore Story-Based Learning for Organisations — original stories and tailored learning resources that help your people grow, independently or together in facilitator-supported sessions.

Share This Piece

If this piece resonated with you, or made you think of someone who might appreciate it, please share it forward.


Discover more from School of WorkLife

Subscribe to get the latest posts sent to your email.

Published by Carmel O' Reilly

I'm Carmel O'Reilly, founder of School of WorkLife. I use story-based learning — characters in real WorkLife scenarios — to help people develop their working lives, through Story Lessons, Guided Programmes, and Professional Self-Coaching resources, and the WorkLife Stories podcast. Irish, London-based, and endlessly drawn to a good story.