Storytelling: How to Make People Remember What You Said

Picture a Monday team meeting at a logistics company. Two people report on the same customer support project. Tomasz goes first. He has a slide with nine bullet points: response times, ticket volumes, a new escalation process, a staffing change, two tools that were replaced. Every point is accurate. He reads them clearly. People nod, and a few write something down.

Then Nomvula speaks. She has no slide. She says: "Three weeks ago a bakery owner called us at six in the morning. Her delivery of flour hadn't come, and she had forty loaves to bake before eight. Under the old process she would have waited until nine for someone to pick up. This time Kiran answered in under two minutes, found the van, and told her it was eleven minutes away. She baked the bread. That is what the new process is for."

A week later, ask anyone in that room what they remember. Almost nobody can give you one of Tomasz's nine points. Almost everybody can tell you about the bakery, the flour and the eleven minutes. Tomasz did nothing wrong. He gave more information than Nomvula, and his information was more complete. But information that is not remembered cannot do any work, and hers was remembered.

This part of the series is about how to do what Nomvula did, on purpose, honestly, and in the time you actually have. We'll start with what a story is, build one step by step from a dull list, and then move to the stories you should have ready for interviews, pitches and presentations.

Why a short story stays when a list of facts fades

You already know this from your own life. Think of a teacher you had at school. You have probably forgotten most of the lessons, but you remember the day the experiment went wrong, or the time the teacher told the class about their own first job. Think of the last wedding or funeral you attended. You won't remember the general praise ("he was a kind man"). You'll remember the speaker who said, "He once drove four hours to bring me a spare key, and then pretended he was in the area anyway."

I won't quote you a figure for how many times more memorable a story is than a fact. You will see such figures repeated in presentations and articles, usually without a source you can check, and I'd rather not pass them on. You don't need a number. The common experience is strong enough, and there are some plain reasons for it that you can test on yourself.

A story has a chain, and a list has none

In a list, each item stands alone. If you forget item four, nothing helps you find it again. In a story, each event causes the next. The flour didn't arrive, so she called, so Kiran looked for the van, so she knew she could wait. If you remember one link, it pulls the next one back into your mind. This is why you can retell a film you saw once, years ago, but can't repeat a phone number you heard this morning.

A story gives the listener pictures

"Response times improved" gives the mind nothing to look at. "A bakery owner at six in the morning with forty loaves to bake" gives it a person, a place, a time of day and a worry. Most people find that things they can picture are much easier to recall than abstract statements. You don't need a theory for this. Try to remember your last three meetings, and notice that what comes back are scenes, not agendas.

A story makes the listener care what happens next

As soon as someone has a problem, we want to know how it ends. That small wish to know the ending is what holds attention. A list creates no such wish. Nobody has ever leaned forward to find out what bullet point six will be.

None of this means facts are unimportant. It means that facts and stories do different jobs. Facts prove. Stories make people understand and remember. The strongest speakers use both: a story so that people care, then the facts so that people can trust it. We'll come back to that combination in the advanced section on stories with data.

Level 1: What counts as a story at work

Many people think they have no stories. When I ask what they mean, it turns out they believe a story has to be dramatic, long, or funny, and that telling one needs a special talent. None of that is true for the kind of story we're talking about.

A story at work can be thirty seconds long. It needs five things:

• A person. Someone specific, with a name or at least a role. It can be you, a colleague, a customer.
• A problem. Something that person wanted and couldn't easily get, or something that went wrong.
• What happened. What somebody did about it.
• What changed. The situation afterwards, different from the situation before.
• What it means. The reason you are telling it to this listener, now.

That's all. If something changed for someone, and you can say why it matters, you have a story. Here is one that takes about twenty-five seconds to say aloud:

"When I joined, our new starters got a forty-page handbook on day one. Mei, who started in March, told me she read it on the train home and still didn't know where to find the printer. So we replaced it with a one-page map and a buddy for the first week. Last month's starter was taking customer calls by Thursday. People don't need more information on day one. They need someone to ask."

Person: Mei. Problem: forty pages and no printer. What happened: a map and a buddy. What changed: taking calls by Thursday. Meaning: the last two sentences.

What is not a story

It helps to know what you're leaving behind. These are often called stories, but they don't work as stories:

