Individual Development Plan (IDP): Template and Examples

Your manager says "let's put together a development plan," hands you a blank form, and asks for it by Friday. Or maybe nobody has asked, but you want a clear way to grow and get support for it. Either way, you're staring at boxes labeled "goals," "actions," and "resources," with no idea what a good answer looks like.

This guide shows you how to write an individual development plan that's specific, realistic, and easy for your manager to approve. You'll get a fill-in IDP template, six complete examples for different roles and stages, a step-by-step writing process, and scripts for the conversation with your manager.

If you're a manager helping someone else build an IDP, there's a section for you too, with the questions and follow-up habits that keep plans from dying in a shared drive.

What an individual development plan is, and what it isn't#

An individual development plan (IDP) is a written agreement about how you'll grow over a set period, usually a year. It lists a few development goals, the actions you'll take to reach them, the support you need, target dates, and how you'll know you've succeeded.

The U.S. Office of Personnel Management describes the IDP as a tool to help employees reach their development goals, built as a partnership between employee and supervisor. OPM is clear that it's not a performance evaluation tool or a one-time activity.

IDP vs. other plans you may hear about#

People often mix these up. They have different purposes, different owners, and different stakes.

If you're starting a new job, a 30-60-90 day plan covers your first three months. An IDP usually takes over after that, once you know the role well enough to choose growth goals.

Who uses IDPs#

IDPs show up in very different settings, but the core is the same everywhere: goals, activities, support, and dates.

• Companies use them in annual review cycles and for high-potential or leadership programs.
• Federal agencies often require them. OPM notes that many agencies require IDPs for new and current employees and encourage annual updates, though IDPs are not federally mandated.
• Universities use them for staff. UC Berkeley HR says managers and employees should create development plans together as part of the annual performance process.
• Graduate programs use them for students and postdocs. UNC's pharmacology program asks students to complete an IDP every year and discuss it one-on-one with their principal investigator.

Why it's worth doing well#

Most people don't get much help planning their growth. LinkedIn's 2025 Workplace Learning Report found that only 15% of employees said their manager had helped them build a career plan in the past six months. The same report found that only 36% of organizations had strong career development programs.

Pew Research Center's 2023 survey found that only 44% of U.S. workers were extremely or very satisfied with their opportunities to train and develop new skills. A well-written IDP is one of the simplest ways to change that for yourself, because it turns "I'd like to grow" into specific requests your manager can say yes to.

What to include in an individual development plan#

There's no single required format. OPM says there is no "correct" one, but lists minimum elements: an employee profile, short- and long-term career goals with dates, development objectives, training and development activities, and sign-off. The table below turns that into a practical structure.

Two kinds of development goals#

UC Berkeley's HR guidance separates job mastery skills, which you need to excel in your current role, from professional development skills that go beyond your job description. A strong IDP usually includes at least one of each.

• Job mastery goal: Get faster and more accurate at the work you already own.
• Professional development goal: Build a skill your next role needs, such as leading people or presenting to executives.
• Optional relationship goal: Build a connection with a mentor, sponsor, or another team you'll need later.

How long an IDP should cover#

Most plans cover one year, matched to the performance cycle. That's long enough for meaningful growth and short enough to stay relevant. Within that year, break each goal into milestones you can reach in a quarter. For graduate students, a plan per academic year works well. If you're in a fast-changing role or a new team, a six-month plan may be more realistic.

Should it include personal goals?#

Keep the plan focused on work-related growth, since your manager is agreeing to support it. That said, some personal goals overlap with work, such as public speaking confidence or managing your time better. Those belong in the plan when they clearly help your performance or career direction. Purely private goals, such as fitness or family plans, can stay in your own notes.

How to write an individual development plan in 7 steps#

Give yourself about two hours for a first draft. Most of that time goes into the first three steps.

1. Assess yourself. List your strengths, gaps, interests, and the kind of work you want more of.
2. Gather input. Review your last performance review and ask your manager and one or two peers for feedback.
3. Set a direction. Write one sentence about where you want to be in two to five years.
4. Choose two or three development goals. Pick the gaps that matter most for your current role and your next one.
5. Pick activities for each goal. Favor real work: stretch projects, shadowing, and practice, with courses where they fill a gap.
6. Define support, dates, and measures. Be specific about what you need and how you'll know you've succeeded.
7. Review and agree with your manager. Adjust, sign off, and schedule check-ins.

Step 1: Do an honest self-assessment#

Answer these questions in writing. Short answers are fine.

• What do I do better than most people on my team?
• What feedback have I heard more than once?
• What part of my job do I avoid, and why?
• Which tasks give me energy, and which drain me?
• What would I need to be able to do to get the next role I want?

