
Some unknowns resolve with time. Others only resolve with action. Most leaders treat them the same, and pay for it either way.
In Your urgency isn't the problem's urgency, I argued that most rushed decisions are sedatives: a way to stop feeling uncomfortable.
Waiting can be a sedative too.
"Let's get more data." "Let's revisit next quarter." "Let's see how the market settles." It sounds prudent. Often, it's the same discomfort in better clothes.

Some unknowns resolve with time. The pipeline numbers land on Thursday. The board meets on the 12th. The regulation gets published. Waiting for these is smart, because time is doing the work.
Others don't. Will this new segment buy? Will the new pricing hold? Does the message land with CFOs, or only with marketers? You can wait a year and know nothing more than you do today. The market won't send you the answer.
Most leaders treat both kinds the same. That's the mistake.

If we do nothing for a month, what will we know that we don't know now?
If the answer is specific, wait, and put a date on it.
If the answer is "not much," waiting isn't caution. It's delay with a respectable name.

When time won't tell you, action will. The job is to make that action small enough to be cheap and sharp enough to be useful.
Not a new strategy. A test. Two weeks of ads aimed at the new segment. Ten sales calls with the new price. One landing page with two headlines. Something with a clear question, a small budget and a date when you'll read the result.
You're not committing. You're buying information.

Uncertainty spreads fastest when nobody names it. So name it:
"Here's what we know. Here's what we don't. Here's what we're testing next."
It tells your team you're not frozen, and you're not guessing. You have a plan for the unknown, not just the known.

I once watched a SaaS company spend two months debating whether to enter a new market. The question sounded strategic: was the market big enough, and would their product resonate with the people they wanted to sell to?
There were spreadsheets, competitor research, pricing discussions and more than one leadership meeting where someone said, "I think we just need a bit more data."
Two months passed.
Eventually, the team stopped trying to answer the question from inside the business and designed a test instead. A simple landing page, messaging adapted for the new audience, and a small paid budget behind it for two weeks. The goal wasn't a pile of leads. It was to find out whether the audience would respond at all.
They did, but not quite the way anyone expected.
The strongest response came from a narrower segment than the one they'd planned to target. That changed the proposition, the audience and the size of the opportunity they were modelling.
They'd spent two months trying to decide whether the market was worth entering. In two weeks, the test gave them a better question: which part of it actually wanted what they were selling?
The lesson wasn't "move faster." It was knowing when more thinking had stopped producing more information.

Wait when time is working for you.
Test when it isn't.
No noise. Only honest strategy, occasional reflection, and the kind of insights you actually want in your inbox.