The simplest test is this: can the listener see one person doing one thing at one time? If not, you have a statement. Statements are useful, but they aren't what people will repeat to their colleagues tomorrow.

Level 2: A simple structure, and one fact list rebuilt as a story

When you're new to this, use a fixed order. It stops you from wandering and it means you always know what comes next, which calms the nerves. The order is:

1. Situation. Who, where, when. One or two sentences.
2. Difficulty. What went wrong, or what stood in the way.
3. Action. What someone did about it.
4. Result. What was different afterwards.
5. Meaning. Why this matters to the person listening.

Beginners usually spend too long on the situation and forget the meaning. As a rough guide, the situation should take no more than a fifth of your time. The difficulty and the action are the middle of the story and deserve most of it.

The starting point: a plain list

Picture Arjun, who manages a small warehouse team. He has two minutes at a regional meeting to explain why other sites should adopt his team's new labelling system. His first draft looks like this:

"We introduced colour-coded shelf labels in April.
Picking errors fell from about thirty a week to about six.
Training time for new staff was reduced.
The cost was low.
Staff feedback has been positive.
We recommend other sites adopt the system."

Everything in it is true and relevant. It is also the kind of update that people forget before the next speaker has finished. Let's rebuild it, one improvement at a time.

Step 1: Find the person

Ask: who felt this problem? Not "staff", but one member of staff. Arjun thinks about it and remembers Joao, who had joined in February and was sent home upset after his third day.

"In February a new picker called Joao joined my team."

Already the listener has somebody to follow. We've replaced "new staff" with a human being.

Step 2: Find the moment of difficulty

Ask: when exactly did the problem show itself? Look for one day, one hour if you can.

"In February a new picker called Joao joined my team. On his third day he sent eleven wrong items in one shift. The shelf codes were eight characters long and two neighbouring shelves differed by a single digit."

Now there is something at stake. We can imagine how Joao felt. We also understand the cause, and it's the system, not the man. That matters: the story is kind to Joao.

Step 3: Show the action as a decision

"We introduced colour-coded labels" is passive and flat. Who decided, and what did they actually do?

"I asked him to show me how he read the labels. He said, 'I don't read them. There's no time. I look at the shape of the number.' So that weekend we bought coloured tape, and gave every aisle a colour and every shelf a large two-digit number."

Notice the line of dialogue. "I look at the shape of the number" does more than a paragraph of explanation. It tells the listener how the error really happened, in the words of the person it happened to.

Step 4: Give the result, with the number in its place

The number from the original list comes back now, and it lands much harder because we know what it means.

"The following week Joao made one error. Across the team, wrong picks went from about thirty a week to about six, and the tape cost less than a team lunch."

Step 5: Say what it means for this audience

Arjun is speaking to managers of other sites. The meaning must be about them.

"If your pickers are making mistakes, I'd ask them the question I asked Joao before you retrain anyone. It may be your labels, not your people. I can send the colour plan to anyone who wants it."

The finished version

"In February a new picker called Joao joined my team. On his third day he sent eleven wrong items in one shift. Our shelf codes were eight characters long, and two neighbouring shelves differed by a single digit. I asked him to show me how he read the labels. He said, 'I don't read them. There's no time. I look at the shape of the number.' So that weekend we bought coloured tape, and gave every aisle a colour and every shelf a large two-digit number. The following week Joao made one error. Across the team, wrong picks went from about thirty a week to about six, and the tape cost less than a team lunch. If your pickers are making mistakes, ask them what I asked Joao before you retrain anyone. It may be your labels, not your people. I can send the colour plan to anyone who wants it."

Said at a normal pace, that is a little under a minute. It contains every important fact from the list: the date, the fall in errors, the low cost, the recommendation. Two items were cut ("training time was reduced" and "staff feedback has been positive") because they were vague and the story makes them obvious. Nothing was invented. Arjun simply went back to what really happened and chose to tell it through one person.

Level 3: Details that make a story real, and cutting the rest

A story feels true when it has a small number of exact details. It feels slow when it has many. The skill is choosing. There are five kinds of detail worth looking for, and you rarely need all five in one story.

One person

Tell it through one person, even if forty were involved. "Our customers were frustrated" becomes "A dentist in a small town rang us three times in one afternoon." If other people are needed, give them roles instead of names: "her receptionist", "my manager". A listener can comfortably hold two or three characters in a short spoken story. Beyond that, they start to lose track of who is who, and while they work it out they stop listening.

