How to Create a Career Development Plan That You Will Actually Use

A career development plan is a practical record of where you want your working life to go, what skills and experiences will help you move in that direction, and the actions you will take to get there.

It is not the same as a performance appraisal. A performance appraisal looks at your contribution and expectations in your current role. A development plan asks what you would like to learn, practise or move towards next. The two can inform each other, but they are not interchangeable. If you are preparing for a formal review, my guide to preparing for a performance review covers that conversation.

It is also not a promise of a promotion. Career development might mean becoming an expert, gaining more responsibility, changing direction, preparing to lead others or finding work that feels more satisfying.

I think that distinction matters. Not everybody wants to be a manager, and someone who loves their current role should still have the opportunity to develop.

Before opening a spreadsheet or choosing a course, ask yourself a simpler question: what would I like more of in my working day?

Perhaps you want to solve more complex problems. Perhaps you enjoy coaching people, writing, building systems, understanding technology or improving how a team works. Perhaps you want a little more influence over decisions. Or perhaps your current role suits you perfectly, but you want to feel more confident doing part of it.

Try finishing these sentences:

You do not need to find one grand purpose. You are looking for a direction that feels relevant to you.

A manager’s perspective: when someone tells me they want to develop, my next question is usually “towards what?” Not because I expect them to know exactly where they will be in five years, but because the answer helps us choose the right support and opportunities.

Many development plans begin with a list of weaknesses. I would rather start with what is already working.

Which situations bring out your best work? What have colleagues recognised? What do people trust you to handle? Where have you made progress recently? Then look at the gap between those strengths and the type of work you want to do next.

For example, someone who wants to lead more projects may be good at organising tasks but need more practice managing expectations with stakeholders. Someone interested in a specialist role may need deeper technical knowledge rather than better presentation skills.

You can gather evidence from recent work, feedback and job descriptions for roles that interest you. Do not treat a job advertisement as a checklist of everything you must already possess. Use it to understand which capabilities are repeatedly mentioned.

One useful exercise is to write three columns, as in the example below. The example is illustrative; replace it with evidence from your own work.

A career plan becomes a second job if it contains every possible ambition you have ever had. I would choose one substantial development goal and, if useful, one smaller supporting goal. Both should connect to opportunities that actually exist.

A vague goal sounds like this: “Become a confident leader.”

A more useful one sounds like this: “Over the next three months, lead the agenda and follow-up for one cross-team meeting, ask for feedback twice and identify one change I want to make next time.” The second version has a behaviour, a timeframe and something to review. It does not pretend confidence is a number you can magically increase.

For technical development, an equivalent goal might be: “Complete a relevant introductory course, apply one technique to a real piece of work and have an experienced colleague review the result.”

A goal should be challenging enough to be meaningful and realistic enough to survive an ordinary busy month.

I enjoy formal learning, and a good course can be a wonderful investment. But a certificate is not the whole development plan. What will you do with the knowledge afterwards?

I would always look for a way to practise. That might mean taking responsibility for a small project, shadowing a colleague, presenting a recommendation, joining a working group, solving a problem with someone more experienced or asking for feedback after a difficult task.

CIPD guidance also recognises that professional learning can combine planned activities with learning as part of the work itself. That is a useful way to think about a development plan: formal learning provides input, and actual work gives you somewhere to apply it.

For each development goal, choose three elements:

If you cannot identify a practice opportunity, the goal may be too abstract, or you may need a conversation with your manager about creating one. I have written about how to have a career development conversation with your manager for exactly that moment.

This is the part I feel particularly strongly about.

A good manager should not simply tell somebody to develop and leave them to work everything out alone. The manager has a responsibility to clarify expectations, help identify opportunities, offer feedback and explore appropriate support. Equally, the employee has an active part to play: engaging with the opportunity, practising, asking questions and following through. A useful development plan separates the two, as in the table below.

Not every request can be funded or accommodated immediately. That is part of the conversation. A sensible alternative might be a smaller project, a mentor or a different timeframe.

And if there is genuinely no room to develop in the direction that matters to you, that is useful information too. You can explore other opportunities without making an impulsive decision.

I favour simple systems because they are easier to revisit. Below is an example of what a one-page career development plan might look like over twelve weeks. It is a fictional example, not a record of a particular employee or employer.

There is nothing wrong with a sophisticated tracker if you enjoy using one. But a beautifully designed plan cannot substitute for the actual conversations and opportunities. Start with a single page, and build a system only if you need it.

A plan is not supposed to sit untouched until the end of the year. Set a short check-in, perhaps every four to six weeks, and ask:

Evidence might include a piece of work, feedback from a colleague or an improvement you can describe clearly. It does not all need to become a performance metric.

Sometimes the most valuable outcome is that you discover a particular direction is not for you. That is not wasted effort. It is better information.

If a project is cancelled, the team changes or your personal circumstances shift, review the plan. Adaptability is part of good planning.

Then begin with experiments, not a declaration.

Choose something you are curious about and find a low-risk way to experience it. Ask someone what their work involves. Join a project for a limited period if the opportunity exists. Read about a role. Attend a session. Ask for feedback on an ability you already use.

You do not need to commit yourself to a new career simply because you want to learn about one. I find that a little curiosity often creates better direction than forcing yourself to write a confident statement you do not believe.

Make the conversation specific. Find out what the role requires, which responsibilities demonstrate readiness, how opportunities are assessed and what evidence would be useful.

Be honest about the difference between working towards a role and being promised one. Your manager may support your development without being able to guarantee a vacancy, a salary change or a particular outcome.

Ask for experience you can use wherever your career eventually takes you. Those skills remain valuable even if the next opportunity is not available immediately.

First, be specific about the support you need. A request for one hour of feedback or a chance to join a meeting may be easier to discuss than a general statement that you need more opportunities.

Ask what alternatives exist. If resources are constrained, agree what is still possible and when to review the situation.

If a lack of support continues and development matters deeply to you, it may be sensible to explore options elsewhere. That does not require burning bridges or making a decision before you understand your choices.

Keep a brief record of achievements, feedback and what you learn. It can help you see patterns, prepare for conversations and remember progress that gets lost in a busy working year.

Keep confidential employer information in approved work systems. Personal notes should not contain private staff information, internal documents or sensitive project details.

I would also distinguish a record of completed work from an evidence-free list of impressive-sounding claims. Three examples you can genuinely explain are worth much more than twenty vague achievements.

I want to keep learning throughout my career. I want to do work that interests me, see how far I can grow and still recognise myself in the process. I want the same possibility for the people I manage, although the direction they choose may be entirely different from mine.

A career plan is useful when it helps someone take the next step, not when it looks beautiful in a folder and is never opened again.

Choose one direction. Find one opportunity. Ask for the support you need. Then give yourself something real to learn from. That is a very good place to start.