Step 2: Gather input from others#

UCLA's IDP guidance suggests starting by reviewing your latest performance review, noting strengths and development areas, and considering what your unit needs. Add a quick ask to your manager: "What's one skill that would make the biggest difference in my work this year?"

Step 3: Set a direction#

Your direction doesn't need to be a job title. "Lead a small team," "become the go-to expert on our pricing data," or "move into product management" all work. If you're unsure, our career goals examples can help, and the career path explorer maps realistic next roles from your current one.

Step 4: Choose two or three development goals#

More than three goals usually means none get done. Pick goals that serve both your direction and your team's needs, since that's what makes them easy to approve. Write each in SMART form: specific, measurable, achievable, relevant, and time-bound.

Step 5: Pick activities for each goal#

Each goal needs two or three activities. The best plans mix on-the-job experience, learning from people, and formal training. OPM lists many options, including classroom or web-based training, rotations, shadowing, on-the-job training, self-study, and conferences.

Step 6: Define support, dates, and measures#

This is where most plans go vague. "Mentorship" is easy to agree to and easy to forget. "Two hours a month with a senior analyst, starting in February" is something your manager can actually arrange.

For each goal, write the support needed (budget, time, introductions, access), a target date, and a measure that someone else could check, such as a completed deliverable, a feedback score, or a metric.

Step 7: Review and agree with your manager#

Send your draft a few days before the meeting, then walk through it together. Expect edits. The goal is a plan you both believe in, with clear responsibilities on each side.

Individual development plan template#

Copy this template into a document and fill it in. Keep the whole plan to one or two pages so it's easy to review.

If you'd rather start from a draft, the individual development plan generator builds an IDP with goals, actions, resources, and timelines from your role and target.

Individual development plan examples#

These six examples use hypothetical people. Use them for structure and level of detail, then swap in your own goals and numbers.

Example 1: Entry-level analyst building core skills#

Example 2: New people manager#

Example 3: Registered nurse aiming for a specialty#

Example 4: Software engineer moving toward senior level#

Example 5: Employee preparing for an internal career change#

Example 6: Graduate student or postdoc#

IDP goals examples by skill area#

If you know which skill you want to build but not how to phrase it, start here. Each goal below is specific enough to measure. Pair it with activities, support, and a date.

More sample goal statements#

• Coaching others: Mentor one new hire through their first 90 days, meeting weekly, and collect their feedback at the end.
• Writing: Write the team's process guide for onboarding by April, reviewed and adopted by my manager.
• Data skills: Build three dashboards in our BI tool that the team checks weekly by September.
• Influence: Propose one process change to leadership with data behind it and get a decision by year-end.
• Customer insight: Join 10 customer calls this half and summarize the top five issues for the product team.
• Time management: Cut time spent on recurring reports from 6 to 3 hours a week by automating two of them.

Strong goals often draw on both technical and interpersonal ability. Our guide to hard skills vs. soft skills can help you balance the two.

Choosing development activities that actually build skills#

Courses are the easiest activity to list and the easiest to forget. Most real growth happens when you do the work, get feedback, and try again. That's why the strongest IDPs lean on stretch assignments and practice, with formal training used to fill specific gaps.

A practical rule of thumb is to put most of your effort into on-the-job experience, a smaller share into learning from people, and the rest into structured learning. The chart below shows one sample mix for a plan, not a fixed formula.

Turn courses into proof#

If you take a course, attach an application to it. UCLA suggests writing a short summary of key learnings after workshops and sharing highlights with your team. Better still, use the new skill on a real deliverable within a month, so the course shows up in your results rather than just your training record.

Development on a small budget#

Many teams have little or no training money. That doesn't have to stall your plan. Some of the most effective activities cost nothing but time and a manager's approval.

• Volunteer for the project nobody wants. Messy projects build judgment fast and get noticed.
• Ask to shadow a meeting above your level. Most leaders say yes to one quiet observer.
• Teach what you know. A 20-minute session for your team forces you to master the topic.
• Swap skills with a peer. Trade an hour of your expertise for an hour of theirs.
• Use free learning resources. Public courses, documentation, and professional association webinars cover many technical topics.
• Rewrite one process. Pick a recurring task, improve it, and document the result.

Pick skills with long shelf lives#

When choosing what to build, favor skills that transfer across roles and employers: communication, analysis, project leadership, and the core tools of your field. Our guides to in-demand skills and transferable skills can help you choose.

How to discuss your IDP with your manager#

The conversation matters as much as the document. Your manager needs to understand your goals, agree they help the team, and commit to the support you've asked for.

A simple meeting agenda#

