why decisions don’t hold

i’ve watched decisions get made in a meeting and then quietly unmade in the weeks after — not through a formal reversal, just through accumulating exceptions, workarounds, and “we’ll figure that out later”s until the original decision is unrecognisable.

the people in the room would say they made a decision. technically they did. but it didn’t hold.

the most common reason, in my experience, is that the decision resolved the surface question without touching the underlying one.

the meeting is about which direction to take a product. the options are presented. people debate. an option is chosen. but the actual thing generating the disagreement — a difference in how two stakeholders understand what the product is for — never got named. it just got papered over by the specific decision.

so three weeks later, the disagreement surfaces again. different context, same shape. “i thought we decided this” on one side, “but in this case it’s different” on the other. and it is different, technically. but really it’s the same question being asked again because it was never actually answered.

the second reason is that the decision was made by the people in the room, not by the people who have to implement it.

i don’t mean this as a hierarchy thing. i mean it as a buy-in thing. you can get a decision past the stakeholders and still have the team that’s going to execute it operating on a different set of assumptions. they weren’t in the room. they got told the conclusion. and if the conclusion doesn’t match what they understand the problem to be, they’re going to keep solving for what they understand — which means the decision starts leaking the moment it hits the ground.

a decision that hasn’t been absorbed by the people doing the work isn’t really a decision. it’s a plan waiting to meet reality.

the third reason is time. decisions made under deadline pressure, or at the end of a long meeting when everyone’s tired, tend to be under-specified. the room agrees on the direction but not the edges. what does this mean for the adjacent case? what happens when the constraint changes? the ambiguous parts get deferred, and deferral is where decisions go to dissolve.

the fix isn’t a better meeting format, usually. it’s being honest about whether the decision actually resolved the question or just moved past it.

sometimes the question isn’t ready to be decided. the team doesn’t have the information, or the stakeholders haven’t worked through their real disagreement yet. the right move in that case is to say so — “we can make a decision here but i don’t think it’ll hold, here’s why” — rather than make a fragile one that looks solid until it isn’t.

that requires someone who’s tracking not just the surface of the conversation but what’s running underneath it. which is harder to do when you’re also the one presenting, or the one with stakes in the outcome.

if you’re sitting on a decision that keeps coming apart — where the room reached agreement but the execution isn’t following — i offer synthesis. i’ll work through what the decision is actually about and what it would take for it to hold. $300.