Selling ideas and rising as a product leader: Casey Winters on growth and influence

Executive overview

Most product managers under-communicate upward, then blame executives for being out of touch. Executives speak a different language — if you skip the first five chapters of your story, even a correct argument fails to land.

Casey Winters, CPO at Eventbrite, shares frameworks for internal communication, justifying unsexy investments, managing product simplicity at scale, and navigating the path to CPO. Scalable growth loops must be designed before product-market fit, not after.

The single biggest career lever for PMs is learning to write strategy without prompting — everything else is table stakes.

Starting at the right chapter

• Most non-executives start presenting on "chapter six" — skipping the strategic context executives need to follow.
• Starting too early (re-explaining company strategy) wastes time before you reach new information.
• Find the last point completely obvious to your audience, then move forward from there.
• Executive communication is plural — each exec has different concerns; anticipate them individually.
• Pre-meetings surface concerns before the main presentation, not during it.
• Role-play the meeting in advance: predict what the CFO will ask, what the CEO will push on, and answer those questions before they're asked.

Preparing for high-stakes meetings

• Treat important meetings as high-leverage moments — under-preparing directly limits career growth.
• Prep is not about memorising bullet points; it's about knowing every question that could be asked and having the data to answer it.
• Know the complete universe of how the meeting can go before you walk in.
• The measure is readiness, not hours spent — some people need explicit run-throughs; others work from deep written notes.

Justifying non-sexy investments

• Performance, UX debt, and developer velocity get chronically underfunded because they're hard to measure.
• Build custom metrics to surface value; run small tests to prove worth before asking for large commitments.
• Frame the risk: show what product-market fit erosion looks like if the work isn't done — downside framing is often more persuasive than upside projections.
• Align your engineering manager and design lead first — a small coalition makes the broader case far easier.
• User expectations rise every day; competitive baselines improve constantly; standing still means eventual decline.

Keeping products simple at scale

• Scott Belsky's cycle: users flock to simplicity → product adds features for power users → users flock to the next simple product.
• Progressive disclosure, segmentation, and unbundling all have real limits when users span every sophistication level.
• Perceived simplicity: advanced features are discoverable when sought, invisible to users who don't need them.
• Simple defaults with an explicit on-ramp to more control outperforms forcing all users through the same interface.
• WhatsApp is the benchmark: core experience stays simple; deeper features surface only when needed.

Ops as a signal of inefficiency

• Functional ops roles are a hack to deal with a functional problem — acceptable short-term, dangerous long-term.
• The right mandate for ops: find inefficiencies, build process or software to eliminate them, then move on.
• Normalising ops as a stable scaling function compounds the dysfunction instead of fixing it.
• Ops people who eliminate their own role become highly sought-after — there is no career risk in being too effective.

The CPO role and path to get there

• A CPO is accountable for products that deliver customer value that translates into business value.
• Key distinction: a CPO must optimise for the entire company, sometimes at the expense of their own team.
• Refuse to over-specialise early — breadth lets you speak credibly with CEOs on more topics than most peers.
• Learn to assume executive questions are curiosity, not challenges — it changes how you show up.
• The path may look slower early but leads to a higher ceiling.

The PM spectrum and the strategic bottleneck

• One extreme: crazy innovators — many ideas, poor execution, 1-in-10 are game-changers.
• Other extreme: execution-focused PMs — great at shipping, need strategic direction from above.
• When forced to choose, prefer executors — there are always too many ideas and too little focus.
• The great filter for senior PM roles: writing a strategy doc without guidance. Most PMs can't do it.
• To develop strategy skills: structured programs (e.g. Reforge), mentorship, and exposure to strong strategic thinkers.

Growth strategy and timing

• Kindle strategies: non-scalable early hacks to get initial users — done by founders.
• Fire strategies: scalable loops (content, viral, sales, paid) — the thing Kindle strategies exist to unlock.
• Hire a dedicated growth leader once a fire strategy is proven and needs to be 10x'd, not before.
• Scalable acquisition is a requirement for product-market fit — great retention with no acquisition loop is not PMF.
• Building growth loops before PMF is not premature scaling; it is building distribution readiness for when the product is ready.

Emerging growth trends

• Product-led sales: unify self-serve and sales-led B2B acquisition into one loop; product qualifies leads, sales picks up high-value ones with full context. Still early days.
• Data network effects: product usage data that makes the product better over time (personalisation, better ad targeting) is a durable edge, especially as platform-level data from Apple and Facebook becomes less accessible.
• Neither is a new channel — both are ways to extract more leverage from existing ones.