Product Team Competencies Framework for Product Managers

Created by Neal Cabage - https://nealcabage.com/framework/product-team-competencies/

Overview

The Product Team Competencies Framework is Neal Cabage's map of the product manager competencies that the role commonly covers, laid out on one chart so a leader can see which skills an individual PM or a whole product team is strong in and which are missing. Cabage describes it on his Product Team Competencies page as a map of the core skills effective product managers need, built because product management looks different at every company and people are confused about what skills a PM should actually have. He writes that he struggled with this question while learning the craft, and later wanted a way to articulate the full range of product capabilities as a leader.

The chart has two axes. The vertical axis runs from Strategic at the top to Tactical at the bottom. The horizontal axis runs from External on the left to Internal on the right. Along the horizontal band Cabage places five categories, in this order from left to right: Users, Market, Core Product, Business and Technical. Each category holds three competencies above the band, on the strategic side, and three below it, on the tactical side. Under Users, for example, Jobs to be Done sits at the top and Process Feedback at the bottom. Under Technical, Innovation sits at the top and Data Queries at the bottom. The grid in the next section lists every box as it appears on Cabage's diagram.

Cabage uses the two axes to describe where different kinds of PMs spend their time. In his words, junior product managers tend to focus at the bottom of the chart, while senior PMs who think strategically operate in the upper part, "especially team leads, Directors." Technical PMs who work on internal tools and platforms focus on the right side, and PMs on consumer-facing products focus on the left. From those two readings he derives a quadrant for each PM: upper-left for a senior B2C PM, lower-right for a junior internal tools PM (Cabage, Product Team Competencies).

The framework is explicitly not a checklist every PM must complete. Cabage states that it "does not assume every PM should be able to do all of these things." Its purpose is to show what an individual PM should be good at if they want to focus in one direction, and to give leaders a map for balancing a team, so they can see where the team is heavy on some skills and has gaps in others. His worked example is a team lacking in external market strategy: he redraws the chart with the strategic Users and Market boxes greyed out, which makes the deficiency visible for the team to rally around in the coming year.

The model grows out of Cabage's broader view of the role. In The Role of Product Management he argues that the job varies with the type of product (B2C, B2B or internal), with seniority, and with where product reports in the organization, and that the Scrum Product Owner role shifted many product people from strategic product-market fit work toward a more tactical role. He also notes that the role of a junior PM is often more "heads down," focused on feature definition and development. His competencies page includes a companion graphic that contrasts a market-facing "Heads Up" profile (product vision, opportunity discovery, roadmap definition, product evangelism, outcome and KPI ownership) with a technical "Heads Down" profile (Scrum product owner, requirements definition, backlog management, team solution design, launch and release planning). Cabage founded the Product Managers Association of Los Angeles as a Meetup group in 2012, according to his PMA.LA page.

The diagram on Cabage's page carries the mark "@nealcabage 2018" (Cabage), and the product management site Productfolio, in its summary of the framework, dates it "Cabage 2017." Productfolio reads the top half as the competencies for senior "heads up" PMs and the bottom half as the ground of "heads down" Product Owners, and, citing Cabage's example, suggests that a team weak in external market strategy pay more attention to the top-left section, reallocate time, or hire accordingly.

Other PM competency models take different shapes. Ravi Mehta's Product Competency Toolkit groups twelve competencies into four areas and rates each one, and Marty Cagan's skills assessment for product managers scores importance and ability per skill as a gap analysis. As a PM skills framework, Cabage's grid is a spatial map with no rating scale of its own. It shows where a skill sits and who covers it, and teams that need scores add a rating scale on top.

The Competency Grid

The table lists the competencies on Cabage's chart, category by category from the external side to the internal side, exactly as they are labelled on his diagram. Strategic cells list the boxes from the top of the chart down to the band, and tactical cells list them from the band down to the bottom.

Two placements are easy to miss. Product-Market Fit sits below the band, on the tactical side of Market. And the internal side is Business and Technical work, such as portfolio planning, build versus buy decisions and system analysis, rather than people management, which does not appear on the chart as a category.

Core Principles

Map the whole role, then choose a direction

Cabage built the chart to describe the full range of skills associated with product management. A PM is not expected to master every box, and the chart helps them decide which direction to grow in (Cabage). Treat the grid as a menu of specialisms. A development conversation that asks a PM to fill every box produces a vague plan and a discouraged PM.

Height on the chart tracks seniority

The vertical axis doubles as a seniority axis. Cabage places junior PMs at the bottom and senior, strategic PMs, especially team leads and directors, in the upper part. Promotion conversations can therefore ask whether a PM is doing more of the work above the band, such as opportunity discovery, roadmap and business case work. A PM who only gets faster at backlog grooming and requirements has improved without moving up the chart.

Left and right track the kind of product

Consumer-facing products pull PMs to the left, toward users and market. Internal tools and platforms pull technical PMs to the right, toward business and technical work (Cabage). Combining the two axes gives each role a home quadrant, such as upper-left for a senior B2C PM. Use that quadrant to write roles and to judge fit before comparing PMs with each other.

