Career Pathing Grid — Competency, Outcomes, and Development Activities
A practical, ready-to-use career-pathing grid to map role levels to expected outcomes, required competencies, observable behaviors, suggested development activities, and examples of evidence. Includes a worked starter example for an IC product role and guidance for using the grid in career conversations and promotion decisions.
Career Pathing Grid — Template and Guidance
This template helps managers and individual contributors create clear, evidence-based role progressions. Use it to clarify growth expectations, create individualized development plans, and support fair promotion decisions. Keep copies in a shared team folder so each person has a living record of progress and agreed next steps.
How to use this grid
- Choose the role to map (e.g., Product Manager — IC track, Engineering, Customer Success).
- Define 3–5 levels that reflect real opportunities in your organization (titles, bands, or milestones).
- For each level, populate expected outcomes, competencies, observable behaviors, suggested learning activities, and examples of evidence.
- Use the grid during career conversations: agree on priority development activities, timelines, and evidence to collect.
- Review and update at regular check-ins (quarterly recommended) and before promotion decisions.
Grid columns (template)
Fill one row per level. Columns are intentionally concrete so conversations stay evidence-focused.
| Level (name / band) | Expected Outcomes (what success looks like) | Required Competencies (skills, knowledge) | Observable Behaviors (what people see) | Suggested Development Activities | Examples of Evidence (artifacts, metrics) |
|---|---|---|---|---|---|
| Level name | Concise, measurable outcomes | 3–6 core competencies | Specific, observable actions | Training, stretch assignments, coaching | Deliverables, KPIs, peer feedback |
Starter example — IC Product Role
Below is a short worked example showing how one role might be mapped across four levels. Use this as a starting point, not a prescription.
| Level | Expected Outcomes | Required Competencies | Observable Behaviors | Suggested Development Activities | Examples of Evidence |
|---|---|---|---|---|---|
| Associate Product Manager | Delivers small features with clear requirements and stakeholder alignment. | Basic product discovery, writing clear specs, prioritization, data literacy. | Asks clarifying questions, documents acceptance criteria, seeks feedback. | Shadow senior PMs, complete product discovery course, owner of 1 small sprint. | Feature spec, release notes, stakeholder feedback, customer metric lift. |
| Product Manager | Owns end-to-end features that improve a key metric; collaborates across teams. | Customer research, roadmap planning, A/B testing, cross-functional facilitation. | Leads discovery sessions, negotiates scope, tracks outcomes vs. goals. | Lead a discovery initiative, mentor an associate, run A/B test experiments. | Roadmap item delivered, metric improvement, post-launch learnings doc. |
| Senior Product Manager | Drives product area strategy and consistently delivers measurable impact. | Strategic thinking, stakeholder influence, business modeling, team coaching. | Shapes strategy, influences leaders, develops others, balances tradeoffs. | Lead a product area strategy, present to execs, coach PMs, advanced analytics training. | Strategy doc, P&L impact, testimonials from stakeholders, promotion-ready rubric. |
| Lead Product Manager | Sets multi-quarter strategy, grows product capability, and mentors leaders. | Organizational leadership, portfolio management, high-stakes stakeholder management. | Sets direction across teams, resolves escalations, develops leadership bench. | Sponsor cross-functional initiatives, lead org-level planning, executive coaching. | Portfolio outcomes, leadership feedback, succession candidates developed. |
Conversation prompts and coach guide
- Employee: Which outcomes here feel most energizing? Which competency gaps worry you most?
- Manager: Which two outcomes must improve before we consider promotion? What evidence will demonstrate that?
- Coach: What stretch assignment will provide visibility and measurable results in the next 3–6 months?
Evidence-based promotion checklist (use before decisions)
- Has the candidate consistently met the expected outcomes for the higher level for at least one review period?
- Is there demonstrated competency in the core skills (examples documented)?
- Are observable behaviors aligned with the higher level and confirmed by peers or stakeholders?
- Is there a clear plan to close any remaining gaps if promoted (risk mitigation)?
Adaptation and governance
Tailor level names, competencies and evidence types to your organization and document any role-specific deviations. Keep a short governance note (who approves changes to the grid, how often it’s reviewed) to avoid drift across teams.
Quick tips
- Favor specific outcomes and artifacts over vague terms like “strong communicator.”
- Limit competencies to the ones that will change hiring, development, or promotion decisions.
- Use the grid as a conversation tool, not a bureaucratic checklist — it should enable development.
Discussion
Comments and conversation will live here.