What is Product Management?

What is Product Management?

Solving problems
that matter, not just building features

Product management is often misunderstood. Titles exist, but the practices vary. Some Product Managers manage a backlog. Others define strategy. This page helps you understand what modern product management looks like when it’s done well—and why it matters. If you're new to product management, or working with PMs and not sure what their role really is, this page is for you.

Some of our customers and partners:

Simply put

Simply put

Product management is the practice of identifying valuable problems to solve, shaping the right solutions, and directing teams to deliver outcomes that work for both the user and the business.

What is product management?

What is product management?

The Product Work in 6 Phases

We use a practical model based on the Double/Triple Diamond. It's a mix of discovery, validation, and delivery—always grounded in real-world constraints.

🔍

1. Problem Discovery

We start by understanding what’s worth solving. This includes user research, service design, journey mapping, and stakeholder interviews—anything that helps us avoid guessing.

🔍

1. Problem Discovery

We start by understanding what’s worth solving. This includes user research, service design, journey mapping, and stakeholder interviews—anything that helps us avoid guessing.

🔍

1. Problem Discovery

We start by understanding what’s worth solving. This includes user research, service design, journey mapping, and stakeholder interviews—anything that helps us avoid guessing.

🧭

2. Business & Process Analysis

We also look inward. What are the organisation’s goals, bottlenecks, and technical limits? Understanding the system helps us make smarter choices about where and how to build.

🧭

2. Business & Process Analysis

We also look inward. What are the organisation’s goals, bottlenecks, and technical limits? Understanding the system helps us make smarter choices about where and how to build.

🧭

2. Business & Process Analysis

We also look inward. What are the organisation’s goals, bottlenecks, and technical limits? Understanding the system helps us make smarter choices about where and how to build.

🧩

3. Solution Design

Once we know the problem, we explore possible solutions. This includes Jobs to Be Done, impact mapping, co-creation workshops, and lightweight experiments. We decide what’s worth testing, and how.

🧩

3. Solution Design

Once we know the problem, we explore possible solutions. This includes Jobs to Be Done, impact mapping, co-creation workshops, and lightweight experiments. We decide what’s worth testing, and how.

🧩

3. Solution Design

Once we know the problem, we explore possible solutions. This includes Jobs to Be Done, impact mapping, co-creation workshops, and lightweight experiments. We decide what’s worth testing, and how.

🧪

4. Prototyping & UX Testing

Before any code is written, we test assumptions. We use wireframes, prototypes, and usability testing to validate whether the solution is understandable, usable, and promising.

🧪

4. Prototyping & UX Testing

Before any code is written, we test assumptions. We use wireframes, prototypes, and usability testing to validate whether the solution is understandable, usable, and promising.

🧪

4. Prototyping & UX Testing

Before any code is written, we test assumptions. We use wireframes, prototypes, and usability testing to validate whether the solution is understandable, usable, and promising.

⚙️

5. Agile Delivery & Iteration

We build in short, focused cycles—starting with an MVP. We work closely with engineers and designers to deliver value fast, and adapt as we go.

⚙️

5. Agile Delivery & Iteration

We build in short, focused cycles—starting with an MVP. We work closely with engineers and designers to deliver value fast, and adapt as we go.

⚙️

5. Agile Delivery & Iteration

We build in short, focused cycles—starting with an MVP. We work closely with engineers and designers to deliver value fast, and adapt as we go.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support go-to-market, onboarding, analytics, and post-launch learning. If it doesn’t reach the customer, it can’t solve the problem.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support go-to-market, onboarding, analytics, and post-launch learning. If it doesn’t reach the customer, it can’t solve the problem.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support go-to-market, onboarding, analytics, and post-launch learning. If it doesn’t reach the customer, it can’t solve the problem.

Anna-Liisa Reinson, Product Management
Anna-Liisa Reinson, Product Management
Anna-Liisa Reinson, Product Management

In empowered product teams, Product Managers are responsible for value and viability, while POs are responsible for delivery clarity.

Owns vision & strategy

Defines the product’s long-term direction and business goals.

Leads product discovery

Investigates user needs and validates ideas before building.

Writes user stories

Translates validated ideas into tasks for the team

Manages the backlog & execution

Order work items based on business and customer value and keeps delivery on track.

Aligns cross-functional teams

Coordinates across design, engineering, marketing, and stakeholders.

Aligns stakeholders

Get buy-in from execs, design, tech, marketing, and support

Focuses on outcomes, not output

Responsible for impact and business value—not just shipping features.

Product Manager

Own the product vision

Set the long-term direction and define what success looks like

Drive product strategy

Identify opportunities and shape where the product should go

Lead product discovery

Understand problems, test solutions, and reduce risk before building

Write user stories

Translate validated ideas into tasks for the team

Prioritise the backlog

Order work items based on business and customer value

Collaborate with engineering

Work closely with tech leads during delivery

Align stakeholders

Get buy-in from execs, design, tech, marketing, and support

Focus on outcomes, not output

Make sure what’s delivered solves real problems

Accountable for product success

Responsible for solving the right problem and delivering business value

Image Here
Anna-Liisa Reinson, Visiting Chief of Product - Photo: Jake Farra
Anna-Liisa Reinson, Visiting Chief of Product - Photo: Jake Farra
Image Here
Image Here
Image Here
Image Here

What Product Management Isn’t

What Product Management Isn’t

What the role should be—but often isn’t

There’s no shortage of product managers. But in many companies, they’re hired to fix delivery problems or fill in gaps—and not actually empowered to do product work. Here are a few common misconceptions:

Here are a few heading options for that section — introducing the idea that the role of a product manager is often misunderstood, and leading naturally into your Triple Diamond or 6-stage breakdown:

🤹‍♀️

Shouldn’t be a project manager

Product Managers should focus on what gets built and why, not just deadlines and delivery speed.

⛏️

Keeping the team busy isn't Product Managent

A Product Manager’s job isn’t to make sure the team always has something to do. It’s to figure out what’s most valuable to do — and why it matters.

💡

Not the only “idea person”

Product Managers bring direction, not ego. Their real job is to shape, challenge, and refine ideas with the team — not to push their own.

🧯

Shouldn’t fill every gap

A Product Manager’s job isn’t to quietly take on whatever roles are missing—marketing, sales, customer support, QA. If the team is understaffed, that’s a leadership problem, not a product one..

🧠

Shouldn’t have to know or pretend to know everything

A strong Product Manager asks better questions, frames problems, and makes trade-offs visible.


👯‍♂️

A Product Owner isn't the same as Product Manager

Product Owners manage the backlog. Product Managers shape the problem, define direction, and connect business, tech, and user needs.

Product management Audit in Product Organisations - Report
Product management Audit in Product Organisations - Report
Product management Audit in Product Organisations - Report
Product management Audit in Product Organisations - Report

Why Work This Way?

Why Work This Way?

The benefits of empowered product teams

The benefits of empowered product teams

1. Better decisions, faster

Teams talk to users, validate ideas, and make informed choices early—before time and money are wasted on the wrong thing.

2. Stronger business impact

Product managers focus on outcomes, not just features. The team’s work directly supports real business goals.

3. Motivated, accountable teams

When people help define the problem and solution, they feel ownership—not just pressure to deliver.

4. Continuous improvement

With integrated discovery and delivery, teams learn constantly and adapt without waiting for top-down direction.

Ready to build a real product organisation?

We help teams build real product capability through:


Product Trainings – practical, hands-on workshops

Mentoring & Coaching – support for Product Managers and product leads

Product Audits – clarity on what’s working and what’s missing


Let’s figure out what would help your team most.