A leader asks the team what they think, listens carefully, then announces a decision that ignores everything said in the room. Nobody complains out loud — but everyone recalibrates. Next time input is invited, less arrives, and what does arrive is safer. The damage wasn't done by the decision. It was done by the ambiguity: people thought they were voting when they were actually being consulted, and nobody told them.
Four levels, all legitimate
Significant decisions can be made at four distinct levels, and every one of them is legitimate in the right circumstances:
- Managerial — the leader decides and informs. Right for urgent calls, matters of compliance, and decisions the role simply owns.
- Consultative — the leader gathers input, weighs it, and decides. The most common level for consequential calls, and the most abused.
- Joint — leader and team decide together; the group's agreement is the decision.
- Participative — the team decides within an explicit frame, and the leader lives with the outcome.
Problems rarely come from choosing the wrong level. They come from not naming the level — leaving each person in the room to assume a different one. The person who assumed Joint experiences a Consultative decision as betrayal. The leader who assumed Managerial experiences the team's expectation of discussion as obstruction. Both are reacting to a contract that was never actually made.
The consultative contract
Consultative deserves special attention because it carries an implicit contract that most leaders honour only halfway. The full contract is: I will genuinely weigh your input, and when I close the decision I will explain how your input figured in my reasoning — including when I went the other way. The second half is the part that gets skipped, and it's the part that keeps input flowing.
If you can't articulate why their input mattered to your thinking, the team is right to conclude that Consultative was cover for Managerial.
Closing the loop costs a few minutes: here's what I heard, here's what shifted my view, here's what didn't and why. Skipping it converts every future request for input into theatre — and people decline to perform in theatre more than once or twice.
Declare the level in advance
The working discipline is simple: for any significant decision, name the level before the conversation starts. "This one's mine to make — I want your thinking before I do" sets up an entirely different meeting from "we're deciding this together", and both are healthier than the unspoken average of the two. Teams handle almost any level well when it's declared. What they can't handle is discovering the level after the fact — because then the lesson they learn isn't about the decision, it's about whether the invitation to contribute means anything at all.
There's a structural payoff too. Once levels are named routinely, a team can look at its pattern: if everything is Managerial, delegation has stalled and the level below isn't developing; if everything is Joint, the leader may be diffusing accountability for calls the role exists to make. The mix is diagnostic — but only once the levels are visible.