How to Write a Leadership Development Plan You Actually Follow

The key insight:

A plan with five priorities has none. The single most reliable predictor of whether a development plan produces anything is how much it was willing to leave out.

Almost everyone at senior level has written a development plan. Very few have finished one. The failure is so consistent that it is worth treating as structural rather than personal: plans do not collapse because people lack discipline, they collapse because they were built in a way that guaranteed it.

This guide assumes you already know what your gap is. If you do not, that is a separate exercise and the right instruments are a skills gap analysis or a 360 leadership assessment, either of which will give you a starting point better than intuition. What follows is what to do once you have one: how to construct a plan that survives contact with a demanding job, written from the seat the executive search team at JOH Partners occupies, where we see the results of these plans years later in the candidates they produced.

If you want the plan structured for you rather than drafted from a blank page, the Development Plan module on AssessYou turns an identified gap into a sequenced ninety-day plan; create a free account to build one.

Why most development plans fail

Four reasons, and none of them is motivation.

Too many priorities. The plan names five areas because all five are real. Senior capability moves slowly, attention divides, and five areas of slow movement is indistinguishable from none. This is the single most common cause and the easiest to fix, and it is nearly always resisted, because cutting the list feels like conceding that the other four do not matter.

Built from courses. A plan whose actions are all training is a plan to learn about a capability rather than to acquire it. Courses are useful as inputs. They are not development, and a completed course is not evidence of a changed behaviour.

Success defined as completion. If the measure is whether the activities happened, the plan will be completed and nothing will have changed. The measure has to be whether the behaviour moved, which is harder to define and is the entire point.

Nobody is checking. A plan with no observer is a private intention. Senior professionals are unusually good at persuading themselves that something has improved, and the only reliable correction is somebody close enough to the work to notice whether it has.

The six parts of a plan that works

One. The gap, stated as a behaviour. Not "improve strategic thinking" but "I default to the functional answer when the question is commercial, and I do it in front of the executive committee". Vague gaps produce vague plans. If you cannot state the gap as something an observer would see you doing, you do not yet have a gap, you have a category.

Two. Why it matters now. One sentence connecting the gap to something concrete: a role you want, a piece of feedback, a decision that went badly. A plan without a reason attached is the first thing dropped when the quarter gets difficult.

Three. The vehicle. The actual piece of work through which the development will happen. It should be live, it should have consequences, and it should already exist or be plausibly obtainable. This is the part people skip, and skipping it is what turns a plan into a wish.

Four. The evidence standard. What would convince a sceptical observer that this has changed? Write it before you start. It is easier to be honest about the standard in advance than to grade yourself against a moving line afterwards.

Five. The observer. One person who sees you work and will say something true. Not your closest ally, and ideally not your line manager alone, because the line manager relationship carries incentives that distort feedback in both directions.

Six. The date. Ninety days to a review point. Not "ongoing".

The anatomy of a plan that survives contact with the job

Read the right-hand column as a diagnostic. Most abandoned plans have three or four of those failure modes at once, and the first two rows tend to cause the rest.

Choosing the one thing

The hardest instruction in this guide: pick one, and hold a second in reserve.

The way to choose is not by size of gap but by consequence. For each candidate gap, ask a single question. If this were closed, would it change whether I get the role I am aiming at? Most gaps fail that test. The one or two that pass are the plan, and everything else goes on a list you revisit in a year without guilt.

A second filter helps when two candidates both pass. Prefer the gap that unlocks others. Composure under pressure, for instance, is upstream of a great deal: it improves how judgement is perceived, it changes how difficult conversations land, and it makes influence possible in rooms where authority is absent. Commercial breadth behaves similarly. Gaps like these are worth more than their description suggests because closing one moves several.

Be honest about which gap you are choosing to avoid. Almost every senior professional, asked privately, can name the thing they have been not addressing for years. If that thing did not make the plan, it is worth writing down why, because "I chose not to work on this and here is the reason" is a defensible position and quiet avoidance is not.

Exposure beats training

Senior capability is built by doing the thing in a real setting where the outcome matters, and it is built almost no other way.

This is not an argument against learning. It is an argument about sequence and proportion. Reading about influence gives you vocabulary; being handed a cross-functional programme where you have no authority over anyone gives you the capability. If the gap is commercial breadth, the vehicle is the profit and loss conversation you currently leave to someone else, not a finance course. If it is delivering through others, the vehicle is deliberately not doing the thing you are best at and letting someone less experienced do it while you carry the risk.

Three things make a vehicle a good one. It has to be real, so failure has a cost. It has to be visible, so somebody notices the change. And it has to be uncomfortable in the specific way your gap is uncomfortable, because a stretch in a direction you are already strong in is just more work.

Choosing badly here is the most common single error after having too many priorities. People select vehicles that are adjacent to the gap rather than on it, because the adjacent thing is available and the actual thing is daunting. The test is simple: if the vehicle does not make you slightly reluctant, it is probably the wrong one.

Evidence, and the ninety-day cadence

Write the evidence standard before you begin, in a form specific enough that it could return a negative result. "Colleagues would say I am more commercial" cannot fail. "In the next three executive committee papers I write, the recommendation leads with the commercial case and my line manager and one peer both say so unprompted" can. A standard that cannot fail is not a standard.

Then run it in ninety-day cycles inside a twelve-month horizon. At each review, three questions and nothing else. Did the work actually happen, or did it get deferred? Did the evidence appear? And is this still the right gap, given what the last quarter revealed? The third question matters because plans are sometimes wrong, and a plan that cannot be revised becomes a plan that gets abandoned instead.

Two failure patterns show up at the first review with some regularity. The first is that the vehicle never materialised, which is usually a scheduling problem masquerading as a capability problem and is fixed by choosing a smaller vehicle rather than by trying harder. The second is that the work happened and nothing changed, which is more interesting and usually means the gap was misdiagnosed. That is a reason to go back to the assessment rather than to repeat the quarter.

It is worth knowing what kind of change to expect. Behaviour under pressure shifts over quarters rather than weeks, and it shifts unevenly: better in familiar settings first, then in unfamiliar ones. Style is different again, more a matter of range than of replacement, which is the point our guide to types of leadership styles makes at length. And where the constraint is presence rather than capability, the development path is different once more, and executive presence sets out what actually moves it.

Finally, a plan is a response to a diagnosis, and diagnoses go out of date. Re-run the underlying assessment annually. If what you want to know is whether you are progressing relative to your cohort rather than against your own baseline, that is a separate measurement and peer benchmarking is the instrument for it.

Key takeaways

• Development plans fail for structural reasons: too many priorities, actions built from training rather than real work, success defined as completion, and no observer.
• Six parts make a plan work: the gap stated as a visible behaviour, the reason it matters now, a live vehicle with consequences, an evidence standard written in advance, a named observer, and a date.
• Choose one priority by consequence, not by size, and prefer gaps that unlock others. Composure under pressure and commercial breadth both behave that way.
• Exposure builds senior capability and training rarely does. If the vehicle does not make you slightly reluctant, it is probably adjacent to your gap rather than on it.
• Run ninety-day cycles inside a twelve-month horizon, and treat a quarter where the work happened but nothing changed as a diagnosis problem rather than an effort problem.

For more on how senior leaders are assessed and developed, see the full Leadership collection, or create a free account to build a Development Plan.

JOH Partners Intelligence

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

No spam. Unsubscribe any time.