Opening 90 Seconds — 3 Options

The opening 90 seconds has one job: get the room to feel something they recognize before you say a single technical word. The moment sentence — the one about another person's dreams — can only land if the room is already nodding when you say it. These three options reach that landing pad by different routes. The register you pick should be the one you can deliver without performing it. Read each one out loud — or pipe it to say — and the one that doesn't make you want to speed up or add hand gestures is probably the one. Trust discomfort over comfort in this choice: the option that feels a little exposed is usually the one that works.

Option 1: The Cold Statement

Register: Direct, quiet, understated from sentence one. The speaker refuses to warm the room up. The warmth the room feels is recognition, not salesmanship.

Word count (spoken only): 242

Approximate runtime: 88 seconds

I've been writing software for ten years. [pause]

Not "building my career." Not "pursuing my passion." Just — writing software. Mostly for other people. That's how the work comes, for most of us. Someone has a problem, they pay you to solve it, you solve it, and then you move on to the next one. And you get good at it. You get faster. You learn what questions to ask before you start. You learn how to scope something down so it fits the time you have. You learn what to promise and what not to.

[look at the room]

And somewhere in there, you realize that getting good at the work and caring about the work are not the same thing.

That's not a complaint. It's just — accurate. Most of the things I was good at, I built for someone else's deadline. Someone else's roadmap. Someone else's reason for why this thing needed to exist.

[pause]

There's a version of this story where I tell you I loved all of it. But that would be a conference talk, not the truth.

The truth is I got really good at building the right things for the wrong reasons. And at some point, being good at it was the only thing keeping me there.

[look down. one breath. look up.]

Then: "I realized how tired I was working for another person's dreams."

Why this works: The declarative opening signals immediately that this is not a hype talk — it defeats the room's expectation in sentence one. "Ten years" is a number the room will hear and locate themselves against. The line "getting good at the work and caring about the work are not the same thing" is the sentence that makes every developer in the room stop shifting in their seat. It names something they've felt but probably not said out loud. The closing image — "good at building the right things for the wrong reasons" — puts the moment sentence on a perfect tee.

Why this might not work for Ethan: This register requires a voice that is controlled and unafraid of sparse air. If Ethan's instinct under pressure is to fill silence with words or to speak faster to show competence, the pauses will read as nerves instead of intention. It's the most demanding register to deliver flat.

Option 2: The Single Scene

Register: Observational, sensory, small. The room is placed inside one specific moment before they've been asked to agree with anything.

Word count (spoken only): 258

Approximate runtime: 92 seconds

[walks to center. no rush.]

It's late. Doesn't matter what night — it's always a Tuesday somehow, or it feels like a Tuesday.

You've been at this for a while. It's a client project. Something about the way a form submits, or the way a list renders, or some part of the system that should work by now but doesn't. And you've been in this file long enough that the variable names have stopped meaning anything.

[pause]

And here is the specific part. This is the part I want you to hold onto.

There's a moment — usually somewhere after the second hour — where you stop caring if you fix it. You just want to close the laptop. Not because you're tired. Because somewhere in the back of your head, you've started doing the math. And the math is: even if I fix this tonight, I'm going to be back here next Tuesday. A different file. The same feeling.

[pause. quieter.]

The work is fine. The client is fine. The money is fine.

It's just not yours.

[look at a specific section of the room. hold it for a moment.]

I spent a long time pretending that distinction didn't matter. That "fine" was good enough, and the things I actually wanted to build were just — hobbies, maybe. For later. After the work.

There kept not being an "after."

Then: "I realized how tired I was working for another person's dreams."

Why this works: The scene is specific enough to be real but vague enough that every developer in the room fills in their own version of it. "A Tuesday" is genuinely observed — every developer has had that night. The turn — "It's just not yours" — is four words that land like a door closing. It creates an emotional fact before the speaker has made a single argument, which means the moment sentence doesn't need to work as hard to earn its weight.

Why this might not work for Ethan: Scene-setting requires the speaker to slow all the way down and trust that the image is doing the work. If Ethan pushes the pace, the scene feels like a bullet list of things that happened rather than a moment the room is inside. There is also a thin edge between "observed detail" and "performing vulnerability" — the second the delivery gets theatrical, the scene collapses. The fix is to stay descriptive and never editorialize mid-scene.

Option 3: The Stillness

Register: Silence as content. The quiet dev's persona enacted before a word is spoken. Maximum variance: if it lands, nothing at Laracon will feel like this. If it doesn't, it reads as nerves.

Word count (spoken only): 238

Approximate runtime: 90 seconds

[walks to center stage. does not rush to the mic. does not look at the slides. looks at the room.]

[8 seconds. not performing — just present. waiting until the room is actually quiet, not technically quiet.]

Ten years. [pause]

That's a long time to get good at something.

[pause. slow.]

I've shipped a lot of things. Some of them you'd recognize if I named them. Most of them you wouldn't, because they weren't mine to name. They belonged to someone else — a company, a client, a product that existed before I got there and kept existing after I left.

[pause]

I don't say that as a complaint. I want to be careful about that. The work was real. The problems were real. Getting good at something you don't own is still getting good at something.

[looks down for a moment. back up.]

But here's what I noticed, somewhere around year eight or nine.

I had gotten really good at a specific skill that nobody talks about at conferences.

[beat]

The skill of showing up to work that matters to someone else and making it matter to you, too.

[pause. quieter now.]

And I had been doing it for so long that I couldn't quite remember what it felt like to just — skip that step.

Then: "I realized how tired I was working for another person's dreams."

Why this works: The silence at the opening doesn't read as nerves if Ethan walks out with presence — the difference is whether the speaker looks like they're waiting for permission or granting it. If he can hold those 8 seconds with his eyes on the room, not on the floor, the silence signals authority, not anxiety. The phrase "a specific skill that nobody talks about at conferences" earns attention through contrast — the room has been in conference talks all day and suddenly realizes they've been training themselves not to know this thing. The final image sets the moment sentence up as a release.

Why this might not work for Ethan: This is the highest-variance option and the hardest to rehearse. Silent confidence reads differently on a first-time speaker than on someone with visible stage history. If there's any hesitation in the walk to center, or if the 8 seconds ticks to 10 because Ethan lost track of time, it can feel like a stall. He would need to have run this specific opening 20+ times in front of another person before he trusts it with 800.

Recommendation

Go with Option 2: The Single Scene.

Here is why: Ethan is a first-time speaker who is quiet by nature. That is both the asset and the constraint. The Cold Statement (Option 1) depends on controlling sparse air under pressure — it punishes any instinct to fill silence or speed up, which is exactly what nervous first-time speakers do. The Stillness (Option 3) is genuinely the most powerful option on paper, but it requires 8 seconds of silence in front of 800 people with zero safety net, and it has to be rehearsed in front of live humans — not just alone. The variance is too high for a debut.

The Single Scene threads the needle. It gives Ethan something concrete to do in his voice and body — he is narrating an image, not performing an emotion. Narration is forgiving. If the pacing slips slightly, the scene still lands because the details carry the weight. The specific move of "a Tuesday" is already observed reality, not a constructed emotional beat, which means Ethan does not have to manufacture feeling — he just has to describe what he already knows. The turn at "It's just not yours" arrives almost on its own once the scene is established. For a quiet dev who gets things done, showing the room one specific Tuesday night is exactly the right first move.

If Ethan can rehearse Option 3 ten or more times in front of another person before the talk and the 8-second silence starts to feel like ownership rather than exposure, it becomes the stronger option. Upgrade to it if that rehearsal happens. Default to Option 2 if it does not.