A lot of modern leadership advice leans hard toward collaboration, input-gathering, and consensus - for good reason, most of the time it produces better decisions and more durable buy-in. That guidance quietly implies something else, though: that unilateral, decisive action is always a fallback for leaders who haven't learned better. That's wrong, and treating it as true costs real time and safety in exactly the moments that can least afford it.
When directness is actually the right call
A few conditions, any one of which is usually enough on its own:
Delay creates material risk. Safety, legal, financial, or operational risk that grows the longer a decision waits. If waiting for full consensus costs something that can't be recovered once lost, that's a directive-leadership situation.
Authority genuinely needs to be unambiguous. Some moments require everyone to know, immediately, who is deciding and that the decision is final - a crisis response, a safety stop, an urgent client commitment. Distributed, consultative decision-making has a real time cost that not every moment can absorb.
The team lacks the information or capability to decide well right now. Input is only as good as what the people offering it can actually see. If the relevant facts, expertise, or context sit specifically with the leader in this instance, gathering broad input mostly just delays a decision that isn't going to improve much from the delay.
What directive leadership still requires
Being directive changes who decides, not how the person deciding behaves. A leader making a unilateral, time-critical call can still:
- Explain the basis for the decision, even briefly, rather than issuing it with no reasoning attached.
- Communicate honestly about uncertainty, rather than projecting more confidence in the decision than actually exists.
- Protect the dignity of people affected by it, even when they didn't get a vote.
- Stay genuinely open to new evidence and revisit the decision once time allows, rather than treating "I decided" as the end of the conversation permanently.
That combination - unilateral now, accountable and revisable soon after - is what separates directive leadership from leaders who use "someone had to decide" as a permanent excuse to skip input they simply didn't want to deal with.
The honest check
Before defaulting to a directive call, it's worth asking directly: would I be comfortable explaining, afterward, exactly why this moment specifically called for acting without broader input? "There genuinely wasn't time" and "the risk of waiting was too high" are real, defensible answers. "I didn't want the disagreement that asking would have surfaced" is not - and if that's the honest answer, the situation probably called for the harder, more collaborative conversation after all.
The reverse check matters just as much: a leader who is directive by default, in situations that didn't actually require it, pays for it later. Teams whose input is rarely genuinely sought learn to stop offering it - which means it won't be there the next time a decision genuinely does benefit from it.