— 8 min read

The Words Are the Show: Why Most Presenters Get This Backwards

Advanced Scripting & Character Written by Felix Lenhard

There’s a confusion that nearly every new performer carries, and I carried it for longer than I want to admit.

The confusion is about what the show actually is. What is it that the audience is experiencing?

My answer, for a long time, was: the trick. The effect. The impossible thing that happens. That’s the show, and everything else — the words, the framing, the conversation — is the packaging around it. Important packaging, sure, but packaging nonetheless. You could have the same show with different packaging and it would still be roughly the same show.

This is completely wrong. And Pete McCabe’s writing on scripting magic was the thing that made the wrongness finally visible to me.

What McCabe Gets at

The argument McCabe makes in Scripting Magic isn’t complicated, but it cuts against a deeply held assumption. He argues that the presentation — the words, the story, the frame — isn’t packaging around the effect. It IS the effect, from the audience’s perspective.

Think about what an audience actually experiences when they watch a performance. They see what the performer shows them. They hear what the performer says. They feel what the performer’s choices make them feel. That is the totality of their experience.

They do not experience the method. They do not experience the technical work happening beneath the surface. They have no access to that. What they have access to is what is presented to them: the visible, the audible, the felt.

Which means the presentation is not a wrapper around the experience — it IS the experience. Every word the performer speaks is part of what the audience is experiencing. Every pause. Every choice of what to say and when to say it and how to say it.

The method is infrastructure. The presentation is the building.

How I Had It Backwards

When I first started performing material for friends and colleagues — before any real shows, just casual demonstrations — I spent enormous amounts of time on the technical work. Learning the sequence, getting the execution solid, building consistency.

I spent almost no time on the words. I’d figure out roughly what I was going to say while I was saying it. I had a general idea of the frame — “let me show you something interesting” — and then I’d improvise around it.

And the demonstrations were often technically sound and somehow flat. People were impressed, in a polite way, but not moved. There wasn’t the reaction I’d seen when watching skilled performers — that genuine astonishment that produces laughter or silence or a look I can’t quite describe.

I thought the problem was the technical work. I practiced more. The technical work improved.

The demonstrations were still technically sound and somehow flat.

The problem wasn’t the method. The problem was that I had no actual presentation. I had a technical sequence surrounded by improvised commentary. The commentary was undesigned. The audience’s experience of the whole thing — which is to say, their experience of the demonstration — was undesigned.

You cannot fix a presentation problem with more technical practice. That’s like trying to make a film better by improving the camera equipment when the script is the problem.

What a Script Actually Does

McCabe is specific about what scripting accomplishes, and the functions go well beyond just having words to say.

A script creates the experience the performer intends, not the experience that emerges from improvisation. Improvisation produces different experiences every time depending on what comes to mind in the moment. Sometimes those moments are good. Sometimes they’re not. A scripted presentation is designed to consistently produce a specific experience.

A script controls pacing. The speed at which information reaches the audience — what they know when, what they’re wondering, what they’re expecting — is entirely a function of the words and their timing. An unscripted performance leaves this to chance. A scripted performance designs it deliberately.

A script establishes the emotional journey. The audience isn’t just processing information while watching a performance. They’re feeling things. The feeling of curiosity that precedes the effect, the tension during it, the release and wonder at the climax, the satisfaction in the aftermath — these are produced by the words and the structure around them. They don’t happen automatically from the technical work.

A script gives the performer something concrete to work with during rehearsal. You can’t rehearse “I’ll say something interesting here.” You can rehearse specific lines, specific delivery choices, specific pauses. The script makes the presentation something you can actually practice, refine, and improve.

The Shift in Practice Priorities

Understanding this shifted my practice priorities in a way that felt uncomfortable at first.

I started spending more time on what I was going to say than on how I was going to execute the technical work. Not that the technical work didn’t matter — it has to be solid enough to not require conscious attention. But once the technical work was above that threshold, additional technical practice had diminishing returns.

Additional scripting work, on the other hand, produced consistent improvements to the audience experience. Finding a better opening line. Cutting a sentence that wasn’t carrying its weight. Identifying a moment where I’d been talking over the effect rather than letting the effect breathe.

This shift required accepting that writing — actually writing, with a notebook or a screen — was a legitimate and important part of magic practice. Not a supplementary nice-to-have. A core discipline.

The technical work is necessary to make the thing happen. The scripting work is necessary to make the audience experience something.

Finding the Words That Actually Work

What I found when I started taking scripting seriously: first drafts are always bad.

My first scripts were functional but inert. They told the audience what was happening without making them feel anything. They explained rather than created. They covered the structural bases but had no life.

This is normal. First drafts in any writing are rough, and scripting for performance is writing. The assumption that the first version of your words should be the version you say on stage is the same mistaken assumption as thinking your first draft of a business proposal should be the one you send.

The work is in the revision. What can be cut? What’s carrying more weight than its length deserves? Where is the rhythm off? Where are you telling the audience what they’re about to feel rather than letting them feel it?

The question I come back to constantly: what is the audience experiencing at this moment? Not what are they thinking about the effect. What are they experiencing? What are they feeling, what are they wondering, what are they anticipating?

If the words are producing the experience I intend, they’re working. If they’re producing something else — confusion, distance, boredom — they’re not, and they need to change.

The Technical Work Doesn’t Disappear

I want to be clear: none of this makes the technical work less important. It makes it differently important.

The technical work is the foundation that makes the presentation possible. Without solid execution, the script falls apart — you can’t deliver lines you’ve written if your hands are demanding all your attention. The technical work has to be automated enough that the presentation can run on top of it.

But the presentation is not a bonus layer added to the technical work. It’s not a nice-to-have. From the audience’s perspective, it IS the work.

They will remember what you said. They will remember how you made them feel. They will remember the story you told, the moment of wonder you created, the experience they had.

They will not remember the method. They cannot. It was invisible to them.

So the thing they remember — the whole thing — is a product of your words and your choices about those words. That’s what you’re building when you script.

When I finally understood this, it didn’t diminish the technical work I’d done. It just put it in the right place. Infrastructure. Necessary, invisible, and in service of something that matters more.

The words are the show. Design them accordingly.

FL
Written by

Felix Lenhard is a strategy and innovation consultant turned card magician and co-founder of Vulpine Creations. He writes about what happens when you apply systematic thinking to learning a craft from scratch.