Rasp logo

Rasp

Your First 90 Days as a PM: A Survival Guide

•By Rasp Team

You just started as a product manager.

Maybe it's your first PM role ever.
Maybe it's a new company.
Maybe it's both.

Here's what you're feeling:

  • Overwhelmed by information
  • Pressure to prove yourself quickly
  • Uncertainty about priorities
  • Fear of making expensive mistakes

Here's what's actually happening:

  • Everyone expects you to be lost
  • You have permission to ask dumb questions
  • Your early mistakes won't kill your career
  • The first 90 days are about learning, not shipping

Most new PMs fail because they try to ship too fast, make big changes too early, or don't invest in relationships.

The PMs who succeed follow a deliberate 90-day plan that builds credibility systematically.

This is that plan.

The 90-Day Framework

Think of your first 90 days in three phases:

Days 1-30: Learn

  • Goal: Understand the product, team, and business
  • Focus: Listening, absorbing, asking questions
  • Avoid: Making decisions, changing things

Days 31-60: Contribute

  • Goal: Start adding value in small ways
  • Focus: Quick wins, building relationships
  • Avoid: Big strategic changes, rocking the boat

Days 61-90: Lead

  • Goal: Own your domain, show strategic thinking
  • Focus: Driving outcomes, earning trust
  • Avoid: Overconfidence, moving too fast

The key: Each phase builds on the last. Don't skip ahead.

Days 1-30: The Learning Phase

Your only job is understanding the landscape.

Week 1: Information Gathering

Goal: Map the terrain

What to do:

Day 1:

  • Read everything in shared docs/wiki
  • Review product (as user)
  • Note what confuses you
  • Set up 1:1s with team

Day 2-3:

  • Study analytics dashboards
  • Review past roadmaps/PRDs
  • Read support tickets
  • Check user feedback channels

Day 4-5:

  • Use the product extensively
  • Note every point of confusion
  • Try all major workflows
  • Break things in staging

Why this works: Fresh eyes see what insiders miss. Document confusion now — you'll never be this objective again.

Week 2: The Listening Tour

Goal: Understand people and context

Who to meet (15-30 min each):

Your team:

  • Every engineer (if small team)
  • Engineering lead
  • Designer
  • Data analyst
  • QA

Ask:

  • "What's working well?"
  • "What's frustrating?"
  • "What should I know that I won't learn from docs?"
  • "What would you change if you could?"

Cross-functional partners:

  • Sales lead
  • Marketing lead
  • Support lead
  • Customer success
  • Operations

Ask:

  • "How does product affect your work?"
  • "What are you hearing from customers?"
  • "What's your biggest need from product?"

Leadership:

  • Your manager
  • Manager's manager
  • Other product leads

Ask:

  • "What are the top 3 company priorities?"
  • "What does success look like for my role?"
  • "What mistakes do new PMs make here?"

Critical rule: Talk 20%, listen 80%.

Week 3: Deep Dives

Goal: Understand the domain deeply

Activities:

Customer conversations:

  • Talk to 5-10 customers
  • Mix of happy, frustrated, and churned
  • Focus on understanding their world

Questions:

  • "Walk me through how you use [product]"
  • "What problem does it solve for you?"
  • "What's frustrating?"
  • "What would you change?"

Competitive research:

  • Sign up for 3-5 competitor products
  • Use them for real tasks
  • Note what they do better/worse
  • Understand positioning

Data deep dive:

  • Key metrics and trends
  • User cohorts and segments
  • Funnel analysis
  • Feature usage

Create a mental model of:

  • Who uses the product (segments)
  • Why they use it (jobs-to-be-done)
  • How they use it (workflows)
  • Where it breaks (pain points)

Week 4: Synthesize and Align

Goal: Organize what you've learned

Activities:

Write a "30-day reflection" doc:

# 30-Day Observations

## What I've Learned

### Product Strengths
- [Strength 1]
- [Strength 2]

### Product Gaps
- [Gap 1]
- [Gap 2]

### Team Dynamics
- [Observation 1]
- [Observation 2]

### Customer Insights
- [Insight 1]
- [Insight 2]

## Questions I Still Have
- [Question 1]
- [Question 2]

## Initial Hypotheses
- [Hypothesis 1]
- [Hypothesis 2]

## Proposed Next Steps
- [Step 1]
- [Step 2]

Share with:

  • Your manager (for feedback)
  • Your team (for alignment)

Why this works:

  • Shows you're absorbing information
  • Surfaces blind spots
  • Demonstrates strategic thinking
  • Invites correction before you act

What NOT to do in Days 1-30:

  • ❌ Make product decisions
  • ❌ Change roadmap
  • ❌ Criticize how things are done
  • ❌ Commit to timelines
  • ❌ Ship features
  • ❌ Reorganize team processes

