Product teams building on rapidly improving AI models face a structural dilemma: ship only what works today and risk irrelevance, or build for tomorrow's capabilities and ship nothing usable. Tulsee Doshi, Google's head of product for Gemini, offers a concrete split. Speaking on Lenny's Podcast, she recommends dividing every build into roughly 60% that works today, 20% that nearly works, and 20% that is a bet on future model gains. The framework, reported by BigGo Finance from her podcast appearance, gives product leaders a simple diagnostic for judging whether their roadmap is balanced or stranded.
Understanding Google's 60/20/20 AI Product Development Framework
Doshi's rule addresses a question every AI product team now confronts: how far ahead of model capability should you build? Her answer is a proportional allocation of development effort across three buckets, each defined by its relationship to current model capability. The first bucket contains features fully functional with today's models. The second contains features that are almost working—viable with modest near-term model improvement. The third contains speculative bets on capabilities that do not exist yet but may arrive as models advance.
The framework emerged from Doshi's discussion of the practical craft of building AI products, where she also argued that model behavior should be treated as UX and that "good" should be defined through rubrics and evals. The 60/20/20 split is her answer to the pacing problem specifically: it is a rule of thumb for how much of what you build should depend on capabilities you already have versus capabilities you expect. It is not a budgeting mandate but a strategic posture for teams whose underlying technology improves on its own schedule.
The 60% Allocation: Shipping Value Today
The largest share of effort goes to what current models can already deliver. In Doshi's words, "You want to actually build features that aren't necessarily always working today. Build such that 60% of what you've built works now and your prototype is at least functional." The majority of a product, in other words, must be immediately viable: users get real value now, and the product has a stable, functional core rather than a collection of demos.
This floor matters because it disciplines the rest of the portfolio. If less than roughly 60% of what a team builds works today, the product risks becoming an aspiration wrapped around a prototype—impressive in demos but unable to serve users reliably. The 60% bucket is where immediate user value and product stability live, and it anchors the other two allocations. Everything speculative is funded from the margin above this functional core, not instead of it.