One moment

Stories happen at a particular time. "We often had problems with deliveries" is a habit. "On the Friday before the holiday, at ten to five" is a moment. If your story covers months, choose the single scene that shows the problem best and summarise the rest in one sentence.

One line of dialogue

Real speech is the fastest way to bring a person into the room. Compare:

One line is usually enough. If you can't recall the exact words, say so honestly: "She said something like..." That small phrase keeps you truthful and costs you nothing.

One number

A single exact number gives a story weight. Eleven wrong items. Forty loaves. Four hours of driving. Choose the number that a listener would repeat, and leave the others for the handout or the questions afterwards. Three numbers in a row turn a story back into a report.

One sense detail

Something that could be seen, heard or felt: the coloured tape, the flour, the cold of the loading bay, the sound of a phone that keeps ringing. One is plenty. It acts like a photograph pinned to the story. More than one or two and it starts to sound like you're writing a novel, which in a meeting makes people uneasy.

Cutting everything else

Here's the hard part. When something really happened to you, every detail feels important, because you were there. The listener wasn't, and needs far less than you think. Picture Ingrid, a project manager, describing a software launch to a new client:

First version: "So this was back in, I think, 2021, or it might have been early 2022, because it was just after we moved offices, and we had a client, a mid-sized insurance firm, well, actually they were a broker, not an insurer, and their head of operations, who'd been there about eleven years and had just come back from leave, contacted our sales director, who then passed it to me because the usual account manager was away..."

Forty seconds in, nothing has happened. Every clause is true and none of it helps. Ingrid's cut version:

Cut version: "Two years ago a broker came to us with a launch date they couldn't move: the first of January, when a new regulation began. It was already October."

Two sentences, and we are in the difficulty. To cut your own stories, ask of each detail: if I removed this, would the listener be confused, or would they miss something they'd enjoy? If the answer to both is no, it goes. The year, the office move, who passed the call to whom: all of it goes.

Level 4: Length control, the same story at 20 seconds, 60 seconds and 3 minutes

You rarely get to choose how long you have. Someone asks a question in a lift, or the chair of the meeting says, "We're short of time, can you do it in one minute?" A story that only works at one length is fragile. You should be able to stretch and shrink the same story without losing its point.

The rule is simple: the point and the change never get cut. The details do. Picture Chiara, who runs training for a hotel group. Her story is about a night receptionist.

The 20-second version

"Last winter one of our night receptionists, Bao, noticed a guest had left her passport on the desk, and drove it to the airport himself at five in the morning. She has booked with us eleven times since. Nobody told him to do that. We hire for that, because you can't train it."

This version has the person, the action, the result and the meaning. The situation and the difficulty are squeezed into half a sentence. Use it in conversation, in an introduction, or as one example among several.

The 60-second version

"Last winter one of our night receptionists, Bao, was finishing his shift at about half past four. A guest had checked out an hour earlier for an early flight, and when he tidied the desk he found her passport under the key card folder. He rang her mobile. No answer. He had a choice. The rule says lost property goes in the safe and the day manager deals with it. But the day manager starts at eight and the flight was at seven. So he left a note for his colleague, got in his own car, and drove to the airport. He found her at the check-in desk, emptying her bag onto the floor. She has booked with us eleven times since then, and she asks for Bao by name. Nobody told him to do that. We can teach the booking system in a week. We can't teach that, so that is what we look for when we hire."

What was added? A moment (half past four, the key card folder), the difficulty as a real choice between the rule and the guest, and a picture (the bag emptied on the floor). This is the right length for a presentation example or an interview answer.

The 3-minute version

At three minutes you have room for things the shorter versions cannot hold. You don't add more events. You add depth to the ones you have. Chiara would add:

• A little of who Bao is. He had been with the hotel for seven months and was, by his own description, nervous about breaking rules.
• The cost of the decision. He could have been in trouble for leaving his post, and he knew it. He spent a few minutes deciding.
• A line of dialogue. What the guest said when she saw him: "You're from the hotel. Why are you here?"
• What happened afterwards inside the company. The day manager's first reaction was to ask why the rule was broken. The second was to change the rule.
• A fuller meaning. What this changed in how the group interviews people, with one example question they now ask.

