Illustrative Individual Development Plan Examples, Template, and Writing Guide

Overview

An individual development plan (IDP) is a written, forward-looking plan that turns one career-development priority into specific actions, resources, support, dates, and observable success measures. The fastest way to write one is to pick a completed example close to your situation, copy its structure, and replace the details with your own goal, actions, and review dates. This article provides five completed illustrative plans and a fill-in template for exactly that purpose.

The U.S. Office of Personnel Management (OPM) describes an IDP as a tool to help employees achieve their personal and professional development goals, built as a partnership between an employee and their supervisor with preparation and continuous feedback. It is not a performance evaluation and not a one-time activity. Indeed’s employer guidance makes the same point in plainer terms: an IDP focuses on future performance rather than past performance.

The sections below walk through five completed plans in one consistent field order, a copyable template, a step-by-step process for making goals measurable, an activity bank beyond formal courses, a practical ownership split, review guidance, and a carefully qualified comparison with performance reviews and performance improvement plans.

Completed individual development plan examples

The five plans below cover a new employee, a people manager, a technical specialist, a career changer, and an aspiring leader. AIHR notes that IDPs are not meant to follow a single template and can be adapted to career stage, skill level, or development focus, and Paycor organizes its examples the same way, by career stage and development need. Each plan here uses the same field order so you can compare how the goal, actions, support, and measures change across scenarios. These are illustrative syntheses built from the field structures in the cited sources, not documented cases about real employees. Pick the scenario nearest to yours, then adapt every field rather than copying it verbatim.

New employee: Build role proficiency and internal connections

A new employee’s development priority is usually role proficiency: learning the core tasks, tools, and relationships the job depends on. A plan for this stage should target a specific competence gap rather than the vague goal of “getting up to speed.”

• Profile: Customer operations coordinator, month two in role
• Development focus: Reach independent proficiency in the team’s case-management workflow
• Strengths: Strong written communication; prior customer-service experience
• Development need: Limited knowledge of internal systems, escalation paths, and cross-team contacts
• Objective and target date: By the end of month five, handle standard cases end to end without supervisor sign-off
• Actions: Complete the internal systems onboarding modules by week 10; shadow a senior coordinator for two case cycles; take ownership of a small live caseload from week 12; hold introductory meetings with the three teams the role escalates to
• Resources and support: Access to the case-management sandbox; a named shadowing partner; manager agrees to review the first ten independently handled cases and give written feedback on each
• Success measures and reviews: Success is measured by supervisor sign-off being removed for standard cases and by an error rate on reviewed cases comparable to team norms; progress check-ins at weeks 8, 12, and 16

This plan works because each action maps to the stated gap, and the success measure is observable rather than a feeling of confidence. It follows the structure Paycor recommends, where each item specifies the activity, how success will be measured, the resources needed, and a completion date. One improvement worth discussing: the plan could name a strength-based action, such as using the employee’s writing skill to document the workflow as they learn it, which benefits the team and reinforces learning.

Manager: Improve the quality of employee feedback

Feedback skill is one of the most common manager development needs, and it appears verbatim in Northwestern University’s sample IDP, which lists “to learn how to give effective feedback to my team members” as its first development goal. The weak version of this plan is “complete a feedback course.” The strong version defines observable practice.

• Profile: Team lead, four direct reports, 18 months in the management role
• Development focus: Give timely, specific, behavior-based feedback in both directions, positive and corrective
• Strengths: Trusted by the team; strong one-on-one rapport
• Development need: Feedback is currently infrequent, delayed, and framed too generally to change behavior
• Objective and target date: Within six months, deliver specific feedback in every scheduled one-on-one and address performance concerns within one week of observing them
• Actions: Attend a feedback-skills course; read one book on feedback conversations and apply one technique per month; prepare one written feedback point before each one-on-one; ask a peer manager to observe and debrief two feedback conversations
• Resources and support: Course enrollment; time protected for one-on-ones; the manager’s own supervisor agrees to review two prepared feedback plans and role-play one difficult conversation
• Success measures and reviews: Success is measured by a one-on-one log showing feedback delivered in each session, by the elapsed time between an observed issue and the conversation about it, and by direct-report input gathered at the six-month point; monthly check-ins with the supervisor

