LeadershipGlobal

Individual Development Plan Examples
What a Useful One Looks Like at Director Level

Oliver Helvin19 August 2026~8 minGlobal
← Back to blog
An open monthly planner on a wooden desk, the working document behind a real individual development plan

The key insight:

The test of a good individual development plan is not whether it sounds impressive in the calibration meeting. It is whether your manager could read it in thirty seconds and know exactly what to watch for.

Search "individual development plan examples" and most of what comes back is written for a graduate scheme: a template with boxes for "training courses to attend" and "skills to build", filled in with generic entries like "improve communication" and "attend a leadership course." That version has a use, early in a career, when the goal is simply to build a habit of writing anything down. It is close to useless at director level, where the professional filling it in already knows how to write a development goal and the actual failure is that the goal is too vague to survive contact with a busy quarter.

This guide is not about the method behind building a plan; our guide to writing a leadership development plan you actually follow covers that in full, the six parts that make a plan survive and the four structural reasons most plans fail. This guide is about the artefact itself: what a genuinely useful individual development plan looks like once it is written down, shared with a manager, and put to work, with worked examples of the gap between a plan that sounds right in a review meeting and one that actually changes what happens next.

If you want a structured starting point rather than a blank page, create a free account on AssessYou and the Development Plan module will turn an identified gap into a sequenced plan for you. And if you have not yet identified the gap with any confidence, take the free Leadership Psychometric first; it is the fastest honest starting point for knowing which of your five leadership dimensions is actually the constraint.

JOH Partners Intelligence

Get the fortnightly brief on GCC careers, salaries, and market moves.

No spam. Unsubscribe any time.

The one distinction that separates a useful IDP from a wasted one

Specificity. Not effort, not ambition, not how many boxes are filled in. A plan that names a behaviour an observer would actually see is workable. A plan that names a category is not, no matter how sincerely it was written.

The table below shows the same underlying gap written two ways: as it typically appears in a template filled in quickly before a review meeting, and as it would need to read to actually be actionable.

ElementThe vague version (unworkable)The specific version (workable)
The gap"Improve strategic thinking""In cross-functional forums I default to the functional answer instead of leading with the commercial case, and I have done it three times in the last two exec committee papers"
The vehicle"Attend a strategy course""Own the commercial framing on the Q4 pricing paper, presented to the exec committee myself rather than handed to my VP"
The evidence"Feedback suggests improvement""Two peers and my manager say, unprompted, that the paper led with commercial impact rather than functional detail"
The date"Ongoing""Reviewed at the November one-to-one, before the Q4 paper goes to committee"
The observerNot named"My manager, plus the peer who co-owns the pricing relationship"

Read the right-hand column again. Nothing in it is more ambitious than the left-hand column; it is exactly the same underlying gap. What changed is that every element became something a manager could actually check, three months later, without having to ask the person being developed to grade their own progress.

Three worked examples, by the level of seniority the plan is actually written for

Example one: the individual contributor moving into first management. Gap, stated specifically: "I answer questions myself in team meetings rather than redirecting them to the person who owns the work, which is slowing my team's ownership of their own decisions." Vehicle: the next two sprint planning sessions, deliberately not answering a question directed at the team until someone on the team has answered first. Evidence: the manager and one team member independently notice a shift in who is answering questions in the room. Review: four weeks, because this is a habit correction rather than a capability build, and habit corrections show up faster than capability does.

Example two: the senior manager moving toward director. Gap: "I bring well-researched functional recommendations to the leadership team but rarely frame the trade-off in terms the commercial leaders in the room respond to, so my recommendations get discussed less than their quality deserves." Vehicle: the next three leadership team papers, each opened with the commercial case before the functional detail, reviewed by a commercially-minded peer before submission. Evidence: at least one leadership team member comments unprompted that the papers have become easier to act on. Review: one quarter, tied to the existing leadership team cadence rather than inventing a separate check-in.

Example three: the director building the case for their next step. Gap: "I have never owned a profit and loss line directly, and it is the single most consistent evidence gap identified against me in the last two promotion conversations." Vehicle: negotiate genuine, named ownership of a discrete P&L component in the current role, even a small one, rather than waiting for a bigger mandate to arrive fully formed. Evidence: the finance business partner and the direct manager can both describe, without prompting, a specific decision this person made that moved the number. Review: two quarters, because P&L ownership is a structural change to the role and needs longer to generate real evidence than a behavioural adjustment does.

Notice what is consistent across all three, regardless of level. Each names a behaviour, not a category. Each attaches to work that already exists or is realistically obtainable, which is the principle the Center for Creative Leadership's 70:20:10 research on how leaders actually develop has argued for decades: roughly seventy per cent of real capability growth happens through demanding, on-the-job experience, not through the twenty per cent that comes from other people or the ten per cent that comes from formal training. A plan built entirely from the ten per cent, a course, a workshop, a reading list, is fighting the evidence before it starts.

Pro tool

