Principle
A community is members connecting with each other; an audience is a megaphone
Community is defined by members connecting with and helping each other, not by follower count.
Hoover draws a hard line: Twitter followers are an audience; a community exists when people in the ecosystem connect with and provide value to each other. Communities raise word-of-mouth and retention because people want to stay associated with them (his CrossFit example).
Audit your "community": if the value only flows from you outward, it''s an audience.
“there''s a big difference between an audience and a community and people like mix them up. Like your Twitter followers are probably not a community”Ryan Hoover
Principle
A people/network layer makes a product far more defensible than pure software
Adding a human-network layer to a product creates durability that pure software cannot match.
Hoover notes many built clones of Product Hunt and none worked because it has a brand, a flywheel, and a network that just keeps spinning. He loves multi-party systems (Product Hunt, AngelList) precisely because the people layer resists cloning.
If your moat is only features, assume it''s copyable; a live human network is what endures.
“if you have a people aspect to it, like a network aspect to it, it''s just far more defensible and sustainable I think from like competitors”Ryan Hoover
Principle
Human motivation is the invariant; bet products on what technology won''t change
Anchor product design to durable human motivations, not the current technology wave.
Having worked with Nir Eyal on Hooked, Hoover fixates on psychology because it is the thing that won''t change. The Product Hunt flywheel stays relevant into the AI future because it is ultimately about people gaining status and supporting each other.
When designing for a new tech wave, ask which unchanging human motivation you''re actually serving.
“technology and everything is gonna change dramatically, but like how people think and what they''re motivated by is not gonna change”Ryan Hoover
Principle
Nobody wakes up wanting to join a community — lead with utility
Start a community from a concrete utility people actually want, not from "community" itself.
Hoover compares it to podcasts — nobody wakes up wanting to listen to more podcasts or join another community. You need a hook and a reason to exist; on Product Hunt it was getting users, feedback, and status.
If you can''t name the utility a member gets on day one, you don''t have a community yet.
“people don''t wanna join a community. They''re not like, oh, I''m waking up in the morning. Like, I need to be part of a community”Ryan Hoover
Principle
Reuse behaviors and language users already understand — don''t invent a new verb
Borrow the interaction patterns and vocabulary users already know instead of inventing new ones.
Product Hunt deliberately looked at Reddit and adopted upvotes because people already understood them, and chose "makers" as a flat, inclusive label. Hoover warns people get "too cute" with novel language and UX that fails to communicate.
Before inventing new UX language, check what convention your users already fluently understand.
“what behaviors and actions and language do people already understand? Like up votes. People understand what that is like, especially people in tech. So we''re not gonna invent like a new verb, you know?”Ryan Hoover
Principle
Status is a real, exploitable hook — use it as the entry motivation into a community
Status-seeking is a legitimate design hook that draws members into a community before deeper engagement forms.
Hoover is blunt that makers come to Product Hunt to get users, get feedback, and earn status; status is the initial hook, and higher engagement (events, writing) follows once they''re pulled in. He notes high-status people deny caring, but everyone does.
Give new members a visible status win early; deeper community bonds form after the hook lands.
“you''re trying to earn some sort of status, you know, in the status game”Ryan Hoover
Principle
Know your circle of competence and route everything outside it to specialists
Be explicit about your narrow zone of real value and connect people to specialists for the rest.
Hoover raised from 380 mostly-operator LPs precisely so that a founder with a data-science or enterprise-sales question gets connected to an LP who actually knows, rather than getting Hoover''s guess. Self-awareness about competence is the operating model.
Map your genuine competence narrowly, then treat your network as the coverage for everything else.
“my background''s like product and community building and like marketing and like anything outside of that, I''m probably not the best person to ask”Ryan Hoover
Principle
At entry, valuation is the one variable you actually control
Since outcomes are unknowable early, discipline on entry price is the primary lever on returns.
Hoover argues that this early, you don''t really know who''s going to be successful, so entry price is the controllable variable. He cites a friend''s CPG investment at $1M post as a case where a low entry makes even a modest exit a strong return.
When the outcome is a coin flip, entry valuation is where your edge actually lives.
“the only thing you can really control is where you come in at”Ryan Hoover
Principle
Compete against bad, misaligned competitors
Pick categories where the incumbents are structurally misaligned and complacent.
Hoover''s CPG example: the stereotypical incumbent is a big corporation owned by passive index funds and run by managers with little stock who care about hitting the next earnings target for their bonus — versus a founder who owns 60% and wants a $10B company. Misaligned incentives make incumbents beatable.
Score a market by how misaligned the incumbents'' incentives are with building long-term value.
“you wanna compete against bad competitors”Ryan Hoover
Principle
Optimize for what''s sustainable and what you''re suited for, not fund size or status
Choose the game that fits you and is sustainable over the one that maximizes size or status.
Hoover could raise a $200M fund but doesn''t want to, because it would force him to lead deals, use sharp elbows, and travel to schmooze — a game he''s not suited for. He deliberately stays small to play the collaborative game he enjoys and can sustain.
Before scaling into a bigger, higher-status game, check whether it''s one you''re actually suited to sustain.
“I want to do what I want to do. I know it sounds like super selfish, but like also I think it''s sustainable and I also wanna do what I think I''m better suited for”Ryan Hoover
Principle
Design social products as flywheels where each participant''s engagement recruits the next
Build products where more engagement mechanically drives more growth or re-engagement back into the product.
Hoover''s core lens on Product Hunt: makers launch, share with their audience, some visitors sign up, some of those are makers who launch too. Each turn recruits the next turn. He treats every social product as a flywheel and then asks where he can speed the spin or lift conversion.
Ask of any social product: does each engagement recruit or re-engage the next participant?
“how do you build these flywheels where the more people engage, the more it either grows or drives more engagement back to the site”Ryan Hoover
Principle
Only raise venture with a secret or traction — wait for one to be true
Don''t raise venture capital unless you have a secret or traction; wait until one exists.
Hoover, having built and raised before, says he sees many founders chasing spaces with no secret and no traction who "might do fine" but shouldn''t take the venture path. He''d wait for one of the two to be true before raising.
Before raising, ask honestly: do I have a real secret, or real traction? If neither, wait.
“I would only do it if I had like a, a secret, like a secret or traction. And I would wait for one of those to be true first”Ryan Hoover
Principle
Build products, not just meetings — leverage that helps while you sleep
Adding value through software scales beyond your time; meetings do not.
Hoover increasingly invests his time in products (Rolodex, and a new tool) rather than meetings because software helps the portfolio in ways that go well beyond his own hours — value delivered "while you sleep."
Whenever you find yourself giving the same help repeatedly, ask whether software could deliver it while you sleep.
“you can make a piece of software and it can exist while you sleep and help people while you sleep”Ryan Hoover