The Baylor University template’s structure fits this plan well: an objective with a date, actions, and a measurement statement framed as “I will measure success by.” Note that the course is only one of four actions. The plan’s real engine is the weekly practice and the peer observation.

Technical specialist: Build an advanced skill through applied work

Technical development plans fail when they consist entirely of courses with no application. A stronger design pairs formal learning with a real project where the new skill produces visible output.

• Profile: Data analyst, three years in role
• Development focus: Move from descriptive reporting to building automated data pipelines
• Strengths: Deep knowledge of the team’s data sources; reliable delivery on reporting requests
• Development need: No production experience with pipeline tooling or code review practices
• Objective and target date: Within nine months, design, build, and hand over one automated pipeline that replaces a recurring manual report
• Actions: Complete a structured course on the team’s pipeline tooling in the first two months; join the engineering team’s code reviews as an observer, then as a contributor; build the pipeline in stages with a senior engineer reviewing each stage; document the pipeline so a colleague can maintain it
• Resources and support: Course access; a named senior engineer as technical mentor; manager agrees to reduce the analyst’s ad hoc reporting load during the build phase and to schedule the handover review
• Success measures and reviews: Success is measured by the pipeline running in production, the manual report being retired, and the mentor confirming the code passed review without major rework; milestone reviews at months 3, 6, and 9

This plan reflects the structure Paycor describes, where every activity carries a resource, a measure, and a date, and it uses the mentoring and project-based activities that AIHR lists as valid IDP action steps alongside training. The manager’s commitment to reduce reporting load is the field most often missing from real plans, and it is frequently the difference between completion and quiet abandonment.

Career changer: Prepare for a move into a new function

A career-change IDP has a different starting point: it must name transferable strengths, identify the gaps specific to the target role, and build evidence of readiness. King County’s published IDP example illustrates exactly this scenario: an Administrative Specialist 3 in Executive Services, dated 8/8/22, planning a move toward an HR career.

• Profile: Administrative specialist, six years’ tenure, targeting a move into HR
• Development focus: Build the HR-specific knowledge and experience the target role requires
• Strengths: Process organization, confidentiality handling, cross-department relationships
• Development need: No direct HR casework experience; limited knowledge of HR policy and systems
• Objective and target date: Within twelve months, be a credible internal candidate for an entry-level HR role, evidenced by completed HR project work and a sponsor’s endorsement
• Actions: Volunteer for HR-adjacent duties such as coordinating onboarding logistics; take on a project supporting an HR process improvement; arrange informational interviews and job shadowing with two HR staff; complete a foundational HR course
• Resources and support: Time approved for shadowing; an HR mentor identified through the informational interviews; supervisor agrees to suggest opportunities, celebrate progress, and work with leadership and HR to address organizational barriers, the support role King County’s guidance assigns to supervisors explicitly
• Success measures and reviews: Success is measured by completion of the HR project with feedback from the HR team, the course certificate, and readiness confirmed in a review conversation with the mentor; quarterly reviews

The design lesson here is proportion. King County’s action plan uses the 70/20/10 learning model, with experience-based activities such as new duties, projects, and volunteer work forming the largest share. For a career changer, experience in the target function is the evidence hiring managers actually inspect.

Aspiring leader: Develop readiness for broader responsibility

A leadership-readiness plan should build and demonstrate capability, not promise a promotion. Completing the plan makes the case for readiness; it does not guarantee an outcome, and the plan should say so.

• Profile: Senior individual contributor, identified as interested in a team-lead role
• Development focus: Demonstrate planning, delegation, and communication at a team-leadership level
• Strengths: Technical credibility with peers; consistent delivery
• Development need: No experience leading work through others or representing the team upward
• Objective and target date: Within twelve months, lead one cross-functional project from planning to delivery and present results to the department
• Actions: Take a stretch assignment leading a defined project with two contributors; meet monthly with a mentor who currently leads a team; attend a leadership fundamentals course; request structured feedback from project contributors at the midpoint and end; deputize for the manager in one recurring meeting per month
• Resources and support: Project sponsorship from the manager; mentor time; manager agrees to observe two project meetings and give written feedback
• Success measures and reviews: Success is measured by on-time project delivery, contributor feedback at the two collection points, the mentor’s assessment against an agreed list of lead-role expectations, and the department presentation; reviews at months 4, 8, and 12

