The First Follower

A solo idea is an opinion. A seconded idea is a movement. Recruit one ally before you propose anything that matters.

Derek Sivers' famous talk about the dancing guy at the festival makes one point that transfers directly to engineering organizations: the lone nut becomes a leader the moment the first follower joins. Not the tenth. The first. Before that person shows up, the crowd is evaluating whether to laugh at you. After, they are evaluating whether to join.

In a meeting room the same physics apply. An unsupported proposal is evaluated as one person's preference — "that's how Priya likes to do things" — and it attracts reflexive skepticism, because skepticism toward a peer's cold pitch is free and often reads as rigor. The identical proposal with one other person visibly agreeing ("we looked at this together, and I think it's right") crosses a social threshold. It stops being a preference and becomes a position. Disagreeing now means outnumbering two people, and most of the room won't spend status doing that without a real objection.

Mechanics

Three forces do the work.

Social proof. People evaluate ideas partly by watching other people's reactions to them, especially under uncertainty. Nobody in the room has fully modeled your proposal; they don't have time. So they read the reactions of people they trust as a proxy for quality. The first supportive voice is disproportionately powerful because it licenses the undecided middle. Once one credible person has said "this is right," agreement costs nothing. Before that, agreement is a bet.

Status defense. Agreeing with a peer's cold pitch feels, at a primate level, like subordinating — you're endorsing their judgment over your own in public, with no cover. This is why smart people reflexively poke holes at proposals they'd happily accept a week later. The objections aren't really about the idea; they're about not being the first to kneel. A pre-existing ally removes the subordination problem: the second and third agreers are joining a coalition, not deferring to an individual.

Reframing the contest. A solo proposal structures the room as you-versus-everyone: your idea against the collective's right to reject it. A pre-recruited ally restructures it as idea-versus-alternatives. The question quietly shifts from "should we let this person have their way?" to "is this the best option on the table?" That second question is the one you actually want debated, and it's the one your idea can win.

Practices

Socialize before you propose. Before bringing anything consequential to a group, take it privately to one or two respected people. This is the meeting-before-the-meeting applied to advocacy: you're not just previewing, you're recruiting. Ask for their honest reaction, and — critically — incorporate their feedback. Once their fingerprints are on the proposal, they are no longer evaluating it; they are defending something partly theirs. People fight for what they helped build.

Choose allies who cover your gaps. Credibility is domain-specific. If you're the backend person proposing a change to the frontend build system, your solo pitch is doubly weak: it's unsupported and it's out of your lane. Recruit a frontend voice. The right ally isn't your closest friend; it's the person whose endorsement answers the room's most likely objection before it's raised.

Let the ally speak early. In the actual meeting, the sequencing matters. If your ally stays silent until minute forty, the reflexive skepticism has already hardened into stated positions, and people defend stated positions. A simple "Dev and I dug into this last week — I was skeptical going in, and I came out convinced" in the first five minutes changes what every subsequent speaker is responding to. Arrange this beforehand. It's not theater; it's accurate information about who has done the diligence, delivered when it's most useful.

Being a first follower yourself

The cheapest high-value move in organizational life is publicly seconding a good idea. It costs you seconds. It earns real gratitude, because the proposer knows exactly what you just did for them — you took the subordination hit so nobody else had to. Do it deliberately: when a colleague floats something sound and the room goes quiet, say "I think that's right, and here's why" with one concrete reason attached, so it reads as judgment rather than loyalty.

This is also how you build the ally network for your own proposals. The people you've seconded will second you, not out of crude reciprocity but because you've established a working relationship where public support is normal.

Notice the courage asymmetry Sivers points out: the first follower takes nearly as much social risk as the leader, and creates most of the value — they're the one who transforms a lone nut into a leader. Which means seconding well is not a supporting role. It IS leadership, exercised from the second chair. Engineers underrate this because it doesn't look like initiative. It is initiative; it's just initiative applied to someone else's idea, which is rarer and therefore more memorable.

Failure modes

Manufactured consensus. If you pre-wire agreement among a clique while excluding the people the decision actually affects, you haven't built a coalition — you've stacked a deck. Real stakeholders detect this quickly ("this was decided before the meeting"), and the resentment outlasts the decision. The fix: the people you socialize with beforehand should include the ones most likely to object, not just the ones most likely to agree. Pre-wiring is legitimate when it's about improving the idea and giving people time to think; it's illegitimate when it's about denying them a real say.

Recruiting only friends. An ally whose support is predictable is worth little as social proof — the room discounts it correctly ("of course he agrees, they always agree"). The most valuable second is a credible skeptic who was persuaded. Their conversion carries information; your friend's loyalty carries none. If you can't convert one skeptic in private, that's data about the idea, and you got it cheaply before the meeting instead of expensively during it.

Diagnostic test

Before any consequential proposal, ask: if I get sick and miss the meeting, is there one person in that room who would argue for this anyway? If no, you're not ready to propose — you're ready to recruit.