5 guests 5 episodes 3,344 words

Twenty People Built the iPhone: The Case For and Against Scaling Design

Should design stay a small, tight elite group with a clear vision, or scale into a large org with structure, leveling, and specialization?

Twenty people are on the patent for the original Macintosh. Twenty-four are on the patent for the iPhone. Two of the most influential consumer products in history were conceived by teams small enough to fit in a conference room. Meanwhile the design orgs at Stripe, Airbnb, and Meta number in the hundreds, structured into specialties — product, brand, research, design ops, content — with leveling ladders and review cadences that would have been alien to the Project Purple crew. Both produce work we admire.

The fight over how big a design team should be is really a fight over what design actually is: a small act of invention that can't be parallelized, or a group operational discipline that holds a quality bar across an ever-expanding surface area. Five voices from Lenny's podcast have argued this out with unusual specificity.

When you are building a product company, should design stay a small, tight elite group that holds a clear vision and ships through tight engineering partnership — or should it scale into a large, structured org with specializations, review processes, and dedicated infrastructure for maintaining quality across a growing surface area?

The 3 Positions

1 / 3

Keep It Tiny Until You Know What You're Building

Bob Baxley · Gaurav Misra · Karri Saarinen

Bob Baxley — Designer and executive with 35+ years of in-the-room experience. Led design on the Apple online store and App Store, ran design at Pinterest, Yahoo, and ThoughtSpot. Now an independent advisor with no org to staff up, which frees him to make the unfashionable small-team argument.

Baxley's argument is rooted in product archaeology. The iconic things Apple built were made by tiny named teams that knew each other's taste intimately — not nostalgia, he insists, but evidence of a law of creative work. Invention doesn't parallelize. You cannot figure out something new in committee, and every additional person in the room lowers the group's ability to converge on a shared picture of what they are building.

"I just always have to point out to people that there are 20 people that worked on the original Mac. I mean it's 20 of them, that's it, 20. Susan Kare was one of them, Andy Hertzfeld, you go through the list, 20 of them are on the patent. There's 24 that are on the iPhone patent. Now there's other people involved, but generally there's 24 people on the iPhone patent. And that was the team. That was Project Purple that was doing that stuff. These are not massive massive groups doing these things."
Bob Baxley
▶ 00:20:54

The generalization isn't just Apple. Baxley reaches for Pixar, where story and scripting teams stay tiny even as production scales massively. Invention on one side, execution on the other; the sizes should be wildly different, and teams get confused when they blur.

"So there's something, four is too few for what we're trying to achieve at scale. But even if you look at Pixar, any good movie on the scripting and story side, it's usually a fairly small team. Even when you move into character development, stuff like that, it's fairly small and then it really scales when you move into production. It's just hard to figure out something new to do together when there's too many people involved."
Bob Baxley
▶ 00:21:27

Crucially, Baxley is not saying design orgs should stay small forever. He draws a sharp before/after line: while you are still figuring out what the thing is, keep it tiny. Once the shared mental model is loaded into everyone's heads, then bring in lots of people to execute.

"You have to bring a lot of people in once you figure out what you're doing. And so to your point, once you realize you're building Disneyland and you've got the whole thing set and people know what it's about, then they can come in and understand, oh, I'm playing my piece over here. I'm supposed to design the line experience for the new ride sitting in Tomorrowland, but I know where that fits into this larger thing."
Bob Baxley
▶ 00:22:13

The mistake he sees repeatedly is companies scaling design headcount before they have the vision. They end up with confused output, because design, unlike sales or engineering, rarely has a budget or an army. Inflating the org adds coordination cost without proportional conviction.

Gaurav Misra — CEO and co-founder of Captions, previously design engineering lead at Snap during its hyper-growth consumer era. Captions is a consumer AI video product with 10M+ users and $100M+ raised. He has built product in both the huge-team and tiny-team regimes.

Misra arrives at the small-team conclusion from a different direction: operating tempo. Captions' engineering goal is that every engineer ships a marketable product every week. That cadence is physically incompatible with a scaled design org — review layers, crits, research phases, and handoffs make weekly shipping impossible by construction.

"Our engineering goal is every engineer should ship a marketable product every week."
Gaurav Misra
▶ 00:00:21

The usual response is that quality must suffer. Misra's counterintuitive move: quality doesn't suffer — scope does. Under time pressure, most teams cut the wrong thing, quietly lowering the polish bar because scope is politically locked in. Good teams do the opposite.

