The 'Solve Before Scale' Protocol
by Aparna Chennapragada • Chief Product Officer, AI Product Strategy at Microsoft
Former CPO at Robinhood, VP at Google (Lens, AR, Assistant), Engineering Leader at Akamai, Board Member at eBay and Capital One.
🎙️ Episode Context
Aparna Chennapragada, CPO at Microsoft, discusses the shift in product development driven by AI. She explores the transition from graphical interfaces to natural language experiences (NLX), the necessity of prototyping as a primary specification tool, and frameworks for evaluating the timing and viability of zero-to-one products. The conversation covers the balance between innovation and governance in enterprise AI, the evolving role of product managers, and the concept of collaborative intelligence between humans and agents.
Problem It Solves
Prevents premature optimization and getting stuck on a 'local hill' by validating the core value proposition first.
Framework Overview
A phased approach to product development that prioritizes solving a core problem with qualitative signals before attempting to scale with quantitative metrics.
📅 Framework Timeline
Phase 1 (Solve): Embrace chaos and 'w...
Phase 2 (Scale): Operationalize, opti...
Prototypes > PRDs: Build to think; us...
When to Use
When building zero-to-one products where the solution shape is not yet defined.
Common Mistakes
Applying false precision (metrics) too early; fearing the chaos of the early 'solve' phase; scaling a product that hasn't truly solved the core user need.
Real World Example
Google Now initially failing with personalization logic, then pivoting to a proactive assistance model ('Solve') before expanding.
If you're not prototyping and building to see what you want to build, I think you're doing it wrong... Solve before scale.
— Aparna Chennapragada