Main idea

The problem addressed, the target, the promise, the priority and the success criterion almost always exist somewhere: in a sales deck, in a product framing note, in a marketing plan, in a tracking spreadsheet. Nothing is missing. What is missing is a place where these elements sit side by side and have to hold together.

As long as the dispersion lasts, everyone can go on working from the version that suits them, without bad faith and without apparent contradiction: sales leans on the broadest promise, product on the most cautious scope, finance on the most conservative figure, and none of the documents proves the other wrong. The incompatibilities are not hidden, they are simply distributed.

Consolidating into a single document brings no new information, and that is precisely what makes it a test: since everything was already written, what appears at consolidation was already true. The first version of the assembled document is often the first time the organization sees its own disagreement.

Why it matters

This explains why a format constraint — one page, a single table, a template with mandatory boxes — produces an effect the sum of the existing documents does not: it removes the possibility of letting two answers coexist without meeting.

It also gives a low-cost move before a launch: copy side by side what each function has already written, reformulating nothing.

Nuances and limits

Consolidation settles nothing by itself. A single document can perfectly well host the broadest version of each element, and reproduce the dispersion inside one page.

And dispersion sometimes has a legitimate reason: separate documents serve different audiences and different horizons, and melting everything into a single artifact can cost more than it clarifies.

Open questions

• What level of consolidation is enough to surface the incompatibilities without imposing a single document on teams that do not have the same needs?