Individual Development Plan (IDP): Template, Examples, and How to Write One That Survives (2026)

Two people at the same company got a development plan in January. The first says: improve leadership skills, attend leadership training, by end of year. The second says: able to run the weekly forecast review alone by 31 May, co-run March with Sam, run May solo, evidence is three reviews unaided with the forecast landing within five percent. By March the first plan has not been opened since it was written and the second one is halfway done. Same manager, same goal underneath, same amount of good intention. The difference is entirely structural, and it is fixable in about twenty minutes.

What is an individual development plan?

An individual development plan, almost always shortened to IDP, is a short written agreement between an employee and their manager covering what that person will get better at over the next six to eighteen months, how, and how both of them will know it worked.

The ownership is the part organisations get backwards. The employee owns the plan; the manager enables it. When the manager writes it, it becomes a set of instructions to comply with rather than ambitions to pursue, and compliance is the first thing to go when a quarter gets busy.

The manager's half of the deal is concrete, and it is three things:

• Provide the assignments. Usually by giving away work they currently do, or arranging exposure the employee could not get on their own.
• Provide the named support. The access, the budget, the introduction, the protected time.
• Turn up to the monthly review. Ten minutes. This is the part that tells everyone whether any of it was serious.

IDP vs PDP vs career development plan vs PIP

Four terms, constantly used interchangeably, and only three of them belong in the same family. Getting the fourth confused with the others is genuinely costly.

IDP and PDP are, in most companies, the same document with a different letterhead. Professional development plans lean a little harder on credentials and are more common in regulated professions where continuing development hours must be logged, but the structure is identical.

A career development plan is genuinely different in scope: two to five years, across several roles, asking where somebody is heading rather than what they should get better at next. The clean way to hold both is that the career plan is the direction and the IDP is the current leg. If someone asks you to write one and the term is ambiguous, ask what horizon it covers. That answer alone tells you which document is wanted.

A performance improvement plan is the opposite of all three. An IDP builds on a standard already being met. A PIP restores one that is not: 30 to 90 days, owned by the manager and HR, triggered by a documented gap, and carrying a consequence.

The individual development plan template, field by field

Seven fields per goal, two or three goals maximum. Five goals do not get five times the attention; they get roughly the same total attention divided into pieces too small to move anything.

Everyone builds the first four fields. Evidence, support and review date are the three that get left off, and they are the three doing the actual work.

Evidencemakes completion falsifiable. Without it, "improve leadership" can be declared done or not done by anybody, at any time, with equal justification.

Supportis the manager's signature on the contract. A plan with an empty support field has quietly become the employee's problem alone, which is exactly what they suspected when they were asked to write it.

Review date converts a document into a recurring obligation. Ten minutes inside an existing one to one is enough. A plan reviewed annually is a plan reviewed once.

Why "attend a course" is usually the wrong action

The 70-20-10 model suggests capability comes roughly 70 percent from doing challenging work, 20 percent from learning directly from other people, and 10 percent from formal training. The precise numbers are a heuristic rather than a measured law, and anyone quoting them to two decimal places is overselling. The ordering, though, is the useful part.

Most real development plans consist of three courses and nothing else, and the reason is structural rather than lazy. A course is the easiest line to write, the easiest to get approved, and the only option that requires nothing from the manager after the budget is signed. Assignments require someone to give away work, arrange exposure, and accept the risk that it goes imperfectly the first time.

Formal training is genuinely useful for vocabulary, frameworks and regulated credentials. It just does not survive on its own: almost nothing sticks unless something in the day job forces the person to use it within a few weeks of learning it.

How to write one, step by step

Development goals that can actually be checked

One test decides everything: could somebody who was not in the room tell whether this happened? If not, it is an intention, not a goal. That test eliminates most of what appears on real plans.

Two of those rewrites deserve a comment. "Become more strategic"is the single most common goal on any development plan and almost nobody can define it, which is why it recurs year after year on the same person's plan. Replace it with the most strategic thing that role can actually do: write the plan for their own area and defend it.

"Complete the leadership course" is worse than vague, it is precise about the wrong thing. It measures attendance. The rewrite measures whether the capability exists, which is a different question with a different answer.

Individual development plan examples

