Slow to decide. Fast to move.

I've been thinking about where owners put their speed. I don't mean how fast they are. I mean where the speed goes.

First-time founders tend to put it in the wrong place. The decision gets made in one meeting. Then the doing drags for weeks. Everyone nods on Tuesday, and nothing has moved by the end of the month.

Owners who have built past ₹5 crore seem to run it the other way round. They're patient before the decision. Once it's made, the patience is gone.

That isn't a personality quirk. I think it's a skill, and you can learn it.

The decision is the expensive part

At a certain size, a wrong call stops being a small mistake. It turns into a payroll problem. A bad hire, a branch in the wrong city, a supplier contract you can't get out of. You don't fix these with an apology. You pay for them every month.

So the thinking has to happen up front. Before you commit, ask three plain questions:

1. Who does this affect?
2. What does it cost if I'm wrong?
3. Can I undo it?

The third question does most of the work. If you can reverse a decision, make it quickly. If you can't, sleep on it. Test it in small pieces first. Try the new supplier on one order before you hand them the whole year.

Not every decision deserves the same patience. That's the point.

Speed lives in the execution

Once the decision is made, things should move by Monday.

Here's how I'd explain it to an owner. By the time you decide, you've already paid for certainty. You spent the time, asked the questions and tested the idea. If you then execute slowly, you're paying interest on a debt that's already settled. Every slow week costs you money and gives you nothing back.

Think slowly before you commit. Move fast after. Never the other way round.

This is where teams get confused. Slow deciding looks like hesitation to them. Fast execution looks like pressure. They think they're working for two different bosses.

They aren't. Both habits come from one idea. Thinking is cheap before you commit and expensive after. Once you see it that way, the two speeds stop looking like a contradiction.

What it asks of the people around you

If you work this way, your team needs to know the rules. Otherwise it feels random to them.

Two things help.

• Bring doubts early. The cheapest time to raise a concern is before the decision. Once you're moving, a late doubt slows everyone down. Tell your team you want the hard questions in the room, not in the corridor afterwards.
• "Not yet" is not "no". When you hold back on a decision, say why. Say what you're waiting to learn. People can live with patience when they understand it. What they can't live with is silence.

It also asks something of you. When you've decided, say so clearly. Don't leave a decision half-made and let people guess. A clear "we're doing this, starting Monday" gives your team permission to go fast.

Try this

Before your next big call, look at it honestly and ask: which part am I rushing?

• If it's hard to undo and you're about to decide in one meeting, slow down. Write down who it affects, what it costs if you're wrong, and whether you can test it small first.
• If it's already decided and nothing has moved in two weeks, that's the part to rush. Name one action that happens by Monday, and who owns it.

Most owners don't lack speed. They just spend it in the wrong place.