Decisions not made don't disappear. They turn into double work.

There’s a phrase that keeps coming back in meetings, especially the uncomfortable ones. Let’s decide later. Let’s stop here for today, we’ll pick this up next week with more data. Let’s keep the option open and see how it evolves. It sounds reasonable, even prudent. In reality, in many cases, that phrase doesn’t postpone a decision. It transfers it.

Transfers it forward in time. Transfers it onto whoever is working downstream. Transfers it onto whoever will have to put the pieces back together when the problem resurfaces in another shape.

A decision left unmade, inside an organisation, doesn’t behave like a file left open on a desktop. It doesn’t sit there waiting to be picked up at the right moment. It seeps into processes and bends how they work.

The dynamic shows up clearly in a concrete example. A mid-sized company decides, in spring, that it’s time to revisit the product portfolio. Three meetings happen. Data gets collected. Discussion happens. The conversation closes with a “let’s gather a bit more, we’ll come back to this in a month”. Meanwhile, the sales team keeps selling what was on the menu before. The marketing team keeps communicating the same lines. The product team keeps developing the evolutions already in motion. Everything keeps going.

In June the decision comes back to the table. But now it’s not a fresh decision anymore. It’s a decision carrying three months of work done under the old assumption. Changing direction now costs more. Pushing back on what’s already been started takes more energy. The conversation, paradoxically, becomes harder than it was in March.

This is the point. The postponed decision isn’t free. It carries a growing cost, paid in work done in vain, in work redone, in cyclical discussions that come back to the same questions without ever closing them.

Double work means exactly this. Work done once because someone has to do it despite the missing frame. And work done again, after, to fix what was built on the wrong frame. You always pay twice. The first time in time. The second time in the friction and frustration of having to undo to redo.

There’s a second layer of cost, less visible but more corrosive. Decisions left unmade erode trust. When people understand that certain calls never really get closed, they stop bringing the prickly topics to the table. They get used to working inside their own perimeters, avoiding the zones where the decision-vacuum makes itself felt. Meetings empty out of real content. People talk about other things. The productive conversation moves to corridors, where at least someone can say what they think without watching their opinion sit in suspension for weeks.

When this dynamic stabilises, the organisation stops growing as a decision-making system. It keeps producing, sure. But the important calls freeze. Postponing becomes normal. Working as if a decision had been taken, knowing it hadn’t, becomes normal. Reopening the same questions every three months without resolving them becomes normal.

Once you recognise this pattern, one thing becomes obvious. Not all decisions need to be perfect. Many just need to be made. Even a decision made with 70% of the information is almost always better than one suspended with 90%, because it frees the system from a distortion.

I tell this often to clients who complain about “teams that don’t execute well”. Almost never is the problem execution. Almost always the team is executing, with difficulty, on decisions that were never made all the way through. They’re carrying alone the weight of choices that should have been made above them.

The cure isn’t more execution discipline. It’s more decision discipline. Deciding earlier. Deciding clearer. Deciding even when some information is missing, knowing you can adjust later. Revising a decision that’s been made is a contained, manageable piece of work. Revising a postponed decision drags along all the work that was done in the meantime, and that work is never manageable.

When you notice that certain topics keep coming back in your team, never closing, it’s not a process problem. It’s a signal. Somewhere, weeks or months earlier, a decision wasn’t made. And it keeps charging interest every time it resurfaces.

Decisions not made don’t disappear. They get paid, slowly, in double work.