Individual Development Plan: How to Build One That Sticks

The individual development plan is usually born in the same meeting where it dies. The manager writes three vague goals into a form, both sides sign, and nobody opens it again until the next cycle.

There is a reason that ritual survives. It is cheap, it can be reported on, and nobody measures whether it worked.

The finding that changes the design

Kluger and DeNisi published the reference meta-analysis on feedback interventions in 1996. They pooled 607 effect sizes across 23,663 observations. Feedback improved performance on average, with a moderate effect. And in more than a third of cases it made performance worse.

That finding organizes everything else. Feedback is not good by definition. The variable that carries the most weight is where it directs the recipient’s attention.

When a comment points at the task, the person adjusts the task. When it points at the person, the person defends themselves. An IDP written in labels — “lacks leadership,” “needs to be more assertive” — points at the self, and triggers the wrong reaction before development even starts.

The four elements of an IDP that gets done

1. One gap, chosen by consequence. Not five. The question that selects it is concrete: which gap, if closed, changes what this person can do next year? Everything else goes on the someday list.

2. The evidence for the gap, in writing. What was observed, when, and in what situation. Without evidence, the conversation is one opinion against another, and seniority wins.

3. The behavior, not the trait. “Be more assertive” cannot be practiced. “Bring a written position to the leadership meeting and hold it until someone refutes it” can. Observable behavior is the unit of the plan.

4. The real task where it gets practiced. A project already on the department’s plan that demands exactly that behavior. Without the task, the IDP is an intention.

Specific goals, not “do your best”

Locke and Latham’s goal-setting research is among the most replicated in organizational psychology. Specific, challenging goals produce better performance than vague ones, including the “do your best” variety.

Applied to an IDP, that means every line has to answer three things. What will be done differently, in which concrete situation, and how you will know it happened. If the third answer does not exist, the line is not a goal.

About 70-20-10

The model that splits development into 70% experience, 20% relationships, and 10% formal training is the most cited reference in the field. It came out of work at the Center for Creative Leadership that asked roughly two hundred executives to recall where their development had come from.

That is retrospective self-report, not an experiment. The exact proportions have no strong empirical backing, and critics have been pointing that out for years.

The underlying intuition does hold up. Most development happens doing the work, not in a classroom. Use it as a heuristic for where to put the effort. Do not use it as if it were a measurement.

Who owns what

This is where most plans fall apart.

The person owns the plan. If the manager writes the IDP and hands it over, the commitment belongs to the manager.

The manager owns the opportunity. Their job is not to teach the competency. It is to land the project where that competency is genuinely practiced, and to protect the space for it to go badly the first few times.

HR owns the cadence. That the conversations exist and are on the calendar. Nothing more.

When those three owners blur, the plan belongs to everyone and to no one.

Quarterly, not annual

An annual cycle puts twelve months between the goal and the review. In that time the context changed, the project was cancelled, and the behavior was never practiced.

A rhythm that works is forty-five minutes a quarter, with three fixed questions. What did you practice since last time. What happened. What changes for next quarter.

Four short conversations a year produce more movement than one long one.

Where the raw material comes from

An IDP written only from the direct manager’s impression inherits one person’s point of view. Three sources improve it.

The trait profile. It says how this person tends to operate, and therefore what will cost them most. Someone with low tolerance for conflict does not learn to give hard feedback in a four-hour workshop. They need a structure, not a talk. The per-dimension reading is in the OCEAN model explained.

Multi-rater competency assessment. The gaps the boss cannot see usually sit with peers. The design is in multi-evaluator competency assessment.

Position on the talent matrix. Someone high on performance and high on potential needs a different plan from someone high on performance and content where they are. How to fill it with data is in talent review and the 9-box.

What an IDP cannot do

Personality traits are relatively stable in adulthood. A development plan does not rewrite them, and promising that produces frustration on both sides.

What does develop is behavior, judgment, and habit. An introverted person does not become extroverted. They can learn to prepare and hold an intervention in a twenty-person meeting, which is what the role needed.

That distinction is what makes an IDP honest. You work on what moves, informed by what does not.

One page, not a form

An IDP that works fits on one page. The gap and its evidence. The observable behavior. The real project where it gets practiced. The four conversation dates. And who lands what.

If your current template has more fields than that, what you are measuring is form completion.