A manager gives precise instructions, follows up on every task on time, and still feels like the team "doesn't own" anything that wasn't explicitly spelled out. Every new project needs a new order. Nobody flags a problem before it's pointed out to them, nobody proposes their own deadline, nobody raises an alternative when something doesn't go as requested. The usual diagnosis is "lack of commitment" or "lack of initiative," but the problem is almost never the people — it's the kind of coordination that leadership style trained into them. An order coordinates compliance. A well-made request coordinates commitment. And a team that only ever received orders acts exactly as it was trained to act: waiting for the next one.
Language doesn't describe the work: it coordinates it
Most leaders believe their core job is communicating well: explaining goals clearly, passing down information without noise, making sure everyone "understood." That's a descriptive view of language, and it's incomplete. From the Ontology of Language, speaking isn't just describing what already exists — it's a form of action that coordinates what doesn't exist yet. Every request, every offer, every promise and every declaration a leader makes doesn't report on the work: it generates the work. The place where leadership actually happens isn't the meeting where the strategy gets explained — it's the series of concrete speech acts — requests, promises, declarations — through which that strategy turns into real actions by real people.
Order vs. request: the difference that decides what kind of commitment you get
An order presupposes a hierarchy that leaves no real room to decline, negotiate conditions, or propose an alternative: it gets carried out because it comes from whoever holds the authority to give it, not because the person executing it has genuinely committed to the outcome. That's why a well-executed order produces literal compliance — exactly what was said, not a bit more — but not necessarily commitment. A well-formed request is different: it has explicit conditions of satisfaction (what's needed, by when, to what standard), and it leaves real room for the other person to accept, decline, or make a counter-offer. It's precisely that possibility of saying no — or proposing something else — that turns a "yes" into a promise with real commitment behind it, instead of obedience disguised as agreement.
Request (Ontology of Language): a speech act in which one person asks another for an action, specifying conditions of satisfaction — what, by when, to what standard — and leaving open the possibility that the other accepts, declines, or counter-offers. An accepted request becomes a promise; an order that gets carried out, by contrast, never passed through that genuine acceptance.
A well-executed order doesn't prove the team is committed: it proves the team knows how to obey.
The cost of leading with orders alone
A team coordinated only through orders develops a predictable pattern: it waits for explicit instruction on anything that wasn't already spelled out, can't delegate with confidence in either direction, and turns meetings into lists of assigned tasks instead of real spaces for coordinating action. When something goes wrong, nobody flags it in time — flagging it would mean admitting the order wasn't fulfilled, and the hierarchy left no room for that conversation — so the problem surfaces late, once it's already more expensive to fix. And since authority discourages counter-offers, critical feedback stops flowing: nobody is going to point out that the original request had a problem if doing so reads as insubordination.
How to lead by coordinating instead of commanding
Coordinating instead of commanding doesn't mean giving up authority or turning every decision into a committee vote: it means exercising authority through well-formed requests instead of orders. A complete request names the action, the deadline, and the standard of satisfaction, and explicitly asks whether the other person can commit to that or needs to negotiate something — less time, a different resource, a different scope. An automatic "yes," with no question or objection, deserves suspicion: it might be a real promise, or it might be the same old literal compliance dressed up as agreement. The leader's job is to notice the difference, insist that doubts get voiced before accepting rather than after failing to deliver, and keep their own promises religiously — because a team's trust is built from the same material on both sides. Ontological coaching works exactly at that level: not improving the leader's personality, but redesigning the concrete speech acts they use to coordinate their team.
Is your team waiting for instructions on everything that wasn't explicitly ordered?
See the free assessment Message on WhatsAppFrequently asked questions
An order presupposes hierarchy and leaves no real room to decline, negotiate, or propose an alternative: it gets carried out because it comes from authority, not because the person has genuinely committed to the outcome. A well-formed request has explicit conditions of satisfaction — what, by when, to what standard — and leaves room to accept, decline, or counter-offer, which is what turns acceptance into a real promise instead of obedience.
Because that's what it was trained to do: if every decision outside what was explicitly ordered has no room and isn't welcome, anticipating or proposing stops making sense. The team doesn't lack initiative — it learned, from repeated evidence, that initiative isn't part of the deal.
By naming the action, the deadline, and the standard of satisfaction precisely, and explicitly asking whether the other person can commit to that as stated or needs to negotiate something. A request that leaves no room to decline or counter-offer is an order in disguise, and it will produce the same literal compliance as always.
Comments