Peter Sellis says the best product teams should be designed like terrorist organizations

Peter Sellis thinks the best startup teams should borrow from terrorist organizations. Not the violence, he says, but the combination of near-religious mission and brutally clear decision rights that lets a group keep moving when central command is absent.

This is the kind of metaphor HR would put in a lead-lined box and bury under the benefits portal. It is also, annoyingly, a real idea. Sellis, the first PM at Snapchat and later head of product at Discord, went on Lenny’s Podcast with no book, no launch, no comms chaperone, and apparently no instinct for making life easy for future employers. What came out was a management theory with a siren on it.

collaboration comes with incredible coordination costs. And coordination costs essentially assure that you’re moving as slow as the slowest node um in the system.

That is the sane core of the whole provocation. Sellis is not making the usual LinkedIn argument for trust, autonomy, and alignment, meaning a carousel post with pastel arrows. He is saying that high-growth companies often drown themselves in well-intentioned collaboration, then call the slowdown maturity. His answer is ideology plus authority. Everyone knows why they are doing the thing. Everyone knows who gets to decide the thing.

A good like terrorist organization [laughter] essentially has two things. One is it has this like uh ideological culture that everyone understands why they are doing what they’re doing. Uh and then it has a very very clear organizational structure of who can be trusted with which decision.

The cult part is not accidental

Lenny Rachitsky offers the softer Silicon Valley version, build a cult. Sellis basically shrugs and says, yes, but less founder-worship, more doctrine. That distinction matters. In his telling, the founder or product leader is not supposed to be a charismatic camp counselor with a Patagonia vest. The leader is supposed to turn strategy into repeatable language so teams can make decisions without holding a séance every time a button moves.

It is not Yeah, you can’t spell culture without cult.

The eyebrow stays raised. The metaphor is grotesque on purpose, and maybe too pleased with itself. But Sellis’s actual test is useful: if your team needs eight people to bless a decision, you don’t have collaboration, you have a hostage situation with calendar invites. The catch is that this only works when the mission is real. If the ideology is vague, the model becomes boss cosplay. If the decision rights are political, it becomes a faster way to make bad calls.

The contradiction is that Sellis is also a product manager who thinks many product managers are bad. He says the profession is structurally set up for mediocrity because the best PMs exit into founding companies or executive jobs, while weaker ones cling to a lucrative, loosely defined role. That sounds like an anti-PM rant until he describes the job he actually respects: taking a founder’s vision and making it executable by people who are not sitting inside the founder’s brain.

Snapchat is the case study hiding inside the grenade

Sellis’s best example is not the terrorist line. It is his description of core product value at Snap and Discord. At Snap, the phrase was essentially that Snapchat is the fastest way to share a moment with the people you care about. At Discord, it was about being the best way to talk and hang out with friends before, during, and after playing games. That is product management as catechism, but with metrics stapled to it.

we actually had an onboarding presentation which I delivered to every single new hire for seven years straight every week or every other week later uh that was about this because like that was part of the cult right like this is how we deliver core product value.

That is the less memeable, more important version of the claim. Sellis is arguing that great teams do not become fast by asking people to be faster. They become fast because the company has already answered the boring questions in advance: what matters, what does not, who decides, and what metric proves the decision worked.

If he’s right, your next team fix is not another sync, another brainstorm, or another doc asking for feedback by Friday. The useful questions are harsher. Does everyone know the religion? And who is trusted to decide before Slack turns the whole company into oatmeal?