The day my workshop stops teaching me something, I should probably stop running it.

After more than 100 storytelling workshops, I’ve started worrying about something.

• Not attendance.
• Not feedback.
• Not outcomes.

Something else.

The day I walk out of a workshop without learning anything new, that’s the day I should probably stop running it.

When workshops become performances

Early on, I thought my job was simple.

Go in, teach storytelling, deliver frameworks, and make it engaging.

And to be fair, that works for a while.

This is what happens really:

• You get better at delivery.
• You refine your slides.
• You know where people laugh.
• You know where they nod.

From the outside, it looks like mastery.

But slowly, something else starts creeping in.

Predictability.

And in this kind of work, predictability is dangerous.

Because the moment a workshop becomes a performance, it stops being a learning space for them and for me.

Why I refuse to run finished workshops

I’ve come to believe this strongly:

A workshop should never feel finished.

Every session I run has to be at least a delta better than the previous one.

Not dramatically different, but sharper.

A better question.

A clearer example.

A simpler way to explain something that earlier felt complicated.

Because storytelling in corporate settings is not static.

It changes with:

• Context
• Pressure
• Roles
• Personalities
• And the reality people operate in

So, if I walk in thinking, “I already know how this works,” I might still sound polished.

But I will stop being useful.

Where the real workshop actually happens

Most people think the workshop happens in the room.

I don’t think so.

The real workshop happens after week one.

Here’s how I run many of my sessions.

In week one, people learn something. Then they go back to work, and they try to use it.

And that’s where things fall apart.

Deadlines, managers, last-minute presentations, and emails that need to go out immediately are the realities of corporate life.

Frameworks don’t fail in theory; they fail in real life.

Then people come back in week two with questions, awkward attempts, resistance, and half-working stories.

That’s when the real workshop begins.

I have 45 seconds. What do I do?

In one workshop, I was explaining story structure.

Tension. Movement. Shift.

All neat and clean.

Then a senior sales leader said, “This is useful. But I have 45 seconds in front of a customer. What do I do then?”

He wasn’t asking about storytelling. He was asking about reality.

That changed how I approached the workshop.

I started simplifying parts of it.

I looked at how to make your point quickly and not just how to tell a great story.

The next batch got a better version of the workshop.

Not because I improved the slides, but because someone forced me to confront how storytelling actually gets used.

The leader didn’t like it

In another workshop, a participant came back in week two looking slightly annoyed.

She had rewritten a leadership message using one of the frameworks. It was structured, clean, and humane.

On paper, it was clearly better.

But she said, “The leader didn’t like it.”

That one line changed the discussion.

Because storytelling is not just about clarity; it’s also about ownership.

People don’t always reject a message because it’s unclear. Sometimes they reject it because it no longer sounds like them.

Since then, I’ve added something new to my workshops:

Don’t just make it better. Instead, make it sound like you.

I understood it, but I didn’t use it.

In another session, a participant from a technical role said something very honest.

I understood the framework. But when I started speaking, I slipped back into explaining everything.

That’s the real problem.

The problem is not about understanding, but defaulting to old habits.

So, we worked on one small shift.

Before explaining anything, he had to first answer:

Why does this matter?

A week later, he came back and said conversations had changed.

People followed him better. They asked sharper questions. They interrupted less.

It was just one small shift practiced consistently, and there was nothing dramatic.

That’s when I realized:

Storytelling is not learned in a workshop.

It is built as a habit.

Why the 4-week model works

This is why I prefer running workshops over multiple weeks.

Not because it sounds structured, but because it allows a cycle to play out:

Learn -> Try -> Struggle -> Return -> Refine.

And something else happens in the room.

Peer learning.

With 10–15 people in a session:

• One person’s mistake becomes another person’s insight
• Someone from sales helps someone in HR
• A leader’s struggle mirrors a marketer’s problem

The room starts teaching itself, and I learn from it all.

What I measure now

Earlier, I evaluated workshops based on what participants learned.

Now, I look at something else.

What did I learn?

• Did someone ask a question I hadn’t thought about?
• Did someone struggle in a way that exposed a gap in how I teach this?
• Did something from this batch make the next batch better?

If the answer is no, that worries me.

The uncomfortable truth

Here’s what I’ve realized.

If I ever reach a point where I can run a workshop exactly the same way, batch after batch, without learning anything new, I may still be effective, but I will slowly become irrelevant.

Because repetition looks like mastery.

But over time, it becomes distant from reality.

What keeps this alive

I don’t think the value of these workshops lies in my teaching storytelling.

I think the value is this:

Together, we keep discovering what storytelling looks like in real corporate life.

Not in theory or frameworks, but in pressure, deadlines, politics, and imperfect situations.

That’s what keeps the workshop alive.

That’s what keeps the learning mutual.

Closing thought

So now, I measure my workshops a little differently.

Not just by what participants learn, but by whether the workshop itself learned something.

Because the day it doesn’t, I might still be running a workshop, but I would have stopped growing.

And in this kind of work, that’s the beginning of the end.