Back to blog
7 min readKoru Team

Personal career development plan: a template based on evidence

Build a personal career development plan from real work evidence. Use the worksheet, completed example, and 90-day proof checkpoints.

career-developmentcareer-planningprofessional-development

A personal career development plan is a short working document that connects your next career direction to the skills, relationships, experiences, and proof you need to build. The useful version is not a wish list. It answers five questions:

  • Where am I trying to move?
  • What does my current work already prove?
  • What gap is still visible?
  • What will I do in the next 90 days?
  • What evidence will show that the plan is working?

That evidence piece is where most plans get weak. A plan that says "become a stronger leader" sounds reasonable, but it does not tell you what to do on Monday or what to show your manager in three months. A better plan says: "Lead one cross-functional project, document stakeholder feedback, and show that I can make tradeoff decisions without my manager in the room."

That is the Koru angle: career planning should start from what your work already proves, then use the plan to close the gaps. The worksheet below works on its own, even if you never use Koru. If you need the raw material first, start with a weekly career journal template or the guide on tracking career achievements.

Why evidence belongs in the plan

The U.S. Office of Personnel Management describes an individual development plan as a tool for personal and professional development goals, often used with a supervisor to set learning objectives and competencies. The National Institute of General Medical Sciences makes a similar point in mentoring contexts: the plan helps structure career conversations and should be reviewed over time.

That is useful, but it still leaves a practical problem. If you start with only "goals," the plan gets aspirational fast. You pick a target role, list a few skills, add a course, and then forget the document until the next review cycle.

Evidence keeps the plan usable. It shows the difference between:

Vague plan

"I want to move into a senior role, improve leadership skills, and get more visibility."

Evidence-based plan

"I have led two launches inside my team. To be ready for a senior role, I need cross-functional evidence: one project with Product, Sales, and Support, plus written feedback from each lead."

The second plan is less polished. It is also much easier to act on.

The evidence-first template

Use this as a one-page worksheet. Fill it from left to right. If a column is empty, that is useful information: it tells you whether you need more reflection, more work evidence, or a better conversation with your manager.

Personal career development plan worksheet
FieldWhat to writeGood example
Target directionThe role, scope, or kind of work you want more of.

Move toward senior product manager scope over the next 6-12 months.

Current evidenceWork that already proves part of the target.

Owned checkout experiments, coordinated engineering handoffs, presented two roadmap updates.

Gap to closeThe missing proof, not a personality flaw.

No evidence yet of leading a cross-functional decision with conflicting stakeholder needs.

90-day actionA specific project, habit, conversation, or learning loop.

Take ownership of the Q3 onboarding redesign discovery, including Sales and Support interviews.

Proof checkpointWhat will show progress at the end.

Decision memo, stakeholder feedback, before/after activation metric, manager review note.

Conversation neededWho needs to agree, sponsor, unblock, or review the plan.

Ask manager to confirm whether this project is the right senior-scope signal.

Keep the plan boring enough to use. One direction, one gap, one 90-day action. You can add another row later.

A completed example

Here is what the worksheet looks like when it is specific enough to guide real behavior.

Example: moving toward senior scope

Target direction

Move from product manager to senior product manager scope within 6-12 months.

Current evidence

  • Led checkout experiment backlog for two quarters
  • Coordinated engineering and design handoffs for the pricing page rebuild
  • Presented roadmap updates in monthly product review

Gap to close

I have evidence of execution inside my area, but not enough evidence of leading a decision across teams when priorities conflict.

90-day action

Own discovery for the onboarding redesign. Interview Sales, Support, Customer Success, and Engineering. Write the tradeoff memo. Bring a recommendation to product review.

Proof checkpoint

  • Tradeoff memo reviewed by at least three team leads
  • Manager feedback on decision quality
  • One shipped change from the discovery work
  • Notes from stakeholder disagreement and how it was resolved

Conversation needed

"I want to use the onboarding redesign as evidence for senior scope. Is this the right project to prove cross-functional decision-making, or should we choose a different one?"

Notice what is missing: no dramatic personal reinvention, no vague "be more strategic," no list of random courses. Training can belong in the plan, but only when it serves a gap you can name.

How to find your current evidence

If you already keep work notes, use them. If you do not, do a quick audit before writing the plan.

  1. 01

    List the work that expanded your scope

    Look for moments where the boundary of your role got bigger: more stakeholders, harder decisions, larger projects, more ambiguous problems, or responsibility that used to sit with someone senior.

  2. 02

    Pull the proof, not the feeling

    "I became more strategic" is a feeling. "I wrote the pricing tradeoff memo that aligned Product, Finance, and Sales" is proof. If you struggle here, use the method in how to ask for a promotion with evidence.
  3. 03

    Name the missing signal

    Do not write "I need confidence." Write the professional signal you still need: presenting to executives, mentoring juniors, owning a budget, handling customer escalations, or leading work across teams.

For new roles, the first 90 days tracking guide is a good source of evidence because the first months show learning speed, pattern recognition, and early contribution.

Use the plan with your manager

A development plan works better when it becomes a conversation, not a private document. Bring a draft to your next 1:1 and ask for calibration.

That question does two useful things. It shows that you are taking ownership of your growth, and it gives your manager a chance to correct the plan before you spend months building evidence they will not value.

It also separates development planning from promotion lobbying. A promotion case argues that your scope already changed. A development plan identifies what proof still needs to exist. If you are closer to promotion season, read performance review prep and build the case from there.

How Koru keeps the plan alive

The plan is only useful if it meets fresh evidence. Otherwise it becomes a tidy document with stale assumptions.

This is where a career journal helps. Each week, capture the moments that relate to the plan:

  • a decision you made
  • feedback you received
  • a difficult conversation
  • a project where your scope changed
  • a skill you used under pressure

Over time, those entries tell you whether the plan is real. Maybe you are building the evidence you intended. Maybe the work is pointing somewhere better. Maybe the target role looks less appealing once you see what the day-to-day proof requires.

That is a good outcome. A personal career development plan should not lock you into an old idea of yourself. It should give you a clean way to notice what your work is already saying.