What you'll learn: What each maturity tier means for your team on Monday morning, how to read the shape of your radar chart, which dimensions to prioritize, and concrete next steps by tier.
You took the PM Team Maturity Assessment. You've got a number out of 27, a tier name, and a radar chart. Maybe a dollar figure that made you wince.
Now the question is: what does any of it mean for your team on Monday morning?
Your PM maturity score isn't a grade. It's a diagnostic. It tells you where your PM operation runs on shared systems and where it runs on individual effort. That distinction determines whether your team gets stronger as it grows or just busier.
This guide walks through each tier, how to read the shape of your radar chart, which dimensions to prioritize, and what to do next based on where you landed. If you haven't taken the assessment yet, start there — it takes five minutes — then come back.
The most common pattern I see is Heads of Product overestimating their Discovery and Strategy scores while underestimating Operations. Teams assume they "do discovery" because they talk to customers occasionally. But when you dig into it, there's no shared system for capturing and synthesizing what they learn. The gap between "we do this sometimes" and "we have infrastructure for this" is where most teams lose points — and most hours.
Understanding the Four AI PM Maturity Tiers
The assessment scores nine dimensions of PM operations on a 0-3 scale, for a maximum of 27. Your total maps to one of four tiers. Each tier represents a fundamentally different operating mode, not just a different score.
Ad Hoc (0-6)
Your PM team is running on individual heroics. Every PM invents their own process. Quality depends entirely on who does the work, and when someone leaves, their knowledge leaves with them.
What this looks like day-to-day: Three PMs on your team, three completely different ways of writing PRDs. Nobody knows what customer insights anyone else has gathered. Prioritization debates are settled by whoever has more exec access. When someone goes on vacation, their workstream stalls because nobody else has the context.
The biggest risk: You're building an operation that can't survive personnel change. Every PM is a single point of failure for their area. You don't have a PM operation — you have a collection of individual PM practices that happen to coexist.
Where to start: Don't try to fix everything. Pick the one dimension that would make the biggest difference and build a shared system there. For most Ad Hoc teams, that's either Discovery (so insights stop living in individual notebooks) or Specs (so engineering gets consistent inputs regardless of which PM wrote them).
Watch out — Ad Hoc teams don't have a PM operation. They have a collection of individual PM practices that happen to coexist. Every PM is a single point of failure for their area.
Your first move: Get the fundamentals in place. You need a shared foundation before anything else compounds. The PM Operating System is designed for exactly this stage — it gives every PM on the team the same infrastructure from day one, covering all nine dimensions. If you want guidance on where to start for your specific situation, book a discovery call.
Assisted (7-13)
AI helps individual PMs, but not the team. You have started using AI tools, but each PM has their own prompts, their own workflows, their own way of getting output. The gaps between PMs are where things fall through the cracks.
What this looks like day-to-day: Your team has a PRD template, but only one PM uses it consistently. You run customer interviews, but the insights don't flow to the rest of the team. You've got a planning cadence, but the prioritization framework changes every quarter. Some dimensions feel solid. Others feel like they're held together by one person's willpower.
The biggest risk: Unpredictable quality. You can't tell from the outside which parts of your operation will hold up under pressure and which will break. A strong quarter masks the gaps. A bad quarter exposes all of them at once.
Where to focus: Look at your radar chart. Which dimensions scored 0 or 1? Those are your critical gaps — the ones that are actively costing you hours every week. Don't spread your effort across all nine dimensions. Close the biggest individual gaps first.
Your first move: Identify your two or three lowest-scoring dimensions and get targeted tools in place. Browse the skills library filtered to those categories. If you want the full system and a faster path, the PM Operating System fills the gaps so your whole team operates at the level of your best PM.
PM OS (14-20)
Your PM operation runs on shared infrastructure. You have built real PM infrastructure. Shared context, shared skills, consistent output across the team. Specific gaps remain, but targeted investment compounds fast.
What this looks like day-to-day: Your team has real infrastructure. PRDs are consistent. There's a planning framework. Customer insights mostly flow where they need to go. But two or three dimensions lag behind the rest — and those are the ones that keep causing problems. Maybe your launches still surprise cross-functional teams. Maybe your competitive intelligence is stale. Maybe knowledge transfer is still manual.
The biggest risk: Assuming the remaining gaps are minor. They're not. A team scoring 16 out of 27 has 11 gap points. At 50 hours per gap point per PM per year, that's still significant. The gap between PM OS and Autonomous PM OS is the difference between a team that works well most of the time and a team that works well systemically.
Where to focus: Your radar chart will have a clear shape — mostly high scores with two or three valleys. Those valleys are your highest-leverage investments. Because everything else is already strong, fixing those specific dimensions will have outsized impact.
Your first move: Your gaps are specific enough that generic advice won't help. Book a discovery call to discuss targeted implementation for your exact situation. Or if you want to start immediately, grab the PM Operating System and focus on the skills that map to your lowest dimensions.
Autonomous PM OS (21-27)
Your PM operation runs and improves itself. Your team has a fully operational PM OS. Context enriches automatically, workflows run on schedules, new PMs ramp in weeks. The system gets smarter with every interaction.
What this looks like day-to-day: A new PM joins and is productive within weeks, not months. Board updates take 30 minutes, not half a day. Any PM can pick up any spec and understand what's being built. Launches are coordinated events, not surprises. The system works even when individual people are out.
The biggest risk: Complacency. Systems decay without maintenance. The processes that got you here were designed for the team you had when you built them. As the team grows, the market shifts, and the product evolves, those systems need to evolve too. The other risk is assuming you've solved everything — there's always a dimension that could be sharper.
Where to focus: Optimization and resilience. Look at your radar chart for any dimension below 3 and ask whether closing that gap would matter. Consider how your systems will hold up when the team grows from 4 to 7 PMs. Invest in making the operation self-maintaining, not just functional.
Your first move: You've built the discipline. Now explore managed PM intelligence for ongoing optimization, or browse the skills library to find AI-powered acceleration for your already-strong operation.
Watch out — This is a self-assessed score, not an external audit. Teams tend to overrate dimensions where they've recently invested and underrate dimensions they haven't thought about. For the most honest picture, have each PM take the assessment independently and compare radar charts — the gaps between individual scores often reveal more than the averages.
Reading Your Radar Chart
The radar chart from the assessment shows your score across all nine dimensions. The shape matters as much as the total score — sometimes more.
Balanced but low
If your chart looks like a small, roughly even shape, you have a systemic issue. No single dimension is catastrophically bad, but none of them are good either. This pattern is common in teams that have grown organically without anyone deliberately building PM infrastructure.
What it means: The problem isn't one specific area. It's that there's no shared operating system underneath the team. Individual PMs have developed their own workarounds, but nothing connects.
What to do: You need a foundation, not targeted fixes. Start with something that covers the full surface area — the PM Operating System is built for this pattern — rather than trying to fix one dimension at a time.
Spiky
If your chart has tall peaks and deep valleys, you have specific strengths and specific weaknesses. This is the most common pattern. It usually means one or two PMs brought strong practices in certain areas, but other areas never got the same attention.
What it means: Your strengths are probably dependent on specific people. The valleys represent areas where nobody has built shared infrastructure yet. Those valleys are where problems concentrate.
What to do: Target the valleys. Your high-scoring dimensions are already working — don't spend energy there. Look at your two or three lowest dimensions and invest there first. The companion article on the nine dimensions breaks down what good looks like for each one.
One dimension at zero
If any dimension scored 0, that's a critical gap that's probably costing you more than you realize. A zero means there's no system at all — not even an informal one. Everything in that area runs on improvisation.
A zero means you have a blind spot. The cost is invisible — it shows up as rework, miscommunication, and missed opportunities that nobody attributes to the root cause.
What to do: Fix the zero first. Read the cost analysis to understand what that gap is costing in dollars and hours. A zero-to-one improvement in any dimension has outsized impact because you're going from nothing to something.
The Three Highest-Impact Dimensions to Fix First
Not all nine dimensions carry equal weight. Three of them have outsized impact because of where they sit in the product development chain. If you're unsure where to start, start with one of these.
Discovery
Discovery is the foundation for everything downstream. If your team doesn't have a shared system for customer insight, every other dimension is built on incomplete information. Strategy is guesswork. Prioritization is political. Specs are based on assumptions instead of evidence.
A team with weak discovery builds the wrong things confidently. A team with strong discovery makes mistakes too, but they're smaller and they correct faster.
If your Discovery score is 0 or 1: This is your highest-leverage investment. Before fixing specs or planning or anything else, fix the flow of customer insight into product decisions.
Specs
Inconsistent specs create engineering rework, and engineering rework is one of the most expensive forms of PM inefficiency. When a spec is ambiguous, engineering guesses. When they guess wrong, the feature gets rebuilt. Multiply that across every feature, every sprint, every quarter.
Specs also affect everything downstream. Sales enablement, launch materials, and support documentation all depend on clear specs. When the spec is murky, everyone downstream is working with incomplete information.
If your Specs score is 0 or 1: Get a shared template and make it the default. Consistency matters more than perfection here. A good template used by everyone beats a great spec format used by one PM.
Operations
Operations is the dimension that makes all the others durable. You can score a 3 on every other dimension today, but if those capabilities live in individual people instead of shared systems, you're one resignation away from losing them.
Operations affects knowledge transfer, onboarding speed, and organizational resilience. It's the difference between a team where new PMs take six months to ramp and a team where they're productive in weeks.
If your Operations score is 0 or 1: Document what your best PM does. Not everything — start with the processes that would hurt most if that person left. That's your operations foundation.
What to Do Next, By Tier
Here's a concrete action plan based on where you landed.
If you scored Ad Hoc (0-6)
You need a foundation, not piecemeal fixes. Adding one tool or one template won't solve a systemic gap.
- Get the PM Operating System. The $499 PM OS gives your team 70+ skills across all nine dimensions. It's designed for teams that need to go from individual heroics to a shared system.
- Or talk to us first. If you're not sure where to start, book a discovery call. We'll look at your specific scores and recommend the fastest path to impact.
- Don't try to fix everything at once. Even with a complete system, roll it out dimension by dimension. Start with Discovery or Specs.
If you scored Assisted (7-13)
You have momentum. The goal is to close your biggest gaps without losing what's already working.
- Identify your lowest dimensions. Look at your radar chart. Which dimensions scored 0 or 1? Those are your priorities.
- Get targeted skills. Browse the skills library filtered to your weakest categories. Download the ones that address your specific gaps.
- Consider the full system. If you have gaps across three or more dimensions, the PM Operating System is more efficient than solving each gap individually.
If you scored PM OS (14-20)
Your infrastructure is real. The remaining gaps are specific and addressable.
- Name your gaps. Your lowest two or three dimensions are holding back the whole operation. Write them down.
- Book a discovery call. At this tier, your gaps are specific enough that a conversation about your exact situation will be more valuable than generic recommendations.
- Target your lowest dimensions with skills. If you want to move immediately, grab the skills that map to your valleys. You don't need the whole system — you need the right pieces.
If you scored Autonomous PM OS (21-27)
You're ahead of most PM teams. The work now is sustainability and optimization.
- Audit for decay. Which systems were designed for a smaller team or an earlier product stage? Those are your maintenance priorities.
- Explore managed PM intelligence. At this level, ongoing optimization matters more than one-time setup. Talk to us about how to keep the operation sharp as you scale.
- Share the assessment. Have every PM on the team take it independently. Compare radar charts. The aggregate view will show you gaps that no individual perspective reveals.
Share Your Results
Three things you can do right now.
Retake the assessment. If you rushed through it or want to reconsider a few answers, take it again. The assessment is designed to be taken more than once — scores should change as your operation improves.
Share with your team. Have each PM take the assessment individually, then compare results. The disagreements are where the real insight lives. If you scored your Specs dimension at 2 and another PM scored it at 1, that conversation is worth having.
Talk to us. If you're a Head of Product looking at these results and thinking about what to build next, book a discovery call. We'll translate your scores into a prioritized plan for your specific team.
Build this for your team → We help Heads of Product translate maturity scores into a prioritized implementation plan — closing the gaps that cost the most hours first. See how it works →
The score isn't the point. The point is knowing where to invest your limited time and budget so your PM operation gets stronger, not just busier.
About the Author
Ron Yang is the founder of mySecond — he builds and manages PM Operating Systems for product teams. Prior to mySecond, he led product at Aha! and is a product advisor to 25+ companies.