"The way to cut down on time, and I think this is a mistake people make a lot of the time, is when time is being pressured downward, a lot of times engineers, PMs, designers, they will cut on quality rather than cutting on scope. And actually you can cut on scope."
Gaurav Misra
▶ 00:16:20

This becomes a structural critique of scaled orgs: scope can't be meaningfully cut inside a large organization because it has already been negotiated across too many stakeholders. A small team has the taste authority and political freedom to strip an idea down to its core. A large team has process where that taste should live. Misra also points to a tooling asymmetry:

"These are the types of things that us as a startup can do that bigger companies can't just, you know, they can't just pull in Devin. They have to get 30 lawyers in the room first before that happens."
Gaurav Misra
▶ 00:25:02

Karri Saarinen — Founding designer at Coinbase, principal designer at Airbnb, now co-founder and CEO of Linear. Linear is the B2B SaaS most commonly cited as the benchmark for craft in its category, built deliberately without traditional design-org scaling.

Saarinen has built Linear as a living rejection of scaled-org design practice. Linear has exactly one product manager — Nan Yu, the head of product — for the entire company. Project teams assemble around a piece of work, ship, and disperse. There is no company-wide review of everything shipped.

"Generally, in the company there's not necessarily a lot of reviews or something that we always review everything that gets shipped this way because we do want people to feel that they can put something in the app and then we can try it out."
Karri Saarinen
▶ 00:11:51

His causal story: craft emerges when the people building the feature feel it all day — where the button goes, how the transition flows — and have authority to fix things without review. Install a PM layer and a review layer and you separate decision-makers from the people with their hands on the detail. Craft dies in that gap.

"When you build a team and you start creating these very specific roles for everything I think that often the PM can be the ones figuring things out and making decisions and guiding the team, but they're not the ones building the feature. They're not there looking at it the whole day like where does this button go or how does it work? I think a lot of that, this craft for us happens when we give the project team this ownership and the project team is just engineering and design."
Karri Saarinen
▶ 00:14:32

The evidence Saarinen points to is unprompted craft work: an engineer named Andreas building dynamic safe zones into right-click submenus so users can move diagonally without pixel-hovering. No PM would spec that. It exists because an engineer who cared had authority to spend time on it. But the model rests on a culture premise most scaled orgs cannot satisfy:

"I think Facebook and Amazon have a very different culture on quality or craft or shipping... You need to align on it. It's like you cannot run a company with multiple different kinds of cultures."
Karri Saarinen
▶ 00:14:00

This is a subtle argument that scaled orgs with heterogeneous hires — ex-Facebook, ex-Amazon, ex-Airbnb people with different quality bars — are structurally prevented from producing Linear-grade work, because process cannot harmonize taste formed in different homes.

When This Applies

when you are genuinely inventing a new product category and the vision is still forming. Mac, iPhone, Project Purple-stage startups.

Quality at Scale Is a Group Effort, Not an Individual One

Katie Dill

Katie Dill — Head of Design at Stripe; previously built and led design teams at Airbnb and Lyft. Scaled each org at least 10x. Two of those three — Airbnb and Stripe — are industry benchmarks for design quality at real scale.

Dill starts from a hard constraint small-team advocates often wave away: Stripe's product surface is enormous — product design, brand, marketing creative, web, research, content, design ops — and Stripe powers checkout for Amazon, Hertz, Shopify, Spotify. You cannot hold quality across that surface with 20 people. Her first requirement is that quality at scale is a group effort. The fantasy that you hire one extraordinary taste-maker who lifts everything around them is, in her experience, a direct route to sinking.

"Number one is that quality is definitely a group effort. You're sunk if you think that you can just hire some incredibly talented person and they'll do it, that'll be fine. The rest of us will do what we're doing and they'll do it, or that it's just one organization that's going to look out for quality or QA is going to solve it all for you. It really does need to be an organizational and a group effort."
Katie Dill
▶ 00:29:28

Her second requirement is explicit vision infrastructure — the GC-and-architect role — because even great designers with perfect taste will fragment under the subjectivity of their own work. A direct rebuttal to Saarinen's "just hire people who share the taste" model.

"If you hire all the best people in the world and you just set them out to go and do their thing, what are the chances that they're all going to end up with something that actually aligns pretty well? Even if they all have incredible taste and they're very good at what they do, there is subjectivity to every decision in some part. So, that they might end up with some things that are really great but don't fit together as a really nice whole."
Katie Dill
▶ 00:30:20

Her third requirement is what she calls gravity. Quality doesn't hold itself in place — it degrades unless the organization actively fights the drift:

