Small-World Dynamics: Product Adoption

What Small-World Networks Teach Us About Product Adoption

By Melissa Beaudette

Have you ever found yourself Googling “quick dinner ideas” and somehow end up watching talking birds? And where did this whole “67” thing come from? And why is Kevin Bacon the center of the universe?

It all comes back to one thing: small-world networks.

And once you see these patterns, it becomes clear they are everywhere, shaping how we think, how information moves, how traffic and transportation systems behave, and how ideas ripple through society. Recognizing these dynamics isn’t just interesting trivia; it can make us better product managers. If we can understand how and why ideas spread, then we can start asking a more valuable question:

How do we harness these same patterns for product adoption and growth?

So what exactly is a network?

The modern understanding of small-world networks comes from the work of Duncan Watts and Steven Strogatz, who showed in their 1998 Nature paper that many real-world systems (i.e. social groups, neurons, power grids, the internet) share a surprisingly similar structure.
(Watts & Strogatz, 1998)

At its core, a network is simply a set of nodes (things) and edges (connections between things). But what Watts and Strogatz discovered goes deeper. Real networks aren’t just a random web. They tend to follow a recognizable pattern: nodes cluster together, and, most importantly for small-world theory, a few shortcuts link those clusters so no group is ever too far from another.

Roads are a perfect way to visualize this.

Nodes
Destinations, like homes, schools, grocery stores, are the nodes.

Edges
Streets are the edges connecting those destinations to one another.

Clusters
A neighborhood forms a cluster because many destinations are connected by lots of short, local roads.

Shortcuts
Highways act as shortcuts, dramatically reducing the number of steps needed to travel between distant clusters.

This is the defining structure of a small-world network:
tight local clusters connected by a handful of powerful shortcuts.

It’s the same pattern behind why your “dinner” search detours to talking birds, why “67” spreads like wildfire, and why Kevin Bacon is apparently everyone’s cousin twice removed.

Why small-world structure matters for adoption

Once you understand the basic shape of a small-world network, tight local clusters connected by a few powerful shortcuts, something becomes clear:

Product adoption behaves the same way.

Most product managers think in funnels: awareness → activation → engagement → retention. Funnels are useful, but they only describe where people drop off. They don’t explain how a product actually spreads across users, teams, or markets—or why adoption accelerates in some places and stalls in others.

Small-world structure does.

Here’s how:

1. Adoption starts in clusters.

As a society, we naturally form clusters— families, niche communities, regional pockets of people, and even temporary groups like new parents. These clusters share language, habits, and pain points, making them the true starting point of product adoption.

A feature often succeeds or fails based on how well it resonates within a specific cluster before it ever reaches the broader population. Trying to launch a feature to “everyone” feels intuitive, but it rarely works. The real skill is choosing the right cluster to start with.

When you design for a tight, cohesive group, adoption takes root quickly.

2. Virality isn’t magic—it’s structure.

Clusters explain where adoption starts, but shortcuts explain how adoption spreads. In network theory, shortcuts are long-range connections that link one cluster to another. In products, shortcuts show up as moments or mechanisms that naturally expose your product to a different group of people.

A shortcut might be a share action, a referral link, a cross-team workflow, an integration, or even a single influential user who spans multiple communities. These moments act like highways in a road system: they let your product jump quickly from one cluster to the next. Without them, adoption stays local.

And here’s the surprising part: a few well-designed shortcuts can outperform massive broadcast efforts. Growth happens when you create opportunities for cross-cluster connection. The more intentional you are about enabling those moments, the easier it becomes for your product to spread.

3. Shortcuts reveal your next cluster.

Once you’ve found product–market fit within a cluster, the instinct is often to ask, “Which adjacent segment should we target next?” A better strategy may be to observe where your shortcuts take you. When shareable moments, handoff workflows, or integrations work as intended, adoption jumps organically, often into a cluster you didn’t anticipate.

Organic jumps reveal where the product delivers unexpected value.

They show you which clusters respond more strongly than the ones you initially designed for. Sometimes the most valuable cluster is not the tangential one you planned to target, but the one that discovered you through a shortcut.

Instead of guessing your next segment, let the network show you where to go next.

4. Adoption issues? Check the network.

When a product isn’t gaining traction—or when growth slows after an initial win—it’s tempting to blame the usual suspects: a feature, the funnel, marketing, or timing. And sometimes those really are the issues.

But there’s another place you can look: the network surrounding your product.

Small-world dynamics give PMs a different set of questions to ask when adoption isn’t where you expect it to be.

Did your first cluster actually adopt the product?

If initial adoption never takes off, it’s rarely a growth problem. Early-stage adoption usually fails because the product didn’t resonate deeply enough with the cluster you designed for—or because that cluster wasn’t the right one.

Shortcut mechanisms matter later, but strong early resonance is the foundation everything else depends on.

Metrics to Consider: activation rate, early retention, depth of engagement (session length or key action completion), and qualitative feedback signals.

If the first cluster did adopt it, did you create any shortcuts?

Many products plateau not because the cluster is unhappy, but because the cluster is isolated.
Without shortcuts that let workflows, artifacts, or invitations travel beyond the original group, adoption stays local.

Metrics to Consider: cross-team or cross-role adoption, sharing or collaboration rates, external engagement with shared artifacts, and usage of integrations or referral surfaces.

Do you know who is actually using the product now?

Sometimes adoption has already jumped to a new cluster organically—but the product team is still focused on the original one. When PMs keep targeting the original cluster, they miss the opportunity emerging in plain sight. If you’re seeing unexpected usage patterns, new personas showing up, or expansion in places you weren’t targeting, the network may be revealing your next cluster.

Metrics to Consider: sign-ups or activation from new segments, retention differences across personas, unexpected referral sources, and patterns in support or feature requests.

A Simple Example: Why Slack Spread So Fast

Slack is a good example to see how shortcuts can reshape a product’s trajectory.

The team originally designed Slack for small engineering groups—a tight, well-defined cluster. But Slack also included a natural shortcut: it was incredibly easy to invite someone into a channel to answer a question, review a design, or coordinate around a task.

Those invitations traveled outward.
Teams didn’t expand because Slack targeted them; they expanded because someone inside the first cluster pulled them in.

Engineers invited PMs
PMs invited marketing
Marketing invited support
Support pulled in sales
Executives joined cross-functional channels

Within many organizations, Slack’s adoption pattern looked like this: strong resonance inside one cluster, followed by organic jumps into adjacent groups. Slack didn’t start with the goal of becoming a company-wide communication platform. But as adoption spread across teams, the network revealed the broader opportunity. Slack eventually repositioned to match the reality of how people were already using it.

It wasn’t just a messaging tool anymore.
It had become the connective tissue between clusters.

Final Reflection

You don’t need formulas to use small-world thinking.
Just the awareness that products grow the same way ideas, memes, and conversations do: within clusters, and through the shortcuts that carry them somewhere new.

See your product as a network, and
see possibilities that funnels alone will never reveal.