Balance belongs to the team

Cabage's closing point is that a balanced product team, in which members complement each other and the necessary skills are represented, supports success across the product portfolio. Individual PMs can be deliberately uneven if the team as a whole covers the grid. Mehta makes a similar argument in What's Your Shape?: "Individuals should be spiky; teams should be well-rounded."

Make gaps visible so the team can act on them

The greyed-out version of the chart is how Cabage illustrates a gap. By dimming the boxes nobody covers, a leader shows the team exactly where it is thin, in Cabage's example the strategic users and market work. A picture of the gap is easier to agree on than a list of individual weaknesses. It also points at the three responses Productfolio draws from the example: pay more attention to that area, reallocate time, or hire.

Context decides which boxes matter

The same chart applies to very different teams because the weight of each box changes with context. Cabage's account of the role says B2C work puts more weight on user experience and discovery, while B2B and internal users tell you what they want and saying no becomes a key skill (The Role of Product Management). Productfolio adds that new startups, or companies launching new products, may prefer someone strong in user research and product-market fit. Decide which boxes your situation needs before you judge anyone against them.

Steps

1. Adopt the grid and agree on definitions Start from Cabage's five categories and their competencies as published, and write one sentence per box describing what the work looks like at your company. Some labels need a local definition: Product Council, for example, only makes sense if your company has one. Mark any box that does not apply to your products and add a box only when real, recurring work has no home. Keep the two axes as they are, because the seniority and product-type readings depend on them. The output is one shared page that every PM and manager reads the same way.

2. Place each role on the chart For every PM role you have or plan to hire, mark its home quadrant using Cabage's two readings: seniority for height and product type for left or right. A senior PM on a consumer app sits upper-left. A junior PM on internal tooling sits lower-right. Write down which categories matter most for each role and why. This becomes the reference that later assessments, job descriptions and interview loops use.

3. Assess each PM against the boxes Ask each PM to mark the boxes they practice regularly and those they do well, then have their manager do the same independently. Cabage's page does not define a rating scale, so choose a simple one, or borrow the gap-analysis approach from Cagan's skills assessment, which rates both how important a skill is for the role and how strong the person is. Discuss differences between the two views using examples of recent work. Frame the exercise as development, so people report honestly.

4. Overlay the team and grey out the gaps Combine the individual results into one chart for the team, which is the product team assessment itself. Shade boxes that several PMs cover and grey out boxes nobody covers, the way Cabage does in his external market strategy example. Look for gaps by region as well as by box: an empty top-left means nobody is doing strategic user and market work. Compare the picture with what the product needs right now, since a gap in a box the team does not need is not a problem.

5. Decide how to close each gap For each gap that matters, choose between the responses Productfolio draws from Cabage's example: shift attention toward the area, reallocate time between PMs, or hire for it. Growth for an existing PM usually means giving them work in the empty boxes. Hiring means writing a role whose home quadrant is the gap. Record the decision and an owner so the gap is tracked instead of noted and forgotten.

6. Turn gaps into individual development plans For each PM, pick a small number of boxes to grow in, chosen by the direction they want to take and the team's gaps. Cagan's advice in his assessment article is to focus on the top 3 areas and review progress at least once a month. Pair each focus area with real work in that box, such as leading a competitive gap analysis or writing a business case. When the gaps close, show the PM how expectations change at the next level.

7. Redraw the chart when the team or product changes The team chart is a snapshot. Redraw it when people join or leave, when a new product line starts, or when the product moves from finding product-market fit to serving many stakeholders, a shift Cabage describes in The Role of Product Management. Compare the new chart with the previous one to see whether development plans and hires actually filled the gaps. Keep old versions so progress is visible.

When to Use

• A product team has grown beyond a few PMs and nobody can say what strong looks like, so reviews and promotions depend on each manager's personal view. A shared chart gives everyone the same reference.
• You are hiring and need to decide what kind of PM to hire. Cabage names this use directly: the chart shows what type of PM a given product role needs.
• A PM asks how to become senior. The vertical axis shows the move toward the strategic work above the band.
• A reorganization, acquisition or departures have changed the team. Redrawing the chart shows which boxes lost their only owner.
• Two PMs keep disagreeing on priorities. Placing both on the chart often shows one working in strategic market boxes and the other in tactical technical boxes, which explains the friction.
• You are setting up a coaching program for junior PMs and need a map of what skills they could acquire next, a use Productfolio highlights.

When Not to Use

• There is only one PM. The team-balance view needs several people, so a simple personal development plan does the job.
• You need to judge one project's outcome. The chart describes standing competencies, so a retrospective or outcome review fits better.
• The real problem is an unclear boundary between product, project and engineering management. The grid assumes you know what the PM role owns. Settle that boundary first.
• You need a numeric leveling scale tied to pay bands. Cabage's grid has no rating scale, so use a detailed leveling matrix such as Mehta's, which describes expectations from APM to VP.