Ask someone to explain their project and they'll give you a list. Phase one, phase two, deliverable A, deliverable B. Clean. Logical. Completely forgettable.
Ask them to tell you the story of that same project and something different happens. They'll tell you about the moment the strategy clicked. The meeting where the CEO finally saw it. The version three that made the client emotional. The launch that changed how the team talked about themselves.
Same project. Entirely different experience of it.
The difference isn't just presentation style. It's a fundamentally different way of understanding what work is — and what makes it worth doing.
Why steps kill projects
A step is a unit of completion. A scene is a unit of meaning.
When you plan in steps, you measure progress by what's been checked off. When you plan in scenes, you measure it by what's been felt. Those are not the same thing. And in the kind of work I do — where the output is a narrative, a brand, a presentation — felt is the only currency that matters.
Steps create a false sense of control. They imply that if each task is completed correctly and in sequence, the project will succeed. But anyone who's shipped a perfectly executed deck to a room that didn't buy it knows that's not how it works. Execution without meaning is just expensive noise.
How scenes work differently
A scene has a beginning, a middle, and an end. It has stakes. It has a shift — something that changes between the opening and the close.
When I approach a project in scenes, I'm asking different questions at every stage. Not "what needs to be done?" but "what needs to happen here?" Not "what are we delivering?" but "what does the audience feel at the end of this?"
For a pitch deck, the scenes might be: confusion (they come in not understanding the problem), recognition (they see the problem clearly for the first time), possibility (they believe a solution exists), desire (they want to be part of it). Each slide isn't a slide — it's a beat in a scene. Remove it and the scene doesn't work.
That's a very different way to design than "here are our key messages in a logical order."
The neuroscience is on storytelling's side
This isn't just philosophy. People retain information delivered in narrative form at dramatically higher rates than information delivered in lists. The brain is literally wired to track stories — it anticipates what comes next, fills in gaps, assigns meaning, creates emotional connection.
Lists ask the brain to do work. Stories do the work for it.
When you brief me with a list of things you want to communicate, I start immediately translating that into a sequence of scenes. What do I want the audience to feel at each moment? What shift do I need to engineer? Where's the tension and where's the release?
That's not decoration. That's architecture.
Breaking your own project into scenes
Try this: instead of writing a project plan, write a story about your project after it's complete. Start from the end — the launch, the presentation, the pitch — and work backwards. What had to happen for that moment to land the way you want it to?
You'll find yourself describing scenes without trying to. The conversation where alignment happened. The moment the team understood what they were building. The look on the client's face when they finally saw it.
Those scenes are your project plan. The steps are just logistics.
The payoff
Projects planned in scenes don't just feel better to work on. They perform better. Because when the team understands not just what to do but what the work is trying to make someone feel, they make better decisions at every level. They know when something is off because it doesn't serve the scene. They push harder because they understand the stakes.
And when the work lands in a room — in a boardroom, on a screen, in front of investors — it lands as a story, not a presentation. It creates the emotional shift that no checklist ever could.
People remember stories. They act on them.
That's why I stopped making to-do lists and started writing scenes.