What is Product Management?

What is Product Management?

From idea to delivery - and everything in between.

It’s more than sprints and backlogs. We break it down clearly- how to build impactful solutions from discovery to delivery.

Some of our customers and partners:

  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here
  • Logo Here

Simply put

Simply put

What does Product Management Cover?

According to Marty Cagan and John Cutler the definition of Product Management goes something like this: Product management is the practice of discovering valuable, usable, and feasible solutions - and delivering them in a way that drives real outcomes. It is is the ongoing process of creating alignment and learning loops that help teams deliver meaningful outcomes in complex, evolving environments.

🔍

1. Problem Discovery

We begin by uncovering what’s actually worth solving. Using service design methods, user interviews, and journey mapping, we identify real user needs and pain points—not assumptions.

🔍

1. Problem Discovery

We begin by uncovering what’s actually worth solving. Using service design methods, user interviews, and journey mapping, we identify real user needs and pain points—not assumptions.

🔍

1. Problem Discovery

We begin by uncovering what’s actually worth solving. Using service design methods, user interviews, and journey mapping, we identify real user needs and pain points—not assumptions.

🧭

2. Business & Process Analysis

Next, we look inside the organisation. We map internal processes, analyse workflows, and assess feasibility. This helps connect user needs to real business constraints and surface opportunities with measurable value.

🧭

2. Business & Process Analysis

Next, we look inside the organisation. We map internal processes, analyse workflows, and assess feasibility. This helps connect user needs to real business constraints and surface opportunities with measurable value.

🧭

2. Business & Process Analysis

Next, we look inside the organisation. We map internal processes, analyse workflows, and assess feasibility. This helps connect user needs to real business constraints and surface opportunities with measurable value.

🧩

3. Solution Design

Here we shape possible solutions using tools like Jobs to Be Done, impact mapping, and other workshops to align ideas with both user goals and business outcomes. The goal is to define a clear direction before building.

🧩

3. Solution Design

Here we shape possible solutions using tools like Jobs to Be Done, impact mapping, and other workshops to align ideas with both user goals and business outcomes. The goal is to define a clear direction before building.

🧩

3. Solution Design

Here we shape possible solutions using tools like Jobs to Be Done, impact mapping, and other workshops to align ideas with both user goals and business outcomes. The goal is to define a clear direction before building.

🧪

4. Prototyping & UX Testing

Before writing code, we test ideas. Through wireframes, clickable prototypes, and usability sessions, we validate core flows and reduce risk. This phase helps ensure what we build will actually work for the user.

🧪

4. Prototyping & UX Testing

Before writing code, we test ideas. Through wireframes, clickable prototypes, and usability sessions, we validate core flows and reduce risk. This phase helps ensure what we build will actually work for the user.

🧪

4. Prototyping & UX Testing

Before writing code, we test ideas. Through wireframes, clickable prototypes, and usability sessions, we validate core flows and reduce risk. This phase helps ensure what we build will actually work for the user.

⚙️

5. Agile Delivery & Iteration

With a clear direction, we build in short, iterative cycles—starting with an MVP. Using agile methods like Scrum or Kanban and close collaboration with engineering, we deliver working software quickly and keep refining it along the way.

⚙️

5. Agile Delivery & Iteration

With a clear direction, we build in short, iterative cycles—starting with an MVP. Using agile methods like Scrum or Kanban and close collaboration with engineering, we deliver working software quickly and keep refining it along the way.

⚙️

5. Agile Delivery & Iteration

With a clear direction, we build in short, iterative cycles—starting with an MVP. Using agile methods like Scrum or Kanban and close collaboration with engineering, we deliver working software quickly and keep refining it along the way.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support launch with onboarding, messaging, and tracking—then analyse usage and feedback to guide the next iteration. If it doesn’t reach the customer, it doesn’t solve the problem.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support launch with onboarding, messaging, and tracking—then analyse usage and feedback to guide the next iteration. If it doesn’t reach the customer, it doesn’t solve the problem.

🚀

6. Go-to-Market & Post-Launch

Shipping isn’t the end. We support launch with onboarding, messaging, and tracking—then analyse usage and feedback to guide the next iteration. If it doesn’t reach the customer, it doesn’t solve the problem.

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

Product Owner vs Product Manager

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

Product Owner

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

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
Image Here
Image Here
Image Here
Image Here
Image Here
Image Here

MORE THAN JUST EXECUTION

MORE THAN JUST EXECUTION

What Product Managers
Are Not

There is an abundance of organisations with product managers as one of the roles within the org. However, not all of those product managers practise product management as such. Not all organisations work with outcomes instead of output — or expect that of their PMs. Product managers are often hired as a remedy to some other issue: unclear ownership, delivery problems, or missing structure.

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

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

🛠

Keeping the team busy isn't Product Managent

A PM’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”

PMs 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 PM’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 PM 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?

If you're tired of backlog maintenance disguised as product work — you're not alone. We help teams move from delivery-focused to outcome-driven through:


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