Sprutia Blog

Insights on management, productivity, and team building

Leadership 8 min read

Individual Development Plan (IDP) Template with Examples

A copy-paste individual development plan template, three worked IDP examples for different roles, and how to keep the plan alive in your 1:1s.

BC

Brad Cypert

Most individual development plans get written once, usually around review season, and never opened again. The plan isn't connected to anything that happens week to week, so it fades.

A useful IDP is short, specific, and reviewed often. It answers four questions: where does this person want to go, what are they already good at, what do they need to get better at, and what are we going to do about it in the next few months?

Below is a copy-paste IDP template, three worked examples for very different roles, and the part most guides skip: how to keep the plan alive by tying it to your 1:1s. If you want the bigger case for developing people instead of always hiring from outside, I wrote about that in Why Upskilling Your Staff Is Often Better Than Hiring External Talent.

What an IDP Is (and Isn't)

An individual development plan is a shared, written plan for how one person will grow over a set period, usually six to twelve months. The employee and manager build it together. The employee owns it; the manager supports it.

It isn't a performance improvement plan. It isn't a list of tasks for their current job. And it isn't a promise of a promotion. It's a plan for building skills and experience that matter to the person and to the team.

The IDP Template

Copy this into a shared doc or tool. Keep it to one page if you can. Two or three goals is plenty; more than that and nothing gets real attention.

INDIVIDUAL DEVELOPMENT PLAN
Name: [Employee]            Manager: [Manager]
Role: [Current role]        Plan period: [Start date] – [End date]
Last reviewed: [Date]

1. Career goal
   Where I want to be in 1–3 years:
   -
   Why it matters to me:
   -

2. Strengths (what I want to keep building on)
   -
   -

3. Growth areas (what would make the biggest difference)
   -
   -

4. Development goals (2–3 max)

   Goal 1: [Specific goal]
   - Skills to develop:
   - Activities (courses, projects, stretch work, mentoring, practice):
   - Support needed (from manager, team, budget, time):
   - How we'll know it's working (measures):
   - Target date:
   - Status: Not started / In progress / Done / Changed

   Goal 2: [Specific goal]
   - Skills to develop:
   - Activities:
   - Support needed:
   - Measures:
   - Target date:
   - Status:

   Goal 3 (optional): [Specific goal]
   - Skills to develop:
   - Activities:
   - Support needed:
   - Measures:
   - Target date:
   - Status:

5. Review cadence
   - Quick check-in: monthly, during a 1:1
   - Full review and update: quarterly
   - Next full review: [Date]

6. Notes and changes
   - [Date] —

A few notes on filling it out.

Career goal comes first, and it's theirs. Ask, don't assign. "I'm not sure yet" is a fine answer. In that case, the goal might be to try a couple of directions and see what sticks.

Strengths matter as much as gaps. People grow faster by leaning into what they're good at than by only patching weaknesses. Naming strengths also makes the conversation feel less like a critique.

Activities should be mostly on-the-job. Courses and books help, but most growth comes from doing: a stretch project, leading a meeting, owning a process, getting coached on real work. Aim for a mix.

Measures should be observable. "Get better at communication" can't be checked. "Run the weekly team sync for a month and get feedback from two teammates" can.

Support needed is the manager's to-do list. If the plan says they need time, budget, an introduction, or a chance to lead something, that's on you.

Three IDP Examples

Here's how the template looks filled in for three different roles. These are illustrative, not prescriptive. Use them to get unstuck, then make the real one specific to your person.

Example 1: New team lead

Career goal: Grow into a confident people manager over the next 18 months, with the option to manage a larger team later.

Strengths: Trusted by peers, strong at the core work, good at explaining things.

Growth areas: Delegating instead of doing, giving direct feedback, planning work beyond the next two weeks.

Goal 1: Delegate effectively.

  • Skills: delegation, setting clear expectations
  • Activities: hand off two pieces of work they'd normally do themselves each month; review how it went in the next 1:1
  • Support: manager coaches on how to frame handoffs; agrees it's okay if delegated work isn't done exactly their way
  • Measures: by the target date, they're no longer the bottleneck on routine work, and teammates report having clear ownership
  • Target date: end of next quarter

Goal 2: Give regular, specific feedback.

  • Skills: feedback, difficult conversations
  • Activities: read a feedback framework and practice it in their own 1:1s; role-play one hard conversation with their manager before having it
  • Support: manager shares how they prepare for tough conversations; recommends our guide to handling difficult conversations
  • Measures: they give at least one piece of specific feedback in each 1:1 they run, and can describe how they handled a hard conversation
  • Target date: six months out

Example 2: Senior individual contributor

This could be a senior engineer, analyst, designer, or account manager. The pattern is the same: someone highly skilled who wants more influence without necessarily managing people.

Career goal: Move toward a staff-level or principal role, known for leading cross-team work.

Strengths: Deep expertise, high-quality output, people come to them with hard problems.

Growth areas: Influencing outside their team, writing proposals that get decisions made, mentoring.

Goal 1: Lead a cross-team initiative.

  • Skills: stakeholder management, written communication, planning
  • Activities: write and circulate a proposal for a problem that spans two teams; run the kickoff and the regular check-ins
  • Support: manager helps identify the right problem and introduces them to the relevant leads
  • Measures: proposal reviewed and a decision made; initiative has a clear plan and owners
  • Target date: within six months

Goal 2: Mentor a less experienced teammate.

  • Skills: coaching, teaching
  • Activities: meet with a mentee every other week; pair on one real piece of work
  • Support: manager makes the match and protects time for it
  • Measures: the mentee can independently handle a type of work they couldn't before; mentee shares feedback on the mentoring
  • Target date: end of next quarter, then revisit

Example 3: Customer support specialist

Career goal: Become a go-to expert for complex customer issues, and explore a path toward support operations or team lead.

Strengths: Patient and empathetic with customers, consistently high-quality responses.

Growth areas: Deeper product knowledge on advanced features, spotting patterns across tickets, sharing knowledge with the team.

Goal 1: Build expertise in one advanced product area.

  • Skills: product knowledge, troubleshooting
  • Activities: shadow escalations in that area; spend time with the product or engineering team that owns it; take on the next few complex tickets with a senior teammate available for backup
  • Support: manager arranges the shadowing and adjusts ticket load to make room for learning
  • Measures: handles escalations in that area with less need for hand-offs; teammates start routing questions to them
  • Target date: four months out

Goal 2: Turn repeat issues into team knowledge.

  • Skills: written documentation, pattern recognition
  • Activities: each month, identify one recurring issue and write or update a help article or internal guide for it
  • Support: manager gives time for writing and shares the work with the wider team
  • Measures: a handful of new or improved articles by the target date, and the team actually uses them
  • Target date: six months out

All three share the same shape: two goals, real work as the main activity, a specific ask of the manager, and measures you can check.

How Managers Tie IDPs to 1:1s

This is the difference between a plan that works and one that gathers dust.

Give it a regular slot. Once a month, spend part of a 1:1 on the IDP. What moved? What got stuck? Does anything need to change? A 10-minute check-in, done consistently, beats an annual deep dive.

Turn goals into action items. Every development conversation should end with at least one concrete next step, with an owner and a date. "Draft the cross-team proposal outline by next 1:1." "I'll introduce you to the product lead this week." Then review those items in the next meeting like any other.

Connect it to day-to-day work. When a stretch opportunity comes up (a project, a presentation, a customer escalation), check the IDP first. Assigning work with growth in mind is one of the most useful things a manager can do.

Do a fuller review each quarter. Update status, adjust goals that no longer fit, and add notes on what changed. Plans should change as people learn what they want.

Keep it collaborative. If only one of you ever touches the plan, it's become a form.

If you set team goals with OKRs, it can help to look at both side by side. Development goals don't have to map to team objectives, but when they do, growth and team outcomes reinforce each other. Our post on effective goal setting goes deeper on writing goals that stick.

Common IDP Mistakes

Too many goals. Five goals means none get real attention. Two is usually right.

Vague goals. "Improve leadership skills" isn't a plan. Name the specific skill and what doing it well would look like.

Training-only plans. A list of courses isn't a development plan. Courses support growth; real work is where it happens.

Manager-written plans. If you write it for them, they'll treat it like your plan. Draft it together, starting from their career goal.

Treating it as a performance tool. If the IDP shows up only when something's wrong, people will stop being honest in it. Keep development and performance management separate.

Never revisiting it. The most common mistake by far. If the plan hasn't come up in a 1:1 for a few months, it's not really a plan anymore.

Making IDPs Easier to Keep Alive

A shared doc can work fine for one plan. It gets harder across a whole team, when every plan lives in a different file and nobody remembers when each was last discussed.

That's why I built individual development plans into Sprutia alongside 1:1s. Both the manager and the employee can edit the plan, add goals, and update progress. You can track skills on a simple four-level scale (Learning, Competent, Proficient, Expert) and compare self-assessments with manager assessments. IDPs show up in your 1:1s, so you can see when a plan was last reviewed and create action items straight from development goals. There are also role-based templates to start from instead of a blank page.

You can start free, and every new workspace includes a 14-day trial of the Team plan, which is where IDPs, OKRs, and peer feedback live. After the trial, IDPs are part of Team; see pricing for details.

Action step: Pick one person on your team and put 30 minutes on the calendar for a development conversation. Bring this template, start with their career goal, and leave with two goals and one action item each. Then add a recurring monthly reminder to check in on it during your 1:1.