What TO do:

  • ✅ Ask questions
  • ✅ Take notes
  • ✅ Build relationships
  • ✅ Learn the domain
  • ✅ Understand constraints
  • ✅ Absorb context

Days 31-60: The Contribution Phase

Now you can start adding value — carefully.

Week 5-6: Quick Wins

Goal: Build credibility through small successes

What to fix:

Type 1: Obvious UX issues

  • Broken links
  • Confusing copy
  • Missing error messages
  • UI bugs

Why these: Low risk, high visibility, show attention to detail.

Type 2: Documentation gaps

  • Missing help docs
  • Unclear tooltips
  • Onboarding improvements

Why these: Helps team, helps users, low controversy.

Type 3: Process improvements

  • Better templates
  • Clearer meeting agendas
  • Simplified workflows

Why these: Helps team immediately, shows you're thoughtful.

How to pick:

  • Takes <1 week to fix
  • Nobody will fight you on it
  • Clear value to users or team
  • Low technical risk

Example quick wins:

  • "I noticed our error messages don't explain what went wrong. I wrote new copy and got it shipped."
  • "Support was getting the same 3 questions. I added tooltips and reduced tickets 30%."
  • "Our PRD template was missing key sections. I updated it based on best practices."

Why this works: Demonstrates you can execute without needing to drive strategy yet.

Week 7-8: Deeper Contribution

Goal: Add value to roadmap and planning

What to do:

Support current roadmap:

  • Write PRDs for upcoming features
  • Run user research for in-progress work
  • Unblock engineering
  • Clarify requirements

Don't: Try to change the roadmap yet.

Contribute to planning:

  • Help prioritize backlog
  • Add data to discussions
  • Offer customer perspective
  • Suggest alternatives when asked

Don't: Push your own agenda.

Share insights:

  • Present customer research findings
  • Share competitive analysis
  • Surface usage data patterns
  • Highlight opportunities

Don't: Expect immediate action.

Why this works: You're adding value without overstepping. You're learning how decisions get made before trying to make them.

Days 61-90: The Leadership Phase

Now you can start owning things.

Week 9-10: Own Something

Goal: Take clear ownership of a domain

What to own:

Option A: Feature area

  • Specific part of product
  • Clear boundaries
  • Existing roadmap

Option B: Initiative

  • Customer segment
  • Workflow improvement
  • Strategic project

How to pick:

  • Aligns with your interests
  • Important but not most critical
  • Room to make impact
  • Clear success metrics

What ownership means:

  • You make decisions in this area
  • You're accountable for outcomes
  • You drive stakeholder communication
  • You set direction

Example:

"I'm taking ownership of the onboarding experience. Success = improving D7 activation from 40% to 50% by end of quarter."

Week 11-12: Show Strategic Thinking

Goal: Contribute to bigger picture

What to do:

Write a strategy doc:

  • Pick your owned area
  • Analyze current state
  • Identify opportunities
  • Propose direction

Format:

# [Area] Strategy

## Current State
- Metrics
- User feedback
- Competitive position

## Problems
- [Problem 1]
- [Problem 2]

## Opportunities
- [Opportunity 1]
- [Opportunity 2]

## Proposed Direction
- [Direction]
- [Why]
- [Expected impact]

## Next Steps
- [Step 1]
- [Step 2]

Why this works:

  • Shows you can think strategically
  • Demonstrates you've absorbed context
  • Opens discussion without demanding action
  • Sets you up to drive initiatives

Lead an initiative:

  • Small to medium scope
  • Clear outcome
  • Cross-functional
  • Realistic timeline (1-2 months)

Example:

"I'm leading a project to reduce support ticket volume by improving in-app help. Working with design and support. Targeting 20% reduction in 6 weeks."

The Critical Relationships to Build

Relationship 1: Your Manager

Meeting cadence: Weekly 1:1s

What to discuss:

  • First 30 days: Questions, observations, alignment
  • Days 31-60: How you're adding value, where you need help
  • Days 61-90: Strategy, ownership, growth

What to ask:

  • "How am I tracking against expectations?"
  • "What should I be doing more/less of?"
  • "Where can I have most impact?"

Why this matters: Your manager is your advocate for promotion, resources, and career growth.

Relationship 2: Engineering Lead

Meeting cadence: Weekly or bi-weekly

What to discuss:

  • Technical constraints
  • Roadmap prioritization
  • Team capacity
  • How to work together better

Why this matters: Product-Engineering relationship determines execution success.

Relationship 3: Design Partner

Meeting cadence: Multiple times per week

What to discuss:

  • User problems
  • Design explorations
  • Feedback on designs
  • Research findings

Why this matters: Product-Design partnership determines quality.

Relationship 4: Cross-Functional Stakeholders

Meeting cadence: Monthly or as-needed

