Question 1

What are the key takeaways from Lane Shackleton's episode on Lenny's Podcast?

Accepted Answer

1. The core job of a product manager is turning ambiguity into clarity - every aspect of the role from target customer to prototype to team role is inherently ambiguous, and great PMs systematically resolve that ambiguity. 2. Systems beat goals every time - instead of setting OKRs like 'talk to 10 customers this quarter,' build default-on habits like weekly customer sessions that compound learning over time. 3. Great teams need a cathedral, not just bricks - PMs must show multiple facets of the vision (writeups, metrics, mocks, billboards) so every team member can see their contribution to the bigger picture. 4. Stop debating and start making - the skippable ads lesson proves that running experiments with extreme variants produces conviction faster than months of discussion, and this applies from ICPMs to CPOs. 5. Separate strategy from OKRs and keep planning under 10% of execution time - conflating strategy with goal-setting is a common trap, and over-planning steals time from the learning that only comes from shipping.

Question 2

What does Lane Shackleton say about product-management and systems-thinking?

Accepted Answer

"The core job of a product person in general is to turn ambiguity into clarity. And if you think about the job of a product leader or a product manager, everything is ambiguous all the time. It's like what's my role on this team? What problem are we solving? Who's the target customer? What prototype is going to solve this particular problem? So it's literally everything." - Lane Shackleton "Instead of being obsessed with the goal, be obsessed with the system that gets you there. Goals with good intentions don't work. A really common example is teams that are trying to learn about customers or do research. A team may have a goal like an OKR of talking to 10 customers this quarter and they may or may not hit that OKR. And then the next quarter, they may not have a goal of talking to customers anymore." - Lane Shackleton "You want your teams to feel like they're building a cathedral and not laying bricks. I think it's really easy when PMs are really busy on a day-to-day to just be one task after the other, really execution oriented and maybe not take the time to help the team take a broader frame, open the aperture a little bit and have a view of what the cathedral is." - Lane Shackleton

Question 3

What are Lane Shackleton's views on product-management, systems-thinking, rituals?

Accepted Answer

Lane Shackleton: "The core job of a product person in general is to turn ambiguity into clarity. And if you think about the job of a product leader or a product manager, everything is ambiguous all the time. It's like what's my role on this team? What problem are we solving? Who's the target customer? What prototype is going to solve this particular problem? So it's literally everything." Lane Shackleton: "Instead of being obsessed with the goal, be obsessed with the system that gets you there. Goals with good intentions don't work. A really common example is teams that are trying to learn about customers or do research. A team may have a goal like an OKR of talking to 10 customers this quarter and they may or may not hit that OKR. And then the next quarter, they may not have a goal of talking to customers anymore."

Lane Shackleton

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

TRANSCRIPT

Lane Shackleton

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

Lane Shackleton

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

TRANSCRIPT

Lane Shackleton

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