Earlier this week I said that most blocked delivery isn’t caused by bad decisions, but by no decisions or late decisions.

That usually isn’t a capability problem. It’s a system problem.

In many teams, decisions slow down because they quietly drift away from the work. People escalate because they feel unsafe deciding. Leaders become bottlenecks without meaning to. Work sits blocked, even when everyone is well intentioned.

One practical rule I often introduce is this: no one is allowed to make a decision alone.

That doesn’t mean consensus, and it doesn’t mean endless discussion. It means decisions are talked through with at least one other person before moving on.

A big part of that conversation should be making assumptions explicit.

What are we assuming to be true? What needs to hold for this decision to make sense?

When assumptions are clear, decisions tend to be stronger. And if one of those assumptions later turns out to be wrong, you still understand why the decision was made at the time.

That’s also why decisions need to be visible.

Not in a separate decisions log that nobody ever looks at, but alongside the work itself. In a ticket. In a design note. In a code comment or commit.

What decision was made. What assumptions it was based on. What other options were considered, and why this path was chosen.

This is powerful later on. When someone asks “why did we do it this way?”, the thinking is already there. Fewer arguments. Less rework. Faster alignment.

This is also where “ask for forgiveness rather than permission” often gets misunderstood.

It’s not about bypassing leadership or being reckless. It’s about reducing friction so work can move forward.

When decisions are shared, visible, and grounded in clear assumptions, delivery becomes the feedback loop. You learn by moving, not by waiting.

This is often the shift teams need when work feels blocked but nobody can quite explain why.

If you want a simple way to sense check where decisions are slowing things down in your team, the Flow Check can help surface that: https://app.agilesecondopinion.com/flow-check

And if you want a second opinion on how to unblock decision making in your context, that’s exactly the space I work in: https://www.agilesecondopinion.com