Behind the scenes of Calendly’s rapid growth | Annie Pearl (CPO)
Executive Summary
Annie Pearl joins Lenny Rachitsky on Calendly's interview-era product organization, target-market choices, integrated OKRs and commitments within a team's control. Selected coverage omits her career history and CPO peer group. Company practices and results are her account, not verified current policy. Untimed editorial topics are not video chapters.
Key Takeaways
Give teams clear users to serve
Pearl describes Calendly's interview-era core, enterprise and platform groups. Core covers end-user features and growth; enterprise serves IT and departmental admins; platform works on integrations and APIs. The structure follows users and problems rather than a universal organizational template.
Move beyond siloed objectives
She recounts a progression from little shared strategy, to product-team OKRs, to company OKRs with integrated plans. The value she describes comes from knowing how work fits together and mapping dependencies. Merely adopting the acronym does not create that coordination.
Narrow the target market
Pearl says serving a broad set of users made prioritization difficult. The team selected sales, recruiting and customer-success personas as its core focus. Work can still help other people, but the explicit target makes tradeoffs easier to explain.
Make strategy a set of choices
She uses Playing to Win to discuss winning aspiration, where to play and how to win. Choosing where not to play is part of the strategy. Product teams can then direct resources toward a defined audience rather than trying to make an average product for everyone.
Connect allocation to the longer-term direction
Pearl describes changing resource shares across three horizons as the strategy developed. Those percentages are her account of Calendly at the time, not recommended allocations for every team. The transferable question is whether the work and resources match the declared strategy.
Turn annual goals into nearer milestones
In her planning account, company key results are annual, with quarterly milestones and product roadmaps supporting them. This creates more frequent opportunities to judge progress. It also connects a specific delivery plan to the business result it is meant to serve.
Commit dates within your control
Pearl distinguishes discovery, testing possible solutions and engineering delivery. A team may commit to finishing research before knowing whether it should build at all. Delivery estimates become more useful after the problem and solution are understood; avoid confident promises for distant, unexplored work.
The Conversation Breakdown
Give teams clear users to serve
⏱ Untimed topicPearl describes Calendly's interview-era core, enterprise and platform groups. Core covers end-user features and growth; enterprise serves IT and departmental admins; platform works on integrations and APIs. The structure follows users and problems rather than a universal organizational template.
Move beyond siloed objectives
⏱ Untimed topicShe recounts a progression from little shared strategy, to product-team OKRs, to company OKRs with integrated plans. The value she describes comes from knowing how work fits together and mapping dependencies. Merely adopting the acronym does not create that coordination.
Narrow the target market
⏱ Untimed topicPearl says serving a broad set of users made prioritization difficult. The team selected sales, recruiting and customer-success personas as its core focus. Work can still help other people, but the explicit target makes tradeoffs easier to explain.
Make strategy a set of choices
⏱ Untimed topicShe uses Playing to Win to discuss winning aspiration, where to play and how to win. Choosing where not to play is part of the strategy. Product teams can then direct resources toward a defined audience rather than trying to make an average product for everyone.
Connect allocation to the longer-term direction
⏱ Untimed topicPearl describes changing resource shares across three horizons as the strategy developed. Those percentages are her account of Calendly at the time, not recommended allocations for every team. The transferable question is whether the work and resources match the declared strategy.
Turn annual goals into nearer milestones
⏱ Untimed topicIn her planning account, company key results are annual, with quarterly milestones and product roadmaps supporting them. This creates more frequent opportunities to judge progress. It also connects a specific delivery plan to the business result it is meant to serve.
Commit dates within your control
⏱ Untimed topicPearl distinguishes discovery, testing possible solutions and engineering delivery. A team may commit to finishing research before knowing whether it should build at all. Delivery estimates become more useful after the problem and solution are understood; avoid confident promises for distant, unexplored work.
Core Frameworks & Ideas
Playing to Win choices
Clarify winning aspiration, where to play and how to win, including where not to play.
Connected planning
Link company objectives, cross-functional dependencies and quarterly product milestones.
Phase-based commitments
Commit to discovery and solution testing before treating engineering delivery as estimable.
Actionable Next Steps
- ✓Write down the target personas and the audiences that are not the focus.
- ✓Map product milestones and cross-functional dependencies to company goals.
- ✓Compare resource allocation with the strategy and its horizons.
- ✓Separate a discovery completion date from an unvalidated delivery promise.
Notable Quotes
“So, anyone in an externally facing role, we're really trying to help them do their jobs better.”
“I think it's one of the harder things for companies to do.”
“We don't know if we're going to actually end up going, and based on the results whether we're going to actually move forward with investing in that area, but that's a body of work we can commit to.”
The One Thing to Remember
Make explicit choices about the customer and strategy, then connect resources, goals and near-term commitments to them.