Clarity that does not exonerate
How decision-making systems use clarity to avoid exposure.
A project review runs ten minutes long. The presenter lands on the final slide; the sponsor says “this is very clear, thanks everyone, let’s keep the momentum.” The meeting closes on time-ish. On slide fourteen, a vendor dependency that would block the critical path in week six is shaded green. No one in the room has said the dependency is green; no one has said it is anything else; the room has moved.
Watch that phrase “this is very clear.” It arrives late in the meeting; it does the work of closing without asking anyone to state which version of the plan they have just endorsed. It is not dishonest; it is something stranger. A piece of language that keeps the group in motion while leaving the authorship of the decision unassigned.
Most people who reach for it mean something real by it. Meetings have to end. Teams have to leave the room with something that functions as a direction; another session is beginning in eleven minutes; the sponsor has five more of these today. The alternative to “this is very clear” is often a twenty-minute conversation about which risk the group is actually willing to carry, and that conversation, done properly, places one person at the head of the table in a position the table was not assembled to contain. Clarity, as a piece of language, is what allows the meeting to operate at the tempo the organisation needs it to operate at. Removing it or replacing it with something slower is not free.
This is the part that has to be granted before anything else. People who lean on “this is very clear” are not, in their own account, performing avoidance. They are solving a genuine coordination problem under time pressure. The problem is real and the phrase works on it. The cost, when it eventually arrives, arrives elsewhere and later, which is why the speaker rarely connects the phrase to the cost.
Certainty sits differently in the mouth. To be certain is to name that a choice has been made; that alternatives which were available a moment ago have been set aside by a specific person at a specific hour. Certainty does not circulate easily inside a meeting because it leaves a residue on the person who produces it. The speaker who says “yes, I am choosing this, and if the vendor slips we absorb the date” has, briefly, stepped out of the collective; the room reads the step-out; the reading is not always generous.
This is where clear begins to do a different kind of work than the word suggests. Clarity, in a system under pressure, does not refer to the visibility of the decision. It refers to the visibility of the process by which the decision was reached. More data; more scenarios; more dashboards; more alignment meetings. The process becomes legible; the decision itself becomes, through exactly the same motion, harder to locate. Data exonerates because it is shared. No one quite owns it; no one is obliged to account for what has been decided on the basis of it. Clarity, in this register, is a distribution mechanism for the exposure the decision would otherwise place on a specific person; the decision itself is no longer where the word points.
Where the word drifts
The vocabulary shifts under repetition. Clear begins to name a person rather than a statement. Someone who is clear becomes someone who is reliable; someone who is reliable becomes someone who is ready. The drift is quiet. The speaker does not notice it; the receivers notice it instantly. They begin producing the social signal of clarity whether or not the underlying judgement has been exercised. Crisp slides and confident voicing; a recommendation delivered in the form the meeting expects to receive it in. The organisation learns that clarity is a surface to be maintained. The judgement that would have been exercised, in the older sense of the word, migrates into private calculations that appear on no document.
Two closings of the same meeting. In the first, the sponsor says “this is very clear, let’s keep the momentum.” The team leaves. The vendor dependency is carried home by the product lead, who rebuilds the plan over the weekend in a way that preserves the green dot without quite defending it. The following Tuesday, when the dependency slips, the sponsor asks who made the call to hold the timeline. The answer distributes across four people, none of whom chose it.
In the second, the sponsor closes the laptop and says “before we move, slide fourteen. Is the green dot a judgement you are making or is it the number the vendor gave you?” The presenter either has the answer or does not. The room stills in a way that feels different. If the answer is not there, the absence becomes visible without anyone having to perform disappointment. The dependency surfaces. The meeting runs five minutes over. The following Tuesday, when the dependency slips, the call is traceable to the person who made it.
The second sponsor has not been harsher than the first. The force of the question is similar. The question has been pointed at the green dot rather than at the presenter, which is a different grammar. What the second sponsor has refused to do is allow the meeting to close on the grammar of clarity when the underlying act being skipped was a grammar of certainty.
What the process is avoiding
Paralysis, inside systems organised this way, does not look like paralysis. It looks like a next step. More input is needed; a further round of alignment would sharpen the picture; the dependency can be re-scoped in the next planning cycle. The language of clarity provides the vocabulary for postponement. Postponement is not registered as postponement because the next step is always reasonable. Reality does not adapt itself to process. Opportunities expire and alternatives disappear; constraints harden into facts that can no longer be chosen against. When action is finally taken, it arrives accompanied by a very clean narrative; the narrative rarely mentions that the decision, by the time it was made, had fewer choices available to it than it would have had three weeks earlier.
The residue is familiar to anyone who has sat through enough of these meetings. A decision is made and the document explaining it is well assembled. The information is complete; nothing was missed; something that should have been crossed has not been. The feeling is hard to name in the moment because the system is functioning. The system functions; it learns very little.
None of this is a failure of clarity. Clarity is a powerful instrument; organisations that lack it fail in more visible and more expensive ways. The question is a smaller one. It is whether, in the moment the phrase “this is very clear” arrives in the room, the speaker is using the word to describe a decision that has been made or to keep open the space in which the decision does not have to be made by anyone in particular.
The meetings continue. The decks become more assembled over time and the language tightens with them. The exposure, which is what certainty would have placed somewhere specific, stays where it was. Distributed across the surface of the organisation and held by no single person whose name will be asked for. Orderly and well explained. Only slightly out of time with what is actually happening.
Human & Machine studies how judgement fails under complexity. This piece is part of that work. Does this pattern feel familiar? You can explore it further through the Decision Audit.