Phased Development Commitments
by Annie Pearl • Chief Product Officer at Calendly
Former CPO at Glassdoor, Director of PM at Box, started career in law before transitioning to product via a startup.
🎙️ Episode Context
Annie Pearl discusses Calendly's transition from a pure PLG motion to adding a sales-led enterprise motion, the cultural shifts required for that change, and how to structure product teams and planning processes at scale. She details frameworks for strategy (Playing to Win), execution (Phased Development), and decision-making (OPA meetings).
Problem It Solves
Eliminates the friction of missed deadlines caused by estimating 'unknowns' and committing to delivery dates six months out without proper discovery.
Framework Overview
A roadmap planning approach that avoids long-term delivery dates for undefined work. Instead, teams commit only to the specific phase they are in, treating discovery and solutioning as distinct commitments from the final build.
📅 Framework Timeline
Only commit to dates for work that is...
Discovery is a commitment to research...
Solutioning is a commitment to design...
Engineering build dates are only set ...
When to Use
During roadmap planning and quarterly execution cycles, especially in organizations where estimation accuracy is a struggle.
Common Mistakes
Committing to a launch date before the problem has been validated or the solution designed.
Real World Example
Calendly breaks work into Discovery, Solutioning, Build, and Launch/Measure, only estimating the timeline for the immediate active phase.
We've gotten a lot better at making the commitments around the work that's right in front of us versus making a commitment around a project six months out.
— Annie Pearl