On this page
- What is an individual development plan?
- Why IDPs matter
- How to build an IDP step by step
- What an IDP actually looks like
- The 70/20/10 development framework
- IDP examples by role
- Common IDP mistakes
- How Huneety builds IDPs from assessment data
- Who uses individual development plans
- Related topics
- Explore the IDP cluster
- Frequently asked questions
THE BASICS
What is an individual development plan?
An individual development plan (IDP) is a structured agreement between an employee and their manager that translates assessment results into specific development actions over a defined period — usually a quarter, a half-year, or a full development cycle.
Unlike a performance review, which looks backward at what an employee has already delivered, an IDP looks forward. It is grounded in two questions: which competencies matter most for the role this person is in (or aspires to) — and how do we close the gap between current ability and required ability?
A good IDP is gap-driven, prioritized, and measurable. It does not list every weakness or every aspiration. It identifies the two or three competency gaps that will have the biggest impact on performance, then commits to a small number of concrete actions for each. The framework most teams use to structure those actions is 70/20/10 — and we'll walk through it in detail below.
BUSINESS VALUE
Why IDPs matter
The cost of un-targeted training
Most organizations spend a meaningful share of their L&D budget on training that nobody follows up on. A workshop happens, the certificate goes in a drawer, and three months later the gap that triggered the training is still there. The reason is rarely the quality of the content. The reason is that the training was not anchored to a specific gap, a specific behavior change, or a specific person.
What an IDP forces up front
An IDP changes the economics of development by forcing three things to happen up front:
- 1A measurable starting point — the competency assessment that established the gap
- 2A specific target — the level the role requires, not a vague aspiration
- 3A plan with owners and deadlines — not a wishlist
From cost to investment
When these three things are in place, development stops being a cost center and starts looking like an investment with a measurable return. The competency that was at level 2 is now at level 3.5. The skill gap that blocked promotion is closed. The capability the team needed to ship a new product is in place. None of that happens by accident, and none of it happens from a one-off training day. It happens because someone wrote it down, made it specific, and checked in on progress — which is exactly what Huneety's IDP module is built to automate from the assessment data it already has.
THE PROCESS
How to build an IDP step by step
Building an IDP is not complicated, but the order matters. Skip a step and the plan becomes a wishlist. Six steps:
Start from assessment data
An IDP without an assessment is a guess. Start from a 360, a self-and-manager evaluation, or any structured snapshot of where the employee is today against the competencies their role requires.
Identify the top 2–3 gaps
List every gap, then pick the two or three that have the highest impact on the current role or the next one. More than three priorities is no priorities — research is consistent on this.
Set a measurable target
For each priority gap, write down the level the role requires. "Improve communication" is not a target. "Reach level 3.5 in stakeholder communication by the end of Q3" is.
Write 70/20/10 actions
For each priority, design 2–4 concrete actions split across on-the-job (70%), learning from others (20%), and formal training (10%). Each action gets an owner and a date.
Get manager validation
The plan is co-owned. The manager confirms the priorities are right, the actions are realistic, and they are committing to make the on-the-job opportunities available.
Review quarterly
An IDP that is written once and never revisited is a document, not a development plan. Schedule a quarterly review to mark progress, adjust actions, and re-check whether the priorities still hold.
AT A GLANCE
What an IDP actually looks like
Here's a real example — a project manager whose career path target is Senior PM (level 4), with a critical gap in project management. The graph below shows how the career target, competency gap, priority, and 70/20/10 action plan all connect. Click any node to see how it fits into the bigger picture.
Click any node in the graph to see how it connects the career path target to a concrete weekly action.
THE FRAMEWORK
The 70/20/10 development framework
The 70/20/10 framework is the most widely used structure for organizing development activities. It originated from research at the Center for Creative Leadership by Morgan McCall, Robert Eichinger, and Michael Lombardo in the 1980s, who studied how successful executives reported having actually learned the skills that mattered. Their finding: roughly 70% from challenging on-the-job experiences, 20% from interactions with others, and 10% from formal coursework or reading.
The percentages are not laws of physics — they are heuristics. The point is the relative weight: most development comes from doing real work that is slightly beyond your current ability, supported by people who can give you feedback, with formal training as a small but specific complement. Each tab below explains what this looks like in practice.
70% — On-the-job experiences
This is where most real development happens. The mechanism is simple: people are placed in situations where their current skills are insufficient, they are given enough support to not fail catastrophically, and they figure it out. Stretch assignments, leading a project for the first time, owning a new client, presenting to a new audience, working in a new function for a quarter — all of these are 70% activities.
The most common mistake here is assuming that someone's current job is the development opportunity. It usually is not. The job is the place where they already perform. Development comes from work that is meaningfully different from what they do today. If you cannot identify a stretch in the current role, the IDP needs a job design conversation, not more training.
BY ROLE
IDP examples by role
What an IDP actually looks like depends on the role and the gap. The four examples below show a single priority competency, the gap, and a 70/20/10 plan with specific actions, owners, and deadlines. Click an activity to mark it complete — these are interactive demos.
Individual Development Plan
Priya Mehta · Marketing Manager
Lead the Q3 brand reposition launch as primary stakeholder owner
Present quarterly marketing results to the C-suite (own the deck)
Bi-weekly 1:1 coaching with the VP Marketing
Communicating with Executives (1-day workshop)
PITFALLS
Common IDP mistakes
Most failed IDPs fail in the same six ways. None of these are obscure — they are the predictable failure modes of a process that is easy to start and easy to abandon. A structured IDP workflow prevents most of them by default, but the antidotes are the same regardless of tool.
Too many priorities
Five priorities is no priorities. The point of the plan is to pick the two or three competency gaps that matter most and accept that the others are not getting attention this cycle. If the plan tries to fix everything, nothing gets fixed.Training-only plans
If the IDP is a list of courses with no on-the-job experiences and no mentoring, it is not an IDP — it is a learning catalog. Real development needs the 70% and the 20% to do most of the work.No baseline assessment
Without a competency assessment, there is no objective gap, just an opinion. The plan ends up reflecting whoever is loudest in the development conversation, not where the actual capability deficit is.Vague targets
"Improve communication" is not a target. "Reach level 3.5 in stakeholder communication by Q3" is. Without a measurable target, you have no way to know if the plan worked.No manager involvement
An IDP that the employee writes alone and the manager skims is theatre. The manager has to commit to making the stretch assignments, the introductions, and the coaching time available — otherwise the plan cannot be executed.Set it and forget it
An IDP that is not reviewed quarterly is a document. The point of the plan is the cadence of check-ins, adjustments, and progress signals — not the document itself.
HUNEETY IDP
How Huneety builds IDPs from assessment data
Huneety automates the path from assessment to action plan. The output is the same gap → priority → 70/20/10 structure described above — rendered as a live, trackable plan instead of a Word doc. The card below is the actual interactive plan view from the product.
Individual Development Plan
Sarah Chen · Product Lead
Lead the Q3 cross-team initiative
Own the next quarterly business review
Bi-weekly 1:1 with VP Strategy
Strategic Leadership 101
Gap-driven by default
Every IDP starts from real assessment data. No guessing, no opinion. The gaps are the gaps.
AI-suggested 70/20/10 actions
Huna AI suggests on-the-job, peer-learning, and training activities matched to each priority gap.
Manager approval workflow
Draft → Pending → Active → Archived. The manager owns the validation step before the plan goes live.
Quarterly check-in cadence
Built-in review cycle so the plan doesn't end up in a drawer. Progress signals roll up to skills analytics.
AUDIENCES
Who uses individual development plans
IDPs sit in two very different operating contexts. Both groups use the same underlying structure, but the deployment model and the value drivers are different.
HR Teams
HR teams use IDPs as the connective tissue between annual assessments, L&D budget, and talent reviews. The plan is the artifact that proves development is happening — and the data the plans generate is what justifies next year's budget.
HR Consultants
Consultants use IDPs as a scalable deliverable. After a 360 assessment project, every assessed employee gets a structured IDP — branded, defensible, and tied to the assessment data the consultant just delivered.
GO DEEPER
Explore the IDP cluster
Four subtopic guides go deeper on the parts of the IDP process that most teams ask about.
70/20/10 Framework
The history, the research, and a practical guide to balancing the three categories in real plans.
IDP Templates
Free downloadable IDP templates by role — manager, IC, technical leader, first-time manager.
Gap Analysis for IDPs
How to translate assessment results into the two or three priority gaps that anchor every plan.
IDPs for Managers
Writing development plans for people who manage people. Scorecards, execution dimensions, and the link to succession planning.
FAQ
Frequently asked questions
The questions teams ask most often when they start using IDPs.