This plan combines the stretch assignments, mentoring, and peer feedback that AIHR names as core IDP activities with the Baylor objective-action-measurement discipline. The milestone structure matters most here: leadership readiness is judged over time, so the plan schedules multiple evidence points rather than one end-of-year verdict.

Individual development plan template

The template below combines the fields that appear consistently across the sourced examples: Indeed’s basic template (profile, development focus, goals, strengths, needs, opportunities, action plan), Baylor’s objective-level structure (objective by date, actions, measurement), and Paycor’s per-item discipline (activity, measure, resources, completion date). Copy it into a document and fill in each line.

Individual development plan

• Name, role, department, date:
• Development focus area: (one priority, such as a skill, role transition, or leadership capability)
• Career goals and aspirations: (short-term and longer-term)
• Strengths and talents: (include at least one strength you will deliberately use in this plan)
• Key development need: (the specific gap between where you are and where the goal requires you to be)
• Objective 1, with date: “By [date], I will…”
• Actions: “To meet my objective, I will take the following actions…” (each with its own completion date)
• Resources needed: (training, mentorship, tools, access, or time, per Indeed’s guidance to identify resources for each action step)
• Manager or mentor support: (what your manager, mentor, or sponsor specifically agrees to do)
• Measurement: “I will measure success by…” (observable evidence, not effort)
• Milestones and review dates: (interim checkpoints and the next scheduled review)

Repeat the objective block for each additional objective. Baylor’s guidance suggests a bounded scope: one to three objectives over the next 6 to 12 months. More than three objectives usually means the plan has not chosen a priority. When adapting one of the completed examples above, keep the field order intact and rewrite every value; a plan with someone else’s actions and your name on it will not survive its first review conversation.

Choose a one-page or detailed IDP format

Neither format is universally better; the right choice depends on how much documentation your situation needs and how much maintenance you will realistically do. Indeed’s basic template and Deel’s customizable blank template represent the lightweight end, while Baylor’s per-objective structure with separate objective, action, and measurement statements represents the detailed end. Deel notes that the main advantage of a blank, customizable template is the freedom to adapt it in Word or Google Docs.

Factor	One-page plan	Detailed objective-level plan
Best for	A single clear priority; employee-led planning; first-time IDPs	Multiple objectives; formal development programs; plans reviewed by HR or a program office
Structure	One block of fields, as in Indeed’s basic template	Repeated objective blocks with per-objective actions, measurements, and dates, as in Baylor’s template
Maintenance burden	Low; easy to update at each check-in	Higher; each objective needs its own milestone tracking
Documentation strength	Enough for a personal or team-level record	Better for consistency across employees and for program records
Main risk	Goals stay vague because fields are broad	The plan is completed once and never revisited because updating it feels heavy

A practical default: start with the one-page format, and move to the detailed format only when you have more than one objective or when a program requires standardized records. The trade-off runs in both directions, since a lightweight plan encourages regular use while a detailed plan improves consistency, and the best format is the one that actually gets reviewed.

How to turn a career goal into a measurable IDP

Most weak IDPs start as reasonable aspirations that were never converted into observable commitments. The conversion follows a repeatable sequence, and each step corresponds to a field in the template above.

Step 1: Narrow the aspiration to one development priority. AIHR’s first step is to define one clear goal, such as preparing for a new role, improving performance, building a technical skill, or becoming a stronger manager, specific enough to guide the plan and realistic within the agreed timeline. “Grow my career” is an aspiration; “lead client meetings independently” is a priority.

Step 2: State the baseline and the target behavior. Write down what you can do now and what the goal requires you to do. This pairing is what makes measurement possible later. The gap between the two is your development need, and it should be written in behavioral terms, not personality terms. “I present data clearly in writing but have not presented to executives” is workable. “I lack executive presence” is not.

Step 3: Choose actions across more than one activity type. For each action, apply Paycor’s per-item rule: name the activity, the measure, the resources, and the completion date. Mix applied practice, input from others, and formal learning rather than defaulting to a course, using the activity bank in the next section.

Step 4: Name a strength you will deliberately use. Northwestern’s sample plan treats development as building on what already works, not only fixing gaps. Asking “which existing strength makes this action easier?” is a practical planning question. A strong writer developing presentation skills can script talks in writing first; a well-networked employee developing technical skills can recruit reviewers quickly.

