12 Individual Development Plan Examples (+ Template)
An individual development plan (IDP) is only as useful as the goals it contains. Vague goals — "develop leadership skills," "improve communication" — produce vague development. The examples below show what specific, actionable IDPs look like across 12 different situations: IC growth, new managers, senior leadership, performance gaps, career changes, and promotion preparation.
Each example includes the context, three concrete goals, the actions that support each goal, a realistic timeline, and a success measure. Use them as a starting structure and adapt the specifics to reflect the employee's actual situation.
The anatomy of an effective IDP
Before the examples, a brief note on structure. An IDP with goals but no actions is a wishlist. An IDP with actions but no success measures is a to-do list. An effective IDP has five components that connect:
- Career goal — where the employee wants to go (next role, skill area, or level)
- Current state — honest assessment of strengths and gaps relative to the goal
- Development goals — 2–4 specific, measurable targets to close priority gaps
- Actions — concrete activities: training, stretch assignments, mentoring, reading, projects
- Success measures and timeline — how you know the goal was met and by when
Personal development plan vs IDP vs career development plan: what is the difference?
A personal development plan (PDP), an individual development plan (IDP) and a career development plan cover overlapping ground, and the names are often used interchangeably. The practical differences are who writes the plan, what it focuses on and how far ahead it looks.
| Plan | Who writes it | Focus | Typical time horizon |
|---|---|---|---|
| PDP (personal development plan) | The individual, often on their own or as a student or job seeker | Personal skills, habits and learning goals, not always tied to one employer | 3 to 12 months |
| IDP (individual development plan) | The employee with their manager | Skills and experiences needed in the current or next role at the organization | 6 to 12 months, reviewed quarterly |
| Career development plan | The employee, sometimes with a manager or coach | The path to a target role, level or field, including role changes | 1 to 5 years, with 6 to 12 month steps |
The 12 examples below work for all three. For a PDP, drop the manager-support lines. For a career development plan, add a long-term target role above the goals. For the definition, see what an IDP is.
IDP goal examples: 10 SMART goals with measurable completion criteria
A good IDP goal names one change, how it will be measured and a date. These ten goal lines can be copied and adapted. Each states its completion criterion in the sentence.
Skills and communication
- Present the monthly metrics review to the leadership team three times by the end of Q3, and collect written feedback from at least two attendees after each session.
- Write a one-page decision memo for every project longer than two weeks this quarter, and have the manager confirm that at least four of five were clear enough to act on without a follow-up meeting.
- Facilitate the weekly team meeting for eight consecutive weeks, ending each one on time with recorded owners for every action item.
Leadership
- Hold a monthly 1:1 with each direct report for six months with no more than one skipped session per person, and use a written agenda shared 24 hours ahead.
- Delegate ownership of one recurring deliverable to a team member by the end of Q2, with the deliverable meeting its deadline for three cycles in a row without manager rework.
Technical
- Complete the intermediate SQL course by March 31 and apply it by replacing two manual spreadsheet reports with queries, each saving at least two hours a month.
- Earn the cloud practitioner certification by June 30, then lead one infrastructure change reviewed and approved by the platform team.
- Own the on-call runbook for one service: rewrite it by the end of Q1 and run one tabletop exercise where a teammate resolves a test incident using only the runbook.
Career moves
- Shadow three people in the target team for two hours each by the end of Q1, and write a one-page summary of the skills the role requires that the employee does not yet have.
- Complete one stretch project in the target function by the end of Q3, with the project sponsor giving written feedback against the target role's expectations.
Group 1: IC growth — 3 examples
Example 1: Junior engineer growing toward L2
Context: 12 months in as L1 engineer, strong execution on well-scoped tasks, needs to grow independence and code quality.
Goal 1: Write code that requires minimal review iteration
Action: Complete two code review deep-dives with senior engineer monthly. Review team's top 5 PR comments from last quarter and create personal checklist. Timeline: 3 months. Success measure: PRs requiring <2 review rounds on 80% of submissions.
Goal 2: Independently scope and complete a medium-complexity task
Action: Lead one mid-sized feature end-to-end (design, implementation, testing, deploy). Manager provides context, not scaffolding. Timeline: Q2. Success measure: Feature shipped on time with no unresolved blockers carried forward.
Goal 3: Document work so teammates can onboard to it
Action: Write README and inline documentation for the two features owned this quarter. Receive feedback from one teammate who tries to onboard to the code. Timeline: Ongoing. Success measure: Teammate confirms documentation is sufficient without additional explanation.
Example 2: Mid-level engineer targeting Staff
Context: Strong L3 engineer, consistently rated high on delivery and technical depth. Gaps in cross-team scope and organizational influence — the gap between L3 and Staff.
Goal 1: Lead a cross-team technical initiative
Action: Own the migration to the new logging standard across 3 teams — write the RFC, get alignment, coordinate implementation. Timeline: Q2–Q3. Success measure: All 3 teams migrated with no regressions; RFC approved in first review cycle.
Goal 2: Develop organizational communication skills
Action: Present one technical decision to the broader engineering team each quarter. Write one internal blog post on a technical topic. Get feedback from skip-level on effectiveness. Timeline: Ongoing. Success measure: Skip-level confirms presentations are clear and influential.
Goal 3: Mentor two junior engineers toward L2
Action: Weekly 30-minute 1:1 with each junior. Set quarterly goals together, track their progress. Timeline: 6 months. Success measure: Both junior engineers self-report improved code quality and confidence.
Example 3: Data analyst targeting senior
Context: Solid mid-level analyst with strong SQL and visualization skills. Gap: stakeholder communication and ability to frame analysis as business recommendations.
Goal 1: Translate analysis into business recommendations
Action: For each major analysis, write a one-page executive summary (what we found, what it means, what we should do). Share with manager before presenting. Timeline: Ongoing. Success measure: Stakeholders act on 3 recommendations in the next quarter.
Goal 2: Own a business domain end-to-end
Action: Become the analytics owner for the churn metric — build the dashboard, define the methodology, present at the monthly business review. Timeline: Q2. Success measure: Dashboard is live and used in business review; no dependency on senior analyst for methodology questions.
Group 2: New managers — 2 examples
Example 4: First-time engineering manager (3 reports)
Context: Promoted from L3 IC 6 months ago. Strong engineering judgment. Gaps: feedback delivery, prioritization delegation, holding people accountable without micromanaging.
Goal 1: Deliver specific, behavior-based feedback consistently
Action: Complete "Radical Candor" book review with manager. Write feedback notes before each 1:1. Review with manager monthly for first 3 months. Timeline: 3 months. Success measure: Direct reports report in skip-levels that feedback is clear and actionable.
Goal 2: Effectively delegate and hold team accountable without doing the work
Action: For one current project, explicitly delegate ownership to one report (not just tasks). Check in on blockers, not on execution choices. Timeline: Q2. Success measure: Project ships on time; zero manager interventions on implementation decisions.
Goal 3: Build individual growth plans for each direct report
Action: Create an IDP with each report by end of Q1. Check in on IDP progress in monthly 1:1s. Timeline: 6 weeks. Success measure: All 3 reports have an active IDP with at least one measurable goal in progress.
Example 5: Senior manager expanding from 5 to 12 reports via reorg
Context: Experienced manager, strong with small team. New org requires managing through two tech leads and scaling communication across a larger group.
Goal 1: Effectively manage through tech leads
Action: Define explicit decision authority for each tech lead (what they own fully vs. escalate). Weekly 30-min 1:1 with each. Timeline: Q1. Success measure: Tech leads report they have clarity on scope; escalation rate drops 50%.
Goal 2: Maintain team visibility without creating bottlenecks
Action: Introduce weekly team health check (5-question async survey). Use data to identify who needs more attention. Timeline: Q1. Success measure: Survey response rate >80%; no direct report feels unheard in skip-level reviews.
Group 3: Leadership development — 2 examples
Example 6: Director preparing for VP role
Context: Strong operational leader. Gap: strategic contribution, executive presence, cross-functional influence without authority.
Goal 1: Contribute meaningfully to one company-level strategy discussion
Action: Request inclusion in one cross-functional strategy working group. Prepare a written point of view before each meeting. Timeline: Q2–Q3. Success measure: Executive sponsor cites input as influential in at least one decision.
Goal 2: Build executive communication clarity
Action: Prepare and deliver one board-level presentation (with executive coach review). Reduce slide count by 40% from current baseline. Timeline: Q2. Success measure: CEO rates communication clarity as "clear and compelling" post-presentation.
Example 7: HR Business Partner developing strategic credibility
Context: Strong operational HRBP. Gap: data fluency, proactive business partnership (vs reactive), executive communication.
Goal 1: Lead with data in every business partner conversation
Action: Complete SQL basics course (Mode Analytics, 4 weeks). Build a monthly people metrics dashboard for supported business unit. Timeline: Q1–Q2. Success measure: Business unit leader references HRBP's data in at least 2 leadership team conversations.
Goal 2: Move from reactive to proactive business partner
Action: Monthly 30-min meeting with business unit leader to discuss upcoming people challenges before they become urgent. Bring one proactive recommendation per meeting. Timeline: Q1. Success measure: Business unit leader initiates conversations rather than waiting for HRBP to be looped in.
Group 4: Performance gaps — 2 examples
Example 8: Engineer underperforming on communication
Context: Strong technical contributor. Feedback from peers and product: blockers not surfaced proactively, status unclear, project visibility gaps.
Goal 1: Surface blockers proactively — before they delay delivery
Action: Post a daily standup update with any blockers. Use a shared doc to track project status. Check in with manager within 24h when a blocker appears. Timeline: 6 weeks. Success measure: No delayed deliveries attributable to unraised blockers. Manager and team confirm visibility has improved.
Goal 2: Align on scope and expectations before starting a task
Action: Before starting any task >1 day of work, write a brief scope note (what I'm building, what's out of scope, expected time) and share with product. Timeline: 4 weeks. Success measure: Product team confirms alignment at start of work on 90% of tasks.
Example 9: Manager receiving consistent low-score feedback from reports
Context: Mid-level manager. 360 feedback: reports feel unclear on expectations and underrecognized for contributions.
Goal 1: Ensure every direct report understands their current expectations and standing
Action: In the next 1:1 with each report, explicitly discuss: what success looks like in their role this quarter, and share one specific recent example of what they did well. Timeline: 3 weeks. Success measure: Each report can articulate their success criteria back accurately in subsequent 1:1.
Goal 2: Give recognition publicly and specifically
Action: Implement a weekly team standup shoutout — specific contribution, not generic praise. Track that each report receives at least one public recognition per month. Timeline: Ongoing. Success measure: Improved scores on recognition in next 360 cycle.
Group 5: Career changes — 2 examples
Example 10: Support engineer moving into SRE/DevOps
Context: 2 years in customer support engineering, strong debugging skills. Target role requires infrastructure and automation experience.
Goal 1: Build foundational infrastructure skills
Action: Complete AWS Cloud Practitioner (self-paced, 6 weeks). Spend 20% of one sprint shadowing SRE on-call. Timeline: Q1. Success measure: AWS cert passed; SRE mentor confirms adequate foundational knowledge.
Goal 2: Automate a manual support process
Action: Identify the highest-volume manual support task and build an automation script. Ship to production with SRE review. Timeline: Q2. Success measure: Automation reduces manual task time by 50%; code reviewed and approved by SRE team.
Example 11: Marketing manager moving into Product
Context: Strong demand-gen marketing manager with analytical background. Wants to move into product management. Gap: technical communication, roadmap thinking, user research.
Goal 1: Develop product thinking and user empathy
Action: Shadow 4 user interviews in Q1. Write problem statements for 2 of them. Get feedback from product manager on user research quality. Timeline: Q1. Success measure: PM confirms problem statements accurately capture user needs.
Goal 2: Contribute to a product roadmap discussion
Action: Prepare a one-page opportunity brief for a feature informed by user research. Present in product review meeting. Timeline: Q2. Success measure: Brief is considered seriously in prioritization; at least one recommendation is incorporated.
Group 6: Promotion preparation — 1 example
Example 12: Preparing a promotion package for L3 → Staff
Context: L3 engineer with strong competency ratings. Manager believes they are approaching Staff readiness. IDP is a 6-month promotion preparation plan.
Goal 1: Demonstrate organizational scope on one initiative
Action: Lead the adoption of a new observability standard across 4 teams — write the proposal, build consensus, coordinate rollout. Timeline: Q2–Q3. Success measure: All 4 teams have adopted the standard; 3 team leads confirm the initiative was led effectively.
Goal 2: Build a documented promotion case
Action: Keep a running brag document — one concrete accomplishment per week with context, scope, and impact. Manager reviews quarterly. Timeline: Ongoing. Success measure: Promotion document covers all competency requirements with specific evidence at next calibration.
Goal 3: Close the leadership competency gap
Action: Mentor 2 engineers during the promotion window. Contribute to the engineering hiring process (2 interviews). Timeline: 6 months. Success measure: Manager and peer feedback confirm demonstrable leadership behavior at Staff expectations.
Group 7: Lateral growth, not promotion (1 example)
Example 13: Professional development plan example for someone not aiming at promotion
A professional development plan does not have to point at the next title. This example is for an experienced contributor who wants to stay at the same level and broaden what they can do, which is a common and legitimate goal.
Context: Senior operations analyst, six years in role, happy at current level. Wants to widen skills across adjacent functions, stay valuable as the team changes and avoid being the single point of knowledge on one system.
Goal 1: Build working knowledge of an adjacent function
Action: Spend two hours a month with the finance team on forecasting and budget cycles. Complete one joint project with a finance partner. Timeline: 6 months. Success measure: Finance partner confirms the analyst can prepare a forecast input unaided; one joint deliverable shipped.
Goal 2: Reduce single-person dependency on the reporting system
Action: Document the month-end reporting process and train one backup. Run one month-end close with the backup leading. Timeline: Q2. Success measure: Backup completes the close without escalation; documentation reviewed by the manager.
Goal 3: Stay current on one tool the team is adopting
Action: Take the vendor's introductory course, then build one internal how-to guide. Run a 30-minute walkthrough for the team. Timeline: Q3. Success measure: At least five teammates attend; two later report using the guide.
Common IDP mistakes
- Too many goals. An IDP with 8 goals gets treated like a list to check off, not a genuine development plan. Three to four goals per 6-month window is the practical maximum for meaningful progress.
- Goals without actions. "Improve system design skills" is not actionable. "Complete the AWS SA course by March 15 and apply learnings to the Q2 service architecture" is actionable. If a goal can't be broken into concrete steps, it's not ready to be in the plan.
- No manager involvement. IDPs that employees write in isolation without manager input often target skills that don't connect to actual career opportunities at the organization. The best IDPs are co-authored — the employee drives the goals, the manager connects them to real opportunities.
- Reviewing once a year. An IDP checked only at the annual review is not a development plan — it's a document. Monthly or quarterly check-ins turn it into an active instrument.
To create IDPs at scale across your team with structured goal tracking, check-in reminders, and competency-based development suggestions, see Harmny's development plans feature. For an in-depth how-to on the process, see our guide on how to create an individual development plan.