Rasp logo

Rasp

From IC to Product Leader: What Actually Changes

•By Rasp Team

You were a great IC product manager.

Shipped features users loved. Worked well with engineering. Made data-driven decisions. Got promoted.

Now you're a product leader. You manage PMs. You're responsible for the roadmap, the team, the strategy.

And suddenly nothing works the way it used to.

Here's what nobody tells you: The skills that made you successful as an IC are necessary but not sufficient for leadership.

You need new skills. New mindsets. New habits.

Most new leaders fail because they keep doing what worked before — just with more people reporting to them.

This is what actually changes. And how to adapt.

The Fundamental Shift: Maker to Multiplier

As an IC, you ship features.

As a leader, you ship people who ship features.

What This Means in Practice

IC PM:

  • Value = Features you ship × Quality
  • Success = Your execution
  • Impact = Direct output

Product Leader:

  • Value = (Features your team ships × Quality) + (Team capability growth)
  • Success = Team's execution
  • Impact = Amplified through others

The mindset shift: Your job isn't to be the best PM anymore. It's to make your team the best PMs.

Change #1: How You Spend Your Time

IC PM Time Allocation

  • 60% execution (PRDs, specs, decisions)
  • 20% stakeholder management
  • 10% strategy
  • 10% team/culture

Product Leader Time Allocation

  • 10% execution (reviewing, unblocking)
  • 30% people development
  • 30% strategy and vision
  • 20% cross-functional alignment
  • 10% recruiting and hiring

The hard part: Letting go of the execution dopamine hit.

What it feels like:

  • IC: "I shipped 3 features this quarter!"
  • Leader: "I sat in meetings and my team shipped 10 features."

The temptation: Jump back into execution because it feels productive.

The trap: If you're the best PM on your team, you've failed as a leader.

Change #2: From Decisions to Frameworks

As an IC

You make product decisions:

  • Which features to build
  • How to prioritize
  • What to cut

As a Leader

You create frameworks for others to make decisions:

  • Prioritization criteria
  • Decision-making processes
  • Strategy principles

Example:

IC approach: "We should build Feature X because of data Y."

Leader approach: "Here's our prioritization framework. Given this data, what do you think we should build?"

Why this matters: You won't be in every decision. Your frameworks need to work without you.

Change #3: Communication Style

IC Communication

  • Detailed and specific
  • Tactical focus
  • Audience: Your immediate team
  • Goal: Execute this feature

Leader Communication

  • High-level and strategic
  • Vision-oriented
  • Audience: Entire org + external
  • Goal: Align everyone on direction

What changes:

1. Repetition Becomes Essential

As IC: Say it once. Move on.

As leader: Say it 10 times in 10 ways. Still assume half the org didn't hear.

Why: You're not just informing — you're creating alignment.

2. Clarity Over Nuance

As IC: "It's complex. Here are 5 factors..."

As leader: "Our priority is X. Here's why."

Why: Nuance creates confusion at scale. Clarity drives action.

3. Written Over Verbal

As IC: Slack messages and conversations

As leader: Docs, emails, recorded videos

Why: You can't have 50 one-on-one conversations. Write it once, share widely.

Change #4: What "Good Work" Looks Like

IC Good Work

  • Shipped feature on time
  • Users love it
  • Data shows success

Feedback loop: Days to weeks

Leader Good Work

  • Team member develops new skill
  • Product strategy gets clearer
  • Team culture improves
  • Processes become more efficient

Feedback loop: Months to years

The frustration: You won't feel productive day-to-day.

The reality: Leadership impact compounds slowly.

Change #5: Types of Problems You Solve

IC Problems

  • Feature is too complex
  • Engineering estimates are high
  • Design and product disagree
  • Stakeholder wants something unrealistic

Characteristic: Clear and bounded. You can solve them directly.

Leader Problems

  • Team doesn't trust each other
  • Strategy is unclear
  • Organizational silos blocking progress
  • Culture is eroding

Characteristic: Ambiguous and systemic. No obvious solution.

