A leader who demands a lot, gives tough instructions, and never lets a mistake slide has a bad reputation, but in practice they're rarely the one who loses the most people. The real pattern behind high turnover is usually different: a leader who approves a report on Monday and rejects it on Thursday without explaining what changed, who asks for "more commitment" without saying what concrete action they expect, who shifts what counts as "done well" depending on their mood that day. People don't necessarily quit a tough boss — they quit an unpredictable one, because there's no floor to stand on: every task becomes a bet on which version of the boss shows up today.
Demands have a standard; ambiguity doesn't
A demanding leader may ask for a lot, but they generally ask for the same thing: the standard is high, but it's stable, and whoever knows it knows what they need to do to meet it. An ambiguous leader is different: it's not that they ask for too little or too much — it's that they never precisely define what counts as "satisfied." A report that was fine last week now "lacks depth"; a deadline that seemed reasonable suddenly "should have been done sooner." What changes isn't the demand: it's the criterion used to measure whether it was met, and it changes without warning.
Ambiguity is a request with no conditions of satisfaction
From the Ontology of Language, a complete request has explicit conditions of satisfaction: what's needed, by when, to what standard. When a leader asks for "a better report" without specifying in what sense, they're not being ambiguous by accident: they're leaving the standard open to their own judgment in the moment, and that judgment can change from one day to the next with no way for the person doing the work to anticipate it. Ambiguity isn't a personality trait ("they're scattered," "they're moody"): it's the systematic absence of clear conditions of satisfaction in the requests that leader makes.
Condition of satisfaction (Ontology of Language): the explicit criterion used to verify whether a requested action was fulfilled — what was delivered, by when, to what standard. A request with no conditions of satisfaction isn't a complete request: it's an expectation that only exists inside the head of whoever made it.
It's not the demands that make people quit: it's never knowing whether what they did was enough.
The cost of ambiguity: why it wears people down more than demands do
A team that doesn't know what its leader expects develops a predictable pattern: it stops proposing anything, because any proposal can be rejected by a criterion it still doesn't know, it starts asking for confirmation on everything — even the obvious — because confirming is the only way to reduce the risk of getting an invisible standard wrong, and it accumulates a quiet emotional toll that doesn't feel like the fatigue of working hard: it feels more like the constant vigilance of someone who never knows when the ground is going to shift. That toll is rarely named as such when someone leaves — people say they "needed a change" or "didn't fit the culture" — but the automatic judgment left behind is simple: "nothing I do is ever enough." Ambiguity also erodes a team's trust faster than any demand does, because trust is built on promises that get kept predictably, and a standard that shifts without warning means no promise — not the leader's, not the team's — has stable ground to stand on.
How to lead with clear standards without turning rigid
Giving up ambiguity doesn't mean lowering the bar or spelling out every detail in advance: it means naming the conditions of satisfaction for every request that matters — what's needed, by when, to what standard — and, when that standard changes, saying so explicitly instead of letting the person find out through rejection. A request like "I need the report covering these three points, by Thursday, with these numbers verified" leaves far less room for ambiguity than "I need this to be better," even though both can sound equally demanding. Leading by coordinating action instead of commanding starts exactly there. Ontological coaching's job in these cases isn't lowering how much a leader demands: it's helping them notice when their request depends on a criterion that only exists in their own head, and translating it into something the other person can actually fulfill — or decline, with the same clarity.
Is your team's turnover higher than it should be, and you can't quite figure out why?
See the free assessment Message on WhatsAppFrequently asked questions
Because demands, however uncomfortable, have a fixed standard: the person knows what's expected and can either meet it or not. Ambiguity has no floor: the standard shifts with the day or the leader's mood, so no amount of effort guarantees approval. That constant uncertainty wears people down more than any demand, and in most cases it's what pushes someone to look for another job.
A tough leader makes demanding requests but with stable conditions of satisfaction: they ask for a lot, but always the same thing, and they keep their own promises. An ambiguous leader makes requests without clear conditions of satisfaction — or changes them after the work is already done — so there's no way to know in advance what's going to count as fulfilled.
The team stops operating defensively. When the standard is explicit and stable, people can plan, propose alternatives, and own a concrete outcome instead of trying to guess which version of the leader they'll get that day. That doesn't make the leader softer: it makes them more predictable, which is what actually keeps people.
Comments