"The gravitational pull is to mediocrity. It is very easy to fall into a path of a baseline, where what is required to go to that next level where something feels truly great is certainly a lot of effort, and it's a concerted effort."
Katie Dill
▶ 00:26:45

If quality is a gravity problem, then the small-team model is a bet that individual taste can outrun gravity across a product's surface area. Dill is saying that bet loses past a certain scale — and the solution is not to give up on quality, but to build operational infrastructure that holds the bar: shared vision documents, architectural plans, cross-functional reporting lines, review processes that function like editors rather than gatekeepers. At Stripe, the website team has engineering and design reporting into the same place with product marketing embedded — a deliberate choice only a scaled org can make. Structure, done right, enables craft at scale rather than destroying it.

When This Applies

when iteration speed is the moat, the product decomposes into weekly increments, and taste authority is concentrated in a founder. Captions, consumer AI apps, early-stage startups racing incumbents.

Scale Is How You Manufacture the Next Generation of Designers

Julie Zhuo

Julie Zhuo — Former VP of Design at Meta, where she spent 13 years running design for the Facebook app as it scaled from 8 million users to a global platform. Author of The Making of a Manager. Now running Sundial as a founder.

Zhuo's position is less about "big vs. small" and more about what scaled orgs actually produce when done right: opportunity. At hypergrowth companies, new problems arrive faster than experienced people can fill them, so ICs get thrown into roles they haven't been trained for and grow by doing. A 10-person elite team concentrates that opportunity in a few hands and caps how many senior designers the world can produce.

"I was lucky. I was in the right place at the right time. I was at a company that was scaling, and when you're at a company that grows, there's always a lot more opportunity to then be able to try something new, right, to raise your hand, to volunteer for things to be just thrown into because somebody has to do it because it's a growing company."
Julie Zhuo
▶ 00:09:47

She pairs that with an unusual claim: the discomfort of scaling is the mechanism of learning, not a bug. Imposter syndrome, uncertainty, being thrown in because somebody has to — those correlate with the fastest periods of growth in a career.

"Being in an uncomfortable situation, being in a position where you feel like, Hey, do I really know how to do this? I've not prepared for it is kind of coin sides with the fastest and most intense periods of growth in one's career."
Julie Zhuo
▶ 00:09:30

And her advice to designers who want that growth is explicit — not a tiny craft cult, but a growing org where scale creates opportunity:

"If you want those types of opportunities, sometimes you just have to be at a smaller place and you have to be at a place that is going through that rate of growth."
Julie Zhuo
▶ 00:10:10

Zhuo's position is the middle path. She doesn't believe more designers produce better products. But she does believe scaled orgs are the only venues that manufacture the next generation of design leaders. Killing that pipeline in the name of craft is, in her view, a long-term bet against the craft community itself.

When This Applies

when craft in the details is the brand, the product is a single coherent category, and you can screen every hire for shared taste. Linear and craft-forward B2B SaaS benchmarks.

Evidence from the Archive

Apple

The original Mac had 20 people on the patent. The iPhone had 24. These were not massive groups — they were tiny elite teams that knew each other's taste

Bob Baxley uses Apple product archaeology to argue that genuinely new work comes from bands, not orchestras; you scale only after you know what you're building

Bob Baxley · Independent designer; ex-Apple online store and App Store, Pinterest, Yahoo, ThoughtSpot ▶ 00:20:54

Captions

Every engineer at Captions ships a marketable feature every week — a tempo physically incompatible with a large, structured design org

Gaurav Misra's operating model forces smallness: under time pressure good teams cut scope while bad teams cut quality, and scaled orgs default to cutting quality

Gaurav Misra · CEO and co-founder of Captions; previously Snap design engineering ▶ 00:16:20

Linear

At Linear, a Linear engineer named Andreas built dynamic safe-zone behavior into right-click submenus without being asked — the unprompted craft decision a PM would never spec

Karri Saarinen collapses PM/design/engineering hierarchy; project teams assemble around work, ship, and disperse — no durable cross-functional pods

Karri Saarinen · Co-founder and CEO of Linear ▶ 00:14:32

Stripe

Stripe's design org scaled 10x under Katie Dill across product design, brand, marketing creative, research, and content — because at real scale 'the gravitational pull is to mediocrity'

Dill's hard constraint: Stripe powers checkout for Amazon, Hertz, Shopify, Spotify — you cannot hold quality across that surface with 20 people

Katie Dill · Head of Design at Stripe; previously Lyft and Airbnb ▶ 00:29:28

Facebook

Julie Zhuo rose from IC designer to VP of Design entirely inside Facebook as it scaled from 8 million users to global platform — scale was the training ground