What changes:

  • IC: "I'll fix this bug myself."
  • Leader: "I need to create conditions where bugs get fixed systematically."

Change #6: How You Add Value

IC Value-Add

Direct:

  • Writing PRDs
  • Making product decisions
  • Running user research
  • Analyzing data

You know you added value: Something shipped that wouldn't have without you.

Leader Value-Add

Indirect:

  • Unblocking others
  • Providing context
  • Connecting dots
  • Asking good questions
  • Removing obstacles

You know you added value: Someone on your team solved something they couldn't before.

The discomfort: Impact is invisible. You're not "doing" anything tangible.

The truth: Removing friction IS the work.

Change #7: Relationship to Feedback

As an IC

Feedback is about your work:

  • "Your PRD was unclear"
  • "The feature shipped late"
  • "Users are confused"

It's specific and actionable.

As a Leader

Feedback is about your team and culture:

  • "The roadmap is unclear"
  • "Your team seems disorganized"
  • "There's friction between product and engineering"

It's vague and systemic.

What changes:

  • IC: Fix the thing
  • Leader: Figure out why the thing keeps breaking

The hard part: Root causes are hidden in culture, process, and people dynamics.

Change #8: How You Prioritize

IC Prioritization

Question: What should I work on next?

Factors:

  • Impact on users
  • Impact on metrics
  • Effort required
  • Strategic alignment

Timeframe: Sprint-to-quarter

Leader Prioritization

Question: What should the team/org work on next?

Factors:

  • Strategic impact
  • Team capacity
  • Organizational readiness
  • Talent development

Timeframe: Quarter-to-year

What changes:

  • IC: Optimize for shipping great features
  • Leader: Optimize for sustained team performance

Example:

IC decision: Ship Feature X (high impact, high effort)

Leader decision: Don't ship Feature X because team is burned out and needs a win. Ship Feature Y instead (medium impact, low effort, builds confidence).

The Skills You Must Develop

Skill 1: Coaching

What it is: Helping others solve problems without solving it for them.

IC instinct: "Here's what you should do."

Leader approach: "What have you considered? What are the trade-offs? What would you do?"

Why it's hard: Slower than just doing it yourself. Requires patience.

How to practice:

  • Count to 5 before answering questions
  • Ask "What do you think?" first
  • Let people make small mistakes

Skill 2: Delegation

What it is: Giving someone work at the edge of their capability.

IC instinct: "This is important. I'll do it."

Leader approach: "This is important. Who can grow from doing it?"

Why it's hard: Requires trusting imperfect execution.

How to practice:

  • Delegate tasks you're 80% confident someone can do
  • Provide context, not instructions
  • Let them figure out the how

Skill 3: Strategic Thinking

What it is: Connecting short-term decisions to long-term vision.

IC focus: Quarterly execution

Leader focus: Multi-year trajectory

Why it's hard: Requires holding ambiguity and making bets.

How to practice:

  • Write vision docs
  • Make 1-year, 3-year roadmaps
  • Ask "Does this move us toward our future state?"

Skill 4: Organizational Navigation

What it is: Getting things done across org boundaries.

IC focus: Your immediate team

Leader focus: Cross-functional influence

Why it's hard: No direct authority over most people you need.

How to practice:

  • Build relationships before you need them
  • Understand other teams' goals
  • Frame requests around their priorities

Skill 5: Conflict Resolution

What it is: Navigating disagreements between team members or stakeholders.

IC instinct: Avoid or escalate

Leader approach: Surface, discuss, resolve

Why it's hard: Conflict is uncomfortable. Easier to ignore.

How to practice:

  • Address tension directly
  • Facilitate hard conversations
  • Don't solve conflicts FOR people — help them solve together

Common Mistakes New Leaders Make

Mistake #1: Staying in IC Mode

What it looks like:

  • You're the one writing all the PRDs
  • You make all product decisions
  • You're in all the detailed meetings

Why it fails: Bottlenecks everything. Team doesn't grow.

