When to use
Reach for this when you want a deliberate path to a next role or level rather than drifting — defining where you're headed, what you're missing, and the milestones to close the gap. Use before car-job-search-strategy when the target itself is unclear.
Not for: the employer side. Workforce/succession planning and headcount design is hr-org-planning; running an employee's review is hr-performance-review. This skill plans your own growth, self-directed.
Method
- Define the destination — the role, level, or capability you want in 1-3 years, stated concretely enough to know when you've arrived. Decision point: if you can't name it, run a short exploration (informational interviews, job-posting analysis) first.
- Reverse-engineer the target — collect 5-10 real job postings for that destination; extract the required skills, scope, and signals. This is your rubric.
- Gap analysis — rate yourself honestly against each requirement (have / partial / missing). Rank gaps by impact-to-close and effort.
- Set SMART goals — for the top 3-5 gaps, write specific, measurable, time-bound goals with a visible artifact (shipped project, cert, talk, promotion).
- Sequence milestones — lay goals on a 30/90/180/365-day timeline; each milestone has a checkable output and a review date. Decision point: if two goals compete for the same hours, defer one — parallel half-efforts stall.
- Wire in feedback — a mentor or peer to review progress quarterly; adjust when reality diverges from plan.
Example
Destination: move from Senior to Staff Engineer in 18 months. Postings show the gap is "org-wide technical influence." Goal: "Lead one cross-team architecture initiative and publish the design doc by Q3" (measurable, artifact). Milestones — 30d: pick the initiative + sponsor; 90d: RFC circulated; 180d: implementation started with two teams; 365d: shipped + presented at eng all-hands. Quarterly review with your manager as mentor.
Pitfalls
- Vague goals ("get better at leadership") with no artifact or deadline — unmeasurable, so never done.
- Skipping the posting-based rubric and guessing at requirements, then closing the wrong gaps.
- Stacking ten goals in parallel; focus beats a scattered to-do list.
- Writing the plan once and never revisiting it against real progress.
Output format
Destination: role/level/capability + timeframe
Target rubric: [requirements extracted from 5-10 postings]
Gap analysis: requirement | have/partial/missing | impact | effort
Goals (top 3-5): SMART statement + artifact
Timeline: 30d / 90d / 180d / 365d milestones (each: output + review date)
Feedback loop: mentor/peer + review cadence