In two articles (one on this blog, the other forthcoming in the magazine "Proposition g"), the subject is responsibility and trade-offs. The first talks about the brand man to raise a simple question: who is truly accountable for a brand's coherence? The second looked at soft decisions: those decisions that preserve the appearance of consensus while pushing the real choices down into execution.

One more practical question now remains.

How do we avoid getting there in the first place?

How do we surface disagreements before they turn into contradictory messages, competing priorities, confused launches, or late trade-offs?

An organization's spontaneous answer is often to add meetings. More sync points, more committees, more cross-validations. Sometimes that's necessary. But alignment doesn't happen simply because the right people have been gathered in a room.

Alignment happens when the organization has shared objects, stable definitions, explicit criteria, and traceable trade-offs that make disagreements visible early enough to be dealt with.

A coherence tool, then, isn't there to make everyone agree. Its first purpose is to reveal more clearly where the agreement stops.

Alignment Is Not a Mood

The word "alignment" is a trap.

It often evokes a kind of harmony: everyone understands, everyone buys in, everyone moves in the same direction. In practice, many so-called alignment meetings mostly produce an impression of alignment. Participants nod, the broad directions seem shared, the tensions aren't denied but stay general enough not to block what comes next.

The problem is that a mood of agreement isn't enough.

A team can 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. Another can be "aligned" on a launch, yet hold different assumptions about the promise, the scope, the acceptable level of quality, or the role of each function.

Real alignment is more demanding.

It requires sharing a sufficiently stable understanding of the problem, the target, the promise, the priorities, and the criteria for success. It doesn't ask that everyone think the same thing. It asks that the important disagreements be visible before they get baked into execution.

That's where the tools become useful.

Not because they mechanically produce coherence, but because they force the organization to articulate what it already believes it shares.

A Common Language Reveals Hidden Disagreements

The first tool is also the simplest: words.

A common language isn't just for communicating better. It's for surfacing real disagreements before they become inconsistencies in execution.

Two teams can use the same word without talking about the same thing. "Customer" can refer to the end user, the buyer, the prescriber, the strategic account, or the priority segment. "Quality" can mean technical robustness, a premium perception, the absence of defects, functional richness, or ease of use. "Launch" can refer to a production deployment, a public announcement, a commercial opening, or actual availability to the market.

As long as these differences stay implicit, the organization believes it's discussing the same subject.

It isn't.

The conflict is already there, but it stays hidden beneath the same words.

A shared glossary may seem modest, almost academic. Yet it's powerful when it covers a project's critical terms. Not a grand decorative dictionary, but a short list of words that absolutely must be stabilized: customer, target, promise, offer, success, launch, activation, quality, priority.

The value of the glossary isn't to freeze language forever. It's to quickly surface the gaps in definitions.

When one team discovers it wasn't using the same word the same way as another, it often discovers a deeper disagreement. That's good news. A disagreement about definitions found early costs less than an inconsistency found at launch.

A common language doesn't eliminate conflicts, but it keeps them from staying hidden beneath the same words.

The One-Pager Forces Minimal Clarity

The second useful tool is the one-pager.

Its value doesn't lie in its short format on its own. A bad one-pager can be just as vague as a bad fifty-slide presentation. Its strength comes from the constraint: it forces the organization to state the essentials without being able to hide behind volume.

A good one-pager should answer a few simple questions:

• what problem are we addressing?
• for whom?
• what promise are we making?
• which priority comes before the others?
• what primary criterion will let us say we've succeeded?
• which secondary criteria must stay consistent with that primary one?

These questions look elementary. They almost never are.

The difficulty appears the moment you have to choose a single main problem, one priority target, one central promise, one dominant criterion for success. As long as these elements stay scattered across several documents, everyone can keep favoring their own reading. The one-pager forces a first consolidation.

It doesn't guarantee the decision is good. It only guarantees that the ambiguities become more visible.

That's already a lot.

If a team can't write the target clearly, that's not a writing problem. It's often a strategy problem. If it can't formulate the promise, that's not just a marketing problem. It may be that the product, the market, and distribution aren't telling the same story. If it can't choose a primary criterion, it may be that several definitions of success are competing.

The one-pager is useful because it makes these tensions hard to hide.

The PR/FAQ Forces the Customer's Point of View

The PR/FAQ, popularized by Amazon, pushes this logic further.

Its principle is simple: write the press release and the frequently asked questions before building or launching the product. It's not a communication exercise in the superficial sense of the term. It's an exercise in coherence.

The press release forces you to state what exists, for whom, why it matters, and what the customer can genuinely expect. The frequently asked questions force you to anticipate objections, misunderstandings, limits, ambiguous cases.

The value of the PR/FAQ is that it shifts the center of gravity.

Instead of starting from the internal organization, it starts from the customer's point of view. Not "what does each function want to say?" but "what is the customer supposed to understand, believe, do, or feel?"

That shift exposes inconsistencies very quickly.

If the product doesn't deliver on the promise, it shows. If the target is too broad, it shows. If objections are met with vague answers, it shows. If two teams aren't talking about the same product, it shows.

The PR/FAQ is therefore less a storytelling tool than a coherence test. It forces the organization to speak with one voice before it even enters execution.

And if that single voice proves impossible to produce, that's precisely the sign that a trade-off is still waiting to be made.

Metrics Must Be Ranked

Another often-invisible disagreement concerns indicators.

Each function can have good reasons to defend its own criterion for success. Marketing will watch visibility or engagement. Sales will watch volume, conversion, or field presence. Product will watch usage, retention, functional quality. Finance will watch margin, cost, return on investment.

