Professional Development Plan: A One-Page Plan That Gets Used

A useful professional development plan has one capability gap, one work-based practice loop, and one review date. It is a short agreement about what you will practice, where, what support you need, and what evidence will show progress.

Use this template:

• Current evidence: I can already…
• Target capability: I need to become better at…
• Work practice: I will practice it by…
• Support: I need…
• Evidence: I will know I am improving when…
• Checkpoint: I will review this on…

Keep the completed plan to one page. If it cannot fit, the thinking probably needs to become more specific.

What is a professional development plan?

A professional development plan connects current work evidence to one capability you want to build. It names a practice, support, evidence, and checkpoint so development becomes visible in your work.

This is close to the purpose of an individual development plan described by the U.S. Office of Personnel Management: identifying development needs and planning actions that support growth.

The plan should answer:

1. What can I do now, based on actual work?
2. What capability do I need next?
3. Where will I practice it?
4. Who or what will support me?
5. When will I review the evidence?

“Get better at leadership” is too broad. “Lead the next cross-team launch meeting, publish the decision log within 24 hours, and ask the project lead for feedback” gives you a practical starting point.

A broader career development plan may include several roles or ambitions. A one-page plan should stay narrow enough to make the next useful move obvious.

Use the one-page plan

Treat the plan as a working agreement for your next assignment, support conversation, and review.

A course may help, but the project is where the capability becomes real. If you need help translating responsibilities into practice, use O*NET Online to compare tasks, skills, and work activities. Its occupation information is a prompt, not a complete description of your role.

Choose one capability

Choose one capability that would make your current work more effective, and describe it as behavior another person could observe. A capability is more useful than a personality label because it can be practiced and assessed.

“Leadership” is vague. “Set a clear agenda, invite disagreement, make the decision visible, and follow up with owners” is observable.

Start with a gap that matters:

• You produce analysis but struggle to explain the recommendation.
• You coordinate tasks but avoid naming risks early.
• You answer customers well but do not yet coach others.
• You complete projects but do not consistently close decisions.

Then describe the next level of performance. The NIH competencies proficiency scale can help you think in levels of demonstrated capability rather than a yes-or-no trait. Ask what basic, reliable, independent, and advanced performance would look like in your role.

“Can contribute to project meetings” might become “can lead a meeting to a decision.” That is a stronger target than “be more confident.”

Build a work-led practice loop

Use the 70/20/10 split as a planning heuristic, not a universal research finding. Its practical value is that development should mainly happen in real work, be reinforced by people, and be supplemented by focused learning.

• 70% work: Lead a meeting, draft a recommendation, handle a difficult handoff, or own a small project.
• 20% people: Ask a manager to observe, shadow a colleague, request peer feedback, or review an example together.
• 10% course or reading: Take a focused lesson, read a relevant guide, or study a tool you will use immediately.

The percentages do not need to be exact. Exposure is not proof of development: completing a course may provide language and options, but it does not show that you can use the skill under pressure.

Connect the practice to weekly planning, and use how to prioritize tasks when development competes with regular work. A plan that requires heroic extra time is unlikely to survive a normal month.

Three examples

New manager

• Capability: Give clear, timely feedback tied to observable work.
• Practice: Hold one structured one-on-one each week and give feedback on one behavior after a milestone.
• Support and evidence: Ask direct reports whether the feedback was clear; track written follow-ups, agreed next steps, and repeated misunderstandings.
• Checkpoint: Review after 30 days.

Analyst moving toward strategy

• Capability: Turn analysis into a recommendation connected to a business decision.
• Practice: Add a “so what” section to the next recurring report with two options, a recommendation, and the decision required.
• Support and evidence: Ask a strategy partner to review the draft; check that assumptions are stated and the meeting ends with a recorded decision.
• Checkpoint: Review after two reporting cycles.

Customer support lead

• Capability: Coach recurring patterns instead of solving every issue personally.
• Practice: Review recurring cases weekly, identify one pattern, and run a 15-minute coaching discussion.
• Support and evidence: Ask a peer lead to observe one session; keep a shared example and coaching point, then review response consistency.
• Checkpoint: Review after four weeks.

For skills that travel between roles, see transferable skills. The purpose is not to create a perfect future résumé; it is to produce evidence in the job you have now.

Ask a manager for support

Connect one capability to a business outcome and make one modest request:

I want to improve at [capability] because it would help us [business outcome].
I would like to practice it through [work assignment] over the next [time period].
Could you help by [one request]?
I will track [evidence] and bring you an update on [date].
If this is not useful, I will adjust it after the review.

The request might be permission to lead a meeting, ten minutes of feedback, access to a project, or an introduction to someone experienced. Ask for access and feedback before assuming you need a large budget or formal program.

Review monthly

Review by asking what to keep, change, and stop:

• Keep: What practice produced useful evidence?
• Change: What was unclear, too large, or poorly timed?
• Stop: What looked productive but did not build the capability?

Then choose the next smallest experiment. After leading one meeting, you might lead the agenda and close the decision. If feedback was vague, ask for one behavior to repeat and one to change.

A plan is working when it changes what you do at work. If it only creates a tidy page of ambitions, it is paperwork. Start with one capability, one assignment, and one date. For a broader job move, Land the Offer with AI can help after your development evidence is ready.

Frequently asked questions

What should be in a PDP?

A PDP should include current evidence, one target capability, a work-based practice, needed support, observable evidence, and a review date. Make it specific enough that another person could tell whether you practiced it.

How many goals should be in a PDP?

Use one primary capability at a time. Several tasks may support it, but five unrelated goals usually create a list to maintain rather than a behavior to improve.

Is it the same as a performance improvement plan?

No. A professional development plan focuses on building capability and preparing for stronger performance. A performance improvement plan generally addresses current performance concerns through a more formal process. Follow your employer’s policy for the exact distinction and documentation.

What if my manager offers no budget?

You can still build a strong plan through real assignments, feedback, observation, and focused free or existing resources. Ask for access to work and a review date first; funding is only one form of support.