Skip to main content
Next Step PM
Back to the library

Any phase · Craft

Understand what a product manager does

A product manager makes sure the team builds the right thing: something users need, that works for the organisation and that can be built. Knowing what the role is, and is not, helps you focus your time.

About 1-2 daysEvergreenLast reviewed 5 November 2026

Who this applies to

Skills it builds
Delivery and executionCommunication and influence
PM types
All
Product types
All
Starting points
All
Ways of working
All
Experience
Beginner (under 1 year)
Size of organisation
All

Steps, by experience

Beginner (under 1 year)

  1. Learn the four risks every PM manages: will people want it, can they use it, can we build it, and does it work for the business.
  2. Write down the outcomes you are responsible for, not just the tasks you do.
  3. Find out how your organisation divides work between you, design, engineering, delivery and any product owner.
  4. Book short one-to-ones with each role in your team and ask what they need from you.
  5. Each week, check how much of your time went on users, the team and stakeholders. Aim for a balance.
  6. Pick one experienced PM to learn from and meet them regularly.

Intermediate (1 to 4 years)

  1. Map your responsibilities against value, usability, feasibility and viability.
  2. Agree role boundaries with your team.
  3. Review where your time goes each month.

Experienced (5+ years)

  1. Coach new PMs on the role and on outcomes over output.
  2. Help your organisation define product roles clearly.
  3. Model the role through your own habits.

Who can do this

Owner: Product manager

Can be delegated to

  • Delivery Manager or Scrum Master: Explain how delivery and product work together here

Reviewed by: Delivery Manager

Tool examples

Notion
Keep a simple weekly log of where your time went and what you learned.
Claude
Describe your week and ask which activities moved outcomes and which did not.

Definition of done

  • Outcomes you own written down
  • Role boundaries agreed with your team
  • A mentor or peer to learn from

Common pitfalls

  • Becoming the team's note-taker or ticket-writer only
  • Saying yes to every request
  • Trying to be the designer or engineer as well

Sources