Lenny's PodcastTwitter’s ex-Head of Product on Elon, consumer products, culture, more | Kayvon Beykpour
CHAPTERS
- 0:00 – 0:45
Cold open: Elon’s “swipe left/swipe right” product review vibe
The episode opens with a teaser story about Kayvon’s first interaction with Elon Musk and a preview of Kayvon’s reputation for reigniting Twitter’s product shipping cadence. Lenny frames the conversation around culture change, bold bets, and the many features Kayvon’s org shipped.
- •Elon’s casual invitation to “hang out” and react to ideas (Tinder metaphor)
- •Lenny’s framing: Twitter product org went from stagnant to shipping constantly
- •Kayvon’s mission: inject ambition, creativity, and customer-visible change
- •Rapid-fire list of major launches under Kayvon’s leadership
- •“Sacred cows” as an implicit roadmap for what to change
- 0:45 – 4:38
Kayvon’s arc: Periscope → Twitter leadership, and why this story matters
Lenny introduces Kayvon’s background: founder of Periscope, acquired by Twitter, later becoming head of product and GM of consumer. The setup highlights what the audience will learn—Elon-era transition stories, culture transformation, acquisitions, and product craft lessons.
- •Periscope’s role in popularizing live video across social platforms
- •Kayvon’s progression: acquisition → Periscope lead → Head of Product → GM of Consumer
- •Teaser of key themes: Elon transition, being fired, culture, JTBD, Periscope shutdown lessons
- •Context on Twitter’s scale and the stakes of product decisions
- •Episode expectations: stories not shared elsewhere
- 4:38 – 9:12
Getting Elon up to speed: FaceTime, Twitter HQ, and Walter Isaacson in the room
Kayvon recounts being pulled into the initial post-acquisition chaos to help orient Elon to Twitter—who to talk to, what to look at, and what could matter. The surreal meeting includes Scott Belsky and an unexpectedly silent Walter Isaacson observing the whole conversation.
- •Post-acquisition chaos: Elon rapidly assessing people and projects
- •First meeting via FaceTime; follow-up in-person at Twitter HQ
- •Kayvon returning to HQ after being fired—awkward and rumor-filled
- •Two-hour wide-ranging discussion: past, future, “good/bad/ugly”
- •Walter Isaacson’s presence implies the conversation may be “on the record”
- 9:12 – 11:53
Did the conversation change anything? People, projects, and early bets like Birdwatch
Lenny presses on whether Kayvon influenced Elon’s approach. Kayvon emphasizes that he mainly pointed Elon to exceptional people and promising initiatives—some of which continued and evolved after the acquisition.
- •Kayvon doubts he shaped Elon’s management style or big decisions
- •Focus was on recommending strong internal leaders to empower
- •Product brainstorming and continuing initiatives: Community Notes (Birdwatch), Spaces, Communities
- •Creator monetization efforts as oxygen-worthy bets
- •Reflection: Elon may or may not even remember the conversation
- 11:53 – 18:55
Being let go on paternity leave: leadership change, timing, and mixed emotions
Kayvon explains the circumstances of his departure, rooted in Twitter’s CEO transition (Jack to Parag), a major org restructure, and sudden termination during paternity leave. The timing coincided with the company signing the term sheet to sell to Elon, amplifying the shock.
- •Functional org + Jack’s leadership style led to deadlock and slow execution
- •Parag shifts Twitter toward a GM model; Kayvon promoted to GM of consumer
- •Kayvon goes on paternity leave; Elon drama erupts quickly afterward
- •Parag lets Kayvon go right after returning from the hospital with newborn
- •Emotional conflict: excitement about Elon’s potential + frustration at losing agency
- 18:55 – 21:07
Why Kayvon didn’t return: the “founder PM tension” and passing the torch
After Elon’s takeover, Kayvon is invited to come “hang out” and help with product decisions. Kayvon explains why he ultimately chose to move on—recognizing the inevitable tension between a strong founder-owner and a product leader’s autonomy.
- •Elon’s informal offer and the “swipe left/swipe right” metaphor
- •Kayvon’s sense that it was no longer his canvas to shape Twitter
- •Acknowledgment of the difficulty PMs face under product-obsessed founders
- •Desire to move on after years of investing emotionally in Twitter’s direction
- •Curiosity to see what Elon does next
- 21:07 – 29:26
Changing Twitter’s product culture: momentum, alignment, and breaking “refine the core” inertia
Kayvon breaks down how hard it was to shift Twitter from risk-averse knob-turning to visible innovation. He argues culture can’t change without top-level alignment, and that early wins plus persistent internal storytelling helped teams take bigger swings.
- •First year as Head of Product: bureaucratic, political, exhausting
- •Functional org required consensus-building rather than fast execution
- •“Refine the core” helped restore growth but calcified risk aversion
- •Mission: restore ambition and customer-visible evolution without abandoning fundamentals
- •“Sacred cows” become a built-in roadmap of what to challenge
- 29:26 – 32:44
Case study: Building “Hide Replies” and confronting career-risk fear inside the org
A seemingly small feature—Hide Replies—became a vivid example of Twitter’s cultural resistance to empowering users and changing norms. Kayvon shares how even innocuous experiments were framed as dangerous career moves, and why that mindset had to be rooted out.
- •Before Hide Replies, reporting was the only tool—unscalable moderation model
- •Product principle: you can speak freely, but don’t “scream in my face” in replies
- •Internal pushback: an engineer warned it was “bad for your career” to work on it
- •The story as a microcosm of broader fear around experimentation
- •Need for force of will and leadership backing to ship controversial changes
- 32:44 – 35:07
Bold bets vs. core optimization: building a portfolio that can temporarily hurt DAU
Kayvon explains how Twitter needed both reliable growth work (ML, onboarding, recommendations) and speculative bets (new modalities like Spaces). He describes how rigid metric frameworks can punish long-term innovation—especially when new products require short-term trade-offs.
- •Core work still mattered: recommendations, notifications, onboarding instrumentation
- •Example: SMS verification bugs blocking entire countries from using Twitter
- •Portfolio approach: mix “sure things” with speculative capability expansions
- •Spaces growth required top-of-app real estate and pushes—hurting DAU/revenue short-term
- •Frameworks must accommodate investments that don’t immediately show up in core metrics
- 35:07 – 42:40
Acquihires as a culture accelerator: founders, silos, and protecting risky initiatives
Kayvon lays out Twitter’s strategy of acquiring small teams led by entrepreneurial founders and giving them latitude to run big bets. These leaders brought urgency and ambition, and the organization’s job was to prevent promising projects from being suffocated by the core machine.
- •Small acquihires import founder energy and speed into a big company
- •Examples: Birdwatch/Community Notes (Keith Coleman), creator work (Esther Crawford), Fleets, Communities
- •“Startup within Twitter” structure for highly speculative bets
- •Leadership skill: knowing when to use the system vs. “break” it
- •Betting on people by throwing them into the deep end accelerates growth and learning
- 42:40 – 46:56
Staffing and acquisitions done well: don’t staff by availability; staff by obsession
Kayvon shares practical lessons on why many acquihires and internal initiatives fail: teams get staffed with whoever is free, including skeptics. He argues risky projects require people who are both capable and genuinely obsessed—otherwise execution becomes toxic and self-sabotaging.
- •Common failure mode: projects staffed by availability, not fit or belief
- •Misalignment creates drag even before you face external market risk
- •Speculative bets need near-irrational conviction paired with truth-seeking
- •Lack of a single decision-maker leads to inconsistent staffing and commitment
- •Operating principle: staff risky work with believers who want to will it into existence
- 46:56 – 58:00
Framework overload at Twitter: JTBD, OKRs, and when process becomes the point
Kayvon critiques how Jobs To Be Done was deployed at Twitter—overly rigid, exhausting, and often counterproductive. He broadens the critique to any framework used religiously, arguing that judgment, customer empathy, and trade-offs matter more than adherence to process.
- •Kayvon disliked Twitter’s implementation of JTBD and found it unhelpful
- •Frameworks fail at the limit when used as sole governing principles
- •Customer-hostile outcomes can still be “good for metrics” (Amazon email detail example)
- •Twitter example: forcing ranked feed despite users choosing reverse-chron (“Swish” toggle)
- •Signs you’ve gone too far: bad subjective outcomes and frameworks that prevent bold bets
- 58:00 – 1:07:25
Periscope stories and lessons: Kobe’s troll, retention reality, and why live-only is hard
Kayvon shares an early Periscope story onboarding Kobe Bryant, highlighting what was special about low-latency, interactive live video. He then explains why Periscope ultimately failed as a standalone app: retention issues hidden by bursts of growth, slow integration with Twitter, and the limits of a generalized live-only consumer product.
- •Manual onboarding via private broadcasts before public launch
- •Kobe: “Why would anyone watch live?” → “Just messing with you—this is incredible”
- •Core Periscope issue: weak retention masked by international growth surges
- •Strategic belief: generalized live-only apps are less durable without async scaffolding
- •Integration with Twitter took too long, weakening defensibility
- 1:07:25 – 1:12:05
Video at Twitter: the fatal pattern of internal competition (Vine, Periscope, premium video)
Kayvon describes Twitter’s repeated execution trap: acquiring a promising product (Vine, Periscope), then building competing internal stacks instead of fully integrating. He explains how fragmented leadership and duplicated technical roadmaps wasted time and produced inferior user experiences—while competitors executed cohesively.
- •Vine: acquired, but Twitter built separate native video features that competed with it
- •Periscope: UGC live video competed with separate premium live video initiatives (e.g., NFL)
- •Two stacks/teams/UXs created fragmentation and slowed learning
- •Unified leadership is required to avoid conflicting product decisions
- •Eventually reintegration improved things, but lost time enabled competitors (e.g., Facebook)
- 1:12:05 – 1:17:58
Copying with taste: Clubhouse inspiration, building Spaces, and shipping like it matters
Kayvon argues copying isn’t inherently wrong; it depends on whether it’s done in service of customers and with good taste. He explains Twitter’s internal “Hydra” effort toward synchronous conversation, how Clubhouse clarified the right UX, and why Twitter made Spaces the company’s top priority to avoid repeating Vine/Periscope mistakes.
- •Principle: do what’s right for customers; copy ideas with taste, not cynicism
- •Hydra: pre-Clubhouse experimentation with audio/video conversation formats
- •Periscope insight: most users wanted conversation more than “teleportation” viewing
- •Spaces became #1 company priority; aggressive resourcing to win the category
- •Twitter execution aimed to avoid being too slow again
- 1:17:58 – 1:35:26
Product craft cheat codes, what Kayvon is building next, and lightning round wrap
Kayvon shares how to improve product sense by being a voracious user and staying curious—even about “silly” products. He teases his new consumer startup, then closes with lightning-round recommendations, favorite products, and personal stories about work ethic and Scott Belsky.
- •Get better by using lots of products and developing taste through repetition
- •Kayvon’s new company: early-stage consumer product (not yet announced)
- •Lightning round: sci-fi books, favorite films/shows, interview question about failure
- •Favorite products: Perplexity; shout-out to Particle (news) and Crokinole (game)
- •Life motto: “When you’ve got nothing to do, sweep” + Scott Belsky Periscope origin story
