Jun 8, 2022 · 54m · news
Kayvon Beykpour: How to Structure and Manage the Best Product Reviews | 20VC #894 · 20VC with Harry Stebbings
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of 20VC, product leader Kayvon Beykpour sits down with Harry Stebbings to share foundational insights on scaling product organizations, the art and science of hiring, and the precise execution of effective product reviews.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Harry holds 9.9% of the talking time here. How this is scored →
Harry as informed peer 2.2 Guest teaching 3.8 Guest disagreement 0.6 Harry pushing back 0.6
speaking balance: gold is Harry, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 12:32 Kayvon rejects ratio framing
When Harry asks whether product is an 80/20 or 20/80 split of art and science, Kayvon immediately rejects the quantitative premise, stating that it is hard to put numbers on these concepts.
Hardest push from Harry ▶ 22:51 Harry refuses canned interview answersHarry pushes back on standard candidate responses regarding flexibility, challenging Kayvon to explain how to look past candidates who claim they thrive in ambiguous environments.
Biggest teaching moment ▶ 41:22 Problems vs solutions frameworkKayvon re-educates the host on customer feedback loops by distinguishing between hearing customer problems and accepting their proposed solutions, referencing the Henry Ford faster horse quote.
Harry holds his own ▶ 47:28 Harry synthesizes guest insight with Belsky quoteHarry demonstrates deep contextual awareness by connecting Kayvon's breakdown of Periscope's default persistence flaw directly to Scott Belsky's maxim that the devil is in the default.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Harry as informed peer | Guest teaching | Guest disagreement | Harry pushing back | Why |
|---|---|---|---|---|---|---|
| How Kayvon Met Scott Belsky and the Early Days of Periscope | 1 | 3 | 0 | 0 | Harry sets up the interview by asking about Kayvon's initial encounter with Scott Belsky. Kayvon shares the origin story of Periscope, describing how Belsky wrote a check and joined their early effort before an app was built. | |
| Scott Belsky's Influence and the Power of Storytelling | 2 | 3 | 0 | 0 | Harry prompts Kayvon to reflect on key product lessons from Scott Belsky and asks what defines great storytelling. Kayvon explains how Belsky taught him to bridge mechanical features with aspirational product dreams. | |
| Key Product Takeaways from Periscope and Overcoming Skepticism | 2 | 4 | 1 | 0 | Kayvon details the skepticism surrounding live video apps in 2014 and explains the technical imperative of cutting stream latency from 45 seconds down to under 5 seconds to achieve interactive teleportation. | |
| The Balance of Art and Science in Product Management | 3 | 4 | 2 | 1 | Harry attempts to quantify product management into a percentage split between art and science. Kayvon pushes back on numerical splits, emphasizing that emotion and intuition represent underappreciated art in iconic product design. | |
| When to Hire Your First Product Manager | 2 | 4 | 0 | 1 | Harry uses an advisor roleplay frame to ask when early-stage founders should hire their first PM. Kayvon outlines operational signals such as constant reactive firefighting and lossy team communication. | |
| Best Interview Tactics and Questions for Hiring PMs | 3 | 3 | 1 | 2 | Harry presses on candidate interview clichés, asking how to uncover whether a PM candidate actually handles ambiguity well. Kayvon advises asking for specific anecdotes of past operational friction. | |
| The Biggest Mistake Founders Make in Product Hiring | 3 | 4 | 1 | 2 | Harry digs into the mechanics of product reviews and asks how to identify dysfunction. Kayvon shares how leadership must avoid issuing unintentional directives and explains Twitter's structured review process. | |
| Synthesizing Feedback and Prioritizing the Product Backlog | 2 | 4 | 0 | 0 | Harry asks how product leaders prioritize feedback amidst an overwhelming stream of incoming requests. Kayvon outlines how product managers filter feedback and details Twitter's 15-minute leadership post-review debrief. | |
| Customer Feedback vs. Product Gut Intuition | 2 | 5 | 1 | 0 | Kayvon reframes customer feedback management by advising founders to focus on user problems rather than suggested solutions, invoking Henry Ford's classic faster horse paradigm. | |
| Periscope's Biggest Product Mistake: The Default to Persist Forever | 2 | 5 | 0 | 0 | Harry asks about a past product mistake, leading Kayvon to analyze Periscope's default setting change that kept broadcasts forever instead of keeping them ephemeral, mistaking an exception use case for core product-market fit. | |
| Quick-Fire Round: Admired Leaders, SpaceX's Ambition, and Career Advice | 2 | 3 | 1 | 0 | In the quick-fire round, Harry covers admired leaders, career advice, and angel investing. Kayvon highlights SpaceX's operational velocity and ambition as benchmark inspiration for tech teams. |
Statements from this episode (15)
Scott Belsky wrote a substantial early seed check for Periscope
“Scott was like, I mean, I want to support you guys. He wrote us, I don't want to share how much the check was, but he wrote us a substantially sized check and was like, I want to be on the team and help you guys make this come to life.”
Stebbings: Abundance of capital has reduced the need for founder storytelling
“I think with the proliferation of capital we've seen, the need to tell a great story is almost reduced.”
Beykpour: Periscope reduced live stream latency to sub-five seconds
“Technically what that meant is we had to take what was sort of industry standard as like tens of seconds, if not more of latency and bring it down to like sub five seconds.”
Beykpour: Simple projects at Twitter required dozens of cross-functional team members
“Whereas like, if you bring that out to Twitter scale, most projects, even the simplest projects at Twitter could potentially have dozens of people working on them. And then complex projects have hundreds of people, right?”
Beykpour: Startups need a PM when teams become purely reactive to fixes
“Well, I think one signal is if the team is constantly reacting to what the product needs. Like if you're constantly underwater and the things you end up prioritizing are the things that you learn really late are broken. And you're not feeling like you can be p…”
Beykpour: People who need extreme clarity cannot thrive at startups
“There's so many ambiguities of being at an early stage startup and it is not a role. It's, it is not an environment where people who need extreme clarity can thrive in, I believe, right?”
Beykpour: Waiting too long to fire bad hires is founders' biggest mistake
“I think the most classical mistake is actually not in Making hiring mistakes, but in making the mistake of waiting too long to realize you made a mistake, right? Like that's in my experience, the way harder thing.”
Beykpour: Twitter Held Three 45-Minute Executive Product Reviews Weekly
“So in terms of like the what we have product reviews on a week or I host product reviews on a weekly basis. And the reason I say I is like cascading down our product organization. Some of our product leads have their own cadences around product reviews as well…”
Beykpour: Product Reviews Serve Two Customers, the Team and Leadership
“I think there's like two customers for a product review. There's the team. That's a customer. And then there's like the leadership team. That's a customer.”
Beykpour: Executive Overrules in Product Reviews Signal a Broken System
“Assume everything you hear from like leadership at product reviews, including from my mouth directly is just feedback and input and not a directive unless explicitly stated otherwise. Like in the five percent of time that we make a decision that is overruling …”
Beykpour: Product managers must explicitly ignore certain customer feedback
“And your job as a team and as a product manager is to take all that input in. And make organization and prioritization out of chaos. You cannot react to all the things you should not react to all the things. And you should have a well-tuned barometer about kno…”
Beykpour: Leadership should distill product review feedback into written bullet points
“And so one of the things we've started doing and maybe there are better ways of doing it, but this is just like the way we've adjusted doing it is after the pro after we have the live product review, we have a debrief as a leadership team. 15 minute debrief wh…”
Beykpour: Periscope's biggest mistake was defaulting broadcast retention to persist indefinitely
“I think one of the biggest mistakes we made with Periscope Is we changed the default Sort of data retention to persist indefinitely.”
Beykpour: The product-market fit for live video is hanging out, not news broadcasting
“That is not the product market fit use case. That is the exception use case. The product market fit use case is people use live video to hang out.”
Beykpour: Angel investors shouldn't give unprompted product feedback
“Angel investing as someone who's very, who has strong opinions and convictions around Building product is, is, is always tricky business. Cause you have to know that you're so far from the details and you're, you shouldn't necessarily volunteer your perspectiv…”
Shorts cut from this episode
▶ $100 Million Decision Creating Periscope 🤑 · 20VC with Harr (@8:42)
▶ Product Leader: Feedback vs Directives · 20VC with Harry Ste (@35:39)
▶ Why do a product review · 20VC with Harry Stebbings (@29:24)
▶ What I learned from the founder of Behance · 20VC with Harry (@1:50)
▶ What I learned building Periscope · 20VC with Harry Stebbing (@8:38)