The word counts are rough guides for an unhurried speaking pace with pauses. Your own pace will differ, and if you're speaking to people who are listening in their second language, slow down and use fewer words. A timer tells you the truth. Your feeling about how long you spoke almost never does.

Level 5: Seven stories you should have ready

Good storytellers at work are rarely inventing on the spot. They have a small set of stories they know well, and they pick the one that fits. Seven types cover most situations. The examples below are illustrations with invented people. Yours must come from your own life.

1. Who I am and why I do this work

This is the story behind your introduction from Part 1. It answers the question people don't ask aloud: why should I believe you care about this? Picture Farida, a physiotherapist, at a networking evening:

"When I was fifteen my grandfather had a stroke. The hospital sent him home with a sheet of exercises, photocopied so many times you couldn't see the drawings. He did them wrong for two months. When I qualified, the first thing I made was a set of thirty-second videos my patients can watch on their phones. I work with people recovering at home, and I still think about that sheet of paper."

Why it works: it is short, it names a real moment, and it links the past directly to what she does now. She doesn't say "I'm passionate about patient care". She doesn't need to.

2. A time I solved a problem

This is the story you'll use most in interviews and client meetings. The danger is making yourself sound like a genius. Show your thinking, including what you tried first. Picture Mateus, an accountant:

"A restaurant owner came to me because he was busy every night and losing money. I spent a day on his accounts and found nothing wrong. So I went and sat in the restaurant on a Friday. By nine o'clock I could see it: the most popular dish, a seafood rice, used ingredients that cost more than the price on the menu. Every plate he sold lost him a little. We raised the price slightly and made the portion of rice bigger and the prawns fewer. Within two months he was making a profit on the same number of customers. I learned that the answer is sometimes in the room, not in the spreadsheet."

3. A time I failed and what I learned

People trust you more after this story than after any success, provided the failure is real and the lesson changed what you do. A "failure" like "I work too hard" is not one. Picture Hannah, a team leader:

"In my first month as a manager I rewrote a colleague's report the night before it was due, because I thought it wasn't good enough. I didn't tell her. She found out in the meeting, when she saw slides she didn't recognise with her name on them. She said nothing to me for a week. When we finally talked, she said, 'If it was bad, I'd rather you told me.' She was right. Now I give feedback two days before a deadline, to the person, and they make the changes. It's slower. The work is better, and nobody is surprised in a meeting."

Notice that she doesn't blame the colleague, and she doesn't punish herself at length. One mistake, one consequence, one change.

4. A customer's before and after

This is the working story of anyone who sells, and we'll build on it in Part 8. The customer is the main character. You appear briefly, as the helper. Picture Oluwaseun, who sells scheduling software to clinics:

"A physiotherapy clinic with three rooms was keeping its bookings in a paper diary. The manager, Dalia, told me she spent the first hour of every day phoning people to remind them, and still about one appointment in five was missed. After she moved to automatic text reminders, missed appointments dropped to roughly one in twenty. But that isn't what she mentions when people ask. She says, 'I get to have my coffee sitting down now.'"

You must have the customer's permission to tell this, and the numbers must be theirs, not your hopes. More on that in the honesty section.

5. The origin of a product or company

People want to know where a thing came from, because it tells them what it's for. Keep it to the moment the idea appeared. Picture Linh, who started a small company making lunch boxes:

"My daughter came home from school with her lunch untouched, three days in a row. On the fourth day I asked why. She said the rice was cold and the fruit tasted of rice. I tried eleven boxes from shops. All of them either leaked or mixed everything together. So I drew one with a separate sealed section and a warm layer underneath, and a neighbour who works with plastics helped me make the first twenty. She ate her lunch. Then other parents asked where I'd bought it."

6. A story that explains a value or a rule

Rules without reasons are resented. A story gives the reason. Picture Stefan, a site supervisor, speaking to new workers on their first day:

"You'll see that nobody here walks under a raised load, even for two steps, even when it would save a minute. Four years ago a strap slipped on a pallet of tiles. It landed where a man called Emeka had been standing ten seconds before. He'd moved because he dropped his glove. We were lucky, and luck isn't a system. So the rule is: you walk round. Every time."

Stefan could have read the rule from a safety sheet. The new workers would have agreed and forgotten. They won't forget the glove.

