Speaker Hub uses necessary cookies for secure accounts. With your permission, first party analytics help us improve signup and onboarding. We do not use advertising or cross site tracking cookies. Read the Cookie Policy.
Storytelling in speeches: the part most speakers skip · Speaker Hub
Storytelling in speeches: the part most speakers skip
Most speaker stories fail in the same place, and it is not the beginning. Here is the structure, and the one question that tells you whether a story earns its slot.
•6 min read
Speakers are told to tell stories, so they do, and a lot of the stories do not work. The failure is usually in the same place.
The middle is where they die
Most speaker stories have a decent opening. There is a person, a place, a time. Then the speaker gets nervous about the clock and jumps straight to the lesson.
"So I was in a hospital in Leeds at 4am, and a nurse made a really tough call, and what that taught me is that we need to trust frontline judgement."
Nothing happened. There was a setup and a moral, and the part in between, which is the only part that makes an audience feel anything, has been summarised away.
The middle is the story. Someone wanted something, something got in the way, they had to choose. Cut that and you have an anecdote with a slogan attached.
The shape
You do not need a screenwriting course. Five beats will do:
Someone, somewhere, at some time. Specific. Not "a client of mine once," but "Priya, in the third week of a rollout, on the Friday before a bank holiday." Specificity is what makes an audience picture it, and picturing it is the whole mechanism.
What they wanted. Stakes come from wanting, not from drama. It can be small.
What got in the way. The obstacle needs to be real. If it is trivial, the story has no tension and the audience will feel that even if they cannot name it.
The choice. This is the beat speakers skip and it is the one that matters. What did they do, and what did it cost. A choice with no cost is not a choice.
What happened. Short. One or two sentences. Then stop, and let the room draw the conclusion before you say it.
Do not explain it immediately
The strongest move after a story is silence.
Speakers rush to explain because they are afraid the point was missed. Usually it was not, and the explanation actively weakens it, because a conclusion the audience reached themselves is theirs, and a conclusion you handed them is yours.
Pause. Then say the point in one sentence, not four. If the story worked, one sentence is all it needs.
Put the story first
The instinct is to make the point, then illustrate it. Try the other order.
A story told before the point gives the audience something concrete to attach the abstraction to. By the time you state the principle they already have a specific case in mind, and the principle lands as a name for something they have just experienced.
Told after the point, the same story is an example. The room has already agreed or disagreed with you, and the story is now evidence in an argument they have finished having.
The test
Here is the question worth asking about every story in your talk.
If I cut this, does the point still land?
If yes, it is decoration. It may be a good story, and the audience may enjoy it, and it is still costing you three minutes you could spend on something that does work. This is the most common bloat in a keynote and it is invisible from the inside, because the speaker enjoys telling it.
Be careful with the story you have told fifty times. Those are the hardest to cut and often the least connected to the current talk, because they were built for a different one.
Specificity beats scale
Speakers reach for big stories, thinking impact scales with magnitude. It does not.
A story about one nurse on one shift will do more than a story about a national policy failure, because the room can hold one person and cannot hold a system. The small story is also more likely to be true in the details, and the details are where credibility lives.
If you have a large point, find the smallest concrete instance of it and tell that.
Stories you should not tell
A few categories reliably backfire.
The story where you are the hero. It reads as a brag no matter how it is framed, and audiences are extremely good at detecting it. If you are in the story, be the person who got it wrong.
The story that identifies someone. Change details or get permission. A room that starts wondering whether the person consented has stopped listening to your point.
The story you have not checked. If it is a famous anecdote you picked up secondhand, look it up. A lot of speaking circuit stories are distorted, and being corrected afterwards by someone in the audience is a bad afternoon.
Building it into a specific talk
The same story rarely works unchanged for every audience. Which detail you foreground for a room of clinicians is not the one you foreground for a room of administrators, even when it is the same story with the same point.
That is the job keynote tailoring does: taking material you already have and working out what this particular room needs from it.
Fewer than most speakers use, and each one carrying a specific point. Three well placed stories in a forty minute keynote is plenty. A talk that is all stories has the same problem as a talk that is all data, which is that the audience cannot tell what they are meant to take from it.
Do the stories have to be my own?
No, and pretending a borrowed story is yours is the one version that will damage you. A story about a client, a colleague or a documented case works if you attribute it plainly. What matters is that you know the detail well enough to tell it specifically rather than in outline.
Where should a story go in a talk?
Before the point it illustrates, not after. A story told first gives the audience a concrete situation to hang the abstraction on. The same story told after the point becomes an example, which is weaker, because the room has already decided whether they agreed with you.
