Lane Shackleton on PM Principles, Catalyst, and Learning by Making

Lane Shackleton on PM Principles, Catalyst, and Learning by Making

transcriptlennys-podcastproduct-managementproduct-ritualsteam-culturedecision-making

Lane Shackleton on PM Principles, Catalyst, and Learning by Making

Source: Lenny’s Podcast Speaker: Lane Shackleton Date: ~2023 Link: https://www.lennysnewsletter.com

Key ideas

  • Turn ambiguity into clarity as the PM’s core job. Shackleton’s definition of product management, borrowed from his mountain guide background: the job is to make something actionable out of what is currently undefined. Concretely, this means knowing which decisions unblock other decisions (the eigenquestion logic applied to product work), showing teams what a clear north star looks like, and removing the uncertainty that prevents teams from moving with confidence. The PM who cannot do this cannot lead.
  • Systems beat goals. Rather than setting goals and hoping to reach them, Shackleton’s principle is to install systems — default-on habits — that make the goal an inevitable byproduct. His example: Jerry Seinfeld writes for an hour every morning not because his goal is to be funny but because the system produces the output. Applied to product: a team that talks to customers every few days as a default-on ritual will develop better intuitions than one that sets an OKR to conduct ten customer interviews per quarter. Goals measure; systems produce.
  • Cathedrals not bricks. From a Shishir Mehrotra mentorship story: teams lay bricks all day. Great PM leadership converts brick-laying into cathedral-building — giving the team a vivid, shared image of the completed structure. The key subtlety Shackleton adds: different team members need to see different facets of the cathedral. An engineer, a designer, and a sales lead have different visual vocabularies; a single written vision will not reach all of them. Combine strategy docs with metrics, mocks, billboards, and narrative — show every face of the building.
  • Catalyst: multi-threaded product reviews that solve the throughput problem. The standard single-threaded weekly review meeting is a bottleneck: standing attendees may not be the right attendees for any given decision, and one topic at a time limits how fast decisions get made. Coda’s Catalyst system solves both problems: three one-hour time blocks per week, whole-company calendar holds, four roles per topic (Driver, Maker, Braintrust, Interested), topics added dynamically the day before. Multiple topics run simultaneously when attendees do not overlap. Result: the right people on every decision, much higher throughput.
  • Flash tags: calibrating feedback weight. From Dharmesh Shah at HubSpot: a shared vocabulary for how strongly a feedback-giver stands behind a comment. FYI (information only, no action required), Suggestion (take it or leave it), Recommendation (I have thought about this; please consider it seriously), Plea (I will die on this hill). In practice, the signal quality of feedback collapses without this calibration — leaders inadvertently over-weight their offhand observations and under-weight strong signals from quieter team members.

Overview

Lane Shackleton is the Chief Product Officer at Coda, the all-in-one doc and project tool. He previously held product and growth roles at Google, YouTube (where his team invented skippable ads), and served as an Alaska mountain guide before entering tech. The episode covers his core PM principles (turn ambiguity into clarity, systems not goals, cathedrals not bricks, learn by making), the Catalyst ritual for multi-threaded product reviews, two-way writeups as a successor to Amazon-style one-way memos, flash tags, tag-ups (group one-on-ones), and the story of YouTube skippable ads. Shackleton is writing a handbook on product team rituals with Shishir Mehrotra.