7. A story that makes a number meaningful

Large numbers mean little until they are attached to one case. Picture Priya, presenting to a city council committee about bus routes:

"The report says that the proposed change adds an average of fourteen minutes to journeys from the eastern district. Let me show you fourteen minutes. Mrs Okafor is a cleaner at the hospital. Her shift starts at six. Today she takes the 5.20 bus. With the new timetable, the first bus that gets her there on time leaves at 4.50. That's half an hour less sleep, five days a week, for her and for about three hundred others on that route who start before seven."

The number stays. The story tells the committee what it costs. Be careful that the case you choose is typical. Choosing the single most extreme case and presenting it as normal is a form of dishonesty, even when every word is true.

Level 6: Interview answers as stories

Many interviewers ask what are called behavioural questions: "Tell me about a time when..." you disagreed with a colleague, missed a deadline, dealt with a difficult customer, led something. These are direct requests for a story. The interviewer's thinking is that what you actually did before is a better guide to what you'll do than what you say you would do.

A widely taught structure for these answers has four parts: situation, task, action, result. It is the same shape you learned in Level 2, with one difference. "Task" asks what you were responsible for, which keeps the story about your part. Add a final sentence of meaning, what you learned or do differently, and you have a complete answer.

The weak answer

Interviewer: "Tell me about a time you dealt with a difficult customer."
Candidate: "I deal with difficult customers quite often. I think the key is to stay calm and listen. I'm a good listener and I always try to see their point of view. Customers usually appreciate that."

This is an opinion about customers in general. The interviewer asked for a time and got none. There's nothing here they can believe or check.

The rehearsed answer

Candidate: "The situation was that I was employed as a customer service advisor. The task was to resolve customer complaints. The action I took was to listen actively and offer a solution. The result was a satisfied customer and a positive outcome for the business."

The structure is present, but you can hear the headings. It sounds like a form being filled in, and it's still empty of detail.

The answer that works

Candidate: "Last November a man came into the shop with a laptop he'd bought nine days earlier. It wouldn't switch on, and he had a university deadline the next morning. He was angry before he reached the counter. I was the only one on returns that afternoon, so it was mine to sort out. Our policy was repair, not replacement, and repair took five days. I asked him what he needed by tomorrow. He said, 'My essay. It's on there.' So the real problem wasn't the laptop. I took the drive out, which takes about ten minutes, copied his files to a memory stick, and lent him a display model overnight with my manager's agreement. He handed in the essay. The repair went ahead as normal. He came back the next week and bought a printer. What I took from it is to ask what the person needs today before I start explaining the policy."

That's about seventy seconds. It has a moment, a line of dialogue, a clear statement of what the candidate was responsible for, and an action that shows judgement: he stayed inside the policy and involved his manager.

How to avoid sounding rehearsed

• Never say the headings. Don't say "the situation was" or "the result was". Let the structure be invisible.
• Learn the order of events, not the words. Memorise five or six key words on a card (November, laptop, essay, drive, display model, printer). Tell it slightly differently each time. A word-for-word script breaks the moment you lose your place.
• Say "I" for your actions and "we" for the team's. Interviewers notice both faults: the candidate who hides behind "we" so that nobody knows what they did, and the one who claims everything.
• Answer the question that was asked. If they ask about a disagreement and your best story is about a deadline, don't force it. Prepare six to eight stories so you have a choice.
• Stop after the meaning. Then wait. If they want more, they'll ask, and that becomes a conversation, which is what a good interview is.

One cultural note. In some countries and companies, interviewers expect you to speak plainly about your own achievements, and modesty can be read as a lack of confidence. In others, praising yourself directly sounds arrogant, and it is more natural to credit the team and let the facts show your part. If you're interviewing across cultures, a safe middle path is to describe exactly what you did, in plain verbs, without adjectives about yourself. "I copied his files" works everywhere. "I showed exceptional initiative" works almost nowhere.

Level 7: Stories in a pitch, where the customer is the hero

When people pitch a product or service, the natural mistake is to tell the story of the product ("our platform was built over three years") or of themselves ("I founded this company because I saw a gap"). The listener is polite, and quietly wonders what this has to do with them.

In a pitch, the main character should be someone like the person you are talking to. They have the problem. They make the decision. They get the result. Your product is the tool they picked up, and you are the person who handed it to them.

