Pre-Read Alignment

A design session that discovers a fundamental objection has failed, regardless of how well it was run. The objection existed beforehand; the session merely surfaced it in the most expensive possible venue, in front of an audience, with the proposal's author defending rather than incorporating.

Pre-read alignment moves that discovery earlier and privately, where the proposal can absorb it.

Why it matters

It is the single highest-leverage facilitation practice and it happens outside the meeting entirely. Most review comments and most objections are predictable, and the people who will raise them are identifiable in advance.

It also changes the social dynamic: an objection raised privately and incorporated makes the objector a contributor; the same objection raised publicly makes them an opponent.

Implementation patterns

• Identify who could block it — by authority, by expertise, or by owning something affected — and speak to each before circulating.
• Ask what would make them say no, rather than presenting and asking for approval. The first question produces information; the second produces a position.
• Incorporate or explicitly address each objection in the document, so the session does not rediscover it.
• Circulate a pre-read and require it to be read, with the problem, constraints and options.
• State the decision to be made and who will make it, at the start of the session.
• Separate divergence from convergence — generate options before evaluating, because mixing them means the first option proposed is defended rather than compared.
• Capture the decision and the dissent in the room, since reconstruction afterwards produces a different decision from the one people believe was made.

Industry example

Platform and infrastructure teams such as BrowserStack's, whose decisions affect many consuming teams, face this constantly: a change to shared infrastructure has a dozen stakeholders, several of whom will have a legitimate concern. A session convened without pre-alignment spends its time discovering those concerns; one convened after spends its time deciding.

Failure scenarios

• A session convened to "discuss the approach", which will discuss the approach.
• No pre-read, so context-setting consumes half the time.
• Missing someone whose objection blocks it, requiring a second session.
• Too many participants, so nobody contributes.
• No identified decision-maker, leaving the session seeking a consensus that is rare on architectural trade-offs.
• Pre-alignment used to build a coalition rather than to gather objections, which is manipulation and is detected.

Trade-offs

Pre-alignment takes time proportional to the number of stakeholders, and for a small reversible decision it is disproportionate. It can also shade into pre-deciding, where the session becomes theatre and participants notice they were not consulted.

The distinction is whether the pre-read conversations genuinely changed the proposal. If they did, the practice worked; if the document is unchanged, the conversations were persuasion rather than consultation and the session will be resented.

Interview question

"You have a proposal affecting six teams and a one-hour session scheduled. Describe what you do in the week beforehand, and how you would know whether it worked."