Build a 90-day development plan

Turn your skills gap analysis into a structured plan with milestones and learning priorities.

Build my plan

What a manager needs from the document, specifically

Because an IDP is a shared artefact, it has to work for two readers, not one: the person doing the developing, and the manager who is meant to notice whether it worked. CIPD's factsheet on personal development planning makes a version of this point from the organisational side, that a plan disconnected from a manager's actual view of the work rarely survives past the meeting it was written in.

In practice, that means writing the plan for someone with five minutes and imperfect memory of your last conversation, not for yourself with full context. State the gap in one sentence a stranger to your career could understand. State the vehicle concretely enough that your manager would recognise it happening. And state the evidence standard in a form specific enough that it could genuinely return a negative result at review, because a standard that cannot fail was never a standard.

Choosing the right gap to put in front of your manager

Not every real gap belongs in a shared IDP. Some genuinely private development work, particularly anything touching Composure under pressure in a way that feels exposing, is sometimes better worked through privately or with an external coach before it becomes a shared document with a review date attached. The test is not whether the gap is comfortable to admit; it is whether naming it to your manager helps you close it faster than working on it alone would. If your manager is well placed to notice the behaviour and create the vehicle, share it. If the honest answer is that your manager cannot actually observe the relevant behaviour or has their own stake in how it is framed, that gap may need a different kind of plan first; a skills gap analysis run independently of the review cycle is often the better starting point in that situation, and the Leadership Psychometric is built specifically to surface which of the five underlying leadership competencies is genuinely your constraint before you commit a quarter to the wrong one.

Key takeaways

  • The distinction between a useful individual development plan and a wasted one is specificity, not ambition: a named behaviour an observer would see, not a category.
  • A workable IDP names the gap as a specific behaviour, attaches it to real live work, states an evidence standard specific enough to fail, and sets a review date, in a form your manager could act on with five minutes and imperfect memory.
  • What belongs in the plan changes by level: habit correction for new managers, framing and commercial fluency for senior managers, and structural evidence gaps such as profit and loss ownership for directors.
  • Roughly seventy per cent of real development happens through demanding, real work rather than formal training, which is why the strongest plans build the vehicle from an existing or realistically obtainable piece of work.
  • Not every gap belongs in a shared document; if your manager cannot genuinely observe the behaviour in question, diagnose it independently first.

For the full method behind building a plan that survives contact with the job, see our guide to leadership development plans, or create a free account to build yours in the Development Plan module on AssessYou.

Frequently asked questions

What is an individual development plan?
An individual development plan, usually shortened to IDP, is the short written document a professional completes, typically with their manager, that names one or two capabilities to build, the specific work through which they will be built, and how progress will be checked. Unlike a private development plan you write for yourself, an IDP is a workplace artefact: it is shared, it is usually reviewed at a set point such as a mid-year check-in, and it is meant to be actionable by someone other than the person who wrote it.
What is a good example of an individual development plan?
A good example names a specific, observable behaviour rather than a category, for example "I default to the functional answer in cross-functional forums instead of leading with the commercial case" rather than "improve strategic thinking". It attaches that behaviour to a real piece of upcoming work with genuine stakes, states what evidence would prove it has changed, and sets a review date inside the next quarter. A weak example states an aspiration with no attached evidence and no date.
How is an individual development plan different from a leadership development plan?
In practice the terms overlap heavily, but the IDP usually refers specifically to the shared, manager-facing workplace document, often tied to a formal review cycle or talent process, while a leadership development plan can be a broader, self-directed piece of work covering more ground and answering to nobody but the person who wrote it. Our guide to writing a leadership development plan you actually follow covers the full method behind building either one; this guide focuses on what a strong IDP specifically looks like once it is written down and shared.
How long should an individual development plan be?
Short enough that your manager could read the whole thing in the time it takes to walk between meetings, typically under a page for one priority. Length is not a proxy for seriousness; a two-page plan with five priorities is a wish list, and a five-line plan with one priority, a real vehicle and a genuine evidence standard is a plan someone can actually follow.
What should an individual development plan include for a director-level professional?
At director level and above, the content shifts away from technical or process skills and toward commercial breadth, influence without formal authority, composure under pressure, and delivering through others rather than personally. A director-level IDP that lists a technical certification as its single priority has usually misdiagnosed the actual constraint on the next promotion.
Who should be involved in writing an individual development plan?
At minimum, the professional and their direct manager, because the manager is usually the person best placed to attach the plan to real, live work and to notice whether the behaviour has actually moved. A third, more senior sponsor or an external structured assessment adds real value at director level and above, where the direct manager may share some of the same blind spots as the person being developed.

JOH Partners Intelligence

Get the fortnightly brief on GCC careers, salaries, and market moves.

No spam. Unsubscribe any time.

Pro tool

Build a 90-day development plan

Turn your skills gap analysis into a structured plan with milestones and learning priorities.

Build my plan

More from JOH Partners