None of these indicators is wrong.

The problem appears when each becomes sovereign in its own corner.

Without a hierarchy of metrics, the organization doesn't really share a definition of success. It juxtaposes several possible successes, sometimes incompatible. Each function can then declare its objective rational, and it will be right. But the whole doesn't necessarily produce a single line.

You therefore have to distinguish the primary criterion from the secondary ones.

The primary criterion states what we're truly trying to succeed at right now. The secondary criteria state what must be preserved so that this success isn't achieved at the price of destruction elsewhere.

For example, pursuing volume can be coherent if you accept temporarily reducing the margin. But that choice has to be owned. Pursuing margin can be coherent if you accept giving up certain segments. Pursuing awareness can be coherent if you know how it will then be tied to usage or conversion.

One primary objective, aligned secondary criteria: that too is coherence.

Metrics don't replace judgment. They make explicit the way the organization agrees to judge its own action.

Cost of Delay Makes Delay Visible

The cost of delay is interesting for the same reason: it puts a value on lost time.

As long as a trade-off is postponed, the organization may feel it isn't choosing yet. In reality, it's already choosing. It accepts a cost of delay, often invisible because it doesn't take the form of an immediate expense.

Delay can cost in commercial opportunity, in learning not gained, in coordination energy, in a missed market window, in accumulated confusion. But if that cost is never articulated, it stays abstract. It becomes easy to prolong the discussion, to ask for one more analysis, to wait for the next meeting.

The cost of delay doesn't turn every trade-off into a mechanical calculation. It simply forces you to ask a question that soft decisions often avoid: what do we lose by not deciding now?

Here again, the tool is worth less for its apparent precision than for what it forces into view.

The Decision Log Keeps the Memory of Losses

A trade-off without a memory quickly becomes negotiable again.

A few weeks after a decision, everyone remembers what suits them. The reasons get simplified, the initial constraints disappear, the frustrations remain. People then reopen debates already settled, or interpret differently what had been decided.

The decision log is there to prevent that.

It doesn't need to be heavy. It simply needs to keep a record of the important trade-offs:

• what decision was made?
• why?
• what options were set aside?
• what did we agree to sacrifice?
• who made the call?
• under what conditions should the decision be reopened?

That last point is essential. A decision doesn't need to be eternal in order to be clear. It can be revisable, but you have to know what justifies reopening it. Otherwise, any frustration becomes a reason to start the discussion over.

The decision log therefore protects the organization against amnesia. It makes visible what the soft decision often tries to hide: the loss that was accepted.

It also allows the organization to respect the people who didn't get their way. Their point of view wasn't necessarily ignored; it may have been heard, then set aside for an explicit reason.

That's very different.

Escalation Rules Prevent the Endless Discussion

Even with a common language, a one-pager, a PR/FAQ, ranked metrics, and a decision log, one decisive question remains: what do you do when a disagreement persists?

Many organizations have no clear answer.

They prolong the discussion. They add a meeting. They ask for one more document. They wait for the tension to subside. They hope a synthesis will emerge.

Sometimes that's reasonable. Often, it's a more elegant way of not deciding.

You therefore need escalation rules.

Who decides? At what point? On what kind of subject? Which decision can be made by the team? Which decision must be escalated? Which disagreement deserves further exploration, and which disagreement must now be settled?

These rules aren't there to make the organization rigid. They're there to prevent the endless discussion.

A mature organization isn't one where everything gets escalated. Nor is it one where everyone decides in their own corner. It's an organization that knows where disagreements should live, how long they can stay open, and at what point they must become a decision.

The Bureaucratic Risk

It would be tempting to conclude that you just need to add these tools.

A glossary, a one-pager, a PR/FAQ, metrics, a decision log, escalation rules: the toolkit looks reassuring. It can even give a very professional impression.

But a coherence tool can itself become a soft decision.

A glossary can turn decorative. A one-pager can be filled with vague sentences. A PR/FAQ can become an internal communication exercise. Metrics can be stacked with no hierarchy. A decision log can record choices without ever naming what was sacrificed. Escalation rules can exist without being used.

That's the danger: mistaking the existence of the tool for the existence of alignment.

An alignment tool is only useful if it makes a tension more visible.

If it lets you avoid a difficult conversation, it makes the problem worse. If it turns a disagreement into a polite formulation, it becomes an instrument of fog. If it adds documentation without clarifying the decision, it joins the very bureaucracy it claims to be fighting.

The right question to ask of every tool is therefore simple: what does it force you to make explicit?

If it forces nothing, it probably isn't good for much.

Conclusion

You don't produce alignment with meetings or committees alone.

You produce it with shared objects that force the organization to state what it believes it shares: the words it uses, the problem it's addressing, the promise it's making, the customer it's targeting, the success it's pursuing, the losses it accepts, the conditions under which a decision can be reopened.

These tools replace neither responsibility nor the act of making trade-offs. They prepare them.

They let the committee illuminate instead of dissolve. They let the person in charge make the call without pretending to decide from nowhere. They let disagreements surface early enough not to become inconsistencies visible to the customer.

Their value, then, isn't documentary. It's political in the noble sense: making choices more explicit, tensions more visible, and trade-offs more ownable.

Alignment is not the absence of disagreement. It's an organization's ability to surface its disagreements clearly enough to decide what to do about them.

Further Reading

Why Organizations Prefer Soft Decisions Product Decision Record: tracing the product choices that shape the company The NNL Roadmap: Aligning Without Scattering