Development plan generator, by Resume Worded ★4.9 on Trustpilot · 5M+ job seekers

A professional development plan you will actually run

A professional development plan is a short working document with three moving parts: the two or three areas you are deliberately growing in, the actions that grow them, and a checkpoint that tells you whether it is working. Most plans have none of these; they have an objective, a course, and a signature. Answer five questions and the generator drafts the real kind.

Draft my plan »

Five questions, a three-area plan with a 90-day checkpoint. Free, no account needed.

Development plan · drafting

DEVELOPMENT PLAN · NEXT 12 MONTHS

AREA 1 · SCOPE Own one cross-team project end to end, proposal to postmortem

AREA 2 · VISIBILITY One design doc per quarter, circulated past the team

AREA 3 · CRAFT System design depth, one incident traced per sprint

CHECKPOINTS, ON THE CALENDAR

3 areas, 5 actions, first checkpoint booked. A plan, not a form.

Interactive, answer five questions

Draft your development plan

Tell it what you do, where you want to be in two or three years, the gap you feel most, and how you actually learn. It returns a plan built the way the rest of this page teaches: three development areas balanced across craft, scope, visibility, and leadership, each with actions you could put on a calendar, resources matched to how you learn, and a 90-day checkpoint that names its own evidence.

If your honest answer on direction is "not sure yet", say so. The plan will lean toward areas that compound in any direction, and the career read at the end of it is built for exactly that problem.

The development plan generator

Your current role and field How long you have been working Where you want to be in 2 to 3 years The gap you feel most How you actually learn

Free. Your first two plans need no account.

The reframe

The HR form and the working plan are different documents

Most professional development plans are written in one sitting, for an audience of one manager, in the week performance reviews are due. They list an objective, a course, and a completion date, collect a signature, and are never opened again. Nothing about that document is a plan. It is a record that planning was performed.

A working plan is smaller and harder. It names two or three development areas chosen against a destination (where you want to be in two or three years), and for each area it commits to actions specific enough to put on a calendar, resources you will genuinely use, and a checkpoint date when you will judge whether anything changed. The test of the difference takes one question: does this document change what you do next Tuesday? If it does not, it is the form.

Both documents take an hour to write. Only one of them is still doing anything in June.

One naming note, because the terms blur into each other. When the document is mandated by your employer and tied to the review cycle, it is usually called an individual development plan, and it plays by slightly different rules because it has two readers, you and your manager. We keep a separate guide and generator for that document: the individual development plan generator covers the grid format, the manager conversation, and how to make a mandated plan actually yours.

The four areas

Every development area is one of four kinds

Strip the labels off any development goal and it lands in one of four areas. Craft: the work itself, done at a higher level. Scope: the size and ambiguity of the problems you are trusted with. Visibility: how far your work travels beyond the people who watched you do it. Leadership: getting results through other people. The names matter less than the balance between them.

Craft is the easiest area to buy, which is why plans fill up with it. The middle two columns are where careers get stuck.

The common failure is loading the whole plan into craft. Craft feels productive and is easy to buy, because there is a course for everything, so plans fill up with certifications. But past the early years, promotions rarely stall on craft. They stall on scope, because nobody has seen you run something big, and on visibility, because the people deciding have never seen your work at all. If you are arguing with yourself about whether visibility work is vanity, that is usually the sign it belongs in the plan.

Two working rules when you draft. Pick at most three areas, because a five-area plan is a wish list wearing a plan's clothes. And never pick all three from the same column: three flavors of craft is the most common plan on earth and the least likely to change what you are handed. The generator above applies both rules; it reads the gap you named and balances the other areas around it.

The cadence

The 90-day checkpoint is the whole method

Plans do not fail at the writing. They fail in week six, quietly, when the calendar wins. The fix is not more willpower; it is a review cadence, and 90 days is the right interval: long enough for actions to produce evidence, short enough to change course twice a year.

A checkpoint is 30 minutes, alone, with three questions. First, what did I actually do: audit the calendar against the plan's actions, without editorializing. Second, what changed in the work I am handed: this is the signal that matters, because development that is working shows up as bigger problems arriving at your desk long before it shows up in any review. Third, what does the plan get wrong: cross out what stopped being true and write the next quarter's actions. A plan that has been edited three times is a live document. Version one, untouched in a drive, is the form again.

Three questions, 30 minutes, four times a year. The second question is the one most plans never ask.

Put the checkpoint on the calendar the day you write the plan: a recurring 30 minutes every 90 days, with the plan document linked in the invite. If it is not scheduled, it does not exist, and the plan's life expectancy drops back to six weeks.

Worked examples

Two plans, shown in full

These are real runs of the generator above, inputs included, so you can judge the shape before you use it. Notice what both plans do: areas balanced across the taxonomy, actions you could schedule this month, resources matched to how the person learns, and checkpoints that name their own evidence.

Inputs: Software engineer, product startup · 3 to 7 years · a more senior version of what I do now · gap: scope · learns by doing

Scope, through ownership

Why this one

Senior is not a skill level, it is a trust level, and you named the gap yourself: the problems you get are too small. Scope grows one way, by owning something end to end, including the parts nobody owns.

Actions

Volunteer for the next cross-team project in planning; write the one-page proposal yourself; run the kickoff; own the unglamorous ends, the rollout plan and the postmortem.

Resources

Learning by doing means the project is the course. One supplement: read your company's last three postmortems. They are the syllabus for what big projects break on.

90-day checkpoint

One cross-team project has your name as owner, and you have run at least one meeting where you were the most junior person in the room.

