Guide
Professional development plan examples
A professional development plan is one page that says where you are going, what you will do to get there, and what proof you will collect along the way. Most fail because they describe intentions instead of evidence. Below is a template that survives contact with a real job, plus worked examples for four roles.
The short version
- One or two goals, not nine. A plan with nine goals is a CV wish-list, not a plan.
- Every goal needs an evidence line - what you will be able to point at when it worked.
- Pick goals your day job feeds. Development that fights your workload loses.
- Review quarterly, update whenever something notable happens.
The one-page template
1. The destination: the role or level you are aiming at, and roughly when. "Senior engineer within eighteen months" beats "grow technically".
2. The gap: the two or three things that role needs that you cannot yet prove. Ask someone who hires for it if you are guessing.
3. The goals: one or two statements of what you will be doing that you are not doing now. Each one evidenceable.
4. The actions: the specific projects, responsibilities or asks that will produce that evidence.
5. The proof: for each goal, what dated artefact will exist - a decision you made, a number you moved, feedback in writing.
6. The review: a quarterly date with yourself to check what the record actually shows.
Examples by role
Marketing manager aiming at Head of Marketing
Goal: Own a budget and a strategy, not just campaigns.
- Take ownership of the Q3 campaign budget end to end.
- Present the channel strategy to the leadership team once this half.
- Mentor the new exec through their first product launch.
Evidence when it worked: The budget you controlled and what it returned, the strategy deck and the decision it produced, and dated feedback from the person you mentored.
Software engineer aiming at senior
Goal: Be trusted with ambiguous work without escalation.
- Lead the scoping of one cross-team project per quarter.
- Write the technical proposal for a decision that used to go to a principal.
- Run the incident review process for your area.
Evidence when it worked: Projects you scoped that shipped, proposals that were accepted as written, and incidents where your review changed what the team did next.
Operations lead aiming at Head of Ops
Goal: Move from running processes to designing them.
- Redesign one broken process and measure the before and after.
- Build the hiring and onboarding plan for the next two roles in your team.
- Take over the supplier review cycle from your manager.
Evidence when it worked: The dated before-and-after numbers, the onboarding plan in use, and the supplier decisions you made alone.
HR advisor aiming at HRBP
Goal: Advise on the business, not just the policy.
- Sit in on one department's planning meetings for a full quarter.
- Lead one employee-relations case from first conversation to resolution.
- Present attrition data with a recommendation, not just a chart.
Evidence when it worked: The recommendation you made and what the business did with it, the case you resolved and the outcome, and who now asks for your view unprompted.
Why most development plans die by March
Three killers. First, goals nobody can verify: "improve my communication" fails because there is no artefact that proves it happened. Second, goals detached from the actual job, so the first busy month quietly cancels them. Third, the plan lives in a performance system you open twice a year, so nothing is recorded as it happens and the review becomes an exercise in creative memory.
The fix for all three is the same: every goal gets an evidence line, and the evidence gets captured while it is fresh. Six months from now you will not remember the supplier decision you made in February. Write it down when it happens and the plan reviews itself.
Common questions
What should a professional development plan include?
One or two goals tied to the role you want next, the specific actions you will take, the evidence that will prove progress, and a review date. If any goal cannot be evidenced, sharpen it until it can.
How often should I review a development plan?
Formally, quarterly. Informally, every time something notable happens at work - the plan should absorb real events rather than wait for a scheduled meeting. A plan untouched for six months is a wish list.
What is the difference between a development plan and objectives?
Objectives are what the business needs from you this year. A development plan is what you need from the work - the skills, scope and proof that move you towards the next role. The best plans pick goals where the two overlap, so doing your job builds your case at the same time.
Who owns my professional development plan?
You do. Your manager can open doors, remove blockers and hold you to it, but a plan that only lives in an HR system belongs to the HR system. Keep your own copy and your own evidence.
The plan is the easy part
Look at you go asks you one 90-second question a week and pulls the outcomes, decisions and growing scope into a dated private record - so when your quarterly review comes around, the evidence line is already written. Free to start.
Start my career record