How Did Sam Ovens Build Skool's Network Effect?

TL;DR

Skool pursued growth and engagement by limiting customization, reducing complexity, and concentrating communities on a shared network. Sam Ovens tested the product first with one community from his own business, improved it until members found it useful, and expanded only after other people began asking to use it.

Transcript

So, where I want to start, you remember when you visited me in Scottsdale >> and we were hanging out and I remember we were having dinner at True Food and you told me, so this was back when school was kind of like in its infancy, at least compared to it is now. And you told me you were making a strategic bet because a lot of the other kind of compe... Read More

Key Insights

• Skool's central product bet is that creators value growth and engagement more than extensive customization. Ovens reduced white labeling and feature complexity because he believed a simpler, shared environment would produce the outcomes customers actually wanted, even when their stated requests emphasized appearance and control.
• Shared networks are convenient because users need only one profile, search function, login, and domain. Ovens observed that people have multiple interests and that those interests change, so placing communities together can serve users better than requiring a separate identity and destination for every forum.
• Network distribution is valuable because creators must find audiences as well as operate communities. Ovens connected the success of Facebook groups over independent forums to both user convenience and built-in distribution, then made those advantages part of Skool's strategic direction.
• Feature additions can make software more complicated and sometimes worse. Ovens warns that removing a feature becomes difficult after customers begin using it, which can trap a company into maintaining unnecessary complexity. Technical ability alone is therefore not sufficient justification for shipping something.
• Product prioritization is more useful than treating ideas as simple yes-or-no decisions. Skool considers the most important work that can be completed now, recognizing that finishing those priorities may change what should come next and make distant detailed plans obsolete.
• Skool's detailed product roadmap extends only 30 days into the future. Beyond that window, the company keeps a less specific collection of ideas whose priorities can move as circumstances change, allowing the team to remain deliberate without pretending that distant plans are certain.
• The cold start problem arises because a network's usefulness depends on other participants already being present. Ovens illustrates this with the first telephone, which offers little value without another person to call, making the earliest stage of network creation especially difficult.
• Skool addressed its cold start by beginning with one community from Ovens's own business. He used the product internally, worked to make that contained network functional and useful, and opened it to others only after people began requesting access and offering questions that guided improvements.

Questions & Answers

Q: Why did Skool prioritize engagement over customization?

Skool prioritized engagement because Ovens believed customers ultimately wanted growth, active participation, more members, revenue, and useful experiences for their communities. Extensive customization, white labeling, and numerous features could make the product confusing. By limiting those options, Skool aimed to keep attention on the practical outcomes users sought rather than on surface-level controls they might request.

Q: How do shared networks make online communities easier to use?

Shared networks reduce friction by giving users one profile, one search function, one login, and one domain to remember. They also fit the reality that people have several interests and that those interests change over time. Instead of navigating separate forums and identities, users can participate in multiple communities within a single, familiar environment.

Q: Why did Facebook groups replace many independent forums?

Ovens attributes the shift from independent forums to Facebook groups to convenience and distribution. Facebook gave users a shared profile, search function, login, and domain, while allowing several interests to coexist in one place. It also gave community creators access to distribution, which an independently operated forum would otherwise need to build for itself.

Q: How does Skool decide which product features to build?

Skool evaluates possible work through prioritization rather than labeling every idea as permanently accepted or rejected. Because there are effectively unlimited things the team could build but only a few it can complete now, it selects the most important current tasks. Once those tasks are finished, conditions may change enough to reorder the remaining ideas.

Q: Why can adding too many software features be harmful?

Every added feature can increase complexity and may make the product worse rather than better. Ovens also notes that features become difficult to remove once customers depend on them, leaving a company trapped by earlier decisions. Skool therefore asks whether a proposed addition advances growth, engagement, reliability, member participation, or value instead of shipping it merely because development is possible.

Q: How far ahead does Skool plan its product roadmap?

Skool keeps its detailed roadmap limited to 30 days because priorities and circumstances can change substantially within that period. The company maintains a broader collection of less specific ideas for later work, but those ideas continuously move in priority. This approach focuses engineering effort on immediate needs without treating distant assumptions as fixed commitments.

Q: What is the cold start problem for a network product?

The cold start problem is the difficulty of creating value before enough participants have joined a network. A network becomes more useful as its membership grows, yet early users may see little reason to participate when few others are present. Ovens compares the situation to owning the first telephone, which is useless without another person to call.

Q: How did Skool overcome its initial cold start problem?

Skool began with a single community from Ovens's own business. At first, users could not create additional groups, so the team concentrated on making that one network functional, useful, and pleasant for its members. After sustained internal use, other people asked to use the platform, and their questions helped the team improve it while expanding access.

Summary & Key Takeaways

• Sam Ovens based Skool's product strategy on lessons from the transition between independent forums and Facebook groups. A shared profile, search function, login, and domain made participation simpler, while the larger network supplied distribution. He concluded that creators need growth and users benefit from convenient access to multiple interests.

• Skool deliberately avoided competing with established platforms through extensive customization and white-label functionality. Ovens considered most of those features unnecessary and potentially confusing. He instead reduced the product to the outcomes customers actually sought: attracting more members, generating engagement, making money, and helping community members participate and receive value.

• The network began with one community from Ovens's own business rather than a broad public launch. His team used that contained environment to make the experience functional and useful. Other people eventually asked for access, and their questions informed improvements. Product planning remained flexible, with a detailed roadmap extending only 30 days.