How to write a professional development plan your manager will actually take seriously

Most professional development plans don’t work. Sorry, we said it. 

Not because the idea is wrong, but because of how they get written. A list of vague goals (“improve my leadership skills,” “get better at presenting”) with no timeframe, no clear ask and no connection to anything the business actually cares about. It gets filed somewhere, reviewed once at an annual performance conversation and then quietly forgotten.

If that sounds familiar, it’s not a reflection on your ambition. It’s a structural problem but one that is absolutely fixable.

Here’s how to write a professional development plan (PDP) that actually goes somewhere.

Start with what you want, specifically

The instinct with a PDP is often to make it safe and palatable, to frame your development goals in terms of what your employer needs rather than what you want. There’s a place for that framing, but it comes later. It’s essential to start with what you actually want.

Do you want to move into a more senior version of your current role? Shift into a different function? Build a specific skill set you feel you’re missing? Become the go-to person for something your team currently outsources? Be honest with yourself before you’re strategic about it.

Listing vague desires will produce vague plans. “I want to be better at my job” is not a development goal. “I want to be leading client presentations independently within six months” is. Being specific is what makes the rest of the plan workable; it gives you something to reverse-engineer from and gives your manager something concrete to respond to.

Connect your goals to something your business cares about

This is the step most people skip and it’s the one that makes the difference between a manager who nods politely and a manager who is enabled to actually help.

Every business has priorities. Projects that need to be staffed, skills availability may be limited but there are capabilities the team wants to build. If your development goal connects to one of those (even loosely) it stops being a personal request and starts being a business conversation.

You don’t have to manufacture the connection. If it isn’t there, it probably isn’t the right goal to lead with (you can still pursue it, but it won’t be the one your manager will most easily support). But if it is there, name it explicitly: “I know we’ve been relying on external consultants for this, I’d like to build enough internal capability to reduce that dependency.“

That framing tells your manager you’ve thought beyond yourself. It also gives them something to take to their own manager if they need to justify investing in your development.

Be specific about what you’re asking for

The second most common reason PDPs go nowhere is that they don’t include a clear ask. “I want to develop my skills in X” is not a plan, it’s a wish. A plan includes what you need in order to develop that skill, and what you’re asking your employer to provide.

Resources you might need:

• A course, certification or qualification (and who pays for it and how much)
• Time to pursue internal projects or secondments outside your current role
• A mentor or sponsor, think of someone senior who will advocate for you, not just advise you
• Stretch assignments like being put in the room or on the project before you’re fully ready
• Regular feedback on specific aspects of your performance, not just general check-ins

Be as concrete as you can about what you’re asking for. “I’d like to complete the [specific certification] over the next quarter — it costs $X and takes roughly Y hours of study time” is a request your manager can act on. “I’d like to do some training” is not.

If your workplace uses Employment Hero, the goals feature is a useful place to formally capture your development objectives in a way both you and your manager can see, track and return to. This turns a one-off conversation into an ongoing one.

Map out the next 90 days, not the next five years

While you might be tempted to look far into the future, a PDP that covers five years of career ambitions is a vision document. It might be worth having, but it won’t get traction in a development conversation. What gets traction is a plan for the next quarter. Make sure it’s specific enough to action and close enough to feel real.

For each goal you’ve identified, work backwards:

• What does progress look like in 30 days?
• What do you need to have started, completed or learned?
• What’s the first concrete step? The one you could take this week?

Short horizons make development plans actionable. They also make it easier to show your manager you’re following through, which builds the credibility to ask for more.

Have the conversation, don’t just send the document

A PDP only works if it becomes a shared agreement, not a document you’ve written and handed over. That means having the conversation.

Give your manager the plan in advance of your 1:1 so they have time to read it. Then use the meeting to talk through it and to discuss it. Ask what they think is realistic and what would make them more confident in backing you. Ask if there’s anything on the list they’d prioritise differently.

The goal is to leave with your manager’s input genuinely reflected in the plan, not just their signature on it. A development plan your manager helped shape is one they’ll feel some ownership over. That ownership is what drives the follow-through you need from them.

Come back to it regularly. A monthly check-in doesn’t have to be long, even five minutes in a 1:1 to note what’s progressed and what’s stalled keeps momentum and signals that you’re serious.

When to develop your Professional Development Plan

If you’re writing a PDP for the first time, the best moment to introduce it is slightly ahead of a performance review cycle, not during it. Raising your development goals when the review is already in motion can make it look reactive. Raising them a month or two earlier positions you as someone who’s thinking proactively about their growth, which is a different kind of conversation.

Employment Hero’s goals and 1:1 features are built for exactly this kind of conversation — capturing development objectives, tracking progress and keeping both you and your manager accountable to what you’ve agreed. If your workplace uses EH, it’s worth using these features to formalise your PDP rather than keeping it in a document that only you can see.

Happy planning!

The information in this article is current as at 21 October 2026, and has been prepared by Employment Hero Pty Ltd (ABN 11 160 047 709) and its affiliates (Employment Hero). The views expressed here are general information only, provided in good faith to assist employers and employees, and should not replace professional advice. Some information comes from third-party data believed accurate but not independently verified. No warranties ensure it is complete, accurate, current, or fit for its intended use. Employment Hero disclaims responsibility for inaccuracies and any loss or damage from reliance on this information. You should research and seek professional advice before making decisions or relying on this article.