Scott Williamson: Hiring the Best Product People in Five Steps, Why the Best PMs are Writers | E1118

Scott Williamson was most recently Chief Product Officer for GitLab, where he led a team of 65 in Product Management, Product Operations, Growth, Pricing, and Corporate Development functions. Before GitLab, Scott was VP of Product for SendGrid for over six years, where helped lead the company to a successful IPO and $3B acquisition by Twilio. ----------------------------------------------- Timestamps: (00:00) Intro (00:52) Background (02:31) Is MBA Still Worth it Today? (03:35) Product as Art or Science (05:32) Balancing Science & Art in Leadership (06:20) Transitioning to Science Mode (07:40) Defining the Role of Product Manager (09:47) When to Hire the First PM (11:35) Structuring the Hiring Process (12:59) Core Competencies of PMs (14:18) Effective Peer Interviews (15:42) Importance of Writing Skills for PMs (16:53) Creating Strategy Documents (26:07) Managing PM Performance (28:32) Conducting Effective Case Studies (30:33) Common Hiring Mistakes for PMs (33:21) Managing Performance & Promotions (44:55) Product Review Cycle (48:54) Codifying & Sharing Learnings (49:48) Priorities: Technical Debt vs. Revenue Generation (51:11) Reflection on First Product Leader Position (53:39) Quick-Fire Round ----------------------------------------------- In Today’s Episode with Scott Williamson We Discuss: 1. From Sales to Product Leader: Why does Scott believe sales is a great starting point for product people? To what extent does an MBA help someone wanting to pursue a career in product management? What does Scott know now that he wishes he had known when he started his career in product? 2. What, Who, When: How to Build a Product Team: Is product management art or science? What is the ratio? What are the four core roles of a product manager today? When is the right time to hire your first PM? What is the ideal profile for this first PM hire? What are the single biggest mistakes founders make when hiring PMs? 3. Hiring the Best Product People: What does Scott’s hiring process look like for all new product hires? How does Scott test for systematic thinking and problem-solving ability? What questions does Scott always ask in interviews? What are the best case studies to use to test a candidate’s skill set? How important is it for the candidate to have domain expertise in your product category? 4. The Best Product Teams are the Best Writers: What are the two different types of documents that product teams must use? How do you know when to use a one-pager vs a six-pager? How does the discussion and planning cycle for the different documents differ? How important is it for PMs to be great writers also? ----------------------------------------------- Subscribe on Spotify: https://open.spotify.com/show/3j2KMcZTtgTNBKwtZBMHvl?si=85bc9196860e4466 Subscribe on Apple Podcasts: https://podcasts.apple.com/us/podcast/the-twenty-minute-vc-20vc-venture-capital-startup/id958230465 Follow Harry Stebbings on Twitter: https://twitter.com/HarryStebbings Follow Scott Williamson on Twitter: https://twitter.com/Boulder_ScottW Follow 20VC on Instagram: https://www.instagram.com/20vchq Follow 20VC on TikTok: https://www.tiktok.com/@20vc_tok Visit our Website: https://www.20vc.com Subscribe to our Newsletter: https://www.thetwentyminutevc.com/contact ----------------------------------------------- #20vc #harrystebbings #venturecapital #podcast #business #scottwilliamson #gitlab #projectmanagement #hiring #twilio #productmanagement #arcbrowser #thebrowsercompany

Scott WilliamsonguestHarry Stebbingshost

Feb 20, 202459mWatch on YouTube ↗

WHAT IT’S REALLY ABOUT

Scott Williamson’s Five-Step Playbook For Hiring Elite Product Managers

Scott Williamson, former product leader at SendGrid, Twilio, and GitLab, explains how to hire, evaluate, and enable high-performing product managers, especially in post–product-market-fit startups.
He defines PM as the hub between customers and the company, breaking the role into four core competencies: validation, build, business, and communication.
Williamson outlines a five-interview hiring loop, emphasizes writing and systems thinking as defining skills, and describes concrete tools like opportunity canvases, strategy six-pagers, and KPI-based product reviews.
He also covers when to hire your first PM, how to onboard and manage their performance, and how AI and organizational dynamics (sales, engineering, execs) are reshaping product work.

IDEAS WORTH REMEMBERING

5 ideas

Treat product management as both art and science, calibrated to company stage.

Early-stage teams operate mostly on qualitative insight and intuition (more art), while later-stage and growth PMs lean heavily on instrumentation, experimentation, and data (more science).

Assess PMs across four core buckets: validation, build, business, and communication.

Great PMs systematically gather insights (customer + data), collaborate deeply with engineering, tie work to clear KPIs, and communicate crisply across executives, customers, and technical teams.

Delay hiring your first true PM until you have repeatable product-market fit.

Founders should own vision, strategy, and prioritization until the ICP, retention, and acquisition motion are reasonably understood; hiring too early leads to misalignment and disempowered PMs.

Use a deliberate, five-step interview loop to reduce variance in PM quality.

Williamson recommends: (1) recruiter/hiring-manager screen, (2) hiring manager deep dive on competencies, (3) engineering manager interview on technical + collaboration, (4) peer “think big/think small” working session, and (5) final case-based bar-raiser.

Make writing a central tool for alignment via strategy docs and opportunity canvases.

Long-form strategy documents (2–6 pages) clarify trade-offs over a multi-iteration horizon, while one-page opportunity canvases force PMs to validate big bets with customer interviews, alternatives, risks, and a target KPI before engineering starts building.

WORDS WORTH SAVING

5 quotes

PM is the function that sits between the external and internal worlds, sets direction, makes the priority calls, and decides where this thing should go.

— Scott Williamson

Most PMs spend about 95% of their time facing engineering and zero to five talking to customers.

— Scott Williamson

If you’re a good PM, you have to want it bad. You’ve got to have the strongest point of view of anybody in the company about your ideal customer.

— Scott Williamson

Words matter. If your strategy is just verbal or in bullets, people can hear what they want to hear.

— Scott Williamson

Talk to customers more. I’m guessing 90% of PMs don’t do enough of it, and it shows up in the number of failed products and failed projects.

— Scott Williamson

Art vs. science in product management and how the mix changes by stageDefining the PM role and its four core competency bucketsWhen and how to hire your first PMs and product leadersA structured five-interview hiring process and case study designThe importance of writing, strategy docs, and opportunity canvasesProduct reviews, KPI-driven management, and balancing new features vs. tech debtOnboarding, performance management, promotions, and how AI may change PM work

High quality AI-generated summary created from speaker-labeled transcript.