<- all tokdocs

Peter Sellis on DRIs, Single-Threaded Leaders and Team Design

By , founder of Mavric and Apso

View on TikTok ->

Peter Sellis, a former product leader at Snap and Discord, says strong teams need two things: an ideological culture everyone understands, and a clear structure for who owns each decision. In a TikTok clip from @lennyrachitsky, he groups three terms for that ownership, "directly responsible individuals," "single-threaded," and "throat to choke," and waves them off as "MBA blah, blah, blah." The three terms come from Apple, Amazon and IT vendor sales, and the main academic study of how terrorist groups operate found they run on paperwork.

Where the clip comes from

The clip is cut from the Lenny's Newsletter episode "90 minutes of unfiltered product advice from Snap and Discord's product chief | Peter Sellis," published September 20, 2026, one day before the TikTok. The episode's topic list includes "Why Peter designs teams like . . . terrorist organizations." The framing question in the clip, "You like to design teams like a terrorist organization," is asked by the interviewer.

Lenny's episode description says Sellis was "the inaugural product manager at Snapchat," spent seven years there, and then served as Head of Product at Discord. Crunchbase lists his Discord title as Senior Vice President, Product and his Snap role as Vice President of Product on the revenue product team. The episode was sponsored by WorkOS and Mercury, and the WorkOS badge appears throughout the clip. WorkOS sells SSO, SCIM, RBAC and audit logs as APIs for B2B SaaS apps.

What Sellis says about designing teams

He describes two ingredients. The first is "this ideological culture" that "everyone understands," where the strategy is "almost like a religion to the entire team." The second is a "very, very clear organizational structure" of who owns what:

who are the directly responsible individuals, who's single-threaded on something, who's the throat to choke, use whatever MBA blah, blah, blah-ism you want.

The payoff, in his words, is that the combination works "such that you don't need to over-collaborate and you can be assured of achieving the results that you wanted as if you had collaborated."

What is a directly responsible individual (DRI)?

The term originated at Apple. GitLab adopted it and defines a DRI as someone "ultimately accountable for the success or failure of a specific project, initiative, or activity." Simon Willison, writing in July 2026, points to the GitLab definition as the clearest one available and notes the Apple origin. Neither Willison nor any Apple source located gives an Apple-published definition.

What is a single-threaded leader?

The term comes from Amazon. AWS enterprise strategist Tom Godden, writing on March 18, 2021, defines a single-threaded leader as "a leader who is 100% dedicated and accountable to a specific product, such as your mobile application, customer account, or the search capability in your e-commerce store." The Working Backwards site reduces the idea to three questions, starting with "Who is the most senior leader working full time on this initiative and no other?"

Where does "one throat to choke" come from?

This phrase comes from IT purchasing. It describes buying an entire technology stack from one vendor so the buyer has a single party to hold responsible when something breaks. The phrase has drawn pushback in that industry. Forrester published "One Hand To Shake Beats One Throat To Choke," and Cutter Consortium published "Choking on 'One Throat to Choke'" on February 6, 2008.

So the three terms Sellis treats as interchangeable describe different things. A DRI owns a decision or project. A single-threaded leader works full time on one initiative and nothing else. "Throat to choke" names a vendor to blame.

Do terrorist organizations run without bureaucracy?

The metaphor in the clip suggests low-overhead groups held together by shared belief. Research on real covert groups found heavy bureaucracy.

Jacob N. Shapiro, a Princeton professor of politics and international affairs and codirector of the Empirical Studies of Conflict Project, published "The Terrorist's Dilemma: Managing Violent Covert Organizations" with Princeton University Press in 2013. He analyzed more than a hundred terrorist autobiographies and a cache of internal documents from al-Qa'ida in Iraq. He found that bureaucracy is common in these groups, that al-Qa'ida in Iraq "used so much paperwork to handle its people," and that some groups "resemble miniature firms, complete with line charts and written disciplinary codes."

His explanation is a principal-agent problem. Leaders want control and operatives want secrecy. Leaders who cannot watch their operatives turn to written records and reporting, so in his account shared ideology comes with more paperwork.

Why coordination costs grow with team size

The cost Sellis wants to avoid has a well-known formula. In "The Mythical Man-Month" (1975), Fred Brooks gives the number of communication paths on a team of n people as n(n − 1)/2. A team of 50 has 1,225 channels. Brooks's law states that "adding manpower to a late software project makes it later."

Brooks supports the premise that coordination gets expensive as headcount grows. He does not support the stronger claim that clear ownership lets a team reach the same result collaboration would have reached. No source checked tests that claim.

Bottom line

DRI, single-threaded leader and "throat to choke" come from Apple, Amazon and IT vendor sales, and they mean different things. Clear ownership does cut coordination paths, which Brooks quantified in 1975. The terrorist-cell comparison does not hold up against Shapiro's research, which found these groups depend on paperwork and written rules.

Sources

Published September 21, 2026. Based on a TikTok by @lennyrachitsky. Full video notes (markdown)