Why the Two-Pizza Rule Is Being Reexamined in the Age of AI

For years, the idea that a team should be small enough to feed with two pizzas became a kind of gospel in Silicon Valley. Jeff Bezos popularized it at Amazon, suggesting that if a team couldn’t be fed by two pizzas, it was too big to move fast. The logic was simple: smaller teams mean fewer communication overhead, quicker decisions, and more ownership. It worked well enough to become a shorthand for agility.

But something has shifted. The rise of AI tools, changing work expectations, and a deeper understanding of how innovation actually happens are making leaders rethink what “small” really means. The two-pizza rule isn’t dead, but it’s being questioned — and in some cases, replaced by new models that prioritize capability over headcount.

AI Is Changing What a Small Team Can Do

One of the biggest challenges to the two-pizza ideal comes from artificial intelligence. Tools that can write code, analyze data, draft reports, or even simulate customer behavior are allowing fewer people to accomplish what used to require entire departments. A single engineer with the right AI assistants might now handle tasks that once needed a small team of developers, testers, and product managers.

This doesn’t mean teams are vanishing. Instead, the nature of work within them is evolving. A designer might spend less time on repetitive layout tweaks and more on strategic thinking, aided by AI that generates multiple options in seconds. A marketer might use AI to test dozens of ad variations before lunch, freeing up time for creative direction rather than manual A/B testing.

Leaders are starting to ask: if AI can handle execution, what should humans focus on? The answer often points to judgment, empathy, and complex problem-solving — skills that don’t scale with headcount but do benefit from diverse perspectives. That’s pushing some organizations to think less about minimizing team size and more about optimizing team composition.

The Hidden Cost of Too-Small Teams

While small teams reduce coordination overhead, they can also create blind spots. When a group is too lean, there’s less room for dissenting views, fewer opportunities for mentorship, and a higher risk of burnout. People end up wearing too many hats, not because they want to, but because there’s no one else to share the load.

JPMorgan’s approach with young athletes offers an interesting parallel. They’re not just hiring financial advisors; they’re embedding them in environments where trust is built early — like college locker rooms — so that when those athletes turn pro, the relationship already exists. It’s a long-term play that requires people who can listen, adapt, and show up consistently. That kind of work doesn’t thrive in a two-pizza team where everyone is constantly firefighting.

Similarly, Ron Johnson, who helped scale Apple Stores from zero to hundreds, has reflected on what people misunderstand about Steve Jobs. It wasn’t just Jobs’ vision that drove success — it was the depth of talent around him. Johnson oversaw the creation of 350 stores, a feat that required not just visionaries but operators, trainers, and logistics experts. Innovation at scale often needs more than a tight core; it needs layers of support that small teams simply can’t provide.

When Bigger Teams Actually Move Faster

There’s a growing recognition that under certain conditions, slightly larger teams can outperform their smaller counterparts — not despite their size, but because of it. When a project involves multiple disciplines, regulatory complexity, or global coordination, having dedicated specialists can prevent bottlenecks.

Consider the opening of a new CVS Pharmacy location in Houston. It’s not just about dispensing medicine. It involves real estate negotiations, local hiring, community outreach, inventory management, insurance compliance, and digital integration. No two-pizza team could handle all that well without sacrificing quality or speed somewhere. Instead, the effort relies on coordinated effort across functions — each with enough depth to own their piece without constant context-switching.

This doesn’t mean bloating teams for the sake of it. It means recognizing that some problems require a certain critical mass of expertise. The goal isn’t to maximize or minimize size, but to match the team’s capacity to the complexity of the challenge.

Rethinking ROI Beyond Headcount

The old assumption that smaller teams are inherently more efficient is being tested by new ways of measuring value. Take Molly Moon Neitzel’s ice cream company, where she reimburses employees up to $1,000 per month per child for daycare. On the surface, that looks like a cost center. But she says it delivers a 128% return on investment — not through direct revenue, but through retention, morale, and productivity.

That kind of thinking is influencing how leaders view team structure. If investing in support — whether it’s childcare, mental health resources, or AI tools — lets people do their best work, then the optimal team size might be larger than before, not because we need more bodies, but because we’re enabling the ones we have to contribute more fully.

It’s also shifting the conversation from “how few people can we get by with?” to “how can we structure work so that people thrive?” A team that’s slightly larger but well-supported, with clear roles and access to the right tools, might outperform a leaner team that’s stretched thin and constantly context-switching.

The Future Isn’t About a Number — It’s About Fit

The two-pizza rule wasn’t wrong. It was a useful heuristic for a specific time and context — early-stage startups, rapid prototyping, environments where speed trumped everything else. But as businesses mature and technology evolves, the rules of engagement change.

What’s emerging is a more nuanced view: team size should be driven by the work, not the other way around. Some projects need a tight core of generalists who can pivot quickly. Others need specialists who can go deep. Some benefit from a mix — a small, agile hub surrounded by flexible support that scales up or down as needed.

What matters most isn’t whether you can feed the team with two pizzas, but whether the team has the clarity, capacity, and cohesion to solve the problem at hand. AI might shrink the execution burden, but it hasn’t eliminated the need for thoughtful collaboration. In fact, by freeing people from grunt work, it might be making space for the kind of conversations that only happen when you’ve got enough people in the room to challenge each other — and enough trust to listen.

The days of rigidly counting slices may be over. But the conversation about how we work together? That’s just getting started.