Every company has a folder full of individual development plans, and most of them share a fate: written in an energetic meeting, filed in a drive, and rediscovered eleven months later during review season, untouched.

The plan didn't fail because development doesn't work. It failed because it was designed as a document instead of a system. A good individual development plan is short, specific, tied to real work, and reviewed on a rhythm that keeps it alive.

Below is the template we recommend, six real examples across common roles and career stages, and the operating habits that keep a plan from dying in a drive. There's a downloadable version of the template you can put in front of your team this week.

What Is an Individual Development Plan?

An individual development plan (IDP) is a short, written agreement between an employee and their manager about the skills the employee will build next, why those skills matter to their career and the business, and the specific actions and support that will get them there. It's reviewed and revised on a regular cadence, usually quarterly.

Two things an IDP is not. It's not a performance review; reviews look backward at results, while an IDP looks forward at growth. And it's not a performance improvement plan; a PIP documents a problem, while an IDP invests in a future. Mixing these up is the fastest way to make employees dread a document that should excite them.

The case for bothering is blunt: LinkedIn's Workplace Learning Report found that 94% of employees say they'd stay at a company longer if it invested in their career development. An IDP is the cheapest possible way to make that investment visible, and the absence of one is often the first quiet signal that sends a good person to the job boards.

The Individual Development Plan Template

One page. Four sections. Three goals maximum.

1. Career direction. One or two sentences on where the employee wants to be in one to two years, written in their words, not the manager's. Everything below has to serve this sentence, which is exactly what keeps the plan from becoming a list of trainings someone else thought would be good for them.

2. Development goals (maximum three). For each goal: the skill to build, and why it matters twice over, once for their career, once for the business. A goal that serves only the company reads as an assignment. A goal that serves only the employee won't survive budget season. Goals that serve both get protected.

3. Action plan. The actions that build each skill, with a type, the support needed, and a target date. Mix the types deliberately: a stretch assignment, training with real practice, coaching, a mentor pairing. Reading and watching alone don't change what someone can do.

4. Quarterly check-in notes. A running log: what moved, what changes next quarter. This section is the difference between a plan and a paperweight.

Download the individual development plan template (Word), or rebuild the four sections in whatever tool your team already lives in.

6 Real Individual Development Plan Examples

The template comes alive in the specifics. Here's what it looks like across six common situations, condensed to the career direction, the goals, and a sample of the actions. Notice that none of the actions below is "take a course" standing alone; every plan pairs learning with a place to apply it and someone to give feedback on the attempt.

1. Software Engineer Growing Toward Senior

Career direction: senior engineer within 18 months, known for technical judgment, not just output.

Goals: lead a project end to end; improve technical communication; build code review skills that develop others.

Sample actions: own the next service migration including stakeholder updates; present one architecture decision to the broader team each quarter; pair weekly with a junior engineer and get feedback from their manager on how the mentoring lands.

2. High Performer Preparing for Management

Career direction: ready for a team lead role at the next opening.

Goals: practice giving direct feedback; learn delegation before having authority; understand what the job actually is.

Sample actions: lead the intern program this summer with hiring-manager-style check-ins; run point on a cross-functional project where influence has to substitute for authority; structured pre-promotion training on the core people skills, so day one as a manager isn't the first rehearsal. This is the profile an emerging leaders program exists for.

3. New Manager in Their First Year

Career direction: a manager whose team would choose to work for them again.

Goals: deliver specific feedback weekly; run one-on-ones that people value; delegate two significant responsibilities.

Sample actions: adopt a consistent one-on-one structure and hold the cadence for a full quarter; practice the two hardest upcoming conversations with an expert before having them; hand off the monthly reporting with a defined "done well" standard. The full first-year skill set is covered in our guide to manager training topics.

4. Sales Rep Building Toward Enterprise Deals

Career direction: move from mid-market to enterprise accounts within a year.

Goals: sharpen discovery and listening skills; learn multi-stakeholder navigation; strengthen executive-level communication.

Sample actions: shadow three enterprise cycles and debrief each with the AE; rewrite one proposal per month as a one-page executive summary and review it with the sales director; role-play objection handling monthly with a trainer rather than waiting to practice on live prospects.

5. Experienced Manager Growing Toward Senior Leadership

Career direction: director scope within two years.

Goals: develop the managers below them; communicate upward with more compression; lead through a change they didn't choose.

Sample actions: coach two team leads using a defined cadence and get 360 input on the results; deliver the department's quarterly narrative to the executive team; take the communication lead on the upcoming reorg, with expert practice on the announcement conversation first.

6. Individual Contributor Making a Cross-Functional Move

Career direction: transition from customer support into product operations.

Goals: build data analysis fundamentals; learn the product team's planning process; convert support insight into product influence.

Sample actions: complete a practical SQL course and apply it to a real support-trends analysis; embed with product for one planning cycle; present a quarterly "voice of the customer" readout, with coaching on the presentation itself.

How to Keep the Plan Alive

Notice what the six examples share. Three goals, never eight. Actions built from real work, not course catalogs. And practice woven into nearly every action, because the goals that matter are behavioral, and behaviors don't change by reading about them.

Then there's the operating rhythm, which decides everything:

• Book the quarterly check-in before the plan is signed. A plan without a standing meeting on the calendar is already dead; it just doesn't know it yet.
• Spend ten minutes of one monthly one-on-one on the plan. One goal, one question: what moved? Momentum comes from small, frequent contact, not big annual rewrites.
• The manager brings support, not a scorecard. The check-in exists to unblock: an introduction, a budget approval, protected time for a stretch assignment.
• Change actions freely, goals rarely, and the direction only when the person does. Log every change in the check-in notes, so the plan's history tells the development story when review season arrives.

Individual Development Plan FAQs

How is an IDP different from a career development plan? Mostly scope. A career development plan sketches the multi-year arc; an IDP is the working document for the next two to four quarters, with actions specific enough to start this month. The best setups use both: the career direction line at the top of the IDP is the bridge between them.

Who should have one? Everyone you'd be sorry to lose, which in practice means everyone. Limiting IDPs to high potentials tells the rest of the team what you expect from them, and disengagement follows the signal.

How often should it change? Actions can change every quarter; goals should mostly survive two to three quarters; the career direction changes when the person's ambitions change, and not before. A plan rewritten from scratch every quarter isn't a plan, it's a journal.

What if the employee's goal points away from the company? Develop them anyway. The choice was never between developing people who might leave and keeping them; it's between developing people who might leave and not developing people who definitely will.

The Plan Names the Skill. Something Still Has to Build It.

Here's the honest limit of every IDP, including the ones above: the document identifies what someone needs to learn. It doesn't teach them. The gap between "improve feedback skills" written in a plan and feedback actually delivered well in a tense moment is the gap where most development plans quietly fail.

Closing it takes practice with an expert: real scenarios, real feedback, enough repetition that the new skill holds up under pressure. That's what Bundle provides, live, 1:1 training built for each person's role, level, and industry, so the goals in the plan become behavior on the team. See how Bundle training works, or talk to a learning expert about turning your team's development plans into changed behavior.