Deciding isn't the job. Assuring is.

There's a one-word distinction from Management Essentials at HBS that I've never been able to shake: the difference between assuming implementation and assuring it. Most managers assume. We make the call, communicate it and quietly believe that because the decision is made, the thing will now happen. It often doesn't. Plans don't execute themselves. The gap between a decision and a result is where most good intentions quietly die and the manager's real work lives in that gap, not in the moment of deciding.

I've written before about a payment system we rebuilt at Hubtel, how it got worse before it got better. Here I want to pull a different thread from it, because that rebuild is the clearest example I have of assuring rather than assuming.

We could have decided to rebuild and left it there. A direction announced, a new architecture chosen, everyone nodding in a meeting. That's the assuming version and it would have failed. What actually carried it was the assuring: a working demo put in front of the CEO before anyone committed, so the decision rested on something real and not a slide. Engineers brought in close enough to own the new design rather than have it handed to them. War rooms when things broke. The constant, unglamorous checking that what we'd decided was actually becoming true in the code. None of that is the decision. All of it is the assurance. And the assurance is what shipped.

The lesson stuck hard enough that I built it into how my teams run, in small, deliberate ways. We added a short learning prompt to our daily stand-up, a simple "what did we learn yesterday?", because it surfaces tiny course corrections before they grow into real problems. And every key objective has a named owner who files a brief risk-and-progress note each week. That one habit changed the temperature of the whole team. When a plan has a face attached to it and a standing moment where that person reports on reality, you stop assuming it'll execute itself. You've built assurance into the calendar.

Here's the uncomfortable part for those of us who like being decisive: deciding feels like leadership and assuring feels like admin. Making the call is the part with the adrenaline. Following through, checking, adjusting, owning the gap between intention and reality, that part is quieter and far less flattering. But it's the part that actually determines whether anything you decided ever happens. The decision is a hypothesis. The assurance is the experiment that tells you if it was true.

I still catch myself wanting to believe a decision is the finish line. It isn't. It's barely the starting gun.