By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Lenny's Podcast

What sets great teams apart | Lane Shackleton (CPO of Coda)

Lane Shackleton is CPO of Coda, where he’s been leading the product and design team for over eight years.

Lane ShackletonguestLenny Rachitskyhost

Oct 1, 20231h 29mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

CHAPTERS

Jump to publisher timestamps

Chapter summaries

“Oh shit” moments as a sharper measure of career growth
Lane opens with a practical reframe for career development: instead of asking whether you feel like you’re growing, ask how many moments recently made you feel underqualified or uncomfortable. Those moments signal real stretching and learning, and their absence can be a warning sign of stagnation.
- •Growth is better measured by discomfort than by vague self-assessments
- •Track “oh shit” moments over 6–24 months as a career signal
- •If you haven’t had any in a long time, it may be time to change something
- •Seek situations that stretch your capabilities and reset your baseline
Lane’s background: from Alaska guiding to Google/YouTube to Coda CPO
Lenny introduces Lane Shackleton, CPO of Coda, and tees up the episode’s focus: principles and rituals that make product teams great. They briefly touch on the Shackleton explorer connection and the themes of leadership and putting people first.
- •Lane’s path: Alaska guide → Google/YouTube → Coda CPO
- •Episode focus: principles, rituals, and how great product teams operate
- •Shackleton story as an early influence (Endurance, people-first leadership)
Working as a guide in Alaska: high-stakes decision-making and why he left
Lane recounts his time as an Alaskan mountain guide, including a pivotal incident that made him reconsider the risks. The story highlights how real stakes clarify priorities and can force honest choices about what you want long-term.
- •Guiding attracted Lane because he loved the outdoors and climbing
- •A dangerous fall while roped to a client changed his risk calculus
- •Realization: he didn’t want life-or-death dependence on strangers
- •Experience still shaped his approach to work and leadership
Parallels between guiding and building software: preparation, checklists, calm under pressure
Lane connects guiding lessons to product work: rigorous preparation, redundancy via checklists, and staying calm in scary scenarios. He shares an example of an injury rescue that reinforced clear prioritization and decisive action—skills that translate to software crises.
- •Preparation for expeditions mirrors preparation for launches
- •Checklists and redundancy prevent catastrophic misses
- •Staying calm: assess → prioritize → act
- •High-stakes scenarios create durable leadership instincts
Why Lane started studying and writing about product principles (and frustrations with ladders)
Lane explains why he began documenting principles: he kept repeating the same advice, writing clarifies thinking, and feedback improves it. He also critiques overly complex career ladders and wanted principles that transcend level and role.
- •Repeated 1:1 advice is a signal to write and scale learnings
- •Publishing forces sharper thinking and invites corrective feedback
- •Traditional career ladders are often overcomplicated and inconsistent
- •Goal: principles that apply from new PM to head of product
Coda’s career ladder design: five role stages and incentives that stay team-first
Lane describes Coda’s approach to leveling: five “role stages” (apprentice → principal), shared across functions at a high level, with a deliberately high bar at the top. Coda also minimizes title focus, hides levels broadly, and uses a centralized compensation committee to reduce manager-driven comp bias and level-chasing incentives.
- •Delayed formal ladders to avoid shifting incentives to individual-first
- •Five role stages vs. 10–15 levels at many large companies
- •Levels not emphasized publicly; titles de-emphasized
- •Central comp committee decides pay rather than direct managers
Principles of great PMs: turning ambiguity into clarity (systems not goals)
Lane’s unifying thesis: PMs exist to convert ambiguity into clarity. He illustrates “systems, not goals” using Jerry Seinfeld’s daily writing/performance routine, then applies it to product habits like continuous customer learning versus one-off OKRs.
- •Core PM job: identify ambiguity and create clarity
- •Focus on repeatable systems rather than goal statements
- •Example: continuous customer conversations beat quarterly “10 interviews” targets
- •Default-on rituals create compounding product instincts
Two leadership principles: “cathedrals not bricks” + cultivating beginner’s mind
Lane shares the cathedral metaphor: teams do better when they see the larger purpose, not just tasks. He also discusses beginner’s mind—using “walkthrough” rituals to experience the product like a new user and uncover hidden complexity.
- •Cathedrals not bricks: orient teams around meaning and mission
- •Different people need different “facets” of the cathedral (write-ups, metrics, mocks)
- •Beginner’s mind helps escape entrenched assumptions
- •Walkthrough ritual: watch someone operate as a true novice and fix what breaks
Developing your own guiding principles: read broadly, notice patterns in your advice
Lane explains how to form principles: draw inspiration from outside tech and observe the advice you give repeatedly. They discuss learning from sports, storytelling, and studying top practitioners to reverse-engineer craft and decision quality.
- •Read beyond PM literature (sports, storytelling, other crafts)
- •Notice the advice you repeat—those are your underlying principles
- •Storytelling insight: transformation moments are the “nugget” of great stories
- •Learn fastest by studying the best and then practicing under pressure
Rituals of great product teams: how Lane discovers them and why they matter
Lane outlines his approach to rituals: start by “noticing,” then ask questions, get introduced to teams, and study how work really gets done. He describes Coda’s ritual dinners and ongoing cataloging of team practices—especially those that improve decisions and velocity.
- •Good product starts with noticing (and curiosity-driven investigation)
- •Rituals dinners: leaders share specific operating practices
- •Rituals are the “engine room” of how teams execute and decide
- •Coda increasingly co-creates new rituals with customers
Ritual examples: HubSpot FlashTags + Coda’s Catalyst decision forum
Lane shares two standout rituals. FlashTags create shared language for calibrating feedback intensity (FYI → suggestion → recommendation → plea). Catalyst redesigns review forums by removing standing attendees and enabling parallel decision sessions with clear roles to reduce bottlenecks.
- •FlashTags: explicit labels prevent overreacting to every piece of feedback
- •Language helps leaders avoid accidental “commands” in meetings
- •Catalyst fixes review bottlenecks: right people, right time, higher throughput
- •Parallel sessions + roles (driver/maker/brain trust/interested) increase velocity
Adopting and evolving rituals: what to borrow, what to change, and the “tag-up” anti-1:1 pattern
Lane discusses when rituals transplant well (small team practices like $100 voting) versus when they require authority and cultural buy-in (company-wide review redesign). He introduces “tag-ups” as an alternative to discussing project work in manager 1:1s—reducing telephone games by bringing key stakeholders together with prioritized topics.
- •New PMs can adopt lightweight rituals (e.g., $100 voting) without org-wide change
- •Big rituals require agency (often head/VP-level) and careful rollout
- •Keep a stable backbone, iterate continuously on top (Catalyst/tag-ups/bullpen)
- •Tag-ups move project discussions out of 1:1s into aligned group context
Learn-by-making: the skippable YouTube ads story and testing extremes
Lane recounts how skippable ads emerged at YouTube—an unpopular idea with advertisers and sales at the time. His leader pushed them to stop debating and “test the extremes” quickly; rapid experiments created conviction and reinforced a core principle: make something and learn, instead of circular discussion.
- •Early YouTube context: lawsuits, weak advertiser trust, nascent sales motion
- •Skippable ads were initially unwanted internally and externally
- •Advice: test upper/lower bounds fast (tiny vs giant skip button experiments)
- •Meta-lesson: prototypes/experiments/docs beat endless debate
From ad approvals to CPO: customer-facing reps, product instincts, and planning/strategy rules
Lane shares his early Google path—manual AdWords approvals and support roles—arguing customer proximity builds durable product judgment. He also covers two-way write-ups (making reading, questions, and sentiment explicit) and closes with strategy/planning heuristics: OKRs aren’t strategy, and planning shouldn’t exceed ~10% of the execution window, followed by a lightning round of books, questions, and life mottos.
- •Customer-facing roles teach what customers truly care about (not the product details)
- •Two-way write-ups: track who read, upvote key questions, capture sentiment/pulse
- •Strategy should be distinct from OKR-setting to avoid confusing goals with choices
- •10% planning rule prevents over-planning and preserves execution velocity

Publisher timestamps

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.