What to discuss:

  • Their needs from product
  • Your roadmap
  • Collaboration opportunities
  • Feedback loops

Why this matters: You can't succeed without sales, marketing, and support.

Common Mistakes New PMs Make

Mistake #1: Moving Too Fast

What it looks like:

  • Changing roadmap in week 2
  • Proposing big initiatives in week 3
  • Telling team "here's what we're going to do"

Why it fails:

  • You don't have context
  • You haven't earned trust
  • You miss important constraints

Fix: Follow the 90-day phases. Don't skip learning.

Mistake #2: Not Building Relationships

What it looks like:

  • Skipping 1:1s
  • Only talking to immediate team
  • Treating people as blockers

Why it fails:

  • Product is collaboration
  • You need allies
  • Relationships take time

Fix: Invest heavily in relationships first 60 days.

Mistake #3: Trying to Prove You're Smart

What it looks like:

  • Pointing out problems constantly
  • Criticizing past decisions
  • Acting like expert

Why it fails:

  • Comes across as arrogant
  • Demoralizes team
  • Ignores context you lack

Fix: Be curious, not critical. Ask "why" not "this is wrong."

Mistake #4: Not Asking for Help

What it looks like:

  • Struggling silently
  • Pretending to understand
  • Making decisions without input

Why it fails:

  • Miss important information
  • Make avoidable mistakes
  • Slow learning

Fix: Ask lots of questions. People expect and respect this.

Mistake #5: Staying in Learning Mode Too Long

What it looks like:

  • Month 3: Still just observing
  • Not taking ownership
  • Waiting for perfect knowledge

Why it fails:

  • Need to demonstrate value
  • Team needs you to contribute
  • Learning by doing is essential

Fix: Start contributing small things by week 5. Own something by week 9.

The 90-Day Checklist

Days 1-30

  • Used product extensively as user
  • 1:1 with every team member
  • 1:1 with cross-functional partners
  • Talked to 5-10 customers
  • Reviewed analytics and key metrics
  • Studied competitor products
  • Read all documentation
  • Created 30-day reflection doc
  • Aligned with manager on priorities

Days 31-60

  • Shipped 2-3 quick wins
  • Wrote first PRD
  • Ran user research
  • Contributed to roadmap discussions
  • Built relationship with engineering lead
  • Built relationship with designer
  • Shared customer insights with team
  • Improved team process or documentation

Days 61-90

  • Took ownership of specific area
  • Led cross-functional initiative
  • Wrote strategy doc for owned area
  • Made decisions independently
  • Shipped feature from start to finish
  • Presented to stakeholders
  • Built credibility across org
  • Set goals for next 90 days

How to Know You're Succeeding

Week 4 check:

  • ✅ People are open with you
  • ✅ You understand product and domain
  • ✅ You know key metrics and trends
  • ✅ You have strong relationship with manager
  • ✅ Team asks you questions

Week 8 check:

  • ✅ Shipped visible improvements
  • ✅ Contributing to roadmap discussions
  • ✅ Engineering trusts your judgment
  • ✅ Stakeholders include you in decisions
  • ✅ You're unblocking others

Week 12 check:

  • ✅ Own specific domain
  • ✅ Make decisions independently
  • ✅ Team looks to you for direction
  • ✅ Stakeholders value your input
  • ✅ Clear on priorities for next quarter

Your Week-by-Week Action Plan

Week 1: Onboarding

  • Read all docs
  • Use product
  • Meet immediate team
  • Set up 1:1s

Week 2: Listening Tour

  • 1:1 with everyone relevant
  • 80% listening, 20% talking
  • Take detailed notes

Week 3: Deep Learning

  • Customer interviews
  • Competitive analysis
  • Data deep dive
  • Domain research

Week 4: Synthesis

  • Write reflection doc
  • Align with manager
  • Identify quick wins

Week 5-6: Quick Wins

  • Fix 2-3 obvious issues
  • Write first PRD
  • Support roadmap

Week 7-8: Contribution

  • Ship improvements
  • Add value to planning
  • Share insights

Week 9-10: Ownership

  • Own specific area
  • Set success metrics
  • Drive decisions

Week 11-12: Leadership

  • Write strategy
  • Lead initiative
  • Plan next quarter

Final Thought

The first 90 days set the trajectory for your entire tenure.

Move too fast → lose credibility.
Move too slow → seem ineffective.

The balance is:

Days 1-30: Learn everything. Change nothing.
Days 31-60: Contribute carefully. Build trust.
Days 61-90: Own things. Show leadership.

By day 90, you should:

  • Understand product deeply
  • Have strong relationships
  • Own clear domain
  • Be driving outcomes
  • Have earned trust

You won't know everything.
You'll still make mistakes.
That's expected.

But you'll have a foundation to build on.

Start with the listening tour.

Everything else flows from there.

Welcome to product management.

You've got this.