Social Network Webbing: The Adoption Map That Isn't the Org Chart

We shipped structured call notes in Recap CRM — a template that replaced the free-text box with four prompted fields — and dogfooded it inside our own twenty-two-person GTM org first. Six weeks in, adoption was 31% and flat. We’d done the normal things: an all-hands demo, a Loom walkthrough, manager reminders in one-on-ones, a Slack announcement with 14 thumbs-up reactions.

What we hadn’t done was ask who each rep actually learns their habits from. Social Network Webbing asks precisely that, and it took ninety minutes and a very large sheet of paper to find the answer.

What it is and how it runs

Social Network Webbing is a Liberating Structure for mapping the informal network around a challenge, then choosing next moves based on that map instead of on the org chart. It runs in small groups of four to seven, each with a large sheet:

1. Name the challenge in one sentence — ours was “get structured call notes used on every customer call by December.”
2. Individually list people and groups relevant to that challenge — anyone who influences whether it happens. One name per sticky note. Insiders, outsiders, anyone.
3. Place them on the sheet and draw the connections. Who talks to whom, and how strongly? We used two line weights: heavy for “they’d ask this person for advice,” light for “they interact.”
4. Read the map together. Where are the hubs — people with many strong lines? The brokers, connecting otherwise-separate clusters? The isolates? Where are the gaps?
5. Decide two or three concrete next steps, each naming a specific person and a specific conversation.

The step people underrate is step three. Listing names produces a roster; drawing lines produces a structure, and the structure is where the surprise lives.

What our map showed

Twenty-two people, three groups drawing in parallel, and all three maps had the same hub: a senior AE who had been at the company four years, held no management title, sat in no rollout plan, and had a heavy advice-line from eleven of the twenty-two people on the sheet. Two of the three groups also drew her as the broker between the SDR cluster and the account-management cluster, which otherwise barely touched.

She was not using structured call notes. Not out of resistance — she’d tried it, found the four prompted fields slower than her own shorthand for renewal conversations specifically, and gone back. Nobody had asked. And because eleven people copied her habits, our 31% was almost exactly the population of people not strongly connected to her.

The maps showed two other things. The regional sales manager we’d leaned on hardest for the rollout had lots of light lines and almost no heavy ones — plenty of interaction, very little advice-giving. He’d been dutifully reminding people in one-on-ones for six weeks with no effect, and now we understood why. And one SDR was drawn as an isolate on all three maps, connected to almost nobody, which was a different and more urgent problem than adoption.

Our next steps were embarrassingly small: one conversation with the AE about what specifically didn’t work for renewals, one design change to let a template be skipped per-call-type, and one ask for her to show her own adapted version at the following Thursday’s GTM sync. Adoption was 74% four weeks later. We didn’t run another campaign.

Why drawing the lines works

The claim underneath this structure is that practices spread through relationships of trust, not through channels of authority, and that most rollout plans are built on the org chart because the org chart is the only map anyone has written down. Social Network Webbing produces the other map in an hour, from the people who actually live in the network.

The specific mechanic that matters is that everyone draws simultaneously in separate groups. Three independent maps that agree on a hub is strong evidence; one map drawn by a facilitator interviewing people is just a facilitator’s theory. And having participants place their own connections means the map includes relationships that don’t exist in any system — who eats lunch with whom, who came from the same previous employer, who quietly answers questions at 9pm.

It also reframes resistance usefully. Had we noticed the AE’s non-adoption at all, we’d have filed it as a laggard problem. The map made her a distribution problem, which has completely different solutions.

When to skip it, and how it gets ugly

This structure produces a document with real people’s names and visible judgments about their influence, and that can go badly. A map showing that a manager isn’t a trust hub is genuinely uncomfortable, and a map showing someone as an isolate is information about a colleague they didn’t consent to have discussed. We kept the sheets in the room, photographed nothing, and took only the action items out. I’d do that every time. If your org would treat these maps as an influence-ranking artifact to circulate, don’t run it.

Skip it when the barrier isn’t social. If a practice isn’t spreading because the tool is slow, or because nobody has permission, mapping the network just tells you a well-connected person also hates the slow tool. And it needs a group with real relational knowledge — a room of new joiners will produce a map of the org chart, which you already have.