It’s 3:47 PM on a Thursday. A product recall decision has to reach legal in thirteen minutes or the regulatory window closes for another quarter. Four people are around the table. Two are arguing about root cause. One is on Slack pulling logs. The fourth keeps looking at the VP, waiting.
The VP has two choices. She can run the collaborative decision framework she’s trained the team on, the one with the input-gathering round and the dissent check. Or she can say, in five words, what the call is. She picks the framework. At 4:02, the window closes. The recall gets pushed to next quarter. Three customers get hurt in the interim.
That’s the scenario where the commanding leadership style earns its place. And it’s the scenario most managers misread in both directions: the cautious ones hesitate when they shouldn’t, and the anxious ones command when they don’t need to. Commanding leadership isn’t a personality flaw to apologize for. It’s a precision tool that a lot of leaders either fear or badly overuse. I’ve done both. Earlier in my career, running corporate strategy inside a large multinational, I overcommanded because I didn’t yet trust my own judgment and speed felt like confidence. Running Risely now, I’ve watched myself reach for command when the honest answer was that I didn’t want to sit in a hard conversation.
This piece is the second in a six-part series on the Goleman leadership styles. If you haven’t read the first on visionary leadership, start there, because commanding only makes sense as one mode inside a larger repertoire.
What Commanding Leadership Actually Is
Daniel Goleman introduced six leadership styles in his 2000 HBR essay “Leadership That Gets Results.” The style we’re discussing today was the first one on his list, and it’s the one he had the hardest time naming. In the original article he called it “coercive.” That word did real damage. Readers heard “coercive” and pictured a shouting boss bullying people into compliance, so they filed the whole style under “leadership mistakes” and moved on. Goleman later started using “commanding” to describe the same pattern, which is a cleaner word for what’s actually happening.
The coercive leadership style and the commanding leadership style are the same thing. Same behaviors, same use cases, different label. The behaviors are specific and observable. A commanding leader expects immediate compliance. Feedback loops are short, sometimes a single sentence: “Do this now, report back in an hour.” Directional control is tight. The leader decides, the team executes, and the deliberation that normally happens before a decision happens inside the leader’s head in compressed time.
Goleman was clear-eyed about the cost. In his research, commanding was the style with the most negative impact on team climate across almost every metric: flexibility, responsibility, standards, rewards, clarity, commitment. Used as a default, it poisons the room. He wasn’t recommending it as a primary style. He was saying that skilled leaders keep it in their kit and pull it out for specific situations where nothing else works. Think scalpel, not sledgehammer. The question isn’t whether commanding leadership is good or bad. The question is whether the situation in front of you is the one it was designed for.
When Commanding Leadership Is the Right Call
There are four situations where the commanding leadership style is genuinely the right tool, and it’s worth being narrow about them because the list gets stretched by people looking for permission.
The first is a safety or legal crisis with a narrow time window. A contamination report that has to reach the regulator by end of day. A safety issue on a factory floor where the next shift starts in ninety minutes. A legal deadline measured in hours. In these moments the cost of a wrong decision is real, but the cost of no decision is larger, and the clock is doing the deliberating for you.
The second is a team that’s frozen or in open conflict, where a decision is needed right now. You’ve seen this room. Two senior people are locked in a circular argument. Three others have stopped contributing and are waiting for the argument to resolve itself. The meeting is fifteen minutes from its hard stop. Collaboration has broken down, and the reason isn’t unwillingness from the people in the room. The situation has simply exceeded what the group can process in the time available. Someone needs to call it.
The third is when an external stakeholder requires a single authoritative voice. A regulator on the phone. A major customer escalating to the CEO. A press inquiry with a one-hour response window. These moments need one person to speak with clarity on behalf of the organization, and the internal debate about what to say has to happen privately and fast.
The fourth is a brand-new team with no shared context yet. If you’ve just inherited a team in the middle of an in-flight project, you don’t yet have the relational capital or shared language to run a consensus process. For the first week or two, clear directional calls are what the team needs. They’re trying to figure out how you think. Ambiguity from you reads as absence.
I’ll tell you the signal I use, because it’s the one I wish someone had given me earlier in my career. I ask myself: is the constraint in this room information, time, or trust? If the constraint is information, I should be asking questions. If it’s trust, I should be listening. Only when the constraint is time, genuinely time, should I be issuing directives. That single filter has saved me from most of my worst command moments, and the times I’ve ignored it are the times I regret.
Knowing which mode to pick under pressure is a decision-making skill and an adaptability skill braided together. Neither one on its own is enough.
The Self-Awareness Blind Spot
This is the part of the commanding leadership conversation almost nobody covers, and it’s the part that matters most.
Two managers, both convinced they’re being decisive, can behave almost identically in a meeting and produce completely different outcomes over six months. I’ll call them the anxious defaulter and the legitimate crisis responder, because those are the two profiles I see in our coaching data over and over again.
The anxious defaulter reaches for command because the alternative is uncomfortable. Collaboration feels slow. Sitting with disagreement feels like losing control. When a discussion gets messy, the defaulter’s nervous system reads the mess as danger, and a directive feels like relief. They’ll tell you, with full sincerity, that the team needed direction. And sometimes they’re right. But if you track their behavior across a quarter, you’ll notice the same pattern in low-stakes situations that had plenty of time for discussion. The commanding move is a stress response dressed up as a leadership philosophy.
The legitimate crisis responder looks similar in the moment, but the underlying read is different. They default to questions and collaboration in normal operating conditions. They’ve built enough psychological safety in the room that people challenge them. When they do switch into command mode, it’s because they’ve actually assessed the constraint, seen that time is short and the cost of waiting is concrete, and decided on purpose. The switch is visible to the team. People can feel the gear change.
The behavioral tells that separate the two profiles are subtle but reliable. The anxious defaulter commands in small meetings with no stakes, commands in emails that didn’t need to be commands, and gets visibly irritated when someone asks a clarifying question. The legitimate responder lets the team argue in meetings that can afford it, takes clarifying questions without defensiveness, and uses command voice sparingly enough that it still lands when it shows up.
I’m being honest when I say I’ve been both, at different points in my career. The earlier version of me, running corporate strategy inside a large company, commanded too much because my competence was real but my confidence was performed, and directives felt like the fastest way to close the gap. The version of me running Risely commands rarely, and when I do, it’s because I’ve been paying attention to the meeting for long enough to know the room can’t get there on its own. I still get it wrong sometimes. The difference is I notice faster now.
The self-awareness here is a function of emotional intelligence. You can’t tell the difference between a crisis response and a stress response without being able to watch your own internal state in real time.
When to Stop Commanding: The Exit Criteria
The hardest part of using commanding leadership well isn’t entering the mode. The hard part is leaving it.
Most managers who get commanding right in the moment still fail at the exit. They stay in command mode for a day or a week longer than the situation needed, and by the time they notice, the team has either gone quiet or started routing around them. The cost of overstaying is worse than the cost of never commanding at all, because it trains people to stop bringing you their thinking.
The exit criteria are behavioral, and you can spot them if you’re watching for them. The first signal is questions. When a team is in crisis execution mode, they don’t ask questions. They take the instruction and move. The moment you notice people starting to ask clarifying questions again, questions that sound like thinking rather than confusion, the crisis window has closed. The second signal is lateral information flow. If you’re the center of the wheel, everyone is reporting to you because speed requires it. When information starts moving between team members without you as the hub, they’ve regained enough context to coordinate without your direction. The third signal is the decision set narrowing. In the early crisis hours, there are too many options and not enough time to evaluate them. Once the options have been pressure-tested and you’re down to two or three viable paths, the team can evaluate them collaboratively, and they should.
The mental test I use is a single question: is my team still frozen, or am I frozen by habit? If the answer is the team, keep commanding. If the answer is me, stop. That single question, asked honestly every morning during an extended crisis, is what separates leaders who use commanding as a tool from leaders who let the tool become their identity.
The Trust Repair Move
Almost nobody does this next part, and it’s the move that decides whether your team follows you into the next crisis or just tolerates you in this one.
In the forty-eight hours after you exit command mode, you need to name what just happened out loud. Not in a theatrical way. Just acknowledge it. Something like: “I want to flag that I ran the last three days pretty tight. I made calls without running them past you because the clock was short. I want to open that up now and hear what you’d have pushed back on.” Then you sit and listen. You don’t defend the calls. You don’t explain why the situation justified the commands. You let people tell you what it felt like on their side of the table.
Here’s a dialogue fragment from a real conversation I had with a team lead named James after a weekend outage at Risely, anonymized:
Me: “I want to go back to Friday night. I called the rollback decision at 11 without asking you. What would you have said if I had?”
James: “Honestly? I’d have said the same thing. But I would’ve wanted thirty seconds to flag the customer comms piece first, because I knew something you didn’t.”
Me: “Tell me what I missed.”
That’s the move. You restore voice before you restore process. You don’t rush back to your normal collaborative cadence and pretend the command episode didn’t happen, because the team already knows it happened, and pretending just adds distance. You name it, you invite the retrospective, and you receive whatever comes back without flinching.
The skill underneath this is active listening, and specifically the version where you listen to something uncomfortable about your own behavior and don’t reach for an explanation. If you can do that once a quarter, your team will follow you through command episodes without losing trust in you. If you can’t, every command episode costs you capital you won’t get back.
When Commanding Backfires
Commanding leadership fails predictably when it gets applied to the wrong situations, and there are three overuse patterns worth naming.
The first is command applied to routine decisions. If you’re issuing directives about meeting agendas, file naming conventions, or which vendor to use for a non-critical service, you’re not being decisive. You’re just not trusting your team to think. Routine decisions are where people build judgment, and when you take them, you starve the team of the practice they need.
The second is command applied to a high-autonomy team that’s already solved the problem. This one’s embarrassing to write because I’ve done it. You walk into a meeting with a plan, the team has independently reached a better plan while you were in another meeting, and instead of asking what they’ve been working on, you issue your original plan as a directive. Now you’re asking a team that just did good work to unwind it and do your work instead. They’ll comply once. After that, they’ll stop doing good work when you’re not in the room.
The third is command used as a substitute for a hard conversation. This is the most damaging pattern and the one I see most often in coaching conversations at Risely. A manager has a performance concern with someone on the team, doesn’t want to sit in the discomfort of raising it directly, and instead starts issuing tight directives to that person as a way of managing around the conversation. The person being managed can feel exactly what’s happening. They don’t get feedback, they get controlled. The commanding leadership examples that end up in HR aren’t usually about crisis moments gone wrong. They’re about this: a manager who couldn’t have a direct conversation and used command voice as a substitute.
If you’re reading any of those three patterns and feeling called out, that’s useful information. It doesn’t mean you’re a bad manager. It means you’ve been reaching for the wrong tool in a situation where a different one would serve you better.
Developing Style-Switching as a Skill
Everything we’ve discussed so far points to the same meta-skill: the ability to switch leadership styles based on what the situation actually needs. Goleman’s six-style model includes the visionary style we covered in part one, plus affiliative, democratic, pacesetting, and coaching. The best leaders in his research used four or more of these styles fluidly, picking the right one for the moment without thinking about it consciously. This includes knowing when quiet leadership outperforms commanding — a distinction the best style-switchers make instinctively.
Style-switching is learnable, though reading about the styles won’t get you there. The actual growth comes from building enough self-awareness to notice which mode you’re defaulting to, and enough range to pick a different one when the default isn’t serving the room. That’s coaching work. It’s the kind of pattern that’s hard to see in yourself because the default feels like “just how I lead” until someone helps you see it as a choice.
If you’re running a team and you want to build this range in your managers, our leadership development solutions are built around exactly this problem. And if you want to see how a coaching conversation about your own default style actually sounds, you can talk to Merlin for free. Merlin will walk you through a short self-assessment on which Goleman style you reach for under pressure and where your next growth edge probably sits. The coaching skill assessment and the broader leadership skill assessment will give you a structured starting point for the work.
Pick One Thing
Before you close this tab, do one small thing. Think about the last time you reached for command voice at work. Maybe it was an email that started with “We need to” and ended with “by Friday.” Maybe it was a meeting where you cut off a discussion because the ambiguity was getting to you. Maybe it was a genuine crisis and you handled it well.
Now ask yourself the question from earlier. Was the constraint in that moment information, time, or trust? If it was time, you probably used the right tool. If it was either of the other two, you reached for commanding because the correct tool felt harder.
That single honest answer is the starting point for every leader who’s ever wanted to build real style range. If you want help working through it, open a conversation with Merlin and walk through a recent moment. It takes about ten minutes, costs nothing, and it’s the kind of reflection that sticks because it’s about your actual behavior, not a framework in the abstract.
Part three of this series covers affiliative leadership and why the “people first” style is both underrated and easy to get wrong. It’ll land next week.
Frequently Asked Questions
Is commanding leadership the same as autocratic leadership?
They overlap but they aren’t identical. Autocratic leadership describes a default operating mode where one person makes most decisions across most situations. Commanding leadership, in Goleman’s framing, is a situational tool you reach for when speed and clarity matter more than consensus. The autocratic leader commands all the time. The commanding leader commands on purpose, for a defined window, then steps back.
Can commanding leadership work with experienced teams?
Yes, but the window is shorter and the exit has to be cleaner. Experienced teams tolerate direct orders during a genuine crisis because they can read the situation themselves. What they won’t tolerate is staying in command mode after the crisis ends. If you keep issuing directives once the room has stabilized, you’ll lose the people you most need to keep.
How do I know if I’m commanding out of habit?
Run a simple check. Look at your last five directive moments and ask whether the situation actually required speed, or whether you just found collaboration uncomfortable. If four of the five could’ve been handled with a question instead of an instruction, you’re defaulting to command because it feels safer, not because it’s working.
What’s the difference between commanding and coercive leadership?
They’re the same style under two different labels. Goleman originally called it “coercive” in his 2000 HBR piece, which caused people to misread it as abusive. He later used “commanding” to describe the same pattern: immediate compliance, tight directional control, short feedback loops. The behavior is identical. Only the name softened.