A decision that hasn't been communicated clearly isn't really a decision yet. It's a private conclusion that hasn't become action in the world. The language of decision-making — how choices are announced, contested, finalised, and acted on — is one of the most consequential areas of leadership communication.
For non-native English speakers in leadership roles, this is often underdeveloped. The ability to make good decisions is present. The language that communicates those decisions with the right clarity and authority may be less practised. The result is decisions that don't land as decisions — that get relitigated, ignored, or misunderstood — not because the thinking was wrong but because the communication didn't match it.
How Decisions Sound in English Leadership Contexts
There is a specific register in English that signals a decision has been made. It is direct, first-person, and present-tense. It does not hedge.
Decision register:
- "We're moving forward with [X]."
- "I've decided to [X]. Here's the rationale."
- "The direction is [X]. This is where we're going."
Not decision register:
- "I've been thinking that maybe we should consider [X]..."
- "It seems like it might make sense to move toward [X]."
- "The thinking is moving toward [X]."
- "I wonder if [X] might be the right approach?"
The second set of phrases signals that a decision is forming, not that it has been made. If you have made the decision but communicate it in the second register, the room will treat it as a discussion still open for contribution. You will re-have the conversation you thought you'd concluded.
This is one of the most common leadership communication failures in English-language organisations: leaders who have decided but speak as if they haven't, then are frustrated that the team isn't moving.
The Distinction Between Consulting and Deciding
Not every decision warrants the same approach. The critical skill is being clear — to yourself first, then to your audience — about which mode you're in.
| Situation | Appropriate language | Effect |
|---|---|---|
| Decision made, alignment needed | "We're doing [X]. Here's why. I want to make sure everyone understands the reasoning." | Creates alignment without reopening the decision |
| Decision pending genuine input | "I haven't decided yet. I want to hear your views on [X] before I do." | Makes clear the decision is yours; input is genuinely wanted |
| Decision by consensus | "I'd like us to decide this together. Here's the question: [X]." | Appropriate for decisions with shared ownership |
| Decision made, but open to new information | "The direction is [X], unless someone has something material I haven't considered." | Signals openness without abandoning authority |
The confusion between consulting and deciding — communicating consultation when you've decided, or communicating a decision when you're still consulting — is the source of much leadership friction. Teams either stop contributing useful input (if they think you've decided when you haven't) or they relitigate settled questions (if they think you're consulting when you've decided).
Getting Commitment After a Decision
Making a decision and communicating it are not the same as getting commitment to execute it. This is a distinct step, and it requires its own language.
After announcing a direction, create space for final objections: "I want to make sure we're all clear and we're all behind this. Are there concerns I should hear before we move?"
This is not reopening the decision. It's an invitation for any final objections that need to be addressed before execution begins. Unaddressed objections don't disappear — they surface later, in execution, at higher cost.
When commitment is reluctant: "I hear that you don't agree with this direction. I'm not asking you to agree — I'm asking you to commit to making it work. Can you do that?"
The distinction between agreement and commitment is important. Demanding agreement is coercive and produces compliance at best. Asking for commitment — while explicitly acknowledging disagreement — is legitimate and often sufficient.
When someone is non-committal: "I need to know whether you're in or not. What's your position?"
Ambiguity about commitment is more costly than a clear no. A clear no can be managed. Passive, ambiguous commitment produces unreliable execution.
Reversing a Decision
Reversing course — changing a position you've committed to — is one of the more demanding communication moments in leadership. Done badly, it erodes authority. Done well, it builds trust.
The language that maintains authority while reversing:
"I've thought about this more and I've changed my view. What I said last week was [X]. I'm now going in a different direction — [Y]. Here's what changed my thinking."
Explicitly naming what changed, and why, is more credible than letting the reversal speak for itself. It shows the original decision was reasoned, not arbitrary, and that the new decision is also reasoned. Arbitrary decision-makers are more worrying than ones who change course with good reason.
What doesn't work: pretending the reversal isn't a reversal. "We're updating our approach to reflect new information..." — the team knows what happened. Naming it directly is stronger, not weaker.
The addendum that's often worth including: "The original direction made sense with what we knew at the time. What's changed is [X]." This isn't a justification — it's the context that shows your decision-making is consistent even when your conclusions change.
Communicating Uncertainty Decisively
Some decisions are genuinely uncertain at the time they need to be made. The language that handles this well is direct about the uncertainty rather than hedging the decision itself.
"I'm making this call with incomplete information. Here's what I know, here's what I don't know, and here's why I'm going in this direction anyway."
"We're deciding now because waiting for certainty would cost us [X]. Here's the decision and here's what we're watching."
"This is my best call given what we have. I want us to monitor [specific indicators] closely so we can adjust quickly if needed."
Each of these is a decision — clearly made and clearly owned. The uncertainty is acknowledged, but it's not located in the decision itself. The leader is uncertain about the outcome; they are not uncertain about the direction.
The Language of Escalation and Sign-Off
In organisations with multiple levels of authority, decisions often need sign-off or escalation. The English conventions for this:
Seeking sign-off: "I've decided to [X]. I'm bringing it to you before we move because [reason — outside my authority / significant resource commitment / potential risk to the relationship]. I'd like your sign-off to proceed."
This is different from asking for a decision: you've already formed your view. You're not asking them to decide; you're asking them to approve your decision.
Escalating a decision that's above your authority: "This decision is above what I can sign off on. Here's my recommendation: [X]. Here's the reasoning. What I need from you is [a decision / approval to proceed]."
The person escalating should always have a recommendation, not just a question. "What should we do?" is the wrong escalation frame. "Here's what I think we should do — I need your approval" is the right one.
Frequently Asked Questions
How do I make a decision sound final without seeming autocratic?
Share the reasoning. "We're doing [X], and here's why" is final but not autocratic — it respects the team's intelligence while making the direction clear. Autocracy is decision without explanation; authority is decision with explanation.
What if a decision I've made turns out to be wrong?
Name it directly: "I made the wrong call. Here's what I missed and here's the new direction." Leaders who can say "I was wrong" are trusted more than those who can't. The willingness to reverse course with honesty is a mark of confidence, not weakness.
How do I handle it when someone keeps relitigating a settled decision?
"We've covered this ground and made the decision. If you have something material and new to add, I want to hear it. Otherwise, I need us to move forward." Clear, respectful, final. After this, continuing to relitigate is a different problem — about follow-through or alignment — not a decision-making question.
Is it appropriate to involve the team in a decision you've already made?
If you've genuinely decided, don't simulate consultation. It wastes everyone's time and, when the team realises the decision was already made, damages trust. Be honest: "I've made this decision, but I want to walk you through my reasoning and hear if I've missed something before we execute." That's genuine openness without false process.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.