Individual Development Plan Examples: 4 Plans to Copy

What goes into an individual development plan

An IDP is not a career plan and not a performance plan. A career plan looks years ahead and covers the roles you want. An IDP covers the next 3 to 12 months and the skills you will build in your current job. The company starts a performance improvement plan when results fall short, and that plan carries consequences. The employee usually starts an IDP, and its purpose is growth, not correction.

Many plans also use the 70-20-10 model. It suggests that about 70 percent of learning comes from experience on the job, 20 percent from other people and 10 percent from formal training. Treat it as a rule of thumb, not a quota. Its real value is that it keeps a plan from turning into a list of courses.

Many IDP templates include the same core elements, and each example below has all of them:

• Competency and skill analysis: where you are now and where you need to be.
• Goals: one or two, written in SMART form.
• Actions and resources: what you will do and what you need for it.
• Milestones and progress tracking: checkpoints with dates.
• Success criteria: how you and your manager will know it worked.
• Timeline: start date, review dates and end date.
• Support and accountability: who helps and who checks.

Example 1: Product manager moving to senior (6 months)

Gap: you write good feature specs, but you have never built or defended a roadmap on your own.

Goal: By the end of month 6, own the quarterly roadmap for one product area and present it to leadership without your manager in the room.

• Experience (70): run discovery for one new feature from start to finish, and write the next quarterly roadmap draft.
• People (20): shadow your manager in two leadership reviews, and hold a monthly session with a senior PM from another team.
• Training (10): one course on prioritisation or product strategy, finished by month 2.
• Support: two leadership review slots, and time on your mentor's calendar.
• Milestones: discovery summary shared in month 2, roadmap draft reviewed in month 4, solo presentation to leadership in month 6.
• Review dates: a monthly check-in, plus full reviews at the end of month 3 and the end of month 6.
• Success measure: leadership approves the roadmap with no more than one rework round.

Example 2: New manager taking over a team (90 days)

Gap: you were a strong individual contributor, but you have not yet run one-to-ones, team planning or development talks.

Goal: Within 90 days, run one-to-ones and a team planning cycle on your own, and agree a development goal with every direct report.

• Days 1 to 30: hold a first one-to-one with each person, write down how the team works today, and read the last two quarters of team results.
• Days 31 to 60: run weekly one-to-ones, lead your first planning meeting, and ask your own manager for feedback afterwards.
• Days 61 to 90: agree one development goal with each direct report, and give your first piece of difficult feedback with guidance from your HR partner.
• Training: your company's manager programme, or one book on giving feedback, finished by day 45.
• Support: your HR partner for the feedback conversations, and a 30-minute weekly slot with your own manager.
• Milestones: every one-to-one in place by day 30, first plan delivered by day 60, every report with a written goal by day 90.
• Review dates: day 30, day 60 and a full review on day 90.
• Success measure: your manager confirms in the day-90 review that you set the team plan without their help.

Example 3: Cloud engineer growing into an architect role (12 months)

Gap: you run and fix cloud services every day, but you have never designed a system or defended a design in front of the architecture board.

Goal: Within 12 months, design and document the migration of one production workload, approved by the architecture board.

• Experience (70): in months 1 to 3, study the current setup of one service and write its architecture document. In months 7 to 9, draft the migration design for one workload and present it to the board. In months 10 to 12, support the migration and write up the lessons learned.
• People (20): join the architecture board meetings as an observer from month 1, and pair with an architect on one design in months 4 to 6.
• Training (10): the associate-level cloud certificate your company uses, finished by month 6.
• Support: exam fee, two hours of study time per week, and an architect as mentor.
• Milestones: first architecture document in month 3, certificate in month 6, design approved in month 9, migration live in month 12.
• Review dates: a monthly check-in, plus full reviews at the end of months 3, 6, 9 and 12.
• Success measure: the board approves the design with no more than one rework round, and the team uses your lessons learned document to plan the next migration.

Example 4: Project manager stepping into a PMO lead role (9 months)

Gap: you deliver your own projects well, but you have never tracked a whole portfolio or helped leadership choose between projects.

Goal: Within 9 months, set up a monthly portfolio review for all active projects and run it for three cycles in a row.

• Months 1 to 3: list every active project with its owner, status and next milestone, and agree one status format with the other project managers.
• Months 4 to 6: build the portfolio view, run the first review with the director, and collect feedback after each session.
• Months 7 to 9: add a risk and dependency check to the review, and coach one junior project manager.
• Training: one course on portfolio management or governance, finished by month 4.
• Support: a monthly slot in the director's calendar, and agreement from the other project managers to share their status each month.
• Milestones: project list in month 2, first review in month 4, three reviews in a row by month 9.
• Review dates: a monthly check-in, plus full reviews at the end of months 3, 6 and 9.
• Success measure: the director uses the review to make at least one funding or priority decision.

How to present your IDP to your manager and ask for budget

Most IDP examples stop once the template is filled in. The plan only works if your manager agrees to it and protects the time. Treat the meeting like a short project pitch. Your manager has to see what the team gets out of it, not only what you get.

When you ask for money, tie each cost to one milestone. Give the course name and the date you will finish it. That way the budget line becomes a decision to approve, not an open question. Your manager may have to justify the spend to their own boss, so make it easy for them. Write one sentence they can reuse, such as "This course prepares the roadmap draft due in month 4, which the team needs for the next planning cycle."

A 5-minute script that works for most roles:

• Minute 1, the gap: "This quarter the team needs X. Today I can do part of it, and here is the part I can't do yet."
• Minute 2, the goal: read your SMART goal and its success measure out loud.
• Minute 3, the plan: show the phases and milestones on one page, with dates.
• Minute 4, the ask: name the exact support, for example a mentor, two hours a week, one course or a seat in a meeting.
• Minute 5, the check-ins: propose your review dates and ask what would make this a clear yes.

How often to review an individual development plan

Hold a short check-in every month and a full review every quarter. Pick one rhythm and put the dates in the calendar on the day the plan is signed off, as each example above does. A plan with no review date almost always gets forgotten.

If the business changes, change the plan. Move the goal or swap the stretch project, and write the new date down. Changing a plan is normal. The real failure is a plan nobody looks at.

At each check-in, look at three things only:

• Which milestone is due, and is it done?
• Which action has stalled, and why?
• Does the goal still match what the team needs?