Employee Development Plan
A development plan is a dated commitment that names one or more assessed proficiency gaps, states the target level for each, assigns the learning and experience that will close them, and defines the evidence that will show the new level has been reached.
By Samantha, SkillsDB|Published |Updated
What It Is
A development plan is the operational link between a gap and its closure. It starts from an assessment, not an aspiration: the person holds level 2 on a competency the current or next role requires at level 3. The plan then commits to a target level, a set of actions with owners and dates, and a form of evidence that will be accepted as proof, followed by a reassessment that records the new level. Plans typically run 6 to 12 months and carry two to four priority gaps; more than that dilutes effort and is rarely completed. A competency development plan is the variant anchored to a role's competency framework, so that the target levels are the role's required levels rather than numbers chosen in a conversation. Plans that skip the evidence and reassessment steps become course lists, and course lists are why most development programs cannot show that anyone became more capable.
Key Facts
- A plan has five elements: the gap, the goal, the learning or experience, the evidence, and the review.
- Every goal is a proficiency level on a named skill or competency, taken from the role's required level, not a free-text objective.
- Two to four priority gaps per plan is the practical ceiling; completion rates fall sharply above that.
- Learning is the input and a reassessed level is the output; a plan is closed by the reassessment, not by course completion.
- A development path is a sequence of plans across roles, each one starting from the gaps the previous role's assessment left.
- At scale the constraint is manager time; plans need to be generated from gap data and reviewed in minutes, not authored from blank templates.
The Five Elements
| Element | Field on the plan | Example value |
|---|---|---|
| Gap | Skill or competency, current level, required level | Incident response: level 2 now, level 4 required for Shift Lead |
| Goal | Target level and target date | Level 4 by 30 April |
| Learning | Actions with owner and due date | Shadow three live incidents (lead, by Feb); lead two under supervision (by Mar); root-cause write-up reviewed (by Apr) |
| Evidence | What will be accepted as proof of the new level | Two supervised incident leads signed off; write-up accepted by the site operations manager |
| Review | Check-in cadence and reassessment date | Monthly one-on-one; practical reassessment 15 April |
How SkillsDB Models It
SkillsDB has no separate plan document; a development plan is the combination of four things the platform already records. Take a Project Coordinator graded 2 on Stakeholder Communication against a benchmark of 3 for her level. The target is the benchmark itself, which her manager can raise to a personal 4 for a stretch goal in the batch grading view of a manager assessment. The priority is a Focus flag she applies to the skill herself from the career detail view, which lifts it into the Highlights section of her Skills page. The actions are the resources she and her manager add to her Learning Plan from the Upskilling view, each tied to that skill and moved from To Do through In Progress to Completed on the board. The evidence is the next manager assessment: the plan is done when it records a 3 and the badge turns from red to green. Completing a course changes the plan's progress, never the grade. See Learning Plans and Talent Development.
Related
A plan is a gap with a deadline.
See how SkillsDB builds development plans from assessed gaps and closes them with a reassessment, not a checkbox.
Book Demo