User-led growth gets talked about like a miracle, mainly because nobody wants to admit they built a product that needs paid reach to be noticed.
In practice it is simpler, and slightly more annoying. Stuff spreads when people have a reason to pass it on, and a low-friction way to do it inside their normal day.
That’s diffusion, in the boring, old sense of the word, as something moves through a social system over time via communication channels.
The part most teams miss is that “a reason” is rarely a rational argument. A lot of sharing behaves like social signalling, emotional release, or the low-stakes helpfulness of “I thought you’d find this useful”.
Berger and Milkman’s work on virality is still a useful reminder that emotional arousal can push transmission, including awe, anger, and anxiety.
In product terms, that maps to a blunt question.
What does your product reliably make people feel, and does anyone else ever see it?
The viral checkbox trap
Most “user-led growth” plans are a bundle of features someone can point at.
Add invites, add sharing, add templates, add a referral programme, then wait for the compounding to arrive like a Deliveroo order.
What usually happens is a thin trickle of invites, a handful of shared artefacts, and a dashboard full of self-soothing ratios.
The organisational mirror is familiar from tooling surveys: Gartner reported marketers using about 42% of their martech stack’s capabilities, which is a different domain but the same shape of busy surfaces that do not change the underlying outcome.
It persists because it’s measurable, it is shippable, and it fits quarterly roadmaps. It also keeps Product and Marketing safely separate, because nobody has to change the core workflow to earn distribution.
The mechanics people keep rediscovering
In practice, user-led growth shows up when a product gives users something worth carrying outside the product.
Sometimes that is a feeling worth passing on. High-arousal emotion can make people more likely to share, but the emotion still needs somewhere to go.
Sometimes it is visibility. Word of mouth is shaped by the channel, the object being shared, and how easy it is to show someone else without breaking the workflow.
Sometimes it is status. Recommending tools can make someone look competent, generous, early, or useful in front of peers.
Sometimes it is a trigger. A recurring work cue gives the product another chance to be remembered after the first “this is cool” moment has faded.
You can see this pattern in companies that grew through usage spilling into other people’s field of view.
Slack told investors its growth was largely driven by word-of-mouth recommendations and organic adoption inside organisations.
Zoom’s S-1 defines a “host” as someone who initiates a meeting and invites participants, which is a neat way of saying the product’s core action involves pulling other people into the room.
Notion’s template gallery is the cleaner template example: the artefact itself can be duplicated, adapted, and shared.
None of this is mystical, and none of it’s guaranteed.
The awkward bit about B2B sharing
In B2B, sharing is rarely free.
It’s a reputational bet, because “you should use this” can become “you made us look foolish for picking this” with one bad implementation. It’s also political, because sharing a workflow can expose the mess people have been managing without admitting it, and mess has a way of making enemies.
Then there’s governance, where admins, procurement, and security controls can turn a “viral loop” into a permissioned request queue. That last one is a hidden constraint teams love to discover after they have already built the referral programme.
A concrete example: the KPI report nobody forwards
Imagine a B2B analytics tool used by a small marketing team inside a regulated firm.
The user logs in once a month, exports a PDF, renames it “Final_Final_v7.pdf”, then emails it to three stakeholders at 10:47pm the night before the exec meeting.
If your product makes that export painful, you lose satisfaction and distribution at the same time. The stakeholders never see the interface, never see the brand, and never associate the result with anything other than “the monthly numbers”.
Now change one thing.
Make the default output a clean, branded, stakeholder-friendly live link that opens without an account, with sensible access controls, and a one-click “Copy link for email” button placed exactly where the user already goes at month-end.
Your product is now travelling through an existing behaviour, rather than asking users to invent a new one.
You’ll also annoy some security people, so you’ll need proper permissioning and audit trails, because reality ruins everything.
Why this keeps happening
Most teams build for adoption and retention first, then try to bolt on sharing later. That is rational, because retention is a survival metric and virality feels like a bonus - especially in companies already tempted to believe that PLG keeps marketing lightweight.
The issue is that distribution features often require workflow changes that are expensive, cross-functional, and socially risky to ship.
Marketing wants “shareable”, Product wants “usable”, Security wants “controlled”, and Sales wants “anything that creates pipeline before quarter-end”.
So the easy compromise is a share button nobody uses, because it does not align with a real moment of sending, showing, or signalling.
There is also a measurement problem, because the strongest user-led signals are often messy, qualitative, and external to your analytics stack. That is where the old assumption that if we can measure it, it worked becomes especially misleading.
You can instrument invites forever and still miss the real action, which is screenshots in Slack groups, forwarded links in email chains, and “can you send me that template” in DMs you will never see.
Product decisions that change distribution
-
Design one core artefact that naturally leaves the product. That choice will shape the UX, permission model, and data structure more than a share button ever will.
-
Put visibility where the work is already happening. Enterprise buyers may still need tighter controls, but the default experience should not hide the useful thing before anyone else can see it.
-
Treat emotion as part of the product experience, especially where relief, confidence, or control are part of the job. In stressful work, “delight” can become one more thing to distrust.
-
Make recommending the product socially safe. That usually means clearer defaults, better onboarding, fewer embarrassing failure states, and enough reliability that the user does not feel exposed for sharing it.
-
Attach the product to a recurring trigger. Recurring usage creates more chances for distribution, but it also exposes every piece of friction you hoped nobody would notice.
A diagnostic that starts with the send moment
Start by mapping the moments a user already has to communicate something to someone else.
If you cannot point to at least one weekly or monthly “send” moment that your product makes easier, your “user-led growth” plan is going to be paid growth with a nicer story.
Watch the ratio of active accounts that generate an external touchpoint, like an invite, a forwarded link, a shared output, or a co-worker pulled into a workflow. If that number barely moves, the loop is probably decorative, even if retention looks fine.
Also watch where sharing dies, because the failure mode is usually boring, like an extra permission step, a confusing access error, or an output that looks unprofessional when forwarded.
User-led growth depends on the product helping people communicate, signal, or cope in a way other people can actually see. Otherwise the product sits there idle until you pay to make people notice it, which is a grim way to discover you built a closed system.