Main idea

When a decision falls apart in execution, the reflex is to act on the meeting: prepare it better, run it better, close it better. The lever is weak, because what is missing does not live in the session but between sessions.

What holds between two meetings are objects: a vocabulary whose words have a shared definition, legible objectives, success criteria explicitly ranked between primary and secondary, framing documents, sometimes a decision log that keeps what was settled, when, and by whom. These objects depend on no individual memory and survive the departure of the people who were in the room.

Their own effect is to make gaps visible earlier. Two teams using the same word with two definitions discover it by rereading the entry that fixes it, not six weeks later, when the deliveries fail to fit together.

Within that family, the decision log has a proven form and constraints of its own. On the product side, it amounts to a few cross-cutting rules a year — on the priority given to the customer or the supplier side of a marketplace, on the languages supported by default — each written with its context, the alternatives set aside, its consequences, and what could make it change. What sets this object apart from the other shared objects is that it does not get updated: it accumulates. And it is only worth something while it stays rare, where a glossary gains from covering the whole disputed vocabulary.

Layer added by "Product Decision Record: tracing the product choices that shape the company" (2026-06-03).

Layer added by "The Tools of Organizational Coherence" (2026-09-15). The list extends beyond the vocabulary and the log: the one-pager, the PR/FAQ, the metrics hierarchy and the escalation rules belong to the same family, and what they have in common is not durability alone. Each imposes a constraint of form that a disagreement cannot survive — one definition per word, a single page, a voice addressed to the customer, a rank between criteria, a deadline. It is that constraint, and not the artifact's lifespan, that explains why a better-run ritual does not produce the same effect: a meeting can always accommodate two readings, a constrained document cannot.

Why it matters

It points the improvement effort toward durable artifacts rather than rituals, in a field where energy spontaneously goes to the latter.

It also gives a precise use to the glossary and the decision log: they are not compliance documents, they are the objects that keep a shared vocabulary from operating without a shared definition.

Nuances and limits

Shared objects expire: a success criterion ranked last year and never revisited misleads more than an absent criterion.

And they do not replace arbitration: a perfectly kept decision log can record, decision after decision, a series of formulations that settled nothing.

Open questions

• What minimum upkeep does a decision log require to stay a reference rather than an archive?