Teams misidentify which type of network effect they have and build the wrong system. A product that needs a data network effect (more usage improves a model) builds for a direct network effect (referral programmes, social sharing). The resulting architecture serves the wrong mechanism and the growth strategy produces users who do not improve the model.
Cold-start solutions that degrade with scale are a second failure. A product that seeds its network with bot-generated content attracts real users who discover the content is synthetic and churn. A product that achieves local density in one city expands too quickly before network density is established elsewhere. The cold-start strategy that works at small scale creates a dependency that cannot be maintained at large scale.
Concept: Network effects make products more valuable as they grow. The mechanism — direct, indirect, data, or protocol — determines the architecture required to capture the effect.
Thread: T3 (Graphs) ← a network is a graph; the value of the graph scales with the square of its node count → architecture must handle superlinear growth in connections and data
Core Idea: Metcalfe’s Law creates winner-take-most dynamics. Network effects are architecturally expensive. The cold-start problem must be solved before network value exists, and single-player value is the most durable cold-start strategy.
Tradeoff: AT5 (Centralisation vs Distribution) — network effects require centralised data aggregation to improve the product; distribution of that data at scale requires sharding strategies that conflict with centralisation
Failure Mode: FM5 (Thundering Herd) — fanout events from high-degree nodes (celebrity accounts, viral content) generate traffic spikes that overwhelm systems designed for the average case
Signal: When users find the product more useful because other users are using it, the product has a network effect — and the architecture must be designed to grow with that dynamic
Maps to: Reference Book, Framework 9 (Laws)