How to write a career development plan

A career development plan written by a manager for an employee is a to-do list. Co-created, it becomes a commitment.

The distinction matters because motivation works differently depending on the source of a goal. People are significantly more likely to follow through on development goals they helped shape than ones that were assigned to them, even if the goals themselves are identical. Process determines ownership.

A career development plan is a documented agreement between an employee and their manager about where the employee wants to grow and what they will do to get there. It is not a performance improvement plan. It is not a job description. It is a forward-looking map, built on what the employee actually wants.

What a career development plan is (and is not)

A career development plan covers development goals, skills, responsibilities, and expertise the employee wants to build beyond their current role. It is different from a performance plan, which addresses what needs to improve to meet the requirements of the existing job.

Both can exist at the same time, but mixing them in the same document creates confusion. An employee who sees development goals and performance concerns on the same page is likely to read the whole thing as remediation.

A career development plan also does not need to be long. A single page with three goals, a timeframe, and a check-in cadence is more useful than a detailed document no one opens again until the annual review.

Step 1: Start with what the employee wants

Before you open a document, have the conversation. Ask where they see themselves in two to three years. Ask what kind of work they find most energising. Ask what they want more of and less of in their current role. Take notes, their answers drive everything else.

Do not go in with a draft. A manager who opens the conversation with "I was thinking you could work toward X" has already skipped the most important step. Their ambition is not the starting point. The employee's ambition is.

Some employees struggle to articulate what they want, particularly early in their careers. That is fine. Useful prompts: "What would you do if the current constraints didn't exist?" "What would you find it hard to give up?" "Who in the organisation is doing work you find interesting?"

Step 2: Map ambitions to what is available

Once you understand what the employee wants, explore what the organisation actually offers. What roles exist on the trajectory they are describing? What skills are typically needed to get there? What does the realistic timeline look like?

Be honest about what is and is not possible. A manager who makes implicit promises they cannot keep, "I see leadership potential in you" with no specific path behind it , does more damage than one who is direct about the constraints. If the organisation cannot support the ambition, say so. That conversation is better had now than in two years.

This step also includes identifying the gaps. If the employee wants to move toward management, what specifically needs to develop? Technical skills? Influence? Experience leading a project? Name the gaps so the goals you set can address them.

Step 3: Set 3 to 5 specific goals

Translate the conversation into concrete goals. Each goal should have:

• A specific description of what "done" looks like
• A realistic timeframe, typically 3 to 12 months
• A connection to the longer-term ambition

Vague goals do not work. "Improve leadership skills" is a direction, not a goal. "By the end of Q3, take ownership of running the weekly team standup, including agenda setting and follow-up on actions, as preparation for putting my name forward for team lead roles next year" is a goal.

Three focused goals are more useful than eight scattered ones. If the employee tries to pursue too many development areas at once, they end up progressing slowly on all of them rather than meaningfully on a few.

Step 4: Define how progress will be tracked

Agree on a cadence for check-ins. Monthly is usually the right frequency, frequent enough to stay relevant, light enough not to become another process to manage.

A check-in does not need to be a dedicated meeting. Three questions at the end of a regular 1:1 is enough: How is the development goal going? What progress has happened since we last spoke? What would help in the next month?

Without a defined cadence, the plan goes into a folder and gets opened again at the annual review, at which point both parties have largely forgotten what was agreed.

Step 5: Connect it to the performance cycle

Development goals should be reviewed at formal performance check-ins and the annual review. When development and performance are treated as entirely separate conversations, development becomes optional, something to fit in if there is time.

Including development in the performance review sends a clear signal: growth is part of the job, not an extracurricular.

Frequently asked questions

What should be in a career development plan?

A career development plan should include the employee's longer-term ambition, 3 to 5 specific development goals tied to that ambition, a timeframe for each goal, and a defined check-in cadence. It should be built with the employee, not for them, the plan only works if the employee feels genuine ownership over it.

How often should you review a career development plan?

At a minimum, twice a year, at the mid-year check-in and the annual review. A brief monthly check-in at the regular 1:1 is usually enough to keep the goals alive between formal reviews. Without regular check-ins, the plan loses relevance quickly.

What is the difference between a career development plan and a performance plan?

A performance plan addresses what needs to improve to meet the requirements of the current role. A career development plan is about growth beyond the current role, where the employee wants to go and what they will do to get there. Both can exist simultaneously but should be kept in separate conversations to avoid one being read as a cover for the other.