Opinions expressed by Entrepreneur contributors are their own.
Key Takeaways
- Your team doesn’t need perfect certainty; they need consistent direction they can confidently act on.
- Silence creates uncertainty, but clear priorities give people confidence to keep moving forward.
I wrote recently about the decisions that define you, the ones you make blind, with partial information and real stakes. That piece was about what happens inside the leader. This one is about what happens around the leader, because while you are wrestling with an uncertain call, your team is watching, waiting and drawing conclusions.
Here is what three decades in wealth management have taught me about those conclusions: your team does not need you to be certain. It needs you to be clear.
Silence is always interpreted as risk
When conditions get murky, the responsible instinct is to slow down. Hit the brakes and be more catious. Commission another analysis. Schedule another round of reviews. Wait for the fog to lift. The intention is diligence. The effect is corrosive, because while leadership waits, teams are left to interpret silence and silence is always interpreted as risk.
People tolerate ambiguity about outcomes far better than they tolerate ambiguity about priorities. A team can accept that the destination might shift. What it cannot accept is not knowing what matters most right now. Every day you spend privately deliberating, your best people are publicly guessing, and guessing is expensive. Work gets duplicated. Initiatives stall halfway. The most anxious voice in the room starts setting the agenda.
Direction is a decision, not a prediction
Leaders often confuse these two things. A prediction says this is what will happen. A direction says this is what we will do, and here is what would make us change course. Predictions invite debate about the future, which nobody in the room controls. Directions invite commitment to the present, which everybody in the room controls.
I hold direction to three tests before I communicate it. Is the logic sound? Is the downside survivable? Does the team know exactly what signal would trigger a change of course? When those three answers are yes, waiting longer adds cost without adding insight. When one of them is no, that is the work, not another week of deliberation.
Give the checkpoint, not the destination
The most practical shift I have made as a leader is defining the next checkpoint rather than the final destination. A ninety-day horizon with explicit review criteria gives people something concrete to execute against. It also gives leadership a dignified mechanism for changing its mind, which is the real prerequisite for decisiveness. People commit faster when they know the plan includes a way to correct it.
This is also where transparency earns its keep. Tell the team what you know, what you are assuming and what you will be watching between now and the checkpoint. Teams do not lose trust when leaders admit uncertainty. They lose trust when leaders pretend it does not exist and are later proven wrong.
One habit makes this durable: restate the priority out loud, every week, in the same words. It will feel repetitive to you long before it feels repetitive to the team. Leaders live inside their own reasoning all day, while the people executing hear only a fraction of it, so what feels like over-communication from your chair usually lands as the first clear signal from theirs. Repetition is not a failure of imagination. It is the delivery mechanism for direction.
Push the decisions down
Here is the test of whether your direction is actually clear: can your frontline people resolve most questions without you? When direction is specific, they can, because they can weigh any choice against the stated priority. When direction is vague, every question travels upward, and the organization becomes a bottleneck shaped exactly like its own leadership.
I have found that pushing decision rights down does more for speed than any process improvement, and it does something better than speed. It teaches people how to think about tradeoffs instead of waiting to be told, which is the difference between a team that executes and a team that merely complies.
Clarity compounds
There is a compounding effect here that never shows up in a spreadsheet. A team that receives clear direction this quarter moves faster next quarter, because it has learned that leadership will decide, communicate and adjust in the open. Hesitation compounds the same way in reverse. Every stalled decision teaches the organization to wait, and waiting quietly becomes the culture.
None of this is an argument for recklessness. Direction without judgment is just noise with confidence behind it. The point is narrower: stop treating certainty as the precondition for movement. The preconditions are a clearly stated priority, a survivable downside and a visible plan for revision.
Markets will keep withholding certainty. That is not a flaw in the environment. It is the environment. Your job is not to predict the fog away. It is to hand your team a compass, name the first landmark and start walking.
Key Takeaways
- Your team doesn’t need perfect certainty; they need consistent direction they can confidently act on.
- Silence creates uncertainty, but clear priorities give people confidence to keep moving forward.
I wrote recently about the decisions that define you, the ones you make blind, with partial information and real stakes. That piece was about what happens inside the leader. This one is about what happens around the leader, because while you are wrestling with an uncertain call, your team is watching, waiting and drawing conclusions.
Here is what three decades in wealth management have taught me about those conclusions: your team does not need you to be certain. It needs you to be clear.
Silence is always interpreted as risk
When conditions get murky, the responsible instinct is to slow down. Hit the brakes and be more catious. Commission another analysis. Schedule another round of reviews. Wait for the fog to lift. The intention is diligence. The effect is corrosive, because while leadership waits, teams are left to interpret silence and silence is always interpreted as risk.