• Your direction (2 minutes): Where you want to be in a few years, and why.
• Your goals (10 minutes): Walk through each goal and how it helps the team.
• Support (5 minutes): Review each request and agree on what's possible.
• Check-ins (3 minutes): Agree on when you'll review progress together.

Script for opening the conversation#

If your manager isn't engaged#

Some managers are busy, new, or simply not used to development conversations. Don't wait for them to start it. Bring a complete draft, keep requests small and specific, and ask for 20 minutes rather than an hour. If you still get little response, ask HR whether the company has development programs, mentoring, or training budgets you can tap directly.

For managers: how to support an employee's IDP#

If you manage people, your role is less about writing the plan and more about making it possible. UCLA's guidance describes the supervisor's job as preparing for the discussion, guiding choices, completing the form, and following up in regular one-on-ones.

Questions that help employees think clearly#

• What part of your work do you want more of next year?
• What skill would make the biggest difference for you right now?
• Where do you see yourself in two or three years?
• What's one thing I could do that would help you grow?
• What's getting in the way of your development today?

When you can't support a goal#

Sometimes an employee asks for something you can't provide, such as a costly certification or a role that doesn't exist on your team. Say so plainly, explain why, and offer the closest alternative you can support. A lower-cost course, a smaller stretch project, or an introduction to someone on another team keeps the goal alive. Silence or a vague "we'll see" does more damage than an honest no.

Make it part of normal one-on-ones#

UCLA recommends bi-weekly one-on-ones to check progress after the plan is set. You don't need to review the whole IDP each time. A single question, "What did you do on your development goals since we last met?", is enough to keep it moving.

How to track progress and keep your IDP alive#

Most IDPs are written in January and forgotten by March. The fix is a short, regular review habit and a simple way to see progress.

A review rhythm that works#

• Monthly: Spend five minutes updating the status of each activity.
• Quarterly: Review the plan with your manager, close finished items, and add new ones.
• Annually: Reflect on the year, update your direction, and write the next plan.

Track status at a glance#

A simple status column, such as not started, in progress, or done, makes check-ins fast. The chart below shows how activities in a sample plan might progress through a year.

Capture results as you go#

Every time you complete an activity, write down what you did and what changed. These notes become the evidence for your next review, your self-evaluation, and your resume. A completed stretch project with a clear result is worth far more than a list of courses.

Using your IDP for promotions, career changes, and feedback#

An IDP is most valuable when it's tied to a decision that matters to you.

When you want a promotion#

Ask your manager what the next level requires, then build your goals around the gaps. When you can show you've closed them, you have a strong case. Our guide on how to ask for a promotion covers how to make the request, and the promotion request generator turns your IDP progress into a written case.

When you want to change roles internally#

Use your IDP to test the new direction before you commit. Shadowing, a small project with the target team, and informational conversations are low-risk ways to find out whether you'll enjoy the work. If you're thinking of a bigger move, our guide on how to change careers covers the broader process.

Be open with your manager about the direction. Most managers would rather help you move within the company than lose you to another one, and their support makes introductions much easier.

When you update your resume#

Completed IDP goals make strong resume bullets because they already include an action and a result. Rewrite each finished goal as an accomplishment, leading with what you did and ending with what changed.

After difficult feedback#

If your review pointed out a gap, an IDP turns the feedback into a constructive plan. Pick one goal that directly addresses it, with clear activities and a measure. This shows you took the feedback seriously, and it gives you something concrete to point to at the next review.

Common IDP mistakes to avoid#

Even well-meant plans fall apart in predictable ways. Watch for these.

• Too many goals. Five goals means none get real attention. Stick to two or three.
• Courses only. A list of trainings with no application rarely changes how you work.
• Vague support. "Mentorship" and "more opportunities" are easy to agree to and easy to forget.
• No measures. If nobody can tell whether a goal is done, it usually isn't.
• Written for HR, not for you. Choose goals you actually care about, or you won't follow through.
• No check-ins. Without scheduled reviews, the plan disappears until next year.
• Never updated. A plan written for a role you no longer have isn't helping anyone.

Your next steps#

A good individual development plan takes a couple of hours to write and pays off all year. Start small, be specific, and keep it moving with short check-ins.

1. Spend 30 minutes on the self-assessment questions above.
2. Ask your manager for the one skill that would make the biggest difference.
3. Draft two or three goals with activities, support, dates, and measures using the template.
4. Send the draft ahead and walk through it with your manager.
5. Schedule monthly or quarterly check-ins before you leave the meeting.

If you're starting from scratch, the free career goals generator can help you choose a direction, and the individual development plan generator turns it into a first-draft IDP you can refine. Keep notes as you complete each activity, and add the results to your resume and LinkedIn as you go, so your leadership skills and other growth show up when it counts.