Individual Development Plan (IDP) Template You'll Actually Use

I found last year's development plan the way you find an old gym membership — by accident, months later, vaguely embarrassed. Three courses I never took. One line about 'growing as a leader' I couldn't have measured if I'd tried. I'd always assumed the problem was me: not disciplined enough, too busy, the usual excuses. It wasn't. The plan had been built to be filed, not used — a form for the review meeting rather than an instrument for the year. The fix turned out to be the template itself, which is a small change with an outsized payoff.

What an individual development plan actually is

An individual development plan is the artifact version of a career development plan: a short, shareable document that names the capabilities you are building, the actions that will build them, and how you will know they grew. The broad plan is yours and private; the IDP is the part you hand to a manager so they can resource it — stretch assignments, a mentor introduction, budget for the one course that earns its place. If the two feel redundant, you have written the IDP too abstractly.

The distinction matters because the IDP has an audience. A manager cannot act on 'become a better leader.' They can act on 'own the incident review process for one quarter, with you reviewing my first three writeups.' Specific is not a stylistic preference here — it is what makes the document fundable.

Why most IDPs die in a drawer

Two failure modes account for nearly all of them. The first is the course list: a plan that is mostly training, because training is the easy thing to write down. The second is the unmeasurable goal: 'improve communication,' with no signal that would ever tell you it happened. Both produce a document that cannot be reviewed, and a document that cannot be reviewed will not be.

Goal-setting research is unambiguous about the second failure: specific, appropriately difficult goals produce higher performance than vague 'do your best' ones, and they do it precisely because they give you something to measure against. An IDP line that cannot be scored at the end of the quarter is not a goal — it is a wish with a deadline.

The 70-20-10 split your plan should follow

The course-list failure has a known antidote. When researchers asked successful executives where their development actually came from, the answer landed near a 70-20-10 split: roughly seventy percent from challenging on-the-job work, twenty percent from other people — coaching, feedback, watching someone good — and ten percent from formal courses. The model is a generalization, not a law, but the direction is the point: most growth is reps, not curriculum.

A template that respects this allocates its lines accordingly. For every skill you are building, the bulk of the plan should be the work that will build it, a smaller part the people who will accelerate it, and only a sliver the formal training. If your draft IDP is three courses and nothing else, you have planned the ten percent and skipped the ninety.

70 — the assignments

Name the specific piece of work that forces the skill. Not 'practice system design' but 'design the export pipeline rewrite end to end.' The assignment is the development; everything else supports it.

20 — the people

Name who you will learn from and how: a mentor with a standing slot, a senior reviewer on your first attempts, one person whose feedback you will deliberately seek. Development from others does not happen by proximity — it happens by arrangement.

10 — the formal learning

The one course or certification that earns its place. The workplace-learning data is consistent year over year: people invest in formal learning when it ties to a real role outcome, and abandon it when it is generic. Make the ten percent specific too.

The IDP template

One row per capability, three to five rows total. More than that and you are listing, not planning. Copy this structure:

• Capability — the specific skill or competency, in the language your team actually uses (not 'leadership' but 'running a postmortem that changes behavior').
• Current level → target — where you are now and where this quarter ends, in concrete terms a third party could verify.
• 70 — the assignment: the real piece of work that builds it.
• 20 — the people: who you'll learn from, and the standing arrangement that makes it happen.
• 10 — the formal input: the one course, book, or cert that directly serves the assignment.
• Evidence — the dated artifact that will prove movement: a shipped thing, forwarded feedback, a decision on record.
• Review date — when you score this row, and who you'll discuss it with.

Fill it in with evidence, not aspiration

The evidence column is the one most templates omit and the one that does the work. An IDP without it is a list of hopes; with it, each row has a falsifiable claim. 'Owned the export rewrite — shipped March 4, design doc reviewed by two staff engineers' either happened or it did not. That is the difference between a plan you can review and a plan you can only feel guilty about.

Which exposes the real dependency: the evidence has to exist when review time comes, and memory will not hold it. The forgetting curve has been the same since 1885 — most of what you did this quarter is gone within weeks unless something caught it. The plan works only if a capture habit runs underneath it, logging the reps as they happen so the quarterly review is reading, not reconstruction.

A worked example

Capability: incident response — current, I run the technical fix; target, I run the review that prevents the repeat. 70 — own the postmortem for the next three incidents on my service, start to finish. 20 — shadow the staff engineer who runs the best reviews, then have her review my first two writeups. 10 — read the one book on blameless postmortems, applied to the next real incident, not in the abstract. Evidence — three published postmortems with action items that closed, plus her sign-off note. Review date — end of quarter, in my 1:1.

Notice what the example is not: it is not 'improve incident skills,' and it is not three courses. It is one capability, anchored to work that will happen anyway, with a person attached and a dated artifact promised. That row can be funded, done, and scored. That is the whole bar.

Review cadence: quarterly, not annually

An IDP reviewed once a year is a New Year's resolution with letterhead. The organizations that rebuilt performance management around continuous check-ins did it because annual cycles let goals drift untouched for eleven months — and your private plan drifts the same way at the same cadence. Score each row quarterly: did the assignment happen, did the evidence land, what is the next rep. Thirty minutes, four times a year.

The quarterly review is also where the plan connects outward — to the goals it serves, the growth it should be moving, and eventually the case it builds if a promotion is in reach.

The plan finally worked the quarter I stopped treating it as a document and started treating it as a loop — name the gap, do the reps, log the evidence, review. Copy the template tonight. Fill a single row with work that's already on your plate, attach a real person and a real date, and let a capture habit handle the evidence column for you. The first review you run from entries instead of memory is the one that converts you for good.