Fix: Deliberately hand off work. Coach instead of do.

Mistake #2: Optimizing for Being Liked

What it looks like:

  • Avoid giving hard feedback
  • Say yes to everything
  • Don't make tough calls

Why it fails: Team needs direction, not a friend.

Fix: Prioritize respect over popularity.

Mistake #3: Neglecting 1:1s

What it looks like:

  • 1:1s get cancelled for "urgent" work
  • 1:1s become status updates
  • You don't invest in relationships

Why it fails: You lose connection to team. Small problems become big problems.

Fix: Protect 1:1 time. Make them meaningful.

Mistake #4: Not Setting Clear Expectations

What it looks like:

  • Team doesn't know what success looks like
  • Feedback surprises people
  • Unclear role boundaries

Why it fails: Confusion breeds anxiety and poor performance.

Fix: Be explicit about expectations. Document them.

Mistake #5: Micromanaging

What it looks like:

  • Editing every PRD
  • Second-guessing every decision
  • Redoing work to "your standard"

Why it fails: Kills team autonomy and morale.

Fix: Set quality bar, then trust. Intervene only when necessary.

Mistake #6: Not Giving Feedback

What it looks like:

  • Avoiding hard conversations
  • Letting small issues grow
  • Annual review surprises

Why it fails: People can't improve without feedback.

Fix: Regular, specific, timely feedback. Both positive and constructive.

The 90-Day Leadership Transition Plan

Days 1-30: Listen and Learn

Goals:

  • Understand team dynamics
  • Learn individual strengths/gaps
  • Identify immediate problems

Actions:

  • 1:1 with every team member
  • Shadow team meetings
  • Review past work
  • Talk to stakeholders

Resist urge to: Make big changes. You don't know enough yet.

Days 31-60: Set Direction

Goals:

  • Clarify vision and strategy
  • Establish ways of working
  • Build trust

Actions:

  • Share vision doc
  • Create team charter
  • Establish rituals (standups, reviews, retros)
  • Start regular 1:1s

Resist urge to: Implement everything at once.

Days 61-90: Build Momentum

Goals:

  • Empower team
  • Unblock execution
  • Create early wins

Actions:

  • Delegate key projects
  • Remove obstacles
  • Celebrate wins
  • Address performance issues

Resist urge to: Jump in and do the work yourself.

Measuring Success as a Leader

Stop Measuring

  • Features you personally shipped
  • Hours you worked
  • How busy you are

Start Measuring

  • Team velocity and quality
  • Team member growth
  • Team retention
  • Stakeholder satisfaction
  • Strategic clarity

The metric that matters most: Are people on your team better PMs than they were 6 months ago?

What Good Leadership Feels Like

It doesn't feel like:

  • Constant productivity
  • Immediate wins
  • Being the hero

It feels like:

  • Lots of conversations
  • Slow progress
  • Supporting others' success

The validation:

  • Your team ships great work without you
  • People grow and get promoted
  • Strategy becomes clearer over time
  • Team culture strengthens

The paradox: The better you are as a leader, the less visible your contribution.

When You Know You've Made the Transition

Signs you're thinking like a leader:

  1. You celebrate team wins more than personal ones
  2. You say "we" instead of "I"
  3. You ask questions instead of giving answers
  4. You invest time in people who need it most (not who deliver easiest wins)
  5. You're comfortable with ambiguity
  6. You delegate work you'd love to do yourself
  7. You measure success in quarters, not weeks
  8. You see coaching as productive work, not a distraction
  9. You proactively give feedback
  10. You think about team sustainability, not just delivery

Final Thought

The transition from IC to leader is uncomfortable.

You'll feel less productive.
You'll miss executing.
You'll question if you're adding value.

This is normal.

Leadership is a different job than IC work.

It requires different skills, different mindsets, and different measures of success.

The PMs who struggle are those who try to be super-ICs with direct reports.

The PMs who succeed are those who embrace the multiplier role.

Stop being the best PM on your team.

Start making your team the best PMs in the company.

That's leadership.