Her argument: scaled, hypergrowth design orgs are the only environments that reliably produce new senior designers, because ICs get thrown into roles they haven't been trained for

Julie Zhuo · Founder of Sundial; previously VP of Design at Meta/Facebook ▶ 00:09:47

The Synthesis

Baxley, Misra, Saarinen, and Dill are not actually disagreeing about whether design can be done well at scale. They are disagreeing about what the unit of building should be.

The Invention Unit

What's your smallest irreducible building unit?

Gravity Toward Mediocrity

What's actively fighting quality drift?

Scope, Not Quality

When time pressure hits, what do you actually cut?

Pods Inside Scale

Can you get invention dynamics and coverage dynamics at once?

The Talent Pipeline Argument

Where do the next design leaders come from?

Baxley, Misra, and Saarinen aren't arguing that companies should be tiny — they're arguing that the invention-and-shipping unit should be. Twenty people on the iPhone patent; one PM at Linear; weekly shipping at Captions. Every small-team advocate is making a claim about the unit of building, not the size of the company.

Katie Dill's gravity argument: the gravitational pull is to mediocrity, and holding quality across a large surface requires concerted effort. At Stripe's scale — powering checkout for Amazon, Hertz, Shopify — the fantasy that one taste-maker lifts everything around them is a direct route to sinking. Quality at scale is a group effort or it isn't.

Misra's counterintuitive rule: under pressure, teams cut quality when they should cut scope. But scope can't be meaningfully cut inside a large org because it's been negotiated across too many stakeholders. Small teams have the taste authority to strip an idea to its core; large teams have process where that authority should live.

Coda's one-PM / one-designer / two-to-four-engineer pods are the operational template: Baxley's small invention unit living inside Dill's structured company. Scale headcount at the org level, preserve smallness at the unit of building. Most 'we scaled design' stories that work are actually this, not monolithic scaling.

Julie Zhuo's tiebreaker: small elite teams produce better single artifacts, but scaled orgs manufacture senior designers at volume. The craft-forward AI-era startups now winning are staffed by people who grew up at Facebook-scale orgs in the 2010s. A world of only Linears produces great products and very few leaders capable of running one.

Which Approach Fits You?

Answer 3 questions about your situation. We'll match you to the right approach.

Question 1

What phase is your product in?

Question 2

What is your most acute constraint?

Question 3

Which failure mode would be most expensive for you?

Notable Absences

The Bottom Line

Zhuo is the tiebreaker. Small elite teams produce better single artifacts. Scaled orgs produce more senior designers. These are different outputs, and the industry needs both. A world of only Linears produces beautiful products and few design leaders capable of running a hundred-person team. A world of only Stripes produces consistent quality across massive surfaces and hundreds of leaders but fewer category-defining aesthetic leaps. Right now, with craft-forward AI-era startups proliferating, the Baxley-Saarinen-Misra model is ascendant precisely because the Facebook-scale design pipeline of the 2010s already produced the talent now going out and building small.

Both things can be true at once, and the Lenny's Newsletter evidence points exactly there. "How Coda builds product" describes small autonomous pods — roughly one PM, one designer, and two to four engineers — operating inside a scaled org. That is Baxley's small unit living inside Dill's structured company: scale headcount at the org level, preserve smallness at the unit of building. "How Ramp builds product" adds that "you ship your org structure" — a Dill-aligned view that org design and product quality are the same object. And Dill's own newsletter piece on the PM-design partnership is the written defense of the scaled-org model she practices at Stripe: explicit partnership infrastructure, not Saarinen's one-PM-for-the-whole-company.

Sources

Bob Baxley — "35 years of product design wisdom from Apple, Disney, Pinterest, and beyond | Bob Baxley" — Lenny's Podcast, June 12, 2025
Gaurav Misra — "How to win in the AI era: Ship a feature every week, embrace technical debt, ruthlessly cut scope, and create magic your competitors can't copy | Gaurav Misra (CEO and co-founder of Captions)" — Lenny's Podcast, March 27, 2025
Karri Saarinen — "Inside Linear: Building with taste, craft, and focus | Karri Saarinen (co-founder, designer, CEO)" — Lenny's Podcast, October 8, 2023
Katie Dill — "Building beautiful products with Stripe’s Head of Design | Katie Dill (Stripe, Airbnb, Lyft)" — Lenny's Podcast, October 15, 2023
Julie Zhuo — "Julie Zhuo on accelerating your career, impostor syndrome, writing, building product sense, using intuition vs. data, hiring designers, and moving into management" — Lenny's Podcast, June 7, 2022