Model 65 of 74 · Customer & Growth

Product Management Maturity Assessment

Assess how well your organisation decides what to build, why, and whether it worked.

Levels

  1. 1Order-TakingBuilding what's asked
  2. 2Discovery-DrivenEvidence-informed
  3. 3Outcome-LedEmpowered & measurable

01 Product Strategy & Vision

Does each product have a clear vision and strategy linked to the organisation's goals?

0/4 answered

SV-1How clearly is the vision and strategy for each product defined?

Think about whether a product team could explain who the product is for, what problem it solves and how it will win, without referring to a feature list.

SV-2How well does product strategy connect to company strategy?

Consider whether product investment decisions clearly support the organisation's wider goals.

SV-3How well does your organisation understand its market and competitors?

Think about market size, segments, trends and competitor moves, and whether that knowledge reaches product decisions.

SV-4How are product investment decisions made across the portfolio?

Consider how the organisation decides which products receive more or less investment.

02 Customer Discovery & Insight

Are product decisions grounded in real evidence about customers' needs and behaviour?

0/4 answered

CD-1How often do product teams speak directly with customers?

Think about whether product managers, designers and engineers have regular, direct contact with the people who use the product.

CD-2How well do product teams understand the problems they are solving?

Consider whether teams can describe the customer problem and its importance before discussing solutions.

CD-3How are product ideas tested before significant investment?

Think about prototypes, experiments and other ways of checking that an idea will work before building it fully.

CD-4How is customer insight shared and reused?

Consider whether research findings are accessible to everyone, or stay in individual documents and heads.

03 Prioritisation & Roadmapping

Are priorities set transparently using clear criteria, and communicated through useful roadmaps?

0/4 answered

PR-1How are product priorities decided?

Think about whether priorities follow clear, agreed criteria or the opinion of the most senior or loudest person.

PR-2How are requests from sales, customers and executives handled?

Consider whether requests go straight onto the roadmap, or are assessed alongside other opportunities.

PR-3What do product roadmaps look like?

Think about whether roadmaps list features with fixed dates, or communicate goals and problems to solve.

PR-4How are delivery commitments made?

Consider whether dates are promised before the work is understood, and what happens when plans change.

04 Delivery Collaboration & Launch

Do product, design and engineering work as one team, and are launches planned for success?

0/4 answered

DL-1How closely do product, design and engineering work together?

Think about whether they collaborate from the start, or hand work over in sequence.

DL-2How are launches coordinated with marketing, sales and support?

Consider whether go-to-market teams are ready when new products or features are released.

DL-3How are new features released to customers?

Think about whether releases go to everyone at once, or are rolled out gradually so risks can be managed.

DL-4How is launch success judged?

Consider whether success means 'it shipped' or 'it achieved what we expected'.

05 Product Measurement & Analytics

Does the organisation measure how products are used and whether they deliver value?

0/4 answered

MA-1What does your organisation measure about its products?

Think about usage, engagement, retention, satisfaction and business results, not just revenue or delivery dates.

MA-2How well instrumented are your products?

Consider whether you can see how customers actually use the product, or rely on assumptions.

MA-3How does your organisation use experiments to make product decisions?

Think about whether changes are tested against alternatives to see what works better.

MA-4How does data influence product decisions?

Consider whether data is used to make decisions, or to justify decisions already made.

06 Product Lifecycle & Capability

Are products managed across their whole life, and is product management capability developed?

0/4 answered

LC-1How are products managed across their lifecycle?

Think about whether products are reviewed as they mature, and whether underperforming products or features are ever retired.

LC-2How is the balance between new features and maintaining product health managed?

Consider technical debt, usability debt and reliability, and whether they are given time alongside new features.

LC-3How well defined is the product manager role?

Think about whether product managers make product decisions, or mainly coordinate projects and write requirements.

LC-4How does your organisation develop product management capability?

Consider training, coaching, shared practices and tools that help product teams work well.

Self-assessment report

Product Management

Answer the questions above and your report builds here: an overall score, a score and target for each area, and the three changes that matter most.

About this model

About this assessment

About the Product Management maturity model

Building things is rarely the hardest part. The hardest part is deciding what is worth building: which problems matter most to customers, which ideas will actually solve them, and how they create value for the organisation. Without good product management, teams work hard on features nobody uses, roadmaps become lists of promises to the loudest stakeholders, and success is measured by what was shipped rather than what changed.

This model assesses product management as a discipline that connects customer needs, business goals and delivery. It looks at whether products have a clear strategy, whether decisions are grounded in evidence about customers, how priorities are set and communicated, how launches are handled, whether outcomes are measured, and how products are managed across their whole life. It applies to digital and physical products, internal platforms and services that are managed as products.

