Why force a verdict at the end of a sprint?

Because unresolved experiments cost more than failed ones. An idea with no verdict keeps drawing attention indefinitely. Giving it a bit longer is how a two-week test becomes eight months. Forcing a yes or no on a fixed date bounds the cost of being wrong in advance.

How long should a test run?

Long enough to produce a signal. Short enough that the outcome is not sunk cost. In practice that is usually two to four weeks. The more important variable is deciding what would count as a no before you start. After you have invested, almost any result can be read as encouraging.

What happens to ideas that get killed?

They get written up with the reasoning and published in the Idea Vault. A kill log is more useful than a wins page. The reasoning transfers to the next decision, and a success story usually does not. It also makes it much harder to quietly resurrect a question already answered.

The operating system

Experimentation

The method for deciding whether an idea deserves more resource. And for killing it cleanly when it doesn't.

Experimentation is a method for testing an idea cheaply before committing to it. It is also a method for killing it cleanly when the answer comes back no. A time-boxed sprint with a verdict forced at the end, so ideas cannot survive on ambiguity.

This works when the experiment is bounded and measurable. A routine change, a content cadence, a tool adoption. It degrades badly for anything with diffuse outcomes. The scorecard can't hold a real signal. You end up scoring a vibe. The recurring failure mode is running a test with no exit criteria. It drifts until it's abandoned rather than reaching a verdict. An abandoned test teaches you nothing while still costing you the month. The structure below forces the verdict before the experiment starts. Not after it stalls.

№ 01

Time-boxed Sprint, Forced Verdict

A bounded test against a falsifiable claim, scored on defined metrics, ending in a mandatory binary decision: promote or retire.

Window: Two weeks beats a month, in practice
Hypothesis: Falsifiable claim — not a goal
Scorecard: One primary metric beats a composite
Ending: Mandatory verdict — promote or retire
Record: Both outcomes archived — killed tests are assets

Five components. A named hypothesis: a specific falsifiable claim, not a goal. That distinction is the one most people skip. It determines whether the test can produce information at all. Defined inputs: the routine, tool or behaviour under test. A scorecard mixing subjective markers with something objectively countable. A reflection loop partway through. And the decision at the end.

That last component is what separates this from an informal trial. The experiment doesn't simply stop. It receives a verdict. The verdict is recorded whichever way it goes. Killed tests are as much of an asset as promoted ones. They're considerably more likely to be forgotten if nobody writes them down. The record is what stops the same idea arriving again. Eight months later, wearing a different name.

In practice the hypothesis and scorecard stages get completed reliably. The mid-point reflection frequently gets skipped. Experiments with a clear daily signal are tracked consistently. Ones needing assessment across a longer arc are consistently under-reviewed. The honest read: a two-week window beats a thirty-day one. A single primary metric beats a composite score. I've adjusted toward both.

Define the exit before the start. A test with no kill criteria doesn't end. It just gets abandoned.

Writing on this

Questions

This is the method. What actually got run, and what it cost, lives on the field tests page.

The rest of the system