How to Reject an Idea Properly

Every programme rejects ideas constantly, and almost no programme keeps any record of it. The idea is declined in a meeting, or quietly deprioritised, or simply left to age at the bottom of the backlog, and the reasoning, whatever it was, evaporates. Then, six months later, the idea comes back. Different sponsor, new words, same idea. And because nothing was recorded, the organisation pays for the same debate twice. Then a third time. Teams that have run experimentation for years report spending real fractions of their planning time re-litigating ideas that were already examined and declined. The fix rests on a reframe. A rejection is a decision. It was made for reasons, on evidence, by people. Decisions deserve records, and rejected ideas are the half of your decision history that almost nobody keeps.

What to record

A rejection record is four lines, not a form.

The idea, stated plainly enough that its next incarnation is recognisable.

The reason, from a short menu: contradicts existing evidence, already tested, weak hypothesis, no capacity now, does not serve current objectives. The menu matters, because "rejected: contradicts evidence" and "rejected: no capacity in Q3" have completely different futures.

The evidence, linked. If the idea conflicts with research or a past experiment, the record points at it. This is what turns the record from an opinion into a decision.

The revisit condition. Some rejections are permanent; most are circumstantial. "Revisit if the pricing model changes" turns a dead idea into a dormant one and makes the record a planning asset rather than a graveyard.

How to say no without the politics

The quiet benefit of rejection records is that they depersonalise refusal. Without them, declining a stakeholder's idea is one person's judgement against another's enthusiasm. With them, the evidence does the refusing: this was examined in March, here is what we found, here is the condition under which it reopens. The stakeholder is not being overruled; they are being shown the organisation's memory. It is remarkable how much easier no becomes when it arrives with receipts.

The compounding payoff

The first month of keeping rejection records feels like admin. The value arrives from the second occurrence onward, and it compounds. Triage gets faster, because returning ideas are recognised in a minute instead of debated for an hour. Intake quality rises, because a visible record of what gets declined and why teaches people what a strong idea looks like. And the programme accumulates the rarest kind of institutional knowledge: not just what it learned, but what it decided, including what it decided not to do.

A programme that only remembers its wins has half a memory. The rejections are the other half.