Here is a short pitch story in full. Picture Rania, who sells a stock-counting app, talking to the owner of two hardware shops:

"You said you count stock twice a year and it takes a weekend each time. A customer of ours, Henrik, has three shops a bit like yours. He used to close on a Sunday, bring in his family, and count with clipboards. He told me the worst part wasn't the counting. It was Monday, typing it all in, and finding the numbers didn't match. He started scanning shelves with his phone, one aisle a day, while the shop was open. He hasn't closed for a stock count in two years. I don't know yet whether your shops would work the same way, so can I ask how your shelves are labelled?"

Look at what she did. She began with the listener's own words. The hero is Henrik, who resembles the listener. She appears only as someone Henrik spoke to. And she ends with an honest limit and a question, which returns the conversation to the customer. That ties to Part 5: a story in a sales conversation should follow listening, because only then do you know which story fits.

There is an honest and a dishonest way to use customer stories. The honest way: a real customer, their real result, told with their permission, with a clear statement if their situation differs from the listener's. The dishonest way: an invented or exaggerated customer, the best result you ever saw presented as the usual one, or a story chosen to frighten. If the only story that would persuade this customer is one that isn't true, you don't have a story problem. You have a product that doesn't fit, and the right thing is to say so. Part 8 builds the whole pitch on this foundation.

Level 8: Delivery, or how to tell it aloud

A well-built story can still fall flat if it is read like a report. You already have the tools from Part 3 (body language) and Part 4 (voice). Here is how they apply to a story.

Slip into the present tense for the key moment

Tell the background in the past tense, then move into the present for the scene that matters. "It was a Friday in October. I'd been in the job three weeks. So I'm standing at the counter, and this man walks in holding a laptop like a tray." The change of tense puts the listener in the room. Use it for one moment only, then return to the past. If English is not your first language and the switch feels risky, stay in the past tense and use a line of dialogue instead. It does the same job.

Pause in two places

Pause just before the turn ("He rang her mobile. Pause. No answer.") and just before the meaning. Two seconds of silence feels long to you and natural to the listener. It tells them something important is coming.

Let your voice and hands follow the story

Slow down at the difficulty. Speak a little more quietly for the line of dialogue, without acting out an accent or imitating the person. Use one or two gestures that show something real: the size of the box, the two shelves side by side. Then let your hands rest. Constant movement takes attention from the words.

Look at people, one thought at a time

In a group, give one sentence to one person, then move to another. On a video call, look at the camera for the turn and the final point, even though it feels strange. Remember from Part 3 that comfortable eye contact differs between cultures: in some places steady eye contact shows honesty, in others a softer, shorter gaze is more respectful, especially toward someone senior. Watch what your listeners do and match it.

End on the point, then stop

This is where most stories are spoiled. The speaker reaches the end and keeps going.

Know your last sentence before you begin. Say it, lower your voice slightly at the end, and be quiet. The silence afterwards is where the story does its work.

Honesty: the rules that keep your stories worth telling

A story persuades because the listener believes it happened. That is exactly why invented stories are a serious wrong and not a small shortcut. If one is discovered, people stop believing your true ones, and they are right to.

• Never invent a story and present it as true. If you want to use an imagined example, say so: "Imagine a shop owner who..." or "Picture a typical Monday." Listeners accept that happily. This article does it throughout.
• Don't improve the facts. If errors fell from thirty to six, don't say "almost zero". If it took four months, don't say "within weeks". Choosing which true details to include is editing. Changing them is lying.
• Don't merge several events into one and call it a single true event. If you combine, say "this is a mix of several customers I've worked with".
• Protect privacy, and say that you've done it. Changing a name, a town or a job title to protect someone is fine and often kind. Add a few words: "I've changed her name" or "I've altered some details so the company can't be identified."
• Don't take credit for a team's work. Say what you did and what others did. "Samira found the fault. My part was persuading the client to give us two more days." This makes you more believable.
• Ask permission to tell other people's stories. A customer's results, a colleague's mistake, a friend's illness: these belong to them. Ask, tell them where you will use it, and accept a no. For customers, check whether a contract or confidentiality agreement applies. For anything involving health, money or family, change the details or choose another story, even with permission, if there's any chance of embarrassing them.

