Storytelling for managers: how to make a message land

Most managers already tell stories.

They tell them in team meetings, in one-on-ones, when a project slips and they want people to understand why the new plan matters.

The problem is that most people never decide what the story is for.

They just tell it. Whatever memory hands them comes out, in the order it happened, with whatever details show up. Then they wonder why the room nodded politely and went back to doing things the old way.

That's the gap I care about when I teach storytelling to managers. Not literary craft. The message.

Why a manager's story is a tool, not a performance

I believe every conversation has one goal: influence. You talk because you want something to shift in the other person. Sometimes it's a decision. Sometimes it's only how they feel. There's always a purpose, even when it's hard to see, like in a phone call with your mom.

Once you accept that, stories stop being a nice extra.

Think about how many things you already know that don't move you at all. Facts rarely change people. Emotion and stories do.

That's why, in a recent seminar I ran, no idea or tool stood alone. Every one of them came with a real situation from someone's life, showing why it matters and when to use it. The story is what turns a piece of information into something people can picture themselves doing.

A manager who announces a new process is sharing a fact. A manager who shows people the moment the old process broke is giving them something they'll remember.

Start with the message, not with what happened

Here's something most people never notice. Even if you wanted to tell a story completely, with nothing left out, you couldn't. Try describing a single second in full: the colors, the weather, the smell, how it felt. You'd never finish.

So every storyteller is choosing what goes in and what stays out. The only question is whether they're choosing on purpose.

Most people tell stories on autopilot. What decides which detail gets in isn't the message. It's their attention in that moment. When they're focused, the story is tight. When their mind wanders, they jump from detail to detail, and the listener gets lost right along with them.

The way I put it to the people I coach: telling a good story is deciding where to put the camera. A director leaves whole stretches of what happened on the cutting-room floor. Plenty of other things took place that day. Nobody needs them.

So the question isn't "what happened?" It's "what's my message, and which details have to be there so it gets through?"

A participant I worked with, from a technical field, was sure that any story from work would bury the audience in jargon. So I retold it with no professional terms at all. Someone is stuck on the same broken problem for days, dreading another team meeting where they'll have to say it again: no progress. The day they let go and stop forcing a fix before that meeting, the right ideas come from colleagues, and the problem is closed within a few hours.

Anyone can follow that. The technical details weren't carrying the message. They were in the way.

This is common with experts. The better you know your process, the more you want to explain it. Your team doesn't need the process. They need the moment.

And no, this isn't about lying. It's about telling the truth in a way that plugs into something the listener already knows, so it's easy to understand instead of hard.

One story, many messages

This also means a single story can carry different messages.

I have a story about a student whose life changed. When I teach storytelling, the message is that stories can change people's lives. When I teach fast verbal reframing, it's the same story, and the message is that this skill can change your life. When I teach influence, it becomes a story about authentic influence.

The events don't change. What I emphasize does.

For a manager, that's freeing. You don't need a huge library of stories. You need a few real ones and the discipline to decide, every time, what they're for.

Short beats epic

For years I taught storytelling through the hero's journey, the plot structure behind most Hollywood films. I've mostly moved away from it. Not because it's wrong. Because using it well takes a lot of practice. The short version has at least seven stages. The full one has seventeen. If I have to run through that checklist every time I tell you what happened with my kid this morning, I stop being a storyteller and become a technician.

Managers don't need that. People assume a story has to be long to reach someone emotionally. It doesn't. It needs the right ingredients.

When people ask me how much of their personal story to use, I split stories into two kinds.

The first is short, focused and specific, and it makes one point. Tell as many of those as you like. There's no such thing as too many.

The second is the one big story that tries to cover everything. That's where people fall. It gets long, it gets smeared, the point disappears, and the room drifts.

My advice, especially for anyone less confident in front of a group: cut the big story into several short ones. Each gets a beginning, a middle and an end. There was a hero, something changed, look at them now. Keep each one to about two minutes.

Long stories can be extremely powerful. They're also much easier to get wrong. And getting it wrong doesn't mean anyone boos. It just lands worse.

Show it, don't explain it

One ingredient does more work than almost anything else: something physical.

Here's a made-up example. "I struggled with my weight" is a statement. A kid who has to stop and rest halfway up the stairs to a third-floor apartment with no elevator is a picture. Same fact. Completely different effect.

That's show, don't tell. Instead of telling people what happened, you let them see it, as if you're painting a scene from a movie.

It works the same way in a business talk. I once gave feedback on a talk for a general audience where the speaker went deep into explaining a method, acronyms included. What are the odds a general audience remembers those acronyms afterward? Zero.

Don't explain it. Show them. Better still, give them a small taste of it working on them.

Nobody hears the story until they're ready

A leader doesn't push the message until the other person is actually open to hearing it.

When you try to influence someone, they're quietly asking themselves questions. Why are we doing this? Why me? Why now? What's in it for me? What else will this affect? A story that ignores those questions is talking to a closed door.

So the opening has one job. I call it the "why" stage: convincing people this is relevant to them. Anything that doesn't serve that, I cut.

A common trap is opening with a round of "who here has ever..." questions to create identification. That only works if most of the room actually raises their hands. I want at least 70 to 80 percent. Otherwise you've just framed your talk as something that isn't about them.

Another opening I like: start with one dramatic scene from the story, not necessarily the first one. Then pause it. Take two or three minutes to tell people where you're taking them. Then go back to the story. From there, split what's left into segments, and let each one deliver a single insight.

In a one-on-one it's even simpler. Watch the person. If they're trying to follow and still missing something, give more detail. If they're getting impatient, cut and build curiosity instead. The listener tells you how long the story should be.

Test it on real people first

If there's a story I want to use in front of a big group, I tell it to people one-on-one first. Several times. I watch where they're patient and where they're not, and that's where I fix it.

Stand-up comedians work the same way. They refine their material based on how people react, and a lot of it gets shaped in small conversations with friends, not on the big stage. From a stage you can see the nodding. Understanding what really connects to people's lives comes from sitting across from them.

There's a flip side I learned the hard way. When I went too deep, too fast, without preparing the room, people pushed back on the message. They weren't ready to be that exposed in front of strangers. Everyone has their own pace. A manager who opens a team meeting with a heavy, raw story may get resistance instead of trust.

Let the story carry some emotion

A dry list of credentials rarely starts a conversation. Emotion does.

One participant asked me why she should bring a painful chapter of her life into her content, when her audience wasn't only people who'd been through the same thing. My answer: that chapter is a core piece of who she is, and a big part of her audience would identify with it, including many who hadn't lived it themselves. The emotional part of a story is what gets people reacting and talking. A dry professional background was never going to start a conversation.

That doesn't mean everything becomes a confession. I suggested giving it a fair share of her content, not all of it. And if someone doesn't want to share something, that's a legitimate choice.

Personal stories also have a specific place in how people come to trust you. I think about authority on three levels: formal, like degrees and big stages; social; and you yourself. Your own stories belong to that last level. I use mine all the time, but as one piece alongside the others, not instead of them.

Where this points: Authentic Storytelling

My Authentic Storytelling workshop starts from the same place. It's built for managers, and it focuses on the part of business storytelling most training skips: the message.

We work on short stories that carry one precise message. On making people want to listen, without forcing it. On making sure the core message actually lands. And on what to do when disagreement shows up in the room.

The goal isn't prettier stories. It's managers who can stand in front of their team, pick a real moment, put the camera in the right place, and have people walk out knowing exactly what was meant, and wanting to act on it.