name: career-dev-planner
description: Structures a CS career progression plan from current role to target role by mapping required skills, identifying gaps, defining development milestones, and building a timeline with specific actions. Covers the full CS career ladder from CSM through VP. Use when asked to plan a career path, build a development roadmap, map skills for promotion, structure a career progression plan, or when a CSM wants to be intentional about moving to the next level. Also triggers for questions about CS career progression, promotion readiness, skills for the next level, career planning in customer success, or what it takes to move from CSM to manager to director to VP.
license: MIT
metadata:
author: Stephen Rogan
version: "1.0.0"
standalone: true

Career Development Planner

Maps the path from where you are to where you want to be in your CS career. Not a generic "develop your skills" plan -- a structured assessment of what the next level requires, where your gaps are, and exactly what to do about them.

How to Use

Provide:
- Your current role and level
- Your target role (next level, skip level, lateral move, or specific position)
- Your tenure and key achievements
- Your self-assessed strengths and gaps
- Feedback you have received (performance reviews, manager input, peer observations)
- Your timeline (6 months, 1 year, 2 years)
- Any constraints (company size limits promotion opportunities, need to change companies, etc.)

The CS Career Ladder

Level Progression and Core Requirements

Skills Matrix by Level

Gap Analysis

For each skill domain, assess:

Prioritisation logic:
- Must-have gaps (High): skills the target role cannot function without. These are the gates
- Differentiator gaps (Medium): skills that separate strong performers from adequate ones at the target level
- Nice-to-have gaps (Low): skills that add depth but are not required for the transition

Development Actions by Gap Size

Development Plan Template

## Career Development Plan: [Name]
**Current:** [Role, Level, Tenure]
**Target:** [Role, Level]
**Timeline:** [months/years]

### Gap Assessment
| Domain | Current | Required | Gap | Priority |
|--------|---------|----------|-----|----------|
| [domain] | [level with evidence] | [level] | [S/M/L] | [H/M/L] |

### Priority Actions (Next 90 Days)
Focus on 2-3 high-priority gaps:

**Gap 1: [Domain]**
- Learn: [specific action by date]
- Practice: [specific opportunity by date]
- Reflect: [feedback mechanism]
- Milestone: [what "closed" looks like for this 90-day period]

**Gap 2: [Domain]**
[Same structure]

### Longer-Term Development (6-12 Months)
[Medium and low priority gaps with approach]

### Support Needed
- From manager: [specific coaching, opportunities, sponsorship]
- From peers: [mentoring, peer coaching, collaboration]
- External: [courses, certifications, communities, reading]

### Review Schedule
- Monthly self-check: [date]
- Quarterly manager review: [date]
- Readiness assessment: [target date for evaluating promotion readiness]

The Readiness Conversation

When you believe you are ready for the next level, structure the conversation:

1. Evidence: "Here is what I have demonstrated at the next level" (specific examples per skill domain)
2. Gaps acknowledged: "Here is what I am still developing" (shows self-awareness)
3. Ask: "I believe I am ready for [role]. I would like to discuss the path and timeline"

Do not wait to be asked. Promotions go to people who demonstrate readiness and articulate it, not to people who wait to be recognised.

Quality Gates

• Is the gap assessment honest? If every domain shows "small gap," the assessment is optimistic. Every level transition has at least one large gap -- that is what makes it a transition, not a continuation
• Are the development actions specific and time-bound? "Read about leadership" is not a development action. "Complete [specific course] by [date] and apply the delegation framework to my next onboarding project" is
• Is the manager involved? A development plan without manager buy-in lacks the sponsorship and opportunity allocation that makes the plan executable
• Is the timeline realistic? Skipping a level in 6 months is unrealistic for most people. Moving one level in 12-18 months with deliberate effort is achievable

Principles

• Career development is a project, not a wish. It requires planning, execution, feedback, and iteration -- the same disciplines you apply to managing accounts. Apply them to managing your career
• The skills for the next level are different from the skills that made you successful at this level. A great CSM is not automatically a great CS Manager. The skills that got you here (account execution, customer relationships) are necessary but not sufficient for the next level (team development, process design, metric ownership)
• Your manager is your primary career development partner. They control opportunity allocation, provide coaching, and advocate for your promotion in rooms you are not in. Invest in this relationship
• Lateral moves are underrated. A CSM who moves into CS Ops, then back to a Senior CSM role, has a broader skill set than one who stayed on the same ladder. Consider breadth, not just height