Step 5: Secure a specific support commitment. Record what your manager or mentor agrees to do, in the same concrete terms as your own actions: review two drafts, observe one meeting, free up four hours per month. King County’s supervisor guidance frames this as working collaboratively to provide support and address obstacles.

Step 6: Define the success measure and set review dates. Use Baylor’s sentence stem, “I will measure success by,” and complete it with evidence someone else could verify. Then set the dates on which you will check progress, following AIHR’s fourth step: agree on when each action happens and what progress should look like.

Here is the conversion in miniature. Before: “Goal: improve presentation skills. Action: take a presentation course.” After: “Objective: by 30 September, present the monthly results review to the department without a co-presenter. Baseline: I currently present only within my team. Actions: complete a presentation course by May; co-present the June and July reviews; present August solo with my manager observing. Support: manager reviews my slides for June and July and gives written feedback. Measurement: I will measure success by delivering the September review solo and by my manager’s feedback against three agreed criteria. Reviews: end of June, end of July, mid-September.” The second version takes ten more minutes to write and is the difference between a plan and a wish.

Development activity ideas beyond formal training

The most common IDP design error is assigning a course to every goal. The sourced templates and examples treat formal training as one activity type among several. AIHR lists training, mentoring, job shadowing, stretch assignments, project work, peer feedback, and coaching from a manager as valid action steps, and OPM’s career development guidance adds rotational assignments, on-the-job training, self-study programs, web-based training, and professional conferences and seminars to the list of activities an IDP can record.

Grouped by how the learning happens, the options include:

• Applied work: new duties, stretch assignments, project ownership, rotational assignments, deputizing for a manager, volunteer work (King County names new duties, projects, and community volunteer work as experience-based activities)
• Learning from others: mentoring, job shadowing, peer feedback, coaching, informational interviews, observing code reviews or client meetings
• Formal and self-directed learning: classroom and web-based courses, self-study programs, professional conferences, and books applied to daily work, which Northwestern’s sample pairs with the instruction to apply the learnings, not just read

One optional design lens is the 70/20/10 model. King County’s IDP example structures its action plan around it, with experience-based activities at roughly 70 percent, and Deel describes employees defining activity types per goal using the 70-20-10 approach. Treat the percentages as a diversity check, not a proven formula: the useful question is not whether your plan hits exact ratios but whether it contains any applied practice and any input from other people, or whether it is a reading list in disguise. A plan whose actions are all in the third group should usually trade at least one course for a project or a shadowing arrangement.

Who owns the IDP?

The employee owns the IDP; the manager supports it. That is the consistent position across the sourced guidance, even though the emphasis varies. OPM states that employees take personal responsibility and accountability for their career development, while the IDP itself is a partnership between employee and supervisor involving preparation and continuous feedback. AIHR puts it similarly: employees take the lead in creating their own IDPs, and supervisors provide feedback, guidance, and alignment with organizational priorities. Mentor and HR involvement is context-dependent and should not be assumed.

Participant	Responsibility	What this looks like in the plan
Employee	Owns the plan: drafts goals, completes actions, tracks progress, raises barriers	Every objective, action, and measurement is written in the employee’s own words
Manager	Agrees on the plan, provides feedback and guidance, commits specific support, removes barriers	A named support commitment per objective; King County’s guidance adds suggesting improvements, celebrating progress, and working with leadership and HR to address organizational barriers
Mentor (where available)	Offers perspective, role modeling, and skill-specific feedback outside the reporting line	Scheduled mentoring sessions listed as actions; OPM describes mentoring as a formal or informal relationship, usually with a senior mentor outside the protégé’s chain of supervision
HR or L&D (where present)	Supplies templates, program structure, and access to training resources	Referenced in the resources field, not as the plan’s owner

Alignment with organizational goals deserves one careful note. OPM highlights that career development planning benefits both the employee and the organization by aligning development efforts with the organization’s mission and goals. Alignment strengthens a plan when it identifies projects and assignments the organization will actually sponsor. It weakens a plan when it converts personal career goals into a list of organizational tasks. The practical test is whose aspiration appears in the goal field: it should be the employee’s, with the organizational connection appearing in the choice of actions and the manager’s willingness to sponsor them.

Review and update the plan

