What is an individual development plan?

An individual development plan (IDP) is a structured, forward-looking document that captures where an employee wants to go in their career and the concrete steps that will get them there. Unlike a performance review, which looks backward at what already happened, an IDP looks ahead — it is a shared commitment between an employee and their manager to invest in the employee's growth.

The template below gives you the structure immediately: career goal, current strengths, a development-areas tracker tied to a competency scale, time-bound action steps, success criteria, and a check-in log — so the plan stays a living document instead of a form filled out once a year and forgotten.

What is in the download?

The Excel file has two sheets:

  • IDP Template sheet. The blank form — employee details, career goal, current strengths, a development-areas table with dropdown validation (1–5 proficiency scale, High/Medium/Low priority), an action-steps table with a status dropdown (Not started / In progress / Complete), success criteria, and a check-in log.
  • Filled-In Example sheet. A complete, realistic IDP for a Senior Software Engineer targeting a promotion to Staff Engineer over 12–18 months — four development areas, five action steps with real target dates, and two logged check-ins.

How to fill in an IDP — 5 steps

  1. Set the career goal. Anchor it to a specific role or level — ideally one from your career ladder — over a 12–24 month horizon. "Get better at leadership" is not a goal; "reach Staff Engineer by taking on cross-team technical ownership" is.
  2. Pull development areas from a recent competency matrix. Any competency with a gap of 2 or more between current and target level is a strong candidate. If you have not run one recently, start with our free competency matrix template.
  3. Convert each gap into 1–2 action steps. Every action step needs an owner, the resource or support needed to complete it, a target date, and a status. Vague actions ("read more about leadership") produce vague progress — specific actions ("lead the Q3 platform migration end to end") produce visible evidence.
  4. Agree on success criteria. Write down what "done" looks like in concrete, observable terms — a completed project, a peer-feedback pattern, a calibration outcome — not just "improved leadership skills."
  5. Set a check-in cadence and use the log. Monthly check-ins, even brief ones, keep the plan connected to actual work. Quarterly is the minimum; anything longer and the IDP tends to become a document written once and revisited only at the next review.

IDP example: Senior Engineer targeting Staff

The filled-in sheet shows a realistic case: a Senior Software Engineer (IC3) whose strengths are technical depth and delivery reliability, with a clear gap in Leadership (2 → 4) and smaller gaps in Communication and Technical Depth. The action steps are concrete and dated — leading a cross-team migration project, presenting at an all-hands, mentoring a junior engineer — each mapped to the competency it develops. This is the pattern to follow: every action step should trace back to a specific gap, not a generic "professional development" line item.

IDP vs. performance review vs. PIP

These three documents get confused often, but they serve different purposes:

  • Performance review — backward-looking; evaluates what an employee actually did against expectations for a defined period.
  • Individual development plan (IDP) — forward-looking and growth-oriented; exists for any employee, regardless of current performance, to plan their next step. This is what you are downloading.
  • Performance improvement plan (PIP) — remedial; exists specifically to correct underperformance against current role expectations, with a defined timeline and consequences for not meeting it. Using IDP-style open-endedness for a genuine performance issue delays action that needs to happen faster.