Killing an idea is a result
In every review deck I have seen this year, the killed ideas are missing. They are not framed as losses — they are simply absent. What survives is a curated slide of shipped features and dashboards trending up-and-to-the-right. The graveyard is unmarked.
This is not a documentation problem. It is a definition problem. If killing an idea does not count as a result, then teams have no incentive to kill quickly, and no way to compound the judgment that killing well requires. Every deprecated bet is treated as a small embarrassment instead of a small experiment that returned useful information.
The correction is small and unromantic: write the kill criterion at the same time you write the hypothesis, in the same document, in the same session. Not later. Later never happens. If you cannot describe the observation that would make you stop, you are not running an experiment — you are financing an opinion.
The teams that ship best are not the teams that pick correctly more often. They are the teams that abandon incorrectly faster, and can prove — from their own notes — why.