Move Before You’re Ready: The Discipline of Deciding Before Certainty Arrives

It is 11:42 on a Thursday, and the agenda has the word “decide” on it. The decision was supposed to land last quarter. It did not. Three competent leaders are in the room, each holding more information than they had the last time, and the meeting ends the way the last one ended — with a request for a little more analysis and a date to reconvene. Nobody in that room believes they just made a decision. They did. They decided to wait, and the waiting will cost more than most of them realize.

Certainty rarely shows up before a decision is due. That is not a flaw in your process; it is the nature of real decisions. The important ones arrive with missing information by definition, because if the answer were obvious the decision would already have been made further down the organization. Leadership is what happens at the point where the data runs out and a call is still required. And the leaders who wait for the last thirty percent are not being careful — they are deciding too, just letting the delay make the call, and doing it without owning the outcome.

The discipline that fixes this is not courage, exactly, and it is not instinct. It is a set of habits, and the first is triage. Not every decision deserves the same speed. Some are one-way doors: irreversible, expensive to undo, worth slowing down for. Most are two-way doors: reversible, cheap to undo, and quietly strangled when you treat them with one-way-door caution. The most common decision error in organizations is applying irreversible-decision rigor to reversible decisions — gathering, socializing, and deliberating a call you could have made, tested, and corrected in the time you spent getting comfortable.

Once you know which kind of decision you are holding, the question is whether you have enough to move. Enough is not certainty; it is sufficiency. Four questions get you there: do I understand the problem, do I understand the real options, do I understand the genuine risk, and can I move and still recover if I am wrong? If the answers are yes, you are at a seventy-percent solution — and a seventy-percent solution acted on today usually beats a hundred-percent solution that arrives next month, because by next month the problem has changed and the window has moved.

The reason waiting feels so safe is that its cost is invisible. The risk of moving is easy to picture: the thing that could go wrong is vivid and nameable. The cost of not moving is diffuse — the momentum that bleeds away, the window that narrows, the team that stalls behind an open question, the competitor who ships while you deliberate. Make that cost visible. Put it on paper next to the risk of acting, and the two finally compete on even terms. Most chronic indecision is simply a scoreboard that only shows one side.

Then give the decision a moment to actually happen. An open decision drifts until circumstances close it, so name a commit trigger when you frame the choice: a date and a sufficiency threshold, stated out loud. “By Friday, if we know these three things, we decide.” A trigger turns a decision from a standing worry into a scheduled event, and keeps the call in your hands instead of surrendering it to the calendar. Run a quick pre-mortem before you commit — imagine the decision has failed and ask why — and you will often improve the plan before it ever leaves the ground.

And because you will sometimes be wrong, build in the reverse. On a two-way door, the discipline is not never making a mistake; it is catching it early and turning around fast. A reversible call going sideways is cheap to undo in week one and expensive to undo in month six. The leaders who move fast and reverse faster outrun the ones who tried to be right the first time.

I learned all of this somewhere the stakes were not abstract. A fuel caution lit up in my cockpit in the middle of a live engagement, a ground force depending on us overhead. The total fuel was fine; it was pooling in the wrong cells, a balance problem building quietly under a mission everyone wanted to continue. As the air mission commander, I did not have time to gather my way to certainty, so I didn’t. I decided what mattered most, built a contingency around variables that had not existed ninety seconds earlier, and flew a seventy-percent plan that kept the crews safe and the mission alive. It was not perfect. It was in time, and it was owned.

Disciplined action on incomplete information is not recklessness. It is the definition of command. This is N-3 in the AZMTH Navigate series; the method is unpacked each week on the AZMTH and Colligent Leader Substacks, and the theory behind it lives at azmth.co/the-theory.