The Version Everyone Can Live With: What Consensus Editing Costs a Message

The message left the strategy room at nine words. It arrived at final approval at forty-one.

Nothing dramatic happened in between. There was no crisis, no change of strategy, no new chief executive. There was simply a sequence of reasonable requests from reasonable people, each of whom was protecting something legitimate — a legal exposure, a regional sensitivity, a sales objection, a relationship with a partner. Taken individually, every edit was defensible. Taken together, they produced a sentence that nobody objected to and nobody remembered.

This is the most common way strong messaging fails in Canadian organizations. Not through rejection. Through consensus.

The anatomy of a softened sentence

Start with a claim built to move: We cut warehouse downtime for mid-market distributors by a third, in under ninety days.

Round one, legal: the number needs qualification. In many cases, we have helped clients reduce downtime significantly.

Round two, regional sales: some clients do not have warehouses. We help organizations with distributed operations reduce operational disruption.

Round three, a senior executive who has seen a competitor make a similar claim: We help organizations build more resilient operations.

Round four, brand: it needs a personality. We help organizations build more resilient operations, with a human touch.

Round five, the approval meeting: it feels long. Resilience, delivered.

The final product is not a lie. It is also not a position. It describes a category, not a company, and the only distinctive element left — 'delivered' — is an adjective wearing a verb's clothing.

Each round is locally rational, which is the problem

Consensus editing is not caused by cowardice. It is caused by an organizational design in which every reviewer is accountable for a different risk, and no reviewer is accountable for the coherence of the whole.

Legal is accountable for exposure. Sales is accountable for objections. Regional leads are accountable for local relevance. Communications is accountable for tone. Nobody in the chain holds the mandate for the message's spine — for the one claim the brand will defend when it is inconvenient.

Absent that mandate, the default is subtraction. Removing a claim is always locally safer than defending it. Nobody has ever been reprimanded for deleting a differentiator.

Risk aversion compounds rather than adds

This is the part most organizations underestimate. Each reviewer sees the version that reached them, not the version that started. A qualifier added in round two is read in round three as part of the original claim, and softened again. Four rounds later, the message has been deflated four times and no single person feels responsible, because no single person did it.

Risk aversion in message review behaves like compound interest, except the account shrinks.

The asterisk becomes the voice

Watch what happens to the small print over time. It begins as a tactical concession — one footnote for one claim in one market. Within two years, the footnotes have become a reading experience of their own, and the brand's most distinctive statements are the ones most heavily conditioned.

Buyers notice this faster than brands expect. A message dense with conditions reads as a company that is not certain. That reading transfers. If the claim requires that much protection, the buyer reasons, the confidence behind it must be thinner than the packaging suggests.

Hedged language is not neutral. It is a signal, and it is usually the wrong one.

A feedback audit: four questions per comment

Before accepting any edit to a core message, run it through four questions. It takes ninety seconds and prevents most of the damage.

1. Is this comment adding evidence or removing a claim? Evidence improves a message. Removal is sometimes necessary, but it must be argued for explicitly rather than granted by default.
2. Is this solving a real objection or an imagined one? Cite the objection. Name the buyer who raised it. If nobody can, the edit is speculation wearing a risk hat.
3. Is this asking for clarity or for coverage? Clarity makes a claim easier to repeat. Coverage makes it harder to challenge. These pull in opposite directions, and you can usually only choose one.
4. Would we accept this edit on a competitor's behalf? If the revised sentence would be fine on anyone's website, it is not doing any work on yours.

Two or more 'no' answers mean the comment should be logged as an objection to be resolved by the strategy owner, not applied as a line edit.

Three structural fixes that protect the spine

Name a message owner. One person, senior enough to say no, accountable for the integrity of the claim from strategy through publication. Reviewers advise; the owner decides.

Separate the two kinds of feedback. Collect 'this is inaccurate' and 'this makes me uncomfortable' in different channels, with different response standards. They are not the same category of input and should not be weighed on the same scale.

Count the rounds. Give every core message a maximum of three review cycles, with a named list of reviewers fixed in advance. Most message decay happens in rounds four through seven, when the participants have stopped reading for meaning and started reading for risk.

The cost of unanimity

A message everyone can live with is a message nobody will repeat. That is the trade Canadian organizations keep making without noticing they are making it — trading distinctiveness for internal peace, one round at a time.

The alternative is not conflict. It is authorship. Someone has to be responsible for the sentence that survives the process, and that responsibility cannot be distributed across a committee without dissolving.

Protect the spine. Argue about the rest.