Distribution Requires Permission or Self-Propagation

Someone with a genuinely valuable service spends years trying to find the right person to let them in, a practitioner, an institution, an influential friend, someone with an audience and the standing to say this is worth your attention. Almost every attempt ends the same way. The value is real, the reception is polite, and nothing moves, because the request being made of the gatekeeper is larger than it looks. Vouching for something unfamiliar costs the gatekeeper their own reputation, attention, and authority, and most people, quite rationally, decline to spend that on someone else's behalf.

The instinct at that point is to look for a better pitch, a warmer introduction, a more persuasive case for why this particular gatekeeper should take the risk. That instinct treats the problem as a persuasion problem. It usually isn't. It's an architecture problem, and the architecture in question is how the offering spreads at all. There are exactly two ways a thing can move from one person to the next, and confusing them is what keeps otherwise valuable work stuck at zero.

An offering that requires a gatekeeper's endorsement runs on permissioned distribution. An offering that produces something a user voluntarily hands to the next user, because it already serves that user's own interest, runs on self-propagation. These are different systems with different failure modes, and no amount of improving the pitch converts one into the other.

Two different growth mechanisms

Permissioned distribution moves through people with existing trust and standing: a practitioner referring clients, an institution granting access, an influential figure vouching publicly. Diffusion research going back decades describes exactly this pathway, new ideas and products spreading primarily through opinion leaders whose endorsement transfers legitimacy to something unfamiliar, with adoption rippling outward from that initial, trusted source [1]. This is a real and workable mechanism. It is also structurally slow and bottlenecked, because every new audience requires a new gatekeeper willing to spend their own credibility, and that willingness cannot be manufactured by making the underlying offering better.

Self-propagating distribution works on a completely different mechanism: the product itself creates an artifact that a user is independently motivated to share, not to help the creator, but because sharing serves the user's own goal. Research on product-driven virality has identified specific structural features responsible for this, particularly whether the act of using a product generates something that naturally involves or reaches another person as a byproduct of ordinary use, rather than requiring a separate, altruistic act of promotion [2]. A scheduling link exposes the scheduling tool because sending it is simply how you schedule something. Nobody has to believe in the product first.

Why depth doesn't create its own entrance

This distinction explains why depth, sophistication, and genuine value so often fail to translate into distribution on their own. A complex, valuable offering with no self-propagating mechanism is entirely dependent on the permissioned pathway, and the permissioned pathway has a hard ceiling: it can only grow as fast as gatekeepers are willing to spend their reputation, one at a time. Making the offering deeper does nothing to raise that ceiling, because the ceiling was never about depth. It was about the structural cost of vouching, a cost every gatekeeper bears personally and none of them can be argued out of by a better description of the work.

This is also why so much effort aimed at "finding the right partnership" quietly fails without ever producing a clear rejection. The gatekeeper is not saying no to the value. They are declining to personally underwrite a risk that a better pitch cannot reduce, because the risk was never about whether the work is good.

What a self-propagating artifact actually requires

The alternative is not simply making the offering shareable in a generic sense. It requires identifying the smallest unit of the work that a single person can use immediately, without anyone's approval, that solves a problem they already know they have, and that produces an output naturally worth showing or sending to someone else. Research on engineered virality identifies this as a design property, not an accident: products that embed a reason for the artifact to reach a second person as part of normal use, rather than as an add-on request to share, show measurably different growth dynamics than products that rely on users to promote them out of goodwill [2, 3]. The mechanism has to be built into the smallest usable unit of the product, not added to the outside of the finished, complex whole.

What this reframes

None of this means permissioned distribution is worthless, or that seeking a credible partner or gatekeeper is a wasted strategy. It means the two pathways should not be pursued as if they were the same effort wearing different clothes. Continuing to refine a pitch aimed at gatekeepers, when what's actually missing is a self-propagating unit of the product, spends effort on the wrong lever entirely. The real design question is not "who can I convince to let me in," but "what is the smallest version of this that one person can use alone, immediately, for their own reasons, that naturally puts the result in front of someone else." That question has a design answer. The gatekeeper question mostly doesn't.

The point

There are two structurally different ways an offering reaches new people: through a gatekeeper who spends their own reputation to vouch for it, and through an artifact the product itself generates that a user is independently motivated to pass along. Diffusion research shows the first pathway is real but bottlenecked by the personal cost every gatekeeper bears in endorsing something unfamiliar, a cost that better pitches or deeper work cannot reduce, since it was never actually about quality. Research on product-driven virality shows the second pathway depends on a specific design property: whether ordinary use of the product naturally produces something worth sharing, independent of any goodwill or belief in the creator.

Mistaking one pathway for the other is what keeps genuinely valuable work stuck, because effort spent improving the case made to gatekeepers does nothing to build the self-propagating mechanism that was actually missing, and effort spent hoping a good product will spread on its own ignores that spreading is a specific, engineerable property, not a natural consequence of depth. The real question is not who will let the work in, but what the smallest independently useful unit of it looks like, and whether using it already puts a reason to share in front of the next person.

Sources

1. Rogers, E. M. (1962). Diffusion of Innovations. Free Press. On adoption spreading through opinion leaders whose personal endorsement transfers legitimacy to unfamiliar innovations, and the structural bottleneck this creates for pathways dependent on gatekeeper trust.
2. Aral, S., & Walker, D. (2011). Creating social contagion through viral product design: A randomized trial of peer influence in networks. Management Science, 57(9), 1623-1639. On specific, measurable product design features that drive viral spread independent of product quality or user goodwill.
3. Katz, E., & Lazarsfeld, P. F. (1955). Personal Influence: The Part Played by People in the Flow of Mass Communications. Free Press. On the two-step flow of communication, distinguishing gatekeeper-mediated adoption from direct, peer-to-peer propagation.