Your Storytelling Workshop Is Solving The Wrong Problem

Not long ago, an analytics company asked me to help them with storytelling.

I was excited. Then I read the brief. They wanted their dashboards to look more engaging. Charts in a better sequence. A strong opening slide so executives would stay with the numbers until the end.

That’s useful work. But it isn’t storytelling, and I don’t think it was their real problem either. Somewhere in that company, someone had looked at a room full of executives who weren’t acting on the data and concluded, “We need storytelling.” The label got attached before anyone had worked out what was actually broken.

I see this all the time. Nobody walks into a meeting and says, “Our business needs more narrative capability.” What actually comes through the door is much more specific, and much more urgent:

• A leader who can’t get the strategy across to the people who have to execute it.
• A sales team whose pitches sound the same as every competitor’s, even though the offers are very different.
• A technical team that buries customers in detail and loses the room before the point lands.
• A change program nobody outside the leadership team understands, three months after launch.
• A brand with a lot to say and nothing anyone remembers a week later.

Storytelling is usually what gets proposed for problems like these. And the instinct isn’t wrong. These are communication problems, and storytelling does help with communication.

But the problem is bigger than storytelling. If you treat it as a storytelling problem alone, you’ll almost always under-diagnose what’s actually broken.

Where the real failure happens

Here’s the pattern.

A leader announces a change. The room reacts with confusion or quiet anxiety instead of clarity. Someone in HR or L&D is asked to fix it, and they reach for a workshop, because a workshop is easy to buy, easy to schedule, and easy to defend in a budget meeting.

But the failure didn’t happen in the delivery. It happened earlier, at the point where nobody decided which one idea had to travel through the organization intact, and what should follow it. That’s a failure of narrative strategy. A workshop on delivery, however good, can’t reach a problem that happened before delivery started.

I learned this the hard way in a room full of architects.

I was brought in by their organization to run a storytelling program. Before I’d finished introducing myself, I could see the crossed arms and the chairs pushed back. By lunch, a couple of them told me directly that they were only there because their boss wanted them to be.

They weren’t wrong to feel that way. Nobody in that room had asked for the program, including me. Someone had decided the team needed storytelling, a program was bought, and a room was booked. Nobody had asked the architects what they were actually struggling to communicate, or to whom. I got the day back on track by naming the resistance openly. But I’ve often thought about how different that day would have been if the diagnosis had come before the booking.

The same mistake shows up in sales.

A pitch that sounds like three competitors’ pitches usually isn’t failing because the salesperson can’t tell a story. It’s failing because nobody worked out what decision the buyer is trying to make, and built the pitch around that instead of around the product.

I once spent days on a 30-slide deck for a client meeting. Every chart was labeled, every transition was smooth. I plugged in my laptop, and before I could start, the client asked if he could first tell me what was keeping him up at night.

For 45 minutes, he talked about a problem I hadn’t anticipated: a team that wasn’t working, a market that was shifting, and a promise he’d made to his board. None of it was in my deck. I never opened it. It was the best meeting I’ve ever had.

My deck wasn’t bad, but it was about the wrong thing. I’d built it around what I wanted to say, not around the decision he was trying to make.

Ryan Morel, founder of Kompeld, put it well when he was asked what founders get wrong when they start selling. His answer, roughly: it’s not about you. The passion that builds a company keeps pulling the pitch back to the origin story and the features, when the buyer is thinking about their own operational reality, their urgent problems, and how they’ll decide.

Sending that salesperson, or that founder, to a generic storytelling workshop teaches a skill they never lacked. What was missing was deciding what the story needed to be about.

Separating the layers

It helps to pull apart four things that usually get treated as one:

• Narrative strategy. Deciding which idea matters most, for this audience, right now.
• Narrative design. Shaping that idea into a structure: what leads, what follows, and what gets cut.
• Storytelling craft. Finding the material, rehearsing it, and delivering it well.
• The business application. The leadership update, the pitch, the change announcement, the campaign.

A generic storytelling workshop works almost entirely at the third layer. That makes sense: craft is the same for every client, so it scales into a repeatable curriculum. The first two layers don’t scale that way. They require sitting with one organization’s specific, unglamorous problem long enough to diagnose it.

That’s not a criticism of craft training. Craft matters, and rehearsal helps. It’s an observation about where the failure usually sits, and how rarely the standard fix reaches it.

What it looks like when the emotional question is skipped

Change programs are where this becomes most visible, because the emotional question is so easy to overlook.

In 1985, Coca-Cola ran around 200,000 blind taste tests before replacing its original formula with New Coke. The data was clear: people preferred the new taste. Within days of launch, the company was fielding more than 1,500 complaint calls a day. Seventy-nine days later, the original formula was back on shelves.

The logic was sound. But nobody drinks Coke blindfolded. The tests measured what was in the glass. They never asked how people would feel when they took away something they’d grown up with. As Saahil Mehta put it in his Entrepreneur piece on the episode, being right and being trusted aren’t the same thing.

Most internal change programs are New Coke on a smaller scale. The case is logical. The slides are clear. And it lands as pure anxiety, because the question underneath (what does this mean for me?) was never answered. Better delivery won’t fix that. Only a different decision about what the story is about will.

Why the wrong label sticks

If the pattern is this consistent, why doesn’t it get corrected?

Part of the answer is that storytelling training is easy to buy. It has a recognizable name, a predictable format, a day rate that fits an existing budget line, and plenty of providers. Narrative strategy diagnosis doesn’t have that shelf presence. No finance system recognizes it as a line item, so anyone offering it has to explain the category before they can sell it.

So, both sides reach for the familiar label. The buyer gets something they can defend. The provider gets something they can deliver without redesigning their offer. Everyone behaves reasonably, and the real problem stays where it was.

There’s a second reason too, and I saw it at a management school in Chennai. They invited me to speak on the art of storytelling, and I sent my profile to the coordinator as a story. She called back and politely asked for it in chronological order.

After my 90-minute talk, a student asked whether she could write her own profile as a story. I told her she could, just maybe not for placements there. The room laughed, but the point stands: we teach storytelling, and then, when it counts, we ask for the list: the profile, the appraisal, the proposal template. As long as the formats stay the same, craft training alone won’t change much.

Three questions to ask before commissioning any workshop

Before you agree to a storytelling or communication program, whoever is offering it, ask three things:

• Can anyone name the one idea that isn’t traveling, and to whom?

If the answer is vague (“communication in general,” “our storytelling,” “how we present”), that vagueness is the diagnosis. The strategy layer hasn’t been worked through.

The actual pitch deck, the actual change announcement, the actual technical explanation. A program built without touching the real documents is generic by definition, no matter how well it’s delivered.

If nobody can answer that concretely, the program is designed for a good day in the room, not for a changed outcome.

Where the work should start

Storytelling is a craft, and a valuable one. But it was never meant to describe the diagnostic work that decides what the craft should be used for.

The analytics company didn’t need better-looking dashboards. The architects didn’t need a program they hadn’t asked for. My client didn’t need my 30 slides. And Coca-Cola didn’t need a better taste test.

Each of them needed someone to ask, first: What is the one thing that has to land, with whom, and why isn’t it landing now?

Answer that, and storytelling becomes powerful. Skip it, and even the best-told story is polishing a message that was never organized correctly in the first place.