Someone asks you to "put together a development plan" and you open a blank doc, stare at it for ten minutes, and write "improve communication skills." That's not a plan. That's a wish. I've watched people sit on documents like that for a year and end up exactly where they started, just with a fancier title on their email signature.
Building a leadership development plan that actually changes how you operate comes down to five moves, and none of them involve downloading a 40-page PDF that nobody reads past page three.
Key takeaways
- A development plan is a written commitment with dates, not a list of aspirations.
- Self-assessment is the hardest part, and the most skipped. Budget a full week for it.
- Two or three priorities beat eight. Ruthlessly cut the rest.
- You need one person who will tell you the truth, and one who will hold you to the calendar.
- Review every 90 days. If nothing has moved by day 90, the plan is wrong, not you.
- It works without budget, HR support, or a formal program. I'll show you how.
What a leadership development plan actually is (and what it isn't)
A leadership development plan is a short document that connects three things: where you are as a leader right now, where you need to be in 6 to 12 months to do the job you want, and the specific actions that close the gap. That's it. The moment it becomes a catalogue of every skill you've ever admired in someone else, it stops being a plan.
Here's the distinction most people miss. A training plan lists things you'll consume—courses, books, workshops. A development plan lists things you'll do differently, with evidence attached. Consuming is comfortable. Doing differently is not.
How is it different from a training plan?
Imagine two managers. Manager A signs up for a negotiation course, finishes it, gets a certificate. Manager B runs the next three supplier conversations herself instead of delegating them to her director, then debriefs each one with her own manager. Six months later, only one of them negotiates better. You already know which.
How is it different from a performance review?
A performance review looks backward and belongs to your company. A development plan looks forward and belongs to you. They can reference each other, but they serve different masters. If your plan only contains items your manager wrote down, you're executing someone else's agenda.
Step 1: collect evidence, not opinions
The first move is the one everybody rushes. Before you write a single objective, gather actual data about how you lead today. Not how you feel about how you lead today—that's a different question, and usually a flattering one.
When I built my first version of this, I wrote down "strong strategic thinker" as a strength. Then I looked at my calendar for the previous month and found I'd spent maybe two hours on anything resembling strategy. The rest was firefighting. My self-image and my calendar told two different stories, and the calendar won.
Three sources of honest input
- Your calendar. Where did the hours actually go? This is unfakeable data.
- Two or three people you've worked with closely. Ask one question: "What's the one thing I could change that would make the biggest difference to you?" Then shut up and write it down without defending yourself.
- One recent failure, examined closely. A project that went sideways, a hire that didn't work out, a meeting that turned into a fight. What was your role?
That last one is where the real information lives. I once ran a reorg that lost me two of my best people within a quarter. Took me months to admit the cause wasn't "market conditions." I'd made the decision without consulting the two people most affected, because I was afraid of the conversation. That fear became a priority in my plan, and naming it was worth more than any course I've taken.
Step 2: pick two or three priorities, then defend the cut
Most plans die of ambition. Eight priorities means zero priorities, because attention divides and nothing gets deep enough to stick.
Pick two or three. For each one, write a sentence that connects it to a business outcome you can name. "Improve delegation" is weak. "Delegate the weekly client report so I free up six hours a week for hiring" is a plan item—it has a mechanism, a quantity, and a reason.
A template that takes ten minutes
Click to see the structure I use
- Priority: one sentence, behavioral, specific.
- Why it matters: the business or team outcome it serves.
- Current baseline: what happens today, honestly.
- Actions: two to four concrete things, each with a date.
- Evidence of progress: what will be observably different in 90 days.
- Support: who helps, and what you need from them.
- Review date: a real date in your calendar.
That's your whole template. If you want a PDF version, print this page. I mean that sincerely—the format isn't the hard part.
Step 3: design actions that fit your actual week
Actions that require a calmer calendar than the one you have will not happen. Design for the week you actually live, not the week you wish you had.
| Action type | Cost | Time per week | Best for |
|---|---|---|---|
| Stretch assignment on live work | Zero | Embedded in existing tasks | Building judgment under real stakes |
| Feedback loop with a peer | Zero | 20–30 minutes | Behavior change you can't see yourself |
| Structured course or certification | Moderate | 2–4 hours | Filling a specific knowledge gap |
| External coach | High | 1 hour plus prep | Working through something you can't discuss internally |
| Shadowing a leader you respect | Zero | 1–2 hours | Seeing a different operating style up close |
Notice that the two most effective rows cost nothing. That's not a coincidence. Development happens in the work, not beside it.
Step 4: build accountability that survives a bad month
In my experience, this is where plans actually succeed or fail—not in the design, but in whether anyone notices when you stop. I'll die on this hill: a plan with no witness is a diary entry.
Pick one person. Give them your 90-day evidence list. Ask them to check in once a month with a single question: "Did it happen?" Not "how's it going"—that invites a story. "Did it happen" invites a fact.
And here's the part people hate: when the answer is no, the follow-up is not "try harder." It's "what's in the way, and what are we cutting?" A plan that can't be cut can't be kept.
What if you have no budget and no HR support?
Good news—you don't need either. Build the plan for your own role, find one peer who'll exchange feedback honestly, and use live work as your training ground. I've seen this outperform formal programs, mostly because there's no place to hide behind attendance.
Step 5: review every 90 days, and be willing to throw it out
Ninety days is short enough to stay honest and long enough for something to change. At each review, ask three questions. What moved? What didn't, and why? What should change in the plan itself?
That third question is the one people skip, and it's the one that keeps the document alive. Halfway through one cycle, I realized my top priority—running better meetings—was solving a problem the team had already solved on its own. Keeping it would have been busywork dressed up as growth. I replaced it and moved on.
Do you actually need a plan for your current job?
Not always. If you're happy where you are and growing on the job, a formal document may be overhead. But if you're aiming for a different scope, a bigger team, or a different kind of work, writing it down forces a level of specificity that thinking about it never does. The document isn't the point. The specificity is.
One last thing worth sitting with. The leaders I've watched grow fastest weren't the ones with the most polished plans. They were the ones who picked the uncomfortable priority—the conversation they'd been avoiding, the habit they were a little embarrassed about—and put a date next to it. Everything else is formatting.
So: which priority would you be relieved to not have to write down? That's probably the one.