Three worked examples across different roles and different ambitions, including one for somebody who explicitly does not want to be a manager.

The third example is the one most organisations do not write, and it matters. Not everybody wants management, and a development plan that assumes upward movement is the only direction pushes excellent specialists into roles they did not want and are not suited to. You lose the specialist and gain a reluctant manager. Depth is a legitimate destination and deserves the same seven fields, which is a point our guide to succession planning makes about the 9-box grid as well.

Notice what the evidence column never says: completed. Completion is an attendance record. Evidence is a description of what the world looks like when the capability exists.

Running the conversation, for managers

The conversation fails in a predictable way: the manager asks "so what do you want to develop?", gets a polite non-answer, and fills the silence by suggesting a course. Three fixes.

Send one question in advance. Not the form. One question: what work do you want to be doing in two years that you are not doing now? People give considered answers to questions they have had time to think about, and reflexive ones to questions sprung on them.

Keep it out of the performance review. A conversation that feeds a rating is a conversation where people manage their answers, and naming a real weakness becomes irrational. Our guide to self-evaluations covers the appraisal conversation, which this one is deliberately not.

Commit to your half in the room.Name the assignment you will provide and the support you will arrange, out loud, with a date. If you cannot, say so and say why. An honest "I cannot get you that this quarter, so let us pick a different goal" is worth far more than a plan that quietly depends on something you were never going to deliver.

Writing your own when nobody offers you one

Most people never get handed a development plan. Write one anyway; the self-authored version is usually better, because it starts from something you actually want rather than a form somebody has to fill in.

The method is the same as above with one change: your evidence for the gap comes from the outside market rather than an internal level definition. Pull three postings for the role you want in two years, list what they require, and mark honestly which you could evidence today with a specific example. What is left is your plan, and it will be considerably more concrete than anything self-reflection produces. If most of the gap is in how you describe what you already do rather than what you can do, that is a different and much faster fix, covered in our guides to checking your resume against a job description and writing a resume summary.

Then bring it to your manager as a proposal rather than a request. "I would like to be able to run the forecast review by May, here is how I would get there, and what I need from you is thirty minutes of Sam's time before each one" is a very different conversation from "what is my development plan?". The first is hard to refuse and easy to say yes to. The second puts the work on somebody who has eight other people to think about.

The mistakes that kill development plans

• Five goals instead of two. The attention does not scale with the count. It just gets divided into pieces too small to move anything.
• Goals written as adjectives. More strategic, better communicator, stronger leader. Unfalsifiable, therefore unfinishable.
• Actions that are entirely courses. The line that requires nothing from anyone after approval.
• No evidence field. Nobody can say whether it was reached, so nobody asks.
• No named support.Silently makes the plan the employee's problem alone.
• Annual review only. Guarantees the plan is remembered exactly twice.
• Merged with the performance review. Turns it into a conversation where naming a real weakness is against your interests.
• Confused with a PIP. The most damaging one, and it destroys trust in the whole process for everyone who hears about it.
• Written for the current role rather than the wanted work. The subtle one. Thorough, well-meant, and it develops somebody perfectly for the job they were already doing well.

Why this shows up in your turnover numbers

Development plans correlate with retention, but not in the way the correlation is usually sold. The document keeps nobody. What keeps people is visible movement, and the plan is only the mechanism that makes movement legible.

Lack of progression is one of the most common reasons people leave, and it concentrates at the two-to-four year mark, when someone is good at their job and can no longer see what comes next. That pattern shows up clearly if you split your employee turnover rate by tenure band, and it is a different problem from the first-year exits that trace back to hiring.

The warning is that a plan producing no movement is worse than no plan, because it converts a vague dissatisfaction into a specific and evidenced one: they wrote it down and then nothing happened. That is a sentence that turns up in exit interviews constantly. The honest measure of a development programme is not how many plans exist. It is how many people can name something that changed for them because of one.

Every development plan comes down to one question you can ask in month three: what has actually changed for this person since we wrote it? If the answer is a completed course and nothing else, the plan was a document. If the answer is that they now run a meeting they could not run in January, it was a plan. Start from where you want to be rather than from a skills list, and if you want the fastest possible first draft of the gap, paste your resume and a live posting for that next role into Rankid's resume checker and let the missing requirements write it for you.