How to Stop Re-litigating Past Decisions

Why "we already discussed this" doesn't work

Saying a decision was already made rarely ends a re-argued debate, because it doesn't answer the question the other person is actually asking — which usually isn't "was this decided," it's "why was it decided this way, and does that reasoning still hold?" Without a real answer to that, "we already discussed this" just sounds like resistance to reconsidering something, which invites more debate, not less.

Three reasons the same decision keeps resurfacing

• Nobody who remembers the reasoning is in the room. Teams change. The people who made a call, and the context they had when they made it, aren't always the people re-encountering the question later.
• The decision was recorded, but the reasoning wasn't. "We use X for this" survives. "We evaluated X, Y, and Z, and picked X because of [constraint]" almost never does — which means anyone questioning the choice has no way to tell whether it was carefully considered or arbitrary.
• The original assumption quietly stopped being true. Sometimes re-litigating is actually correct — the constraint that justified a decision may no longer hold. Without a recorded reason, there's no way to tell "this needs revisiting" apart from "this was already settled and someone forgot."

What actually stops it

Not "document more" — document the right thing. A decision record that states the reason and the alternatives considered turns a re-argued debate into a five-minute read instead of a fresh discussion: either the original reasoning still holds (in which case pointing to it settles things quickly), or the situation has genuinely changed (in which case that's worth knowing explicitly, and the old decision should be marked reversed or superseded rather than just quietly ignored).

Make the reasoning easier to find than to re-derive

The practical failure mode isn't that the reasoning was never written down — plenty of teams have it somewhere, in an old doc or a long Slack thread. It's that finding it takes longer than just re-deciding from scratch, so people take the faster path. Whatever you use to capture decisions, the real test is whether "why did we decide X" is faster to look up than to re-argue. If it isn't, the record isn't doing its job, no matter how thorough it was when it was written.

Flag contradictions before they ship

The most expensive version of re-litigating isn't a repeated conversation — it's a decision that quietly contradicts an earlier one and ships anyway, because nobody connected the two. Catching that requires more than a searchable archive: it requires something that actively checks a new decision against recent history and flags a possible conflict at capture time, before it becomes two conflicting things both live in production or in the roadmap at once. That's the specific problem automatic decision links are built to catch.

The short version

Re-litigation isn't a discipline failure — it's what happens by default when reasoning isn't captured, or is captured somewhere slower to check than to just re-decide. Fix the capture (record the reason, not just the choice), fix the retrieval (make it faster to look up than to re-argue), and flag contradictions automatically instead of relying on someone remembering. Do those three things and most re-litigated decisions stop resurfacing on their own.