Building Personalized PM Career Development Plans Using Competency Data
This skill teaches you how to translate raw competency assessment scores into a structured, time-bound career development plan that tells a product manager exactly what to work on, how to work on it, and how to measure progress toward their next role.
Start by mapping your current competency scores across all four quadrants of a PM competency framework: strategic, tactical, internal, and external. Compare those scores to the target profile for your desired next role. Identify the two or three largest gaps, then build a 90-day plan for each gap with specific learning activities, stretch assignments, and measurable milestones. Review progress monthly and adjust priorities based on real performance evidence.
Outcome: You produce a written career development plan with prioritized competency gaps, specific development activities for each gap, clear milestones, and a review cadence, so both the PM and their manager know exactly what growth looks like and how to track it.
Prerequisites
- A completed competency assessment for the PM (see assessing-pm-team-strengths-and-gaps)
- Defined competency expectations for the PM's current and target level (see defining-competency-levels-from-associate-to-senior-pm)
- Understanding of the four-quadrant competency model (strategic vs. tactical, internal vs. external)
- Access to the PM for a collaborative planning conversation
Overview
Every product manager who has ever asked "how do I become a product manager at the next level?" has run into the same frustration: the answer is vague. Managers say things like "show more strategic thinking" or "develop stronger technical skills," but they rarely explain what that looks like in daily work, how to practice it, or how to prove you have improved. This skill closes that gap by turning competency assessment data into a concrete, personalized career development plan that a PM can actually execute.
The Product Team Competencies Framework gives you the diagnostic layer. It maps PM competencies across strategic vs. tactical and internal vs. external axes, and it defines what proficiency looks like at each seniority level. Once you have completed an assessment (covered in Assessing Product Team Strengths and Identifying Skill Gaps), you have a data-rich snapshot of where a PM stands today. This skill picks up exactly where that assessment ends. It takes the scored competency profile and transforms it into a living document: a prioritized list of gaps, a sequenced plan of development activities, measurable milestones tied to real work, and a review cadence that prevents the plan from becoming shelfware.
The artifact you produce is a written career development plan, typically a one-to-three page document or structured template. It contains four sections: a current state summary with competency scores, a target state summary with the scores expected at the next level, a prioritized gap list with no more than three active focus areas, and a 90-day action plan for each focus area specifying learning resources, stretch assignments, coaching touchpoints, and success criteria. For anyone researching how to become a product manager or advance within a PM career track, this plan is the operational bridge between "where am I" and "where do I need to be."
When done well, development plans accelerate promotion timelines, reduce ambiguity in performance reviews, and give PMs genuine ownership of their growth. When done poorly, they become HR paperwork that sits in a shared drive untouched. The difference lies entirely in how specific and actionable the plan is, which is what the steps below are designed to guarantee.
How It Works
The core logic behind this skill is gap-based prioritization combined with deliberate practice design. It works because it replaces the two failure modes of typical career development: trying to improve everything at once (which spreads effort too thin to produce visible growth) and improving things that do not actually matter for the target role (which wastes months on the wrong competencies).
The Product Team Competencies Framework defines competencies along two axes. The strategic-tactical axis captures whether a skill is about setting direction or executing against it. The internal-external axis captures whether a skill faces the team and organization or faces the market and customers. Every PM role weights these quadrants differently. A growth PM leans heavily into external-tactical competencies like experimentation and analytics, while a platform PM leans into internal-strategic competencies like technical architecture decisions and cross-team alignment. When you assess a PM against the profile of their desired next role, you get a numerical gap for each competency. Some gaps are large, some are small, and some competencies may already exceed the target.
The trick is that not all gaps carry equal weight. A PM who scores 2 out of 5 on stakeholder management and 3 out of 5 on competitive analysis has two gaps, but the stakeholder management gap will block their promotion faster because it is more visible and harder to compensate for with other strengths. The prioritization step forces you to rank gaps by a combination of gap magnitude, role criticality, and visibility to decision-makers. You then select no more than three gaps to actively work on in any given quarter.
Once you have prioritized gaps, the plan shifts to activity design. This is where most development plans fail. They list vague activities like "read a book on strategy" or "take an online course." Effective plans instead specify what the PM will do differently in their actual job. A stretch assignment carries ten times the development value of a course because it forces application under real constraints. The plan should pair each gap with one primary stretch assignment, one learning resource for foundational knowledge, one coaching or feedback mechanism, and one observable milestone that both the PM and their manager can evaluate. The milestone is critical because it converts subjective growth into something you can both see.
The 90-day cycle matters because it is long enough to show real improvement on a competency but short enough to maintain urgency and allow course correction. At the end of each cycle, you reassess the competency scores, celebrate progress, and decide whether to continue deepening the same gaps or rotate to new ones. This creates a compounding effect: each quarter, the PM gets measurably closer to their target profile, and both parties have evidence to support promotion conversations when the time comes.
This approach also works for people figuring out how to become a product manager from an adjacent role. The same gap analysis applies, except the "current state" may show zeros or ones across most competencies, and the target state is the Associate PM profile rather than the next rung on a ladder. The plan then emphasizes foundational learning more heavily and uses smaller stretch assignments to build initial evidence of capability.
Step-by-Step
Step 1: Gather and Validate the Competency Assessment Data
Pull the PM's most recent competency assessment scores. This should be a numerical rating for each competency in the framework, scored by the PM (self-assessment) and ideally by their manager or peers as well. Before building a plan, validate that the data is current and credible. Check the assessment date: if it is more than three months old, consider whether significant projects or role changes have shifted the picture.
Compare the self-assessment to the manager assessment and flag any competencies where scores diverge by two or more points, since those disagreements need to be resolved before you can prioritize accurately. Create a simple table listing every competency, the self-score, the manager score, and a consensus score. If no formal assessment exists yet, run one first using the process described in the sibling skill on assessing PM team strengths and gaps.
Tip: When self-scores and manager scores diverge significantly, do not simply average them. Schedule a 15-minute calibration conversation for each disputed competency. Ask the PM for a specific recent example that supports their score, and share the specific example that supports yours. Often the disagreement reveals a blind spot that becomes a high-priority development area.
Step 2: Define the Target Competency Profile for the Desired Next Role
Identify the PM's target role, whether that is a promotion to the next seniority level, a lateral move into a different PM specialization, or an initial transition into product management. Pull the expected competency scores for that target role from your framework's level definitions. If you have not yet defined these, use the sibling skill on defining competency levels from Associate to Senior PM. The target profile should specify a score for every competency in the framework, not just the ones the PM is weak on.
Write out the target profile in the same table format as the current state so you can place them side by side. Also note which competencies are considered "must-have" versus "nice-to-have" for that specific role, since this will affect prioritization in the next step.
Tip: If the PM's desired role is a specialization like Growth PM or Platform PM, adjust the target profile to reflect the quadrant weighting for that role type. A generic Senior PM profile will not serve a PM targeting a highly specialized position. Use the sibling skill on differentiating PM role types to inform these adjustments.
Step 3: Calculate and Rank the Competency Gaps
For each competency, subtract the current consensus score from the target score. This gives you a raw gap number. A positive number means the PM needs to grow in that area. A zero or negative number means they already meet or exceed the target.
List all positive gaps in a table, then rank them using three criteria: gap magnitude (how many points below target), role criticality (is this competency a must-have for the target role, and will its absence block a promotion decision), and developmental leverage (can improvement here unlock progress in other competencies). Assign a simple High, Medium, or Low rating for each criterion. Competencies that score High on at least two of the three criteria go into your priority tier. The goal is to narrow the list to no more than five candidates for active focus, from which you will select three in the next step.
Tip: Do not assume the largest numerical gap is always the highest priority. A gap of 3 points in a competency that is only marginally relevant to the target role is less urgent than a gap of 1.5 points in a must-have competency that the promotion committee explicitly evaluates. Role criticality should outweigh magnitude when they conflict.
Step 4: Select Three Focus Areas for the Next 90 Days
From the priority tier, select exactly three competency gaps to actively develop in the upcoming quarter. Three is the maximum because meaningful competency growth requires sustained, focused effort. Spreading attention across more than three areas results in marginal improvement everywhere and demonstrable improvement nowhere. When choosing among equally ranked candidates, favor gaps that are adjacent to each other in the framework's quadrant model, because working on two related competencies simultaneously creates reinforcing practice opportunities.
For example, improving both "user research" and "market analysis" (both in the external quadrant) means the PM can deepen both through a single competitive landscape project. Write a one-sentence rationale for each selection explaining why this gap was chosen over other candidates, since this rationale will anchor future review conversations.
Tip: If the PM pushes to work on more than three areas, ask them to name which of the three they would deprioritize if a new project consumed 30% of their bandwidth. If they cannot choose, that confirms that three is already at the limit of what they can manage with focus.
Step 5: Design Development Activities for Each Focus Area
For each of the three focus areas, design a specific development plan with four components. First, identify one stretch assignment: a real project or responsibility in the PM's current role that will force them to exercise the target competency under genuine constraints. This is the most important component. Second, select one learning resource, such as a book chapter, a course module, or a case study, that builds foundational understanding.
Keep this targeted; a 300-page book is not a learning resource, but chapters 4 through 6 of that book might be. Third, define one feedback mechanism: a person (mentor, peer, manager) who will observe the PM practicing this competency and provide structured feedback at a defined interval, such as biweekly. Fourth, name one coaching touchpoint: a recurring conversation (monthly is typical) where the PM and their manager discuss progress, obstacles, and adjustments. Write all four components into the plan document with enough specificity that someone reading the plan cold could understand exactly what will happen.
Tip: Stretch assignments work best when they have natural deadlines and visible outputs. "Lead the next quarterly business review presentation" is a better stretch assignment for stakeholder communication than "practice presenting more often," because it has a fixed date, a defined audience, and an observable result that the manager can evaluate directly.
Step 6: Define Measurable Milestones and Success Criteria
For each focus area, write one or two concrete milestones that will signal meaningful progress by the end of the 90-day cycle. Good milestones are observable by both the PM and their manager without requiring subjective judgment. Avoid milestones like "improved stakeholder management" because that is unfalsifiable. " Each milestone should connect directly to the stretch assignment.
Write the milestones into the plan document alongside the development activities so the connection is explicit.
Tip: Test each milestone with the question: "If two reasonable people watched this PM for a quarter, would they agree on whether this milestone was met?" If the answer is no, the milestone is too subjective. Add specificity until agreement becomes likely.
Step 7: Establish the Review Cadence and Plan Format
Lock in a review schedule before the 90-day cycle begins. The recommended cadence is a brief weekly self-check (five minutes, the PM notes what they practiced and what they learned), a biweekly feedback conversation with the designated feedback provider for each focus area, and a monthly 30-minute check-in between the PM and their manager to review progress against milestones. At the end of the 90-day cycle, schedule a formal 60-minute review where you reassess the competency scores for the three focus areas, determine whether milestones were met, and decide the next quarter's focus areas. Write the review cadence into the plan document with specific dates.
If dates are not set at plan creation, the reviews will not happen. Finally, choose a format for the plan itself: a shared document, a template in your PM tool, or a simple spreadsheet. The format matters less than accessibility. Both the PM and the manager need to be able to open and update it in under 30 seconds.
Tip: Put the first monthly check-in on the calendar during the planning conversation, not after it. Plans that launch without a scheduled first review have a 70% abandonment rate within 30 days, based on patterns observed across PM teams. Calendar holds create accountability before motivation fades.
Step 8: Conduct the Collaborative Planning Conversation
Present the draft plan to the PM in a dedicated conversation. Do not email it. This conversation serves three purposes: validating that the PM agrees with the gap prioritization, co-designing development activities that fit their actual workload and interests, and building genuine ownership of the plan. Walk through each section: current state, target state, prioritized gaps, selected focus areas, development activities, milestones, and review cadence.
Invite the PM to challenge any element they disagree with or do not understand. Adjust the plan based on their input. The PM should leave this conversation able to describe their three focus areas, their primary stretch assignment for each, and their first milestone in their own words without looking at the document. If they cannot, the plan is not clear enough.
Tip: Frame the conversation as "here is a draft for us to shape together" rather than "here is your development plan." PMs who feel the plan was created for them rather than with them are significantly less likely to follow through. Co-creation is not a nicety; it is a prerequisite for execution.
Step 9: Launch the Plan and Track the First Two Weeks
In the first two weeks after launching the plan, pay closer attention to execution than you will in subsequent weeks. This is when habits form or do not. Check that the PM has started their first development activity, made contact with their feedback provider, and completed at least one weekly self-check. If any of these have not happened by day 14, schedule a brief conversation to diagnose the blocker.
Common early blockers include stretch assignment timing (the opportunity has not come up yet), competing priorities (a launch or incident consumed all bandwidth), or unclear next action (the PM knows what to work on but not what to do first). Resolve the blocker specifically: reschedule the stretch assignment, protect time on the calendar, or break the first activity into a smaller first step. Document any adjustments in the plan so the living document stays accurate.
Tip: The single strongest predictor of plan success is whether the PM takes a visible action on at least one focus area in the first five business days. If they do, momentum compounds. If they do not, the plan begins to feel abstract. Before ending the planning conversation, ask: "What is the one thing you will do this week toward your first focus area?" and write it down.
Examples
Example: Associate PM at a B2B SaaS Startup Targeting Mid-Level PM
An Associate PM at a 40-person B2B SaaS company has been in the role for 14 months. The team uses the Product Team Competencies Framework with five-point scales. The PM's manager wants to help them prepare for promotion to Product Manager within the next two quarters. The company ships monthly and the PM owns one product area with two engineers.
The manager pulls the PM's most recent assessment. The PM self-scored and the manager scored independently. 0. 0.
0 point gap, important). The manager selects three focus areas: stakeholder communication (largest gap, must-have, highly visible in promotion decisions), data analysis (must-have, blocks ability to justify roadmap decisions), and strategic thinking (unlocks readiness for the PM-level expectation of contributing to product strategy). For stakeholder communication, the stretch assignment is to lead the next two monthly business review presentations to the leadership team, replacing the manager who currently presents. The learning resource is chapters 3 and 4 of a stakeholder management playbook the team already uses.
The feedback mechanism is the VP of Product observing both presentations and providing written feedback. " The plan launches with a 30-minute collaborative conversation where the PM adjusts the data analysis stretch assignment to use an upcoming feature launch as the context for building a measurement plan from scratch.
Example: Career Changer Entering Product Management from Engineering
A senior software engineer at a mid-size e-commerce company wants to transition into product management. They have strong technical skills but limited experience with customer-facing and strategic competencies. Their engineering manager and the Head of Product have agreed to support a structured transition. The company uses the competency framework and the target is Associate PM.
Because the engineer has no prior PM assessment, the Head of Product conducts an initial assessment using the Associate PM target profile as the benchmark. 0 vs. 5 vs. 0 vs.
5 target). 5 vs. 5 vs. 0 vs.
5 gap). Three focus areas are selected: user research (largest gap, foundational to the PM role), stakeholder communication (must-have for cross-functional work), and market analysis (unlocks the external quadrant). For user research, the stretch assignment is to shadow the current PM on three upcoming customer interviews, then independently lead two interviews with existing customers and produce written synthesis documents. The learning resource is a focused online module on customer interview techniques, specifically the first four lessons.
The feedback provider is the current PM who will observe the independent interviews and review the synthesis documents. " The plan is designed for a six-month timeline with two 90-day cycles, since the transition involves building foundational competencies rather than incremental improvements. The first quarterly review will determine whether to proceed with the transition or extend the development period.
Example: Senior PM at a Large Enterprise Preparing for Group PM / Director Role
A Senior PM at a 2,000-person enterprise software company has been at the Senior level for two years. They manage a complex product area with five engineers and strong individual contributor performance. They want to move to Group PM, which at this company requires managing other PMs and contributing to product portfolio strategy. The competency framework includes leadership competencies at the Group PM level.
0). 0). The three focus areas selected are people management (largest gap, entirely new competency), portfolio strategy (requires a shift from feature-level to product-line-level thinking), and organizational influence (the gap is smaller but it is the most visible competency in the promotion panel). For people management, the stretch assignment is to formally mentor two Associate PMs for the quarter, conducting biweekly 1:1s with each, providing written feedback on their work, and supporting one of them through a career development planning exercise (applying this very skill).
The learning resource is a curated reading list of three articles on PM-specific management practices from the company's internal leadership library. The feedback mechanism is the PM's own manager observing one mentoring session per month and providing coaching feedback. " The plan explicitly notes that the PM's individual contributor workload must be reduced by 15-20% to create capacity for mentoring, and the manager commits to redistributing one initiative to another Senior PM.
Example: PM at a B2C Mobile App Company Shifting from Tactical to Strategic Focus
A mid-level PM at a consumer mobile app company with 150 employees excels at shipping features quickly but consistently receives feedback that they do not contribute enough to product strategy. Their manager's assessment shows strong tactical-quadrant scores and weak strategic-quadrant scores. The PM has been in the role for two years and needs to demonstrate strategic capability to be considered for Senior PM.
5 in the strategic quadrants. 0. All three strategic competencies are must-haves for promotion. The manager selects all three as focus areas since they are tightly related and can be developed through interconnected activities.
The stretch assignment is a single large project: the PM will own the creation of a six-month strategic roadmap for their product area, including competitive analysis, market opportunity sizing, and a prioritized initiative list with business case justifications. This replaces the current process where the manager creates the roadmap and the PM executes against it. The learning resources are two specific chapters from a product strategy book plus a recorded internal talk by the VP of Product on how the company evaluates market opportunities. The feedback mechanism is the Director of Product reviewing the roadmap draft at two checkpoints (week 4 and week 8) and providing structured feedback against a rubric that maps to the competency definitions.
" The PM co-creates this plan enthusiastically because the stretch assignment gives them exactly the kind of visibility they need. During the planning conversation, they add a secondary activity: attending two executive strategy sessions as an observer to calibrate their understanding of what "strategic" looks like at the company.
Best Practices
Limit active focus areas to three per quarter, no exceptions. Competency development requires repeated, deliberate practice in context. Four or five focus areas dilute attention below the threshold where any single competency shows visible improvement. You will know you have violated this when milestone reviews show 20% progress across five areas instead of 80% progress across two or three.
Use real work as the primary development vehicle, not courses or reading alone. Stretch assignments embedded in the PM's actual responsibilities build competency three to five times faster than passive learning because they combine knowledge acquisition with application under real stakes. A PM who reads a book on stakeholder management and never practices it in a high-stakes meeting has not actually developed the skill.
Write milestones that are observable by both the PM and the manager without requiring subjective judgment. "Improved at strategy" is not a milestone. "Presented a market opportunity analysis to the leadership team and received approval to proceed" is a milestone. Observable milestones prevent the common failure mode where the PM believes they have improved but the manager sees no evidence.
Reassess competency scores at the end of every 90-day cycle, not just at annual review time. Quarterly reassessment creates a feedback loop that shows the PM their growth in concrete terms and allows the plan to adapt to changing priorities. Without reassessment, the plan becomes a static artifact rather than a living tool.
Always co-create the plan with the PM rather than presenting a finished document. PMs who help shape their own development priorities, select their own stretch assignments, and define their own milestones execute at roughly double the rate of PMs who receive a manager-authored plan. The planning conversation itself is a development activity because it forces the PM to reflect on their own strengths and gaps.
Separate the development plan from the performance review process. If the PM perceives that admitting a weakness will directly reduce their performance rating, they will underreport gaps and the plan will be built on inaccurate data. Position the plan as a growth tool, not an evaluation tool. The plan informs the review, but it is not the review.
Document the rationale for each focus area selection. Three months later, when the PM asks why they are working on stakeholder communication instead of data analysis, the written rationale prevents revisionist second-guessing and keeps the plan anchored to the original gap data.
Keep the plan document short and scannable. One to three pages maximum. If the PM cannot find their current focus areas and next milestones within 10 seconds of opening the document, the format is too complex. A dense five-page plan with narrative paragraphs will not be consulted; a one-page table with focus areas, activities, milestones, and dates will.
Common Mistakes
Creating a plan that tries to close every competency gap simultaneously
Correction
This happens because the assessment reveals many gaps and the instinct is to address them all at once. The result is that the PM works on six or seven areas, makes marginal progress on each, and feels like nothing improved after 90 days. The signal to watch for is a plan with more than three active focus areas or a PM who cannot articulate their top priority without checking the document. Constrain to three focus areas.
Remaining gaps go on a backlog for future quarters.
Defining development activities as passive learning only (courses, books, articles) without stretch assignments
Correction
Managers default to recommending courses because they are easy to assign and feel productive. But competency growth requires application under real constraints, not just knowledge intake. Watch for plans where every activity is "complete course on X" or "read book about Y" with no corresponding on-the-job assignment. For each focus area, identify one real project or responsibility that forces the PM to practice the target competency with actual stakes and deadlines.
Writing vague milestones that cannot be objectively evaluated
Correction
Milestones like "better at data analysis" or "improved communication skills" persist because they feel safe. Both the PM and the manager can claim success or failure depending on their mood. This creates confusion at review time and erodes trust in the plan. The diagnostic signal is a milestone that contains no numbers, no dates, and no specific observable behavior.
Rewrite every milestone to include an action, a context, and a minimum threshold.
Building the plan in isolation without the PM's input and presenting it as final
Correction
This happens when managers view development planning as an administrative task rather than a coaching conversation. A plan the PM did not help create feels like an assignment, not a growth path. The signal is a PM who cannot describe their focus areas from memory or who treats the plan as their manager's document rather than their own. Always draft the plan collaboratively.
The manager brings the data and a proposed prioritization; the PM shapes the activities, selects the stretch assignments that fit their workload, and defines milestones they believe are challenging but achievable.
Skipping the review cadence after the initial planning conversation
Correction
The plan launch generates energy, but without regular reviews, that energy dissipates within two to three weeks. This is the most common failure mode: the plan exists, the PM intended to follow it, but nobody checked in and it quietly died. The signal is that the PM has no updates at the first monthly check-in or the check-in was never scheduled. Prevent this by putting all review dates on the calendar during the planning conversation, not after it.
Treat skipped reviews as seriously as skipped sprint ceremonies.
Using the same generic plan template for every PM regardless of role type or career trajectory
Correction
A Growth PM and a Platform PM have fundamentally different competency profiles, so a one-size-fits-all template produces plans that feel disconnected from the PM's actual work. The signal is a plan where the focus areas and activities could belong to any PM on the team. Always start from the target role's specific competency profile and design activities that match the PM's actual product domain, team structure, and career ambitions.
Other Skills in This Method
Showcasing PM Competencies in Portfolios and Resumes
How to use the competency framework to structure a product manager resume or portfolio that clearly demonstrates breadth and depth across strategic, tactical, internal, and external skills.
Defining Competency Expectations from Associate PM to Senior PM
How to calibrate expected proficiency levels across each quadrant of the framework for associate, mid-level, and senior product manager roles.
Assessing Product Team Strengths and Identifying Skill Gaps
How to use the competency framework to evaluate individual and team-level proficiency, surface blind spots, and prioritize areas for development.
Differentiating PM Role Types Using the Competency Framework
How to use the quadrant model to distinguish technical product managers, growth PMs, and platform PMs from generalist roles based on their competency emphasis.
Mapping PM Competencies Across Strategic vs. Tactical and Internal vs. External Axes
How to plot core product management skills onto the 2D competency grid to visualize where each capability falls along the strategic-tactical and internal-external dimensions.
Writing Competency-Based Product Manager Job Descriptions
How to translate framework quadrants into clear, measurable job descriptions and hiring criteria that attract the right candidates for specific PM roles.
Designing PM Interview Rubrics Aligned to Competency Quadrants
How to structure product manager interview questions and scoring rubrics that evaluate candidates across all four quadrants of the competency framework.
Frequently Asked Questions
How long should a PM career development plan take to create?
Budget two to three hours for the full process: about 30 minutes to gather and validate assessment data, 30 minutes to calculate and rank gaps, 45 minutes to design development activities and milestones, and 45 to 60 minutes for the collaborative planning conversation with the PM. The first plan you create will take longer because you are building your template and calibrating your judgment. Subsequent plans for other PMs typically take closer to 90 minutes total. Do not rush the collaborative conversation, as it is the highest-leverage part of the process.
Should I build a career development plan before or after assessing competency gaps?
Always assess first. The career development plan depends entirely on having accurate, current competency scores for both the PM's current state and their target role. Without assessment data, you are guessing at priorities, and guessed priorities produce plans that feel disconnected from reality. Complete the assessment process described in the sibling skill on assessing PM team strengths and gaps, resolve any score disagreements between the PM and their manager, and only then proceed to plan creation.
How do I build a development plan for someone figuring out how to become a product manager from a non-PM role?
The process is identical, but the inputs differ. The current-state assessment will show zeros or very low scores across most PM-specific competencies, which is expected. Set the target profile to Associate PM or the entry-level PM role at your company. The gap list will be long, so prioritization becomes even more important. Favor foundational competencies that unlock others: user research and stakeholder communication are usually the best starting points because they build the customer empathy and cross-functional habits that every other PM competency depends on. Plan for a longer timeline, typically two 90-day cycles before a role transition, and set milestones that produce tangible evidence the person can include in their internal application.
What if the PM disagrees with the gap prioritization?
This is a productive disagreement, not a problem. Ask the PM to explain which gaps they believe should be prioritized instead and why. Sometimes they have context the manager lacks, such as an upcoming project that would be a perfect stretch assignment for a different competency. Sometimes they are avoiding a competency they find uncomfortable, which is actually a signal that it deserves attention. The resolution is to discuss the three prioritization criteria together: gap magnitude, role criticality, and developmental leverage. If after that discussion the PM still disagrees, defer to the PM on one of the three focus areas. Ownership matters more than optimization.
Why does my development plan keep getting abandoned after the first month?
The most common cause is a missing review cadence. Plans without scheduled check-ins lose momentum because there is no external accountability and no feedback loop. The second most common cause is stretch assignments that never materialize because the right opportunity did not come up or competing priorities consumed all bandwidth. Prevent both by putting review dates on the calendar during the planning conversation and by choosing stretch assignments tied to projects that are already scheduled. If the plan still drifts, reduce the scope: focus on one competency instead of three until the habit of active development is established.
How do I handle a PM whose plan shows no progress after a full 90-day cycle?
First, diagnose whether the issue is effort, environment, or plan quality. Did the PM actually attempt the development activities? If not, the blocker is likely bandwidth or motivation, not capability. Did they attempt the activities but the stretch assignment did not provide genuine practice opportunities? If so, the activity design was flawed. Did they practice regularly but the competency score did not improve? If so, they may need a different type of support, such as coaching from someone who excels at that competency. Adjust the plan based on the diagnosis rather than simply repeating the same plan for another quarter. A plan that produced no results once will not produce results a second time without changes.
Can I use this process for an entire PM team at once, or only for individuals?
You can run it for a team, but each PM must have an individual plan. Team-level patterns from the assessment (for example, if three out of five PMs have a stakeholder communication gap) can inform shared learning resources or group workshops. But the stretch assignments, milestones, and review conversations must be personalized. A team-wide plan that assigns the same activities to everyone ignores the individual gap profiles that make development plans effective. Budget roughly 2-3 hours per PM for initial plan creation, and consider staggering planning conversations over two weeks rather than cramming them into a single day.