Day 18 of 30

The Two-Week Burn Window

You've got fourteen experiments running, three of them from last quarter, and you can't remember why you started half of them. Sound familiar?

Part 1: The Two-Week Burn Window — Concept

+5 XP on completion

Scene 1

You've got fourteen experiments running, three of them from last quarter, and you can't remember why you started half of them. Sound familiar?

Scene 2

Experiments without deadlines don't stay experiments. They become obligations — zombie projects that eat your time and give nothing back.

Scene 3

Every experiment gets exactly two weeks. At day fourteen, you make one call: kill it, scale it, or iterate it into a new two-week window. No extensions, no "let's revisit later."

Scene 4

Two weeks is long enough to get real signal and short enough to stay honest. You define your success metric on day one, check it on day fourteen, and let the data make the argument — not your ego.

Scene 5

Marcus ran a side project for five months because it "showed promise." When he finally set a two-week window with a clear metric, it took him three days to see the answer had been no for a while. Spoiler: the relief hit harder than the disappointment.

Scene 6

The burn window works because it respects your time and your courage equally. In Part 2, you'll practice setting up your own two-week experiment — metric, deadline, and decision criteria. See you there.

Part 2: The Two-Week Burn Window — Practice

+10 XP on completion

Scene 1

Two weeks. That's the window. At the end you make one of three calls — kill it, scale it, or iterate — and you don't get to stall.

Scene 2

Most experiments die of neglect, not failure. They drift past their expiration date, half-forgotten, draining energy from things that actually matter. The graveyard is full of "I'll get back to that."

Scene 3

The technique is called the Burn Window Protocol. On day one you set the timer, define your success signal, and commit to the verdict before you start. The decision isn't emotional — it's structural.

Scene 4

Here's how it works. Day one: write down what success looks like in plain, measurable terms. Day seven: check the signal — are you trending toward it or away? Day fourteen: make the call. No extensions. Pick your verb and move.

Scene 5

Lisa ran the protocol on her side project — a weekly newsletter she'd been "about to launch" for three months. Day seven, she had twelve subscribers and one genuine reply. Day fourteen, she chose iterate: same concept, different format. Six weeks later, the podcast version had four hundred listeners.

Scene 6

You've got a protocol now. Pick one experiment you've been letting drift, set the fourteen-day clock, and write down your success signal tonight. The verdict is already easier than the waiting.