The Product Management maturity model contains 24 questions across 6 areas: product strategy and vision, customer discovery and insight, prioritisation and roadmapping, delivery collaboration and launch, product measurement and analytics, and product lifecycle and capability. Each question describes three levels of maturity through observable practices. It complements the Product / Service Delivery model, which focuses on how products and services are delivered and fulfilled.

Who this assessment is for

  • Chief product officers, heads of product and product leaders
  • Product managers and product owners
  • Founders and executives of product-led companies
  • Engineering, design and research leaders who work alongside product teams
  • Organisations moving from project-based delivery to product-based operating models

The three maturity levels

  • Level 1 — Order-Taking: Product decisions are driven by requests from sales, senior leaders or the biggest customers. Roadmaps are lists of features with dates, rarely linked to a strategy or customer evidence. Product managers act as project coordinators, discovery is minimal, and launches are treated as the finish line. Nobody measures whether features are used or whether they achieved anything.
  • Level 2 — Discovery-Driven: Each product has a documented strategy and vision. Product teams talk to customers regularly, test ideas before committing to build them, and prioritise using agreed criteria. Roadmaps communicate themes and goals rather than only dates, launches are planned with go-to-market teams, and adoption and key metrics are tracked after release.
  • Level 3 — Outcome-Led: Product strategy is tightly linked to company strategy and expressed as outcomes. Empowered, cross-functional product teams discover the best solutions through continuous customer contact and rapid experimentation. Investment follows evidence, products are managed through their whole lifecycle including retirement, and the organisation consistently builds products customers value and that move business results.

The 6 areas assessed

1. Product Strategy & Vision

The direction that guides product decisions. This area covers product vision, strategy and target customers, the link between product strategy and company goals, understanding of the market and competition, and how the strategy is communicated and used.

2. Customer Discovery & Insight

How product teams learn about customers and test ideas. This area looks at the frequency of customer contact, the quality of problem understanding, how ideas are validated before they are built, and how insight is shared and reused.

3. Prioritisation & Roadmapping

How the organisation decides what to work on next and communicates plans. This area covers prioritisation criteria, handling stakeholder requests, the format and purpose of roadmaps, and how commitments are made.

4. Delivery Collaboration & Launch

How product decisions turn into products in customers' hands. This area covers collaboration between product, design and engineering, go-to-market coordination, release practices, and how launches are judged.

5. Product Measurement & Analytics

How product performance is understood. This area covers product metrics and instrumentation, the use of experiments, customer satisfaction and feedback measures, and how data influences product decisions.

6. Product Lifecycle & Capability

How products are managed from introduction to retirement, and how the product discipline itself is built. This area covers lifecycle management, technical and product debt, the role and skills of product managers, and product operations practices.

How this model relates to other frameworks

This is an original, simplified maturity model and is not derived from or intended to replace any of the following. However, organisations that use this assessment may also find value in these established frameworks:

  • Pragmatic Framework — a widely used framework describing product management and marketing activities
  • ProdBOK (Product Management Body of Knowledge) — a body of knowledge for product management published by the Association of International Product Marketing and Management
  • Continuous discovery and opportunity mapping practices — approaches popularised by product practitioners for regular customer research
  • Lean Startup — an approach to testing business and product hypotheses through rapid experimentation

Frequently asked questions

What is the Product Management maturity model?

Assess how well your organisation decides what to build, why, and whether it worked. It is an original, simplified model with three maturity levels (Order-Taking, Discovery-Driven and Outcome-Led), assessed through 24 questions across 6 areas: Product Strategy & Vision, Customer Discovery & Insight, Prioritisation & Roadmapping, Delivery Collaboration & Launch, Product Measurement & Analytics and Product Lifecycle & Capability.

How long does the Product Management assessment take?

Most people finish in 10–14 minutes. Each of the 24 questions has three concrete answer options. Your progress is saved in the page URL, so you can bookmark it and come back later.

How is the score calculated?

Each answer scores 1 (Order-Taking), 2 (Discovery-Driven) or 3 (Outcome-Led). An area's score is the average of its answered questions, and the overall score is the average of the area scores, so every area counts equally. Scores run from 1.0 to 3.0.

Is my data stored or shared?

No. Your answers are never sent to a server. They are stored only in the page URL, which you control. Copy the link to share results with colleagues, or export a PDF or CSV report.

How should I use the results?

Start with "Where to focus" in your report. It lists the questions with the biggest gap to the target you set for each area, and shows what the next level looks like in practice. For a fuller picture, ask several people from different teams to complete the assessment and compare their links. Differences in perception are often as revealing as the scores themselves.