Main idea

The composition of a session is reassuring: the functions concerned were invited, the constraints were heard, the objections were stated. People readily conclude that the organization is aligned. The conclusion doesn't follow: gathering the right people guarantees that the rationalities were expressed, not that they were set against each other to the point where one comes before the other.

Real alignment is recognized by something else: the disagreements have been brought to a degree of sharpness that makes them workable. You know what is a priority and what is sacrificed, who can decide, at what point an exploration must become an arbitration, which words are used without a shared definition, which success criteria are primary and which are secondary.

In other words, alignment isn't the state where nobody objects any more: it is the state where what objects is legible enough to decide what to do about it.

Layer added by "The Tools of Organizational Coherence" (2026-09-15). The misreading this criterion stands against has a more precise name than the composition of the session: alignment taken for a mood. Participants nod, the broad directions seem shared, the tensions stay general enough not to block what comes next. A team can thus be "aligned" on the fact that it needs to improve the customer experience without sharing the same definition of the customer, the experience, the improvement or the criterion for success — and leave the session with, in place of a stated disagreement, an impression of agreement that nothing distinguishes from agreement.

Why it matters

This strips presence of its status as proof, and moves the question from the invitation list to the content: not "who was in the room?" but "what disagreement came out of it stated?".

It also gives a demanding but verifiable definition of alignment, usable at the end of a session without waiting for execution.

Nuances and limits

Clarity has a threshold beyond which it becomes paralysing: making everything explicit, including what would have resolved itself, turns every meeting into an inquiry.

And a perfectly clear disagreement can remain unworkable if nobody has the mandate to settle it; clarity is necessary, it isn't sufficient.

Open questions

• How far must a disagreement be made explicit before it becomes workable, and from what point does making it explicit cost more than it returns?