How to Create a Career Development Plan With Your Manager

Your manager asks in your next one-on-one: "So, where do you see yourself in two years?" And you freeze. Not because you haven't thought about it. Because you have no idea how to turn the vague shape of your ambition into something you can actually say out loud, defend, and get support for.

That gap is where most career development plans die. Not at the signing — at the conversation. A plan built alone in a spreadsheet and dropped on your manager's desk is a monologue. A plan built together is a contract. The difference decides whether you get the training budget, the stretch assignment, or nothing at all.

I've built these plans on both sides of the table — as the person asking, and as the manager being asked. Here's what actually works, including the parts that took me years to stop getting wrong.

How to create a career development plan with your manager (without it becoming a box-ticking exercise)

The failure mode is almost always the same: you write a document full of ambitions, your manager nods politely, and nothing changes. Six months later the file is buried somewhere in a shared drive and neither of you mentions it again. I've been on the receiving end of that twice.

The fix isn't a better template. It's sequencing. You need to do your own thinking before the meeting — not during it.

Do the thinking before the meeting, not in it

Walk in with a draft. A rough one is fine. What kills the discussion is arriving empty and asking your manager to define your future for you. That puts them in a role they shouldn't hold.

Two questions will do most of the work:

• Which parts of my current job give me energy, and which drain it?
• What do I want to be known for in eighteen months — a skill, a domain, a way of working?

Notice I'm not asking about titles. Titles are the least useful unit of career planning because they vary wildly between companies and they hide the actual work. "Senior manager" at one firm means running a team of four; at another it means owning a region.

Turn ambition into a table your manager can react to

This is the part almost everyone skips, and it's where I'd plant my flag: make the plan a table, not a paragraph. Paragraphs invite opinions. Tables invite edits. Your manager can look at a row and say "that deadline is unrealistic" — which is exactly the conversation you want.

Goal	Skill or exposure needed	Concrete action	Deadline	How we'll know it worked	Who owns it
Lead a client project end to end	Stakeholder management	Shadow the Q3 rollout, then own the Q4 one	End of Q4	Delivered on scope; two clients renew	Me, with manager as sponsor
Speak confidently in steering meetings	Executive communication	Present one update per month to the leadership group	Ongoing, reviewed quarterly	Manager reports fewer rewrites of my slides	Me
Build a working knowledge of data tooling	SQL basics, dashboarding	Two courses plus one internal project	Six months	I ship one dashboard the team actually uses	Me; budget request to manager

Six columns is enough. If you add more, nobody reads it.

Walk into the conversation with three asks, not thirty

Here's what I got wrong for years: I'd list everything I wanted to learn and hope my manager would sort out priorities. They never did. What finally worked was narrowing to three asks, each with a cost attached.

Something like: "I'd like the Q4 project to lead, roughly forty thousand on the data course, and ten minutes in the monthly leadership meeting. Can you support the first two and tell me who to talk to for the third?"

Specific asks are easy to answer. Vague ones get deferred forever.

What are the four steps of career planning?

The four steps are self-assessment, exploration, goal setting, and action — and the order matters more than the labels. Skip the first one and everything downstream is built on guesses about what you think you should want rather than what you actually want.

Self-assessment means an honest inventory: what you're good at, what you avoid, what colleagues come to you for. If you're unsure, ask two people you trust. Their answers usually surprise you.

Exploration is where most people underinvest. Before committing to a direction, talk to someone already doing that job — not to read a job description, but to hear what the Tuesday afternoon feels like. I once spent six months aiming at a role, then had one coffee with someone in it and quietly dropped the whole idea. Best six months I ever wasted.

Goal setting turns that direction into something checkable. Action is the boring part: the calendar entries, the budget request, the project you volunteer for.

What surprises people is how little of this happens in the meeting with your manager. The meeting is step two and a half — a reality check, not the source of the plan.

Can you provide some examples of professional development goals for project managers?

Yes — and the useful ones are behavioural, not aspirational. "Become a better leader" is a wish. "Run a retrospective without prompting the team for answers" is a goal.

Four that hold up in practice:

• Own a project with a genuinely unhappy stakeholder and bring them to a neutral or positive position by close. This compresses years of stakeholder experience into a few months.
• Cut your reporting overhead. Target a measurable reduction — say from six hours a week to two — by automating one recurring report and killing another nobody reads.
• Get a formal certification if your organisation values one, and pair it with an immediate application: teach a lunch session on what you learned within a month, or the knowledge evaporates.
• Mentor someone junior for two quarters. Sounds soft. It exposes gaps in your own thinking faster than any course, because you have to explain decisions you normally make on instinct.

Pick two, not four. I've watched people commit to five development goals in January and finish one — usually the easiest.

What are some good questions and answers for a career development discussion?

The questions matter less than the follow-ups. Anyone can ask "where do you see yourself in three years?" The useful move is to press on the answer.

Three questions that consistently produce something real:

• "What's one thing I could take off your plate that would help you — and that I'd learn from?" This reframes development as mutual benefit, which is why managers engage with it.
• "What would have to be true for me to be ready for the next level here?" Forces specifics instead of "keep doing what you're doing."
• "What's the gap between how I see my work and how you see it?" Uncomfortable, and the single most informative question on this list.

On the answer side, be ready for the manager who says there's no budget or no open role. Have a fallback prepared: exposure instead of money, a lateral project instead of a promotion, a mentor instead of a course. A conversation that ends in "nothing available" is a conversation you didn't prepare for.

How to write your own career development plan

Open a blank document. You'll be done in under an hour if you've done the thinking.

1. One paragraph at the top: where you're heading and why, in plain language. Three sentences maximum.
2. The table from earlier — goals, skills, actions, deadlines, evidence, ownership. Two to four rows.
3. A short list of what you need from the organisation. Budget figures, time, access, a name.
4. Your review dates, written down. Quarterly is realistic; annual is theatre.

Keep it to a single page. Mine has been one page for years, and the version that actually changed my trajectory was the shortest one — because my manager read it in the elevator and remembered it.

What if my manager is unsupportive or has no time?

Then shrink the ask. A fifteen-minute conversation with a specific question is much harder to refuse than "can we talk about my career." If your manager genuinely can't engage, find a second reader — a skip-level, a mentor, someone in the function you're targeting. The plan still works; only the sponsorship gets thinner.

How often should we revisit it?

Every quarter, briefly. Fifteen minutes, same document, three questions: what moved, what didn't, what changes. Plans that get an annual review are plans that get abandoned by March.

The document itself is not the point. The point is that you now have a shared reference for a conversation you'd otherwise have once a year and forget. If your plan is still accurate in six months, it was probably too safe — the good ones need rewriting because you moved further than you expected.