Annie Pearl on Product Strategy at Calendly

Annie Pearl on Product Strategy at Calendly

transcript product-management product-strategy calendly plg enterprise lenny-podcast

Annie Pearl on Product Strategy at Calendly

Guest: Annie Pearl — Chief Product Officer at Calendly. Previously: CPO at Glassdoor; Director of PM at Box (where she built the APM programme). Also on the board of two companies; member of Skip (CPO community).
Host: Lenny Rachitsky
Source: Lenny’s Podcast. Recorded ~2022–23.

Overview

Annie Pearl covers how Calendly builds and prioritises product using the “Playing to Win” framework (Roger Martin), three-horizon resource allocation, phase-gated discovery, and the company’s PLG + enterprise sales motion evolution. Also covers how to transition into PM from non-technical backgrounds and how to run APM programmes.

Key ideas

  1. “Playing to Win” strategy framework. Strategy = integrated set of choices outlining how you win. Key questions: winning aspiration; where to play (markets, segments, personas); how to win with the target. Forces explicit choices about where not to play — essential for prioritisation at scale.
  2. Horizon allocation shifting over time. Year 1: 70% horizon 1 / 30% horizon 2 / 0% horizon 3. Year 2: 50/50. Year 3: 30/60/10. Resource allocation communicates strategy; each shift is a deliberate signal about where the company is in its development arc.
  3. Phase-gated product development lifecycle. Four phases: (1) Discovery, (2) Solutioning, (3) Build, (4) Launch, measure and iterate. Only commit to dates for the phase immediately in front of you — not six months out. Dramatically reduces false deadline commitments.
  4. PLG to enterprise motion. Calendly started as bottom-up scheduling tool; enterprise organisations started using it widely, creating inbound enterprise demand. Added sales team on top of the PLG base. Primary target: sales, recruiting, and customer success teams within organisations rather than solopreneurs.
  5. OKR maturation. Progressed through three stages: (1) no clear OKRs; (2) siloed product-team OKRs; (3) three company-level OKRs with tight cross-functional integration and quarterly milestones.

Prioritisation and product strategy

The strategic choice to focus on enterprise ICPs (sales, recruiting, CS teams) over solopreneurs is enforced at the feature level: Venmo integration is consistently deprioritised despite heavy demand from small businesses, because it doesn’t serve the target personas.

Strategic artefacts at Calendly:

  • 3-year strategy deck (presented at all-hands, part of new hire onboarding)
  • Annual OKRs broken into quarterly milestones
  • Feature/project-level docs in Confluence
  • Roadmap tracking in Aha; project management in Jira; collaboration in Slack, Loom, Airtable

Entering product management

Two formal paths: APM programmes (Google, Meta; also possible at earlier-stage companies) or internal transfers from adjacent roles (customer support, sales engineering, implementation). Two informal paths: shadow PMs and offer to take work; join an early-stage startup where everyone wears multiple hats.

APM programme at Box: required clear interview process, explicit expectations, training components, and a clear graduation track from APM to PM.

See also