LLenny's Podcast
← All frameworks
LeadershipFareed Mosavat (Reforge, Slack, Instacart, Zynga, Pixar)

Crossing the Product Leader Canyon

Escape the manager death spiral by shifting from doer to editor and owning outcomes over output.

Difficulty
Advanced
Time to result
~months to results
Steps
3
Confidence
89%

Fareed describes a 'canyon' many PMs never cross: the transition from IC to manager. The trap is that you got promoted by being the best IC, so your instinct is to keep the interesting, high-leverage projects for yourself and hand your team the scraps — a 'manager death spiral' that overworks you, blocks your team, and starves them of growth. Crossing requires shifting from doer to editor, owning business outcomes rather than sub-problems, and marshalling resources instead of accepting the ones you're given.

Origin

Fareed Mosavat's 'product leader canyon' and 'manager death spiral' framing from his writing.

Core principles

  • 01You reached management by being a great IC, so your instincts now work against you.
  • 02A leader's job is to make the work better (edit), not to do the most work.
  • 03Match your input level to each team member's expertise for maximum ROI.
  • 04Leaders own the outcome and must define solutions and secure resources, not just deliver with what they're handed.

How to run it

  1. 1

    Shift from doer to editor

    Redefine your job from 'do the work' to 'make the work better' — plus the work, review it, help others solve problems, being directive when needed and letting strong people run when not.

    Pro tip Think like a lazy editor: what's the least input I can add to make this as good as possible? Judge by ROI, not by how much work you personally do.

    Watch out Keeping the two or three most critical projects for yourself takes learning opportunities from your team and stops you from becoming a leveraged, more-valuable leader.

  2. 2

    Place each person and calibrate your input

    Assess where each team member sits in expertise. For high-expertise people on lower-stakes work, let them run and call you with problems; for the middle, coach to make their work better.

    Pro tip Staff appropriately and hire great people you trust so delegation is safe.

  3. 3

    Own the outcome and marshal resources

    Stop solving problems with only the resources in front of you. Propose what resources the problem actually needs — more people, the marketing or data or finance team's help — and go get them across the organization.

    Pro tip Naming the trade-offs and the resources required up front is baseline expectation at the leadership level, not extra credit.

    Watch out Saying 'we only had four engineers, so this is what we could do' is being a victim of circumstance; you were asked to solve the problem, which may mean arguing for a bigger, smaller, or different team.

In the wild

Fareed's repeated resourcing mistake

On a small team early on, Fareed got a lot done but failed to make the case that the team should grow faster; only when someone else suggested adding people did it happen. At Slack he made the case for new teams but still solved growth as a pure product problem instead of partnering deeply with marketing, sales, data, and finance.

He concluded he'd been 'a victim of the circumstances instead of owning the situation,' a lesson he says he's now made and re-learned multiple times.

Common mistakes

Hoarding the best projects after promotion

Taking the high-leverage work for yourself and giving the team the least interesting tasks overloads you, blocks decisions, and denies your team the growth that makes you leveraged.

Accepting the resources you're given

Solving only within the team you have, then explaining away limited impact, abdicates the leader's real job of proposing and securing the resources the outcome actually requires.

Is it for you?

Best for

Senior ICs newly moving into management or team-lead roles who keep defaulting to doing the work themselves.

Not ideal for

Solo or very early-stage PMs with no team to delegate to yet.

From the transcript

you have to shift from doer to editor is the way I think about it

37:30

manager death spiral this is not unique to product manager this happens in almost every leadership role

36:30

when you're a leader it's now your job to propose what are the resources we need to have the most impact on this problem

38:30

often you like find yourself victim of the circumstances instead of owning the situation

48:30

From the episode

How to build trust and grow as a product leader

Fareed Mosavat (Reforge, Slack, Instacart, Zynga, Pixar)