An Individual Development Plan (IDP) is only as valuable as the conversation it enables. Most organizations have IDPs that employees fill out once a year, file somewhere, and never look at again. Those IDPs are not development tools — they are compliance exercises.

The difference between an IDP that drives real growth and one that collects dust is specificity: specific goals tied to specific career criteria, specific learning activities with specific timelines, and a recurring review cadence that keeps the plan alive. This guide walks through exactly how to build that.

Step 1: Assess current strengths and development areas

The foundation of any good IDP is an honest assessment of where the employee stands today. Pull together three sources of information before this conversation:

Recent performance review feedback. What themes showed up consistently? What did multiple people say independently?
Career level criteria. Where does the employee's current performance sit relative to their level's expectations? Where relative to the next level?
The employee's own self-assessment. Ask them to come to the IDP conversation with their own view of their strengths and growth areas. Gaps between their self-perception and your observation are important data.

Aim to identify 2–3 genuine strengths to build on and 2–3 development areas that will have the most impact on the employee's progression. Resist the temptation to list every gap — that creates overwhelm, not development.

Step 2: Clarify the employee's career goals

Before setting any development targets, understand where the employee wants to go. This sounds obvious but is frequently skipped. Managers assume employees want what they assume is the logical next step — promotion to senior, transition to management, specialization in a particular area — and design development plans accordingly. Sometimes they are right. Often they are not.

Useful questions for this conversation:

"Where do you see yourself in one to two years?"
"What kind of work energizes you most? What drains you?"
"Are you more interested in going deeper in your current specialty or broadening your skills?"
"Is management something you want to explore, or would you prefer to advance as an individual contributor?"

The answers shape everything that follows. An IDP built around a goal the employee does not actually hold will not be pursued.

Step 3: Map gaps between current state and target level

With the career goal clear, use your career ladder to identify the specific gaps between where the employee is today and where they want to be. This is where the competency framework does its most important work.

Be concrete. "Improve communication skills" is not a useful development target because it cannot be observed or measured. Instead: "Lead the cross-functional sprint planning meeting independently, without needing to escalate scope decisions to the manager." That is something both parties can evaluate.

For each career level criterion the employee needs to develop, ask: what would it look like if they were demonstrating this at the next level? That description becomes the success condition for the development goal.

Step 4: Set 2–3 focused development goals

Less is more. Three active development goals are the maximum most people can meaningfully pursue alongside their full-time responsibilities. More than that, and nothing gets the sustained attention it needs.

Each goal should follow the SMART framework:

Specific: What exactly will the employee be able to do that they cannot do today?
Measurable: How will you both know the goal has been achieved?
Achievable: Is this realistic given the employee's current workload and available opportunities?
Relevant: Does this goal directly advance toward the employee's career objective?
Time-bound: When will this goal be complete or reviewed?

Step 5: Define learning activities for each goal

A goal without a plan is just a wish. For each development goal, specify the concrete activities that will build the skill. Research on adult learning consistently shows the "70-20-10" pattern: approximately 70% of development comes from on-the-job experience, 20% from learning from others, and 10% from formal training.

Build your learning activities with this in mind:

On-the-job experience (70%): Stretch assignments, leading a project they have not led before, representing the team in a senior stakeholder meeting, owning a new process.
Learning from others (20%): Mentoring relationships, shadowing, peer feedback, manager coaching during 1:1s.
Formal training (10%): Courses, certifications, books, conferences. These are useful for foundational knowledge but rarely drive behavioral change on their own.

Step 6: Set milestones and a check-in cadence

IDPs fail most often not because the goals are wrong but because there is no accountability structure to sustain them. Schedule quarterly IDP reviews now — not as a vague intention but as calendar events. Treat them with the same protection as 1:1 meetings.

For each development goal, set at least two interim milestones:

A mid-point check: "By month 3, the employee will have led the first planning meeting."
A completion point: "By month 6, the employee will independently lead planning meetings without any manager involvement."

Milestones create natural moments to celebrate progress and course-correct early if something is not working.

Step 7: Review and adjust every quarter

The IDP is a living document, not a signed contract. Roles change, projects shift, and the employee's priorities evolve. A quarterly review keeps the plan current and demonstrates that development is genuinely ongoing — not a once-a-year checkbox.

At each quarterly IDP review, cover three questions:

"What progress have you made since our last review?"
"Are these goals still the right ones, or has something changed?"
"What support or opportunities do you need from me to keep making progress?"

The quarterly review also connects naturally to the performance review cycle. Development progress tracked across quarters builds a documented case for promotion when the time comes — based on evidence, not impression.