Individual development plan template

What an IDP is and is not

An individual development plan is a written agreement between an employee and their manager about what the employee will learn next, how, and with what support. It looks forward and is about growth. A performance review looks back and is about results. A performance improvement plan is about fixing a shortfall within a deadline. Keep the three apart. An IDP that turns into a disguised PIP teaches employees to avoid development conversations.

IDPs are most useful for people who want to grow: high performers, new supervisors, people moving across functions, and anyone named in a succession planning template as a possible successor. They are less useful as a box-ticking exercise for every employee every year.

Building actions with 70-20-10

The 70-20-10 model is a rule of thumb that most workplace learning comes from experience (70), from other people (20) and from formal courses (10). The numbers are not precise, but the point holds: a development plan made only of courses rarely changes much.

Take a contact center agent who wants to become a team lead. A weak IDP says "complete leadership fundamentals course." A strong one says: run the team huddle twice a week for a month (experience); shadow two team leads during coaching sessions and get feedback from one of them after leading a session (others); complete the internal coaching course by the end of Q2 (formal). Success measure: leads three calibrated coaching sessions with QA sign-off. That plan gives the employee real practice and gives the manager evidence for a promotion decision.

Finding the right development areas

Start from the target, not the weaknesses. What does the next role or the bigger version of this role require? Compare that with what the employee does well now. The gap is the development area. A skills matrix or the competency profile for the target role makes this concrete; at team level, a training needs assessment shows which gaps are common enough to address with a group program instead of individual plans.

Limit it to two or three areas. People with seven development goals make progress on none. And include at least one area that builds on a strength. Getting from good to excellent at something often matters more for a career than getting from weak to adequate.

Common IDP mistakes

• Written once, never opened again. Put quarterly reviews in the calendar when the plan is signed.
• Only courses. Training is the easiest action to write and the least likely to change behavior on its own.
• No manager commitment. If the plan says "lead a cross-functional project" and no project ever appears, the employee will stop trusting the process.
• Vague success measures. "Better at presenting" cannot be checked. "Presents the monthly operations update to the site director twice, with feedback from the director" can.
• Treating the IDP as a promise of promotion. Say clearly that building the skills makes the employee a stronger candidate, not a guaranteed one.

IDPs at scale

A 1,500-person operation cannot run a detailed IDP for every frontline employee, and should not try. A practical model: frontline staff get a short development section in their quarterly review with one skill and one action; team leads, high potentials and anyone in a succession pool get the full IDP. Standard development paths for common moves (agent to QA analyst, agent to trainer, associate to shift lead) save managers from writing the same plan from scratch.

Connect IDP goals to the employee's regular goals so development is not something that happens only when work is quiet. Our goal setting template includes a development goal slot that can mirror the top IDP area. Track completion and internal moves by team; the share of promotions filled from people with an active IDP is a simple measure of whether the plans are doing anything.