How to build trust, expand scope, and grow as a product leader

Executive overview

Most PMs plateau because they keep doing what got them promoted — executing well in a narrow lane. The real unlock is learning to generalise, communicate, and scale your scope across unfamiliar types of product work.

Fareed Mosavat (Reforge, Slack, Instacart, Zynga, Pixar) breaks down the PM career acceleration loop, the product leader canyon most ICs fail to cross, and why sponsorship — not mentorship — is what actually moves careers forward.

The core insight: impact = quality of execution × ability to show and communicate that work — and both factors must grow together.

The PM learning loop

• PM skill is specific knowledge — it can only be built by doing real work on real products with real customers.
• Courses, reading, and mentorship are multipliers on execution, not substitutes for it.
• The loop has four steps: execute → generalise → communicate → scale your opportunities → execute again.
• At early career, the pie chart is almost all execution; the balance shifts as you get more senior.
• Generalising means extracting transferable lessons from specific work — e.g. "high-activation products sometimes benefit from higher-friction onboarding" is a generalisation, not a finding.
• Communication is the step most PMs skip: no one knows what you've learned if you don't tell them.

Sponsorship, not mentorship

• Sponsors give you bigger problems to solve; mentors give you advice. Careers accelerate through sponsors.
• Sponsors notice you by seeing how you communicate work and connect dots across the organisation.
• Working on problems that are in the company's top four or five priorities dramatically increases visibility.
• Going two stack levels up and two down — understanding your boss's boss's priorities and the technical details below you — is what signals readiness for bigger responsibility.
• Knowing what's "to the left and right" (adjacent teams, cross-functional partners) builds the same trust.
• Remote environments make this harder; it requires more deliberate one-on-ones rather than ambient proximity.

The product leader canyon

The canyon is the gap between senior IC and effective manager. Most people fall in because they keep doing the work themselves.

• The default failure mode: take on broader scope but cherry-pick the most interesting problems, leaving the rest to the team.
• This creates the manager death spiral — you're overworked, your team isn't growing, and you're not building leverage.
• The shift required: move from doer to editor. Your job becomes making other people's work better, not doing the work yourself.
• Match your level of input to each person's experience and the problem's importance; not everything needs directive management.
• As a leader, your job is no longer to maximise output with the resources you have — it is to define what resources are needed to achieve the outcome.

The four types of product work

A framework developed with Casey Winters at Reforge. Leaders must own a portfolio across all four; specialists in one type tend to mis-apply it everywhere.

1. Feature work — new capabilities that deepen engagement with existing customers.
2. Growth work — connecting a wider range of customers to experiences that already exist; driving top-line or monetisation metrics.
3. Product-market fit expansion — attracting new customer segments. Either same product, new audience (e.g. internationalisation) or new product, same audience (bundling).
4. Scaling work — keeping the product working as volume grows; includes technical scaling, trust and safety, and user-experience degradation at scale.

Most PMs are expert in one type. Crossing the canyon requires building a baseline across all four and allocating portfolio effort appropriately — not letting your dominant lens shape every decision.

Resourcing as a leadership responsibility

• A common trap: treating the team you have as a fixed constraint rather than a variable to argue for.
• Framing shifts from "here's what I did with what I had" to "here's the outcome we need, here's what it requires, here are the trade-offs if we can't get there."
• This is extra credit for senior ICs; it is the baseline expectation for product leaders.
• Cross-functional resourcing matters too — at Slack, partnering more aggressively with marketing, sales, and data would have moved the needle more than purely product-side work.

The portfolio career path for senior operators

• A growing trend: senior operators moving from full-time roles to fractional advisory, writing, workshops, and EIR positions.
• The Reforge EIR program was designed as a transition period — but many residents are choosing to stay in portfolio mode rather than returning to a single full-time role.
• What makes this viable: having narrow, specific expertise that is hard to hire full-time but genuinely accelerates a company in a focused engagement.
• Depth plus breadth is the formula — enough breadth to generalise across industries and problem types, enough depth to be credibly top-tier in a specific area.
• Working at well-known companies matters: it reduces the sales burden when positioning yourself later.

Downsides of the portfolio path

• No health insurance, no employer 401k, no paid leave — all of this must be self-managed.
• Longevity is uncertain: how long can you remain valuable when removed from full-time operating experience?
• Continuous BD and selling is required — if you dislike selling, the path is harder.
• If everyone exits full-time roles, the question of who builds things remains open.