Why Keeping Your Product Team Too Small May Be Killing Your Next Big Breakthrough
In the high‑stakes world of product innovation, a recent statement from Google’s Vice President of Product, Robby Stein, has sparked a lively debate. Stein warned that “teams risk killing breakthrough ideas by staying too small for too long.” This insight challenges the long‑standing “lean team” mantra that has dominated tech culture for years. It forces us to rethink the sweet spot between agility and the capacity to nurture truly transformative concepts.
The Lean Team Myth: Quick, Flexible, Yet Limited?
The lean team model—typically five to seven people, cross‑functional, and rapidly iterating—has been praised for reducing bureaucracy and accelerating time to market. It works wonderfully for incremental improvements and MVPs. But when it comes to the kind of high‑impact, paradigm‑shifting ideas that can define an entire industry, the lean model can become a double‑edged sword.
- Limited Perspective: Fewer voices mean fewer viewpoints, which can inadvertently filter out radical, out‑of‑the‑box thinking.
- Skill Gaps: A small core group cannot cover the full spectrum of expertise needed for a breakthrough, from advanced AI to user research to hardware integration.
- Burnout Risk: Continuous rapid iteration on ambitious concepts can over‑tax a small team, leading to fatigue and stifled creativity.
What Stein Means by “Killing Breakthrough Ideas”
Stein’s caution is rooted in several real‑world scenarios:
- Scope Creep Without Scale: A lean team may start with a bold vision but quickly lose the bandwidth to explore the many layers required for a breakthrough.
- Inadequate Resources: Complex ideas often need more capital, infrastructure, and time—resources that a small squad may struggle to secure.
- Missed Partnerships: Larger teams can cultivate external networks (vendors, universities, regulators) that are essential for cutting‑edge projects.
Case Studies: When Scale Fueled Innovation
Google’s Project Wing (Drones)
Initially conceived by a handful of engineers, Project Wing quickly expanded to include aeronautical experts, software developers, legal teams, and logistics specialists. The breadth of knowledge enabled the company to navigate regulatory hurdles and build a scalable delivery model. A lean approach alone would have left critical gaps in compliance and operational feasibility.
Tesla’s Full‑Self‑Driving (FSD)
Tesla’s FSD program began with a core group of software engineers but soon integrated hardware designers, safety experts, and massive data teams. This scaling was crucial to amass the terabytes of driving data and perform rigorous testing—something a smaller team could not realistically accomplish.
Finding the Right Balance: A Scalable Lean Model
Contrary to the binary view of “lean vs. large,” many leading organizations adopt a scalable lean framework. The idea is to maintain a core agile team while dynamically scaling support as the project demands evolve.
1. Core Team Foundations
- Size: 5‑7 members, covering essential roles—product manager, UX researcher, senior engineer, data scientist, and a quality lead.
- Focus: Rapid prototyping, early validation, and clear milestone definition.
2. Tiered Expansion Strategy
When a concept shows high potential, the core team can activate “scaling tiers.” Each tier adds specialized talent, resources, and infrastructure:
- Tier One: Domain experts (e.g., AI specialists, regulatory consultants).
- Tier Two: Cross‑functional collaborators (marketing, sales, legal, manufacturing partners).
- Tier Three: External advisory boards or university research groups.
3. Governance and Flexibility
To prevent bureaucracy from stifling creativity, governance should be lightweight:
- Monthly “innovation checkpoints” to assess progress and re‑allocate resources.
- Clear escalation paths for critical decisions, but with room for rapid pivots.
- Metrics that balance speed with depth—e.g., “time to prototype” and “time to validation.”
Practical Steps for Product Leaders
- Audit Your Current Team Size: Map out the skill sets present versus those required for your breakthrough vision.
- Implement a Phased Funding Model: Allocate budget incrementally as the idea passes key milestones, reducing waste and ensuring buy‑in.
- Build an External Ecosystem: Cultivate partnerships early—vendors, universities, and even regulatory bodies can accelerate development.
- Champion a Culture of “Scale‑Aware Agility”: Encourage teams to think about growth from the start, not as an afterthought.
Why This Matters for Startups and Enterprises Alike
For startups, the temptation is to keep everything lean to stay nimble. However, failing to scale when the concept demands can mean losing first‑mover advantage or missing market opportunities entirely.
For large enterprises, the challenge is the opposite: avoiding the inertia that comes with size while still allocating enough resources to ambitious projects. A scalable lean model offers a pragmatic middle ground, ensuring that breakthrough ideas receive the support they need without becoming mired in bureaucratic slow‑downs.
Conclusion: Embrace Growth Without Sacrificing Agility
Robby Stein’s warning is a timely reminder that the most innovative ideas often require more than a small, tight‑knit team. By adopting a scalable lean approach—maintaining an agile core while dynamically adding expertise and resources—product organizations can nurture breakthrough concepts without compromising speed or vision.
Ultimately, the goal isn’t to grow a team for its own sake but to create the right environment where daring ideas can be explored, validated, and scaled successfully. The next time you’re tempted to keep your squad small and lean, remember: the real risk lies in holding back the potential of a breakthrough—something Stein’s insight helps us avoid.