One honest test covers most cases: if the listener later learned exactly how this story came to be told, would they feel misled? If yes, fix it or drop it.

Level 9: Advanced techniques

Opening a presentation with a story

The first minute of a talk is when attention is highest, and most speakers spend it on their name, the agenda and a remark about the microphone. Try beginning inside a scene, with no introduction. Picture Aiko, opening a talk on hospital hand-overs: "It's ten past seven in the morning. A nurse who has been awake for thirteen hours has four minutes to tell the next nurse everything about eleven patients." Then she introduces herself. The audience already knows why they're there. Keep an opening story under ninety seconds, and make sure it leads directly to your subject. A good story that has nothing to do with the talk is only a delay.

Contrast and tension

A story needs a gap between what is and what should be. You can widen it honestly by placing the two side by side: "She had the best sales figures in the region, and she was about to resign." Tension comes from delaying the answer a little. State the problem, let the listener wonder for a sentence or two, then resolve it. Don't withhold for long at work. People are busy, and a story that teases becomes irritating.

The unexpected turn

The stories people repeat usually contain a moment where things go differently from what the listener assumed. Mateus expected the answer in the accounts and found it on a plate. You can't manufacture a surprise, but you can look for the one that was really there. Ask yourself: what did I believe at the start that turned out to be wrong? Place that belief early in the story, so the listener shares it, and the turn will work on them as it worked on you.

Humour that includes

The safest humour is aimed at yourself, at a situation everyone in the room has shared, or at your own earlier mistaken belief. It brings people together. Humour aimed at a group, an accent, a customer, a competitor or an absent colleague divides the room, even if people laugh. And never announce a joke. If a light moment lands, good. If it doesn't, you simply carry on, and nobody knows it was meant to be funny.

Telling stories with data

A chart has a story in it if you look for the change. Use the same five parts: what was normal, what shifted, what we did, what happened, what it means. Picture Diego presenting website figures. Weak: "As you can see, sessions were up and conversion was down in the third quarter." Stronger: "Until July, about three in every hundred visitors bought something. In August it fell to two. Nothing on the site had changed. What had changed was where visitors came from: a video sent us thousands of curious people who were never going to buy. Our regular customers bought exactly as before. So we don't have a website problem."

Then pair the pattern with one case, as Priya did with the bus timetable. The order that works best is usually: one person, then the number that shows this person isn't alone, then what to do. Show all the data that matters, including what weakens your argument. A story built on the two convenient points of a graph will be found out by the first person who asks about the third.

Analogies for technical subjects

An analogy is a very short story that borrows something the listener already knows. Picture Nadia, an engineer, explaining to a finance director why the company needs data backups in a second location: "At the moment it's like keeping the spare house key inside the house." Eleven words, and the risk is understood.

Good analogies come from everyday life (kitchens, roads, keys, queues), match the one feature you want to explain, and are dropped once they've done their job. Every analogy breaks somewhere. If you push it too far, a technical listener will correct it and the conversation turns to the analogy. Say where it stops: "It's not a perfect comparison, but the point about the key holds."

Stories across cultures

A story that works well at home can fail abroad for reasons that have nothing to do with its quality.

• References that don't travel. Sports (a story built on the rules of cricket or baseball), television programmes, national holidays, school systems, local politicians. If the listener needs background to follow, choose a different story or replace the reference with something universal: family, food, weather, travel, a first day at work.
• Idioms. "We hit it out of the park" and "back to square one" are puzzles for many second-language listeners. Use plain verbs.
• Humour. Irony, where you say the opposite of what you mean, is the riskiest. It can be taken literally. Light self-directed humour travels better, but in some cultures a senior person joking about their own failings can confuse or worry an audience.
• Humility norms. In some places a story with "I" as the clear hero is normal and expected. In others it sounds boastful, and a story about what "we" did, or about what you learned from an older colleague, is received far better. The failure story also varies. In some business cultures admitting a mistake in public earns respect, and in others it can cause real discomfort or be seen as damaging the team's reputation.
• Directness of the point. Some audiences want the meaning stated plainly at the end. Others consider it more respectful to let the listener draw the conclusion. If you're unsure, state the point once, gently, and don't repeat it.

These are tendencies, not rules about nations, and individuals differ widely. The practical step is to test the story on someone from that background before you use it, and ask, "Is there anything here that wouldn't make sense or might sound wrong?"

