How do you drive consensus across many engineers and teams?

Question

Accepted Answer

Getting many smart, opinionated people to align is one of the hardest parts of senior technical leadership. The goal is **a decision everyone can commit to**, not unanimous agreement (which is often impossible). You build alignment through process, not force.

## How to drive consensus

```text
✓ Align on GOALS/criteria first — most disagreement is about unstated goals
✓ Gather input WIDELY and early — people commit to what they shaped
✓ Write a PROPOSAL (RFC) — a concrete doc beats endless meetings
✓ Steelman objections — address the strongest, not the weakest
✓ Find the 80% everyone shares; isolate the real 20% of conflict
✓ Decide with DISAGREE-AND-COMMIT — alignment, not unanimity
✓ Communicate the WHY — people commit to decisions they understand
```

## Use a written RFC

For cross-team decisions, a written **RFC** (request for comments) circulated for feedback beats meetings. People engage on their own time, objections surface in writing, and you get a durable record. Meetings are for resolving the last sticking points, not for thinking out loud.

## A concrete example

Five teams must agree on a shared API standard. You write a draft RFC, invite comments for a week, address the substantive objections, and hold one meeting to close the gaps. Far better than ten people debating live with no document.

## A pitfall

Mistaking consensus for *unanimity*. Waiting for everyone to fully agree leads to paralysis, or a watered-down compromise nobody likes. Aim for commitment, not universal enthusiasm.

## Why it matters

Decisions that lack buy-in get quietly undermined in implementation, people build something else.

Real alignment, where everyone understands and commits, is what lets a large, distributed group actually move together.