Visibility, through writing

Why this one

Senior is partly a reputation among people who have never paired with you, and the ones deciding your level mostly read. Writing is how your work travels without you in the room.

Actions

One design doc per quarter, circulated beyond your team; one demo at the next all-hands; answer questions in the public channel instead of DMs.

Resources

Steal the structure of the two most-read design docs on your company wiki. Structure, not style, is what makes them read.

90-day checkpoint

An engineer outside your team references your doc without you having sent it to them.

Craft, system design depth

Why this one

The craft that gates senior is design judgment, not syntax. It is also the area you would naturally over-invest in, so it goes last and gets one action, not five.

Actions

Trace one production incident per sprint back to the design decision that allowed it; sit in on architecture reviews and write down the question you would have asked.

Resources

Rebuild the design doc for one core service from scratch, then compare it to the real one. The differences are your curriculum.

90-day checkpoint

You have written one design alternative that changed a decision, even a small one.

Inputs: Marketing manager, consumer brands · 8 to 14 years · leading a team · gap: leadership · learns from people

Leadership, with borrowed reports

Why this one

You do not need the title to practice the job. Interns, agency relationships, and cross-functional squads are management reps available right now, and they are where you find out whether you even like the work.

Actions

Take over the intern program; own the agency relationship including the hard feedback conversations; run one cross-functional working group through a full project.

Resources

You learn from people: book a monthly hour with two managers you respect, one inside the company and one outside, and ask each for one story of a management mistake and what it cost.

90-day checkpoint

Someone you developed shipped something real without you touching it.

Visibility, upward

Why this one

Team leads are chosen by people who already trust them with headcount, and that trust is built in rooms you are not yet in. The path in is becoming the person who explains the numbers.

Actions

Own the monthly performance narrative to leadership, the story of what moved and why, not the raw dashboard; volunteer to present it whenever your director is out.

Resources

Ask your director for their last three board or leadership decks and read them for what got cut. What leadership does not want to hear is half the skill.

90-day checkpoint

You have presented the numbers to your skip level twice, and the second time they asked you a question instead of your director.

Scope, run the planning

Why this one

Managing people is mostly allocating resources under argument. Planning season is that exact skill, practicable this quarter without a single report.

Actions

Own next quarter's channel budget proposal end to end: the numbers, the trade-offs, and the meeting where finance pushes back.

Resources

One working session with whoever ran it last year, focused on a single question: what got challenged and what survived.

90-day checkpoint

The proposal you wrote survived contact with finance mostly intact, and you can name the one trade-off you got wrong.

Plans execute goals; they cannot supply them. If the goals themselves are still foggy, start one page over: the career goals generator writes goals that are specific enough to plan against.

Frequently asked questions

What is a professional development plan?

A professional development plan is a short working document that names two or three areas you are deliberately growing in, the specific actions that grow them, the resources you will use, and a checkpoint date for judging progress. It is written against a destination, where you want to be in two or three years, and edited every quarter. One page is enough; most good ones fit on it.

What should a professional development plan include?

Five things. A destination: where you want to be in two or three years, even roughly. Two or three development areas, balanced across craft, scope, visibility, and leadership rather than stacked in one. Actions specific enough to put on a calendar. Resources matched to how you actually learn, not to what the training portal offers. And a 90-day checkpoint with the evidence named in advance. It does not need a vision statement.

How do I write a professional development plan?

Start from the destination and work backwards: name where you want to be in two or three years, then pick the two or three areas that close the gap, never all from the same category. For each area write actions with dates, the resources you will genuinely use, and what evidence would show progress by day 90. Then book the checkpoint before you close the document. The generator on this page drafts all of it from five answers.

What are examples of professional development goals?

Good ones name their own evidence. Own one cross-team project from proposal to postmortem this year. Present the monthly numbers to leadership twice, solo, by Q3. Trace one production incident per sprint back to its design decision. Develop one intern to the point they ship without you. Weak ones are the familiar kind: improve communication skills, become more strategic. If you want goals shaped properly for your own role, our career goals generator writes them with a first step each.

What is the difference between a professional development plan and an individual development plan?

Ownership and audience. A professional development plan is yours: you write it, you review it, nobody co-signs it. An individual development plan (IDP) is the formal cousin: usually requested by a manager or an HR process, tied to the review cycle, and written for two readers, which changes how the goals need to be phrased. Same underlying method, different document. We keep a dedicated IDP generator and guide for the formal version.

How often should I review my professional development plan?

Every 90 days, for 30 minutes, with three questions: what did I actually do, what changed in the work I am being handed, and what does the plan get wrong. The second question is the real progress measure, because growing scope shows up in your inputs before it shows up in any review. Once a year, rewrite the plan from scratch rather than editing; destinations drift, and an annual rewrite is how you notice.

A plan needs a direction it can trust

The generator drafts the plan; Coached reads the person. From just your LinkedIn profile it maps your strengths, values, and work style, free, so the plan you run is pointed somewhere you actually want to go.

Get your free career read »

Resume Worded

Score My Resume

Targeted Resume

LinkedIn Review

Get Resume Worded Pro

A professional development plan you will actually run

Draft your development plan

The HR form and the working plan are different documents

Every development area is one of four kinds

The 90-day checkpoint is the whole method

Two plans, shown in full

Scope, through ownership

Visibility, through writing

Craft, system design depth

Leadership, with borrowed reports

Visibility, upward

Scope, run the planning

Frequently asked questions

A plan needs a direction it can trust