An IDP that is written once and filed is a form, not a plan. The sourced guidance converges on a bounded planning horizon with a regular review rhythm, though the specific numbers are source examples rather than universal rules. Baylor’s template scopes a plan to one to three objectives over the next 6 to 12 months and instructs employees to keep the IDP fluid, updating development goals throughout the year. AIHR recommends reviewing the plan regularly, usually quarterly or biannually, with monthly or quarterly check-ins to discuss progress, remove barriers, and update goals as priorities change. OPM notes that many agencies encourage employees to update IDPs annually, and that an IDP is not a one-time activity.

A workable review has three parts. First, evidence: compare actual progress against the milestones and measurement statements written into the plan, using the “I will measure success by” line as the agenda. Second, barriers: name what is blocking an action, because barrier removal is the manager’s clearest contribution, as King County’s supervisor guidance makes explicit. Third, revision: adjust dates, swap activities that are not working, and retire objectives that are complete or no longer relevant. Deel’s guidance describes the timeline and review mechanism as what keeps the plan accountable and on track. Put the next review date in the plan itself before the current review ends; an unscheduled review is a cancelled review.

IDP vs. performance review vs. performance improvement plan

These three tools answer different questions. An IDP asks where the employee wants to grow next. A performance review evaluates how the employee performed against expectations in a past period. A performance improvement plan (PIP) is a formal corrective process triggered by performance falling below an acceptable level. OPM is explicit that an IDP is not a performance evaluation tool, and AIHR states that an IDP is neither a review of past performance nor limited to the current job’s responsibilities; it looks ahead.

Dimension	IDP	Performance review	Performance improvement plan (PIP)
Primary purpose	Growth toward future goals and competencies	Evaluation of past performance against expectations	Correction of documented performance deficiencies
Time orientation	Forward-looking	Backward-looking	Short, fixed window; typically 30 business days in the U.S. federal process per OPM’s PIP quick guide
Typical content	Goals, actions, resources, support, measures, review dates	Ratings and assessment against the performance plan	Description of unacceptable performance, critical elements, specific deficiency examples, expectations, support provided, and consequences
Consequences	Primarily developmental; approval requirements and consequences for revising goals depend on employer or program policy, and some organizations use development plans for promotion, selection, salary, or accountability purposes	Feeds compensation, promotion, or development decisions per employer practice	In the federal process, failure can lead to the consequences specified in the PIP
Voluntariness	May be required or optional depending on employer or agency policy; either way, planning is typically employee-led in partnership with a supervisor	Employer-scheduled	Employer-initiated and formally documented

Two boundaries matter in practice. First, scope: the detailed PIP mechanics above come from OPM’s guide for U.S. federal agencies, where PIPs are governed by regulations such as 5 CFR Part 432 or Part 752. Employers in other sectors and countries run corrective processes differently, and the supplied sources do not establish one universal rule for how underperformance must be handled. Second, purpose: research published in Vocations and Learning by Beausaert and colleagues found that employees who perceive a personal development plan as a learning and development tool, rather than a promotion and selection instrument, are more likely to undertake learning activities and perform better, based on a study building on a review of 54 empirical studies. The practical implication is to keep the IDP genuinely developmental. If a serious performance problem exists, address it through the employer’s formal performance process, and let the IDP remain the growth tool it is designed to be.

How should someone create and use an IDP when they do not have a supportive manager or formal employer development program?

Keep a personal IDP using the same evidence-based structure, and replace the manager’s role with feedback sources you can access. Nothing in the template requires an employer program: OPM notes there are no regulatory requirements mandating IDPs even in the U.S. federal government, and the core fields, one priority, baseline and target, actions with dates, resources, and a measurement statement, work in a private document.

Three adaptations make a self-managed plan viable. First, choose actions you control: self-study, applied practice in your current duties, volunteer projects, and informational interviews do not need approval, and King County’s activity model counts volunteer work and new duties as experience-based development. Second, substitute the feedback function: a mentor outside your reporting line, a trusted peer, or a professional community can review your work against your measurement statements, replacing the manager feedback that AIHR assigns to supervisors in the standard workflow. Third, run your own reviews: put quarterly self-review dates in your calendar and treat them as fixed. The plan loses the manager’s barrier-removal power, so keep objectives smaller and fully within your own authority, and revisit the plan if your access to support changes.