Individual Development Plan Generator

About the individual development plan generator

An individual development plan (IDP) is a short written agreement between you and your manager about what you will get better at, how, and by when. Most plans stall because they list vague goals like "improve leadership" with no actions or deadline attached. This free individual development plan generator takes your current role, one development goal, the skills you want to build, and a timeframe, then drafts a plan with actions, resources, checkpoints, and a measure of success.

Treat the draft as the starting point for a conversation with your manager, not as a finished form. The guide below explains what each part of an IDP should contain, how to choose goals that get approved and supported, which actions build skills fastest, and how to keep the plan alive after the meeting so it shows up in your next review and on your resume.

How to use it

1. 1

   Enter your current role

   Use your actual title and level, such as Software Engineer II or Senior Accountant. The level tells the generator what a realistic next step looks like and keeps actions sized to your current scope.

2. 2

   Describe one development goal

   Write the outcome you want, not the course you plan to take. "Lead a project end to end" gives the plan direction. "Take a leadership class" is an action, and it belongs further down the plan.

3. 3

   List the skills and pick a timeframe

   Name two to four specific skills, such as technical design or stakeholder updates. Choose 3 months for one narrow skill, 6 months for a stretch assignment, or 1 year for a move toward a new role.

4. 4

   Edit the draft and bring it to your manager

   Swap generic resources for ones your company offers, add names and dates, and take the plan to a one-on-one. Ask your manager to confirm the support items before you treat the plan as final.

What an individual development plan includes

Formats vary by employer, but nearly every IDP answers the same six questions. A plan missing any of them usually becomes a wish list that nobody opens again.

Keep the whole plan to one page with two or three goals. Past that, each goal gets too little time to show progress before the next review.

• Goal: the outcome you want, stated so someone else could tell whether you reached it, such as "run the Q3 billing migration as technical lead."
• Skills gap: the two to four specific skills standing between you and that goal today.
• Actions: what you will do, mostly on the job: assignments, shadowing, presenting, owning a decision.
• Support and resources: what you need from others, such as a mentor, course budget, protected calendar time, or a seat in a meeting.
• Timeline: a start date, checkpoints, and an end date that lines up with your review cycle.
• Measure: the evidence that will show the goal is met, written before you start.

How to choose goals your manager will approve

Managers approve development goals faster when the goal helps the team as well as you. Before you write a goal, finish this sentence: "If I get better at this, the team will be able to..." If you cannot finish it, the goal may still be worth pursuing, but it belongs in a personal plan rather than one you ask your employer to support.

Balance the plan. A useful mix is one goal that deepens your current craft, one that widens your scope or visibility, and, if you are aiming at management, one that builds people skills. Ground each goal in feedback you have already received, such as a comment from your last review, so the conversation starts from shared evidence instead of opinion.

Write the measure as something observable. "Become a better presenter" is hard to judge. "Present the monthly metrics review to the leadership team three times, with no more than one round of edits from my manager" can be checked against a calendar.

Actions that build skills faster than courses alone

Courses and certifications are easy to list, which is why weak IDPs are full of them. They teach vocabulary, but most work skills grow through practice with feedback. For each goal, include at least one action that changes what you do at work, then add learning resources that support it.

Sequence actions from low risk to high risk. Shadow first, then do part of the work with a reviewer, then own it. That order gives your manager a reason to say yes at each step and gives you evidence before the stakes rise.

• Stretch assignment: take a defined piece of work one level above your role, such as writing the design doc or running the vendor call.
• Shadowing: sit in on the meetings or decisions you want to own later, then debrief with the person you shadowed.
• Mentoring: meet monthly with someone who already does the job well, and bring one specific question each time.
• Teaching: run a lunch session or write internal documentation, because explaining a topic exposes your gaps quickly.
• Formal learning: a course, certification, or book, tied to an action where you will use it within a month.

How to keep your IDP active after the first meeting

Most plans are written in one meeting and opened again at the annual review. Put three things on your calendar the day the plan is approved: a monthly 15-minute self-check, a progress item on your one-on-one agenda every four to six weeks, and a full review at the end of the timeframe.

Keep an evidence log. Each time you finish an action, write one line with the date, what you did, and the result. That log becomes material for your self-evaluation and for new resume bullets. If priorities change and a goal stops making sense, rewrite it openly with your manager instead of letting it quietly expire.

Examples

Frequently asked questions