Lesson 5: Make it a bet, not a task

An initiative is a strategic bet: a group of features aimed at one outcome, with a written hypothesis. It's the layer that separates a product strategy from a to-do list.

The feature factory and how to not become one

A feature factory ships constantly and learns nothing, output without outcomes. The fix is one sentence, written before you build:

If we build [these features], then [this number] moves, as measured by [this metric, from baseline to target].

The hypothesis is falsifiable on purpose. If the number doesn't move, the bet failed, and a failed bet you noticed beats a success you can't prove. Either way you learned; the factory never does.

What goes in an initiative

• A hypothesis in the if/then/measured-by shape.
• Linked features: the work that constitutes the bet (start with one; bets can be small).
• A target date: bets have deadlines; intentions don't.
• An owner: solo, that's you, but writing it keeps the habit for when it isn't.

Do it now

On Initiatives:

1. Create an initiative for the problem your theme named.
2. Link the feature you created in Lesson 4.
3. Write the hypothesis. Real numbers, even if they're guesses, "signup conversion 2.1% → 3%" beats "improve onboarding."