A personal story bank

Keep a simple list, in a notebook or a file. For each story write five things: a short title ("The passport"), the five or six key words that carry the events, the point, the settings where it fits (interview, pitch, team talk), and whether you have permission. Don't write the story out in full. A script makes you recite.

Add to it when something happens, the same day if you can, because the exact line of dialogue is gone by the weekend. Review it every few months. Retire stories that are older than your listeners' patience (a story from ten years ago suggests nothing has happened since), stories whose facts you're no longer sure of, and stories you have told to the same people twice.

Common mistakes

• Too long. The most common fault by far. If a story can be told in one minute, the two-minute version is weaker. Cut the beginning first. Most stories start two sentences too early.
• No point. The story ends and the listener thinks, "And?" Before telling any story at work, finish this sentence in your head: "I'm telling you this because..."
• Too many characters. The manager, the client, the client's assistant, the supplier and the driver. Keep one main person and at most two others, named by role.
• The hero is always you. If every story ends with you saving the day, people stop enjoying them. Tell stories where a colleague, a customer or a junior team member is the one who got it right.
• Starting with an apology. "This probably isn't very interesting, but..." or "I'm not good at telling stories, so bear with me." You have asked the listener to expect little. Begin with the first sentence of the story.
• The moral is hammered. Say the point once. Explaining it three ways tells the listener you don't trust them.

Practice exercises

Exercise 1: A story bank of ten

What to do: Over one week, write ten entries in the format above: title, key words, point, where it fits, permission. Cover all seven types from Level 5, with extra stories for problem-solving, since you'll need those most. To find them, ask yourself: when was I surprised at work? When did I change my mind? What did a customer say that I still remember?

How long: Fifteen minutes a day for seven days.

How to measure: Ten entries, each with a point you can say in one sentence. If you can't write the point, the story isn't ready.

Exercise 2: The one-minute story with a timer

What to do: Choose one story. Record yourself telling it on your phone, with a timer running, and no notes except your key words. Listen back once. Note the time, where you first reached the difficulty, and what your last sentence was. Cut and record again. Then make a 20-second version of the same story.

How long: Ten minutes a day for five days, one story per day.

How to measure: Three targets. Total time between 50 and 70 seconds. The difficulty arrives within the first 15 seconds. The last sentence is the point, with nothing after it. Count your filler endings ("so, yeah", "anyway") and aim for none by day five.

Exercise 3: Retelling to three different listeners

What to do: Tell the same story to three people who differ from each other: for example a colleague in your field, a friend or family member outside it, and someone younger or older than you. Tell it in conversation, not as a performance. Afterwards ask each of them one question: "What would you say that story was about?"

How long: One story a week for four weeks.

How to measure: If all three give back roughly the point you intended, the story works. If they give three different answers, your point is unclear. If they remember a detail but not the point, the detail is too strong or the ending too weak. Also notice what you changed for each listener: which words you explained, which details you dropped. That adjusting is the skill.

One-page summary and checklist

The idea in one sentence: people remember a person, a problem and a change far longer than a list, so tell your facts through one true story with a clear point.

The structure: situation, difficulty, action, result, meaning.

Before you tell a story, check:

• Is it true, and told as it happened?
• Do I have permission, and have I protected anyone who needs it?
• Can I say the point in one sentence?
• Is there one main person the listener can picture?
• Is there one moment, with a time or place?
• Do I reach the difficulty within the first quarter?
• Have I chosen at most one number, one line of dialogue and one sense detail?
• Have I given credit to the people who earned it?
• Will every reference make sense to this listener, in this culture?
• Do I know my last sentence?
• Do I know the 20-second version in case time is short?

While you tell it: begin with the time and the person, not an apology. Slow down at the difficulty. Pause before the turn and before the point. Look at one person per thought. Say the last sentence and stop.

You can now take a dull list and turn it into something people will repeat, at three different lengths, without bending the truth. In Part 8, The Product Pitch, we put this to work where it matters most for many readers: in front of a customer. You'll learn how to present features so that the customer hears what they mean for their own day, how to build an offer around the problem you heard when you listened, and where the customer story from Level 7 fits in the first five minutes of a meeting. Bring your story bank. You'll need at least two customer before-and-after stories, and if you don't have them yet, this week is a good time to ask two customers for permission.