Heat Strategy: What Competitive Surfing Teaches About Launch Day

A professional surfing heat lasts about thirty minutes. Your score is the sum of your two best waves. There is a clock, an opponent, and priority rules governing who gets what.

Notice what that structure does. It makes the sport almost entirely about decisions rather than ability. Two athletes of identical skill will produce wildly different results based on which waves they take, when they take them, and what they do in the last five minutes.

Launch day has the same structure and most teams treat it as a deadline instead of a heat.

Two waves, not twenty

Only your two best waves count. Catch fifteen mediocre ones and you lose to someone who caught two good ones and sat still for the rest.

Launches work identically. Attention is not additive. Ten channels each producing a small ripple gets you less than two channels producing a real wave, because the second one benefits from the first. Someone who sees you on Hacker News in the morning and again from a trusted newsletter at lunch has had a completely different experience from two isolated impressions.

So the planning question is not "how many channels can we hit." It is "which two can we make count, and how do we make the second one land while the first is still moving."

Everything else is a wave you should let pass.

The priority rule

In a heat, the surfer closest to the peak has priority. Take a wave without it and you are penalised. This forces genuine strategy, because sometimes the right move is to give up a wave to hold priority for a better one.

The launch equivalent is your credibility budget with a given audience. You can ask a community for attention a limited number of times before they stop paying it. Every launch, every announcement, every "we shipped a big thing" spends from that account.

Teams spend it carelessly. They announce a minor feature to their whole list because the quarter needed a milestone, and then three months later the thing that genuinely matters gets a fraction of the attention it deserved.

Hold priority. Save the big ask for the wave that is worth it.

Managing the clock

The clock changes behaviour in ways worth copying.

Early in the heat, you take a decent wave to get a score on the board. Not the best one, a solid one. Having a number removes the pressure that makes people take bad waves later. In launch terms, ship something real to a small audience two weeks before the main event. It de-risks the infrastructure, generates a handful of quotes, and means launch day is not the first time anything has been tested.

The middle is where discipline matters. This is where you wait. Teams fill this stretch with activity because waiting feels like wasting time, and the activity dilutes the launch. Sitting still with a plan is not the same as doing nothing.

The last five minutes are where heats are won. If you need a score, you take the first rideable thing that comes. If you are ahead, you stay in position and deny your opponent. The launch equivalent is the twenty four hours after go live, and almost nobody plans for it. Who is answering comments? Who is watching for the negative thread that needs a real response? Who is writing the follow up while attention is still high? Teams put everything into the launch moment and nothing into the window immediately after, which is when the outcome is actually decided.

The part nobody plans

Ask a team what their launch plan is and you will hear about the day. Ask what happens at hour eighteen and you get silence.

Hour eighteen is when the first substantial criticism appears, when the initial spike has decayed, and when everyone is tired. It is also when a thoughtful reply in a comment thread reaches more people than the original announcement did, because that is where the discussion moved.

Assign it explicitly. Someone owns the first twenty four hours, and that is their entire job that day. Not a shared responsibility, which means nobody. One name.

The heat plan

1. Pick two waves. Two channels, not ten. Name them and name why those two.
2. Sequence them. The second should land while the first is still moving. Twelve to thirty six hours apart, usually.
3. Get a score on the board early. A quiet ship to a small audience two weeks out. Test the infrastructure and collect quotes.
4. Check your priority budget. How many times have you asked this audience for attention in six months? If it is a lot, this launch needs to be worth it.
5. Plan the middle as waiting. Write down what you are deliberately not doing.
6. Assign the first twenty four hours to one named person whose only job that day is the response window.
7. Write the follow up in advance. Whatever happens, something goes out within forty eight hours. Drafting it beforehand means it goes out.

Takeaways

• Only your two best waves count. Ten channels producing ripples lose to two producing a wave.
• Attention from an audience is a priority budget. Spending it on minor announcements means having none when it matters.
• Heats are won in the last five minutes. Launches are decided in the twenty four hours after go live, and almost nobody staffs it.

Cut your next launch plan down to two channels and assign the response window to one person. Then go drop into a heat where the clock is honest and the wipeouts are free.