You've been in this meeting. The team settled something three weeks ago. Everyone nodded. Someone sent a summary email. And now you're all back in a room, arguing about it again like the original conversation never happened.

This isn't a personality problem. It's a process problem. And the fix is more concrete than you'd expect.

The Real Reason Closed Decisions Keep Getting Reopened

Most teams have no shared definition of what "decided" actually means. Someone with authority spoke. The room went quiet (that word is banned, so let's say: the room stopped pushing back). Everyone assumed the matter was settled. But "assumed" is doing a lot of heavy lifting there.

According to Bain's RAPID framework, unclear decision accountability is the primary driver of organizational slowdown and repeated deliberation on matters that should already be closed. When nobody explicitly owns a decision, everyone feels entitled to reopen it. That's not stubbornness. That's a rational response to ambiguity.

Research summarized by Heath and Heath, covered at Farnam Street, adds a sharper edge to this: teams frequently revisit decisions not because new information emerged, but because the original process had no defined endpoint. Participants walked away genuinely uncertain whether the decision was final. So they kept the door cracked open, just in case.

That cracked door is your problem. Every meeting you spend relitigating a closed decision is a meeting you didn't spend building something.

What an Actually Closed Decision Looks Like

A closed decision has 3 visible properties. You can see who owns it, you know what would justify revisiting it, and you know when it's next up for review.

If any of those 3 things are missing, the decision isn't closed. It's just paused. And paused decisions have a way of becoming permanent agenda items.

Most organizations skip all 3. They record the outcome (sometimes), assign vague collective ownership ("the leadership team will..."), and leave the door permanently open to anyone with a strong enough opinion or a bad enough week. That's how you end up with a culture where decisions feel soft, where the loudest voice at the next meeting can unilaterally rewind the clock, and where your best people quietly stop trusting the process.

A decision without a named owner isn't a decision. It's a suggestion.

The structural absence of a closure mechanism is what keeps decisions alive long after they should be buried. CHROs and CPOs who want to fix this don't need another alignment workshop. They need to give their teams a repeatable protocol that makes closure explicit and visible.

The 3-Part Protocol That Stops the Loop

This protocol is designed to be bolted onto whatever decision-making process your organization already runs. You don't need to rebuild anything from scratch.

1. Name the Decision Owner Explicitly

One person. Not "the team." Not "leadership." One human being whose name appears next to the decision in writing.

This person doesn't have to be the most senior person in the room. They do have to be accountable for holding the decision and fielding any requests to reopen it. When someone comes back three weeks later wanting to relitigate, there's a named person who can say: "Here's what it would take to revisit this. Does your concern meet that bar?"

Without a named owner, that conversation never happens cleanly. Instead, it happens in side channels, in Slack, in the 5 minutes before the next meeting, and suddenly you're back at square one.

2. Record the Decision With a Reopen Threshold

This is the part most teams skip entirely, and it's probably the highest-leverage change you can make.

When you record a decision, you also record the conditions under which it can be revisited. What new information would justify reopening it? A competitor move? A regulatory change? A budget shift above a certain threshold? Get specific. Write it down.

The reopen threshold does 2 things at once. It protects the decision from being relitigated on a whim, and it signals to the team that the door isn't welded shut forever. It's just closed until something meaningful changes. That distinction matters enormously for buy-in. People accept closed decisions much more readily when they can see the path back to the table, even if they never end up taking it.

A good reopen threshold sounds like: "We'll revisit this if Q3 retention drops below 82%, or if the regulatory guidance changes before October." Concrete. Specific. Not "if we feel like it's not working."

3. Set a Review Date

Every closed decision gets a date on the calendar when it will be formally reviewed. Not relitigated. Reviewed.

The review date is the release valve. It tells the team: we're not ignoring your concerns, we're scheduling them. That framing strips back a huge amount of the anxiety that drives premature reopening. People push back on closed decisions partly because they're afraid the window will close forever. A review date removes that fear.

Six months is a reasonable default for most strategic decisions. Tactical decisions can be shorter. The point is that the date exists, it's visible, and everyone knows when the formal check-in happens.

How to Roll This Out Without Making It a Project

You don't need a new system. You need a new habit.

Start with your next significant decision. Before the meeting ends, answer 3 questions out loud: Who owns this? What would it take to reopen it? When do we formally review it? Write the answers somewhere the team can see them. That's it.

Do it 5 times and it becomes muscle memory. Do it consistently and you'll watch the relitigating slow down, not because people stopped caring, but because the ambiguity that fed it got sanded down to nothing.

Your team isn't difficult. Your closure process is incomplete. Fix the process, and the arguing largely fixes itself.