IDP Templates for Your Team

Most individual development plans die in a shared drive by mid-February. You spent hours in review season filling them out, and then the document never came up again. This guide gives you a practical IDP template you can roll out across a whole team — plus the structure, cadence, and manager habits that keep those plans alive long after the kickoff meeting.

What’s inside

• Why individual development plans for teams usually fail

• The anatomy of an IDP template that gets used

• A copy-and-adapt IDP template

• Rolling plans out across a whole team

• Making managers the engine, not the bottleneck

• Connecting IDPs to your career framework

• Measuring whether development is actually happening

• Keeping plans alive between review cycles

• How Blomma helps you scale development across your team

Why individual development plans for teams usually fail

The problem is rarely the template. It’s that the plan is treated as a compliance artifact instead of a working document. HR asks for one per person, managers fill them out to hit a deadline, and nobody looks at them again until the next cycle forces a repeat.

The second failure mode is scale. A plan that a Head of People writes carefully for one high-potential leader doesn’t survive being copied across sixty people and forty managers of wildly different skill. Quality collapses, and so does trust in the process.

The fix isn’t a fancier form. It’s designing individual development plans for teams around three things: they have to be short enough to actually revisit, specific enough to act on, and owned by the employee rather than the HR calendar. When development stalls, it usually isn’t ambition that’s missing — as Blomma’s team argues in your career isn’t stuck, it’s the lack of a concrete next move. A good IDP names that move.

The anatomy of an IDP template that gets used

A usable IDP template fits on one page and answers five questions. Where is this person trying to go? What capability is the current gap? What will they actually do about it? How will we know it worked? And who is supporting it?

Everything else is decoration. Resist the urge to add competency matrices with twenty rows — nobody fills those in honestly, and they make the plan feel like an audit. Keep the goal count small: two development goals per cycle is plenty. People who chase five goals finish none.

The strongest templates also separate two kinds of growth: performance in the current role, and preparation for the next one. Blur those and you get plans that are all aspiration and no traction, or all firefighting and no future. Name both explicitly so the employee and manager can see the balance — and adjust it when priorities shift mid-quarter.

A copy-and-adapt IDP template

Here’s a structure you can lift directly into a doc or your HRIS:

1. Development goal — One sentence, outcome-focused. “Lead a cross-functional project end to end by Q3,” not “improve leadership.”

2. Why it matters — Tie it to the person’s direction and the team’s needs. This is the motivation that survives a busy week.

3. Current reality — An honest line on where they are today. Skipping this makes progress impossible to see.

4. Actions — Two or three concrete moves: a stretch assignment, a specific skill to practice, a person to shadow. The 70-20-10 rule is a useful nudge here — most growth comes from real work, not courses.

5. Support needed — What the manager, the org, or a coach will provide. Budget, air cover, feedback, introductions.

6. Evidence of progress — What “done” or “better” looks like, checked at a set date.

Give people two goals, one page, and a real review date. That constraint is the feature, not a limitation.

Rolling plans out across a whole team

Going from one plan to forty is where good intentions break. Don’t launch by emailing a blank template to every manager and hoping. Run it like a small change program.

Start with a shared kickoff so everyone hears the same why and sees a worked example. Give managers a filled-in sample plan — a real one, lightly anonymized — so they’re calibrating against a standard instead of inventing their own. Set one deadline for first drafts, and one for the manager conversation that follows.

Crucially, make the employee draft first. When people write their own individual development plans, ownership is baked in from the start; when managers write them, the plan belongs to the manager. The manager’s job is to react, sharpen, and commit support — not to author.

Stagger the rollout if you can. Piloting with two or three teams first lets you fix the template’s rough edges before the whole org forms an opinion. A clumsy first launch is hard to relaunch.

Making managers the engine, not the bottleneck

Your IDP process is only as good as your least confident manager. Some will run a great development conversation instinctively; many won’t, and will quietly avoid the whole thing. Plan for that gap rather than pretending it doesn’t exist.

Give managers a simple conversation guide: ask what the person wants next, name one strength to lean into and one gap to close, agree on two goals, and commit to specific support. That’s it. The magic is in follow-through, not eloquence.

Managers also need to understand how growth and visibility actually convert into advancement, because employees will ask. Blomma’s breakdown of how execs make promotion decisions is a useful thing to put in a manager’s hands — it helps them coach honestly about what moves the needle instead of making promises they can’t keep. When managers can connect a development goal to a real path forward, the plan stops feeling like paperwork and starts feeling like an investment.

Connecting IDPs to your career framework

An IDP floating free of any structure becomes a wish list. Anchored to a clear framework of levels and expectations, it becomes a map. When someone can see what the next level actually requires, their development goals almost write themselves — the gap between “here” and “there” is right there on the page.

This is why individual development plans and career frameworks work best as a pair. The framework defines the destinations; the IDP is the personalized route. Without the framework, every manager invents their own definition of “senior,” and your plans drift into inconsistency and, eventually, into perceived unfairness.

You don’t need a perfect ladder to start. Even a rough sketch of level expectations gives IDPs something to point at. And the framework doesn’t have to imply a single vertical climb — lateral moves and skill breadth are legitimate growth, especially on smaller teams. Ground the plan in shared expectations, and the conversation shifts from “do I deserve a promotion” to “what specifically would get me there.”

Measuring whether development is actually happening

If you can’t tell whether IDPs are working, they’ll quietly become theater. But resist vanity metrics like “percent of plans submitted.” A 100% completion rate on plans nobody revisits tells you nothing.

Track a few signals instead. What share of development goals were actually reviewed at their check-in date? How many people made a visible move — a stretch project, a new responsibility, a lateral shift — that traced back to their plan? Are your internal-mobility and promotion rates trending up as the program matures? And in engagement surveys, is the “I have opportunities to grow here” score improving?

Those are lagging indicators, so give the program a couple of cycles before judging it. Pair the numbers with a light qualitative pulse: ask a sample of employees whether their plan reflects what they actually want. A plan the employee doesn’t believe in won’t move any metric, no matter how neatly it’s filled out.

Keeping plans alive between review cycles

The entire value of an IDP is created between the meetings, not in them. The plan that gets touched monthly beats the perfect plan reviewed twice a year, every time.

Build in lightweight cadence. A five-minute IDP check-in inside the existing 1:1 every few weeks is enough — no new meeting required. The question is simple: what did you move on, and what’s blocking the next step? Momentum matters more than polish, and small, frequent progress compounds.

Make asking for support normal, too. Development stalls when people don’t feel they can request time, budget, or a stretch opportunity out loud. Blomma’s piece on making room for growth is a good conversation starter for teams learning to advocate for themselves. When asking is normalized, plans stay live because people keep pulling on them — instead of waiting for permission that never quite arrives.

How Blomma helps you scale development across your team

Here’s the honest tension: great individual development plans need great coaching to stay alive, and most organizations can only afford that kind of coaching for a handful of executives. Everyone else gets a template and a busy manager.

Blomma closes that gap by giving every person on your team an always-on AI career coach. Instead of a plan that gets revisited twice a year, each employee has a coach in their pocket to break goals into next steps, prep for a stretch conversation, work through a blocker at 9pm, and keep momentum between 1:1s. Managers stop being the sole bottleneck for development, and your IDP process finally has something behind it. See how Blomma coaching works for individuals, and our team plans for rolling it out across a group.

It’s the kind of development support that used to be reserved for the corner office — now available to your whole team, at a cost that actually scales.

Bring Blomma to your team →

Related reading

• Your career isn’t stuck

• How execs make promotion decisions

• Introducing room for growth