A few years ago I flew to North Carolina for a speaking engagement.
Quick trip. 24 hours. I'd packed for trips like this dozens of times, so I figured I could just throw things in a bag without thinking too hard about it.
I got to the hotel and plugged in my phone. Nothing happened. No charger.
Setting up for the talk, I reached into my bag for my clicker. Not there either.
Then I opened the presentation file. The slides wouldn't load.
Three separate things failed before I had said a single word to the audience.
I'd given myself 30 minutes on stage. I'd given myself essentially zero minutes of serious preparation. And the front stage paid for it.
The Ratio That Changes Everything
When you look honestly at any significant deliverable, there's a ratio between what happens on the front stage and what makes it possible behind the scenes.
For a 30-minute talk, that ratio is roughly 50x. Twenty to thirty hours of backstage work — research, outline, drafting, slides, rehearsal, tech check, speaker notes — to produce thirty minutes that look effortless.
The wedding is a perfect illustration. Two days of front stage. An entire year of backstage.
A birthday party might be three or four hours with the people you love. But the invitations, the venue, the catering, the decorations, the coordination — that backstage could easily be 15 to 20 hours.
A major conference talk to a few hundred people: 45 minutes on stage. Probably 100 hours of prep behind it, at least for something genuinely good.
The front stage is what people see. The backstage is what makes it work. And almost everyone underestimates the ratio.
Why Underestimation Is So Common
There are a few reasons the backstage keeps catching people off guard.
First, the front stage is visible and the backstage isn't. When you watch someone give a polished 30-minute talk, you're seeing the output. You're not seeing the five rehearsals, the three outline revisions, the late night finishing slides, the tech check that found a problem two hours before showtime. The process is invisible. So when you plan your own version, you plan for the visible part only.
Second, we tend to anchor on the deliverable when we schedule. “Give presentation” goes on the calendar with a time block that matches the presentation length. What doesn't go on the calendar is everything that has to happen before the presentation exists. The backstage doesn't show up in most people's task lists or calendars. So they're never quite sure why projects take longer than planned — the work they forgot to account for was the majority of the work.
Third, most project planning methods focus on outputs rather than inputs. We define the goal (30-minute talk), put it on the schedule, and assume the backstage will somehow happen in whatever time remains. It rarely does.
The Outcome-First Fix
The most effective planning method I've found for this is what we call Outcome-First Decomposition.
Start with the front stage outcome: “Deliver a 30-minute talk at Thursday's conference.”
Then immediately ask: what does the backstage actually require for that front stage to go well? Write everything down. For a talk, that list might include:
- Define the core idea and angle
- Research any statistics or examples
- Create an outline
- Write a full draft of the talk
- Build the slide deck
- Do at least two rehearsals (one alone, one with feedback)
- Prepare speaker notes
- Do a tech check with the venue or platform
- Pack the checklist: charger, clicker, backup file
Each of those backstage tasks needs its own time estimate and its own slot on the calendar. Not a vague sense that it'll happen — an actual block.
When you do this for every front-stage item, two things happen. You stop underestimating how much time projects require. And you stop being surprised when things take longer than you thought — because now you've actually thought about them.
Applying This to Your Week
The format I recommend to clients is simple.
At the start of the week, look at your task list and flag every item as front stage or backstage. Front stage is anything that produces the visible deliverable — the talk, the article, the product, the decision. Backstage is everything that makes the front stage possible — the prep, the research, the draft, the review.
For every front-stage item, immediately break it into its backstage components. “Give presentation” becomes 8-10 specific tasks, each with a time estimate.
This exercise usually takes 20-30 minutes and it changes the entire week. Suddenly you can see whether your calendar actually has enough room for the backstage work your front stage requires. Often it doesn't. And now you know that on Monday morning instead of Thursday afternoon when it's too late to fix.
The North Carolina trip happened before I'd really internalized this. I knew the front stage (30-minute talk), but I hadn't mapped the backstage seriously. So pieces fell through. Not because I was careless, but because I'd planned for the visible work and skipped the invisible work.
The 50x ratio sounds extreme until you actually list out everything that has to happen for a talk to be good. Then it starts to feel like an underestimate.
This week's action: Take the next major deliverable on your plate — the talk, the pitch, the launch, the demo. Write down every piece of backstage work it actually requires. Then check whether your calendar has room for all of it. The gap between what's on your list and what's on your calendar is your planning problem.
