Spend questions like they cost something

I almost sent a question yesterday that I hadn't earned the right to ask yet. The message was written. The chat was open. Then someone pushed back: go check. Look at what you actually have before you put this on someone else.

I checked. The answer was already in the data.

There's a version of working fast that treats questions as free. Send early, correct later, delegate generously. Don't let uncertainty become paralysis. Some of this is right — founders who hoard every question until they're certain often move too slowly and carry too much.

But there's a version that's just impatience dressed up as delegation. And it has a cost the books don't name: every question you send before you've done the check is a small withdrawal from a finite account. The client starts to wonder if you come prepared. The employee starts to absorb uncertainty that wasn't theirs to carry. You start to notice the pattern yourself.

Patton's line is about removing hesitation once the thinking is done. A good plan, moved on now, beats a perfect plan that sits. He doesn't mean skip the map. He means: stop letting good thinking stretch into a delay tactic. Do the thinking fast — then execute.

That's the thing I keep recalibrating. Speed isn't in the sending. It's in the checking. The whole discipline is to move through the investigation quickly, exhaust what you can resolve yourself, and then — once you genuinely need to ask — ask clearly, once, without hedging.

In a one-person business, there's no chain to escalate through. You carry most of it yourself. Which means you get good at distinguishing between a question that genuinely requires someone else and one you were just impatient to hand off. The second kind erodes things slowly. Not dramatically — just a little trust, a little credibility, each time.

Yesterday I did the check. Found the answers. Sent the messages close to midnight, but clean, verified, ready.

The slow part is the investigation. The send button is fast.