✶Explainer09:30
The Signs It's Time to Hire a Chief Product Officer
Perri explains how to tell when a company needs a CPO. The clearest signal is executives and boards not knowing what's happening in product or whether goals are being hit. She also checks whether teams' work ladders up into a coherent strategy and whether product managers are getting the leadership they need.
- Executives or the board saying they don't know what's going on in product is a red flag
- Test it by asking every team what they're working on and why, then see if it ladders up
- Disconnected work signals no one is formulating and deploying strategy
- Frustrated great PMs, trouble hiring PMs, and lots of untrained juniors all signal a leadership gap
“if your executives and your board are telling you that the person who's communicating those things to them are usually not chief product officer level…”
#cpo#hiring#leadership#strategy
✶Explainer12:30
The Revenue and Portfolio Thresholds for a CPO
Perri gives concrete junction points for bringing on a CPO. Around $20-30M ARR in a high-growth company, and when you move from single to multi-product or expand into new geographies, is when the role becomes necessary. By headcount it tends to land around seven to eight product managers, though scope matters more than the number.
- Above $10M ARR, CPOs usually come on around $20-30M in a high-growth company
- A more complex, multi-product portfolio is the bigger signal than any single number
- Geographic expansion, major pivots, and mergers all point to needing a CPO
- By headcount it's roughly seven to eight PMs, but depends on the rest of the team
“if you're going above 10 million dollars in ar it's usually when you hit around 20 to 30 you start to bring on a cpo…”
#cpo#hiring#scaling
✶Explainer14:30
The Difference Between a Head of Product and a CPO
Perri distinguishes a VP/head of product from a chief product officer. A head of product is a functional leader who runs processes, roadmaps, and trains PMs. A CPO adds executive skills: understanding financials deeply, projecting roadmap to revenue for the board, and overseeing functions beyond product.
- VP and head of product are interchangeable functional leaders over product management
- They implement processes, pull together roadmaps, and train lower-level PMs
- A CPO understands financials deeply and gets from roadmap to revenue projections
- CPOs are executive navigators who can oversee design, analytics, sometimes engineering
“chief product officers have to deeply understand how to get from you know roadmap to revenue and how to analyze those things and put it…”
#cpo#leadership#product-management
✶Explainer21:30
The Signs Your Team Doesn't Actually Have a Strategy
Perri describes what a strategy-less org looks like: teams grinding 80-hour weeks and shipping constantly while none of the metrics move. Executives see product as a black box. The tell is a 'missing middle' — teams know their tasks, but no one can connect that work up to the company's vision and objectives.
- Teams work like dogs, 80-hour weeks, releasing constantly, but metrics don't move
- Executives treat product and tech as a black box
- The 'missing middle' is the gap between team tasks and business objectives
- Often a strategy exists but only in people's heads, never written down
“teams are all working like dogs like they're they're working 80 hours a week i see this all the time”
“none of the metrics are moving so the executive team is going what is happening product is a black box tex tech is a black…”
#strategy#product-management#execution
✶Explainer36:00
What Actually Makes a Good Product Vision
Perri lays out her tests for a strong vision. It should be concrete enough to picture, lofty and far enough away that you can't hit it with one feature, and clearly different from competitors — explaining why you're better, not just that you are. The best visions also state explicitly what you won't do.
- A vision must be concrete enough to picture in your head, not fluffy
- It should be lofty and far off, not something you've already achieved
- It has to say how you're different and why you're better, not just 'the best'
- Great visions also declare what you don't want to do
“one a vision should be concrete enough where people can picture what it will be in their head it can't be a fluffy like be…”
“i think good visions also say what you don't want to do i love i love reading a vision that's like we're not going to…”
#vision#strategy#differentiation
✶Explainer44:00
What Product Operations Is and Why It Emerged
Perri previews her book on product operations, born from watching product management break down at scale — inconsistent roadmaps, no career ladders, wrong people in meetings, customers pestered by multiple teams. Product ops standardizes outputs and check-ins across three parts: internal data and insights, customer/market research, and process cadences.
- Product management at scale breaks: mismatched roadmaps, no ladders, redundant customer outreach
- Product ops standardizes outputs and check-ins to keep strategy on track
- Part one is internal data and insights that surface strategy progress and OKRs
- Part two is customer and market research; part three is standardized strategy cadences
“product management at scale is really hard and that's where product operations comes in”
#product-operations#scaling#process