The individual development plan is the most written and least read document in corporate India. The fix is not a better template — it is a better operating rhythm.
Every appraisal season, lakhs of IDPs are dutifully filled in across Indian organisations. By June, most are forgotten. When we audit development practices for clients, the pattern is depressingly consistent: 90%+ IDP completion rates, single-digit percentages of plans with any recorded action by year end.
The problem is rarely the template. It is what surrounds the template.
Why IDPs fail
- They are written for compliance, not commitment. When the IDP is a mandatory appraisal field, people write what closes the form fastest
- They list courses, not behaviours. "Attend a communication workshop" is an input. It says nothing about what the person will do differently
- Nobody owns the follow-through. The employee assumes HR will schedule things; the manager assumes the employee will drive it; HR assumes the manager is coaching. Everyone assumes, nothing happens
- They are disconnected from real work. Development that requires stepping away from the job loses to the job, every time
- There is no data underneath. Plans built on a manager's impressionistic feedback lack the credibility to motivate effort
Start with evidence, not opinion
An IDP built on objective data gets taken seriously. Before writing a single goal, ground the plan in:
- A strengths assessment such as CliftonStrengths, so the plan builds on talent rather than only patching gaps
- 270/360 feedback that shows how the leader is actually experienced by others
- A structured view of potential and readiness — our Vantage Profile gives leaders and their managers a shared, evidence-based picture to plan from
When a leader sees a pattern across eight raters, the conversation shifts from defensiveness to curiosity. That is the moment a real development goal becomes possible.
Write fewer, sharper goals
The best IDPs we see have two goals, sometimes three. Never five. Each goal should pass three tests:
- Behavioural: Describes something observable. "Run a monthly skip-level conversation and act on one theme each quarter" beats "improve connect with team"
- Anchored in real work: Uses the 70-20-10 logic honestly — the bulk of development should happen inside live projects, stretch responsibilities, and feedback loops, not classrooms
- Time-bound with a witness: Someone specific — manager, mentor, HRBP — knows the goal and the date
Build the operating rhythm
This is the part most organisations skip, and it is the part that matters most.
- Monthly check-in, fifteen minutes: The manager asks three questions — what did you try, what did you learn, what is next. Not a review; a nudge
- Quarterly evidence review: What has actually changed? What would the people around you say? This is where 270-degree pulse feedback earns its keep
- Annual reset: The IDP is rewritten, not rolled over. Goals that survived a year untouched were never real goals
In our experience designing manager capability programmes, the single highest-leverage move is training managers to run that monthly conversation well. A manager who can coach turns every IDP into a living document; a manager who cannot turns every template into shelf-ware.
Make it visible without making it punitive
Some organisations publish IDP completion dashboards and wonder why quality collapses. Measure instead:
- Percentage of IDPs with at least one on-the-job development action
- Percentage of leaders reporting a development conversation in the last 60 days
- Behaviour-change evidence at the year mark, sampled through mini-360s
These metrics reward substance over paperwork.
The honest summary
An IDP is a promise between a leader, their manager, and the organisation. Templates do not keep promises; rhythms and relationships do. If your IDP process produces documents but not development, the redesign should start with assessment data, shrink to two behavioural goals, and live inside a monthly conversation.
Our leadership development practice helps organisations rebuild IDP systems around exactly this architecture — and our work on manager-as-coach capability shows up in several of our case studies. If your next development planning cycle deserves better than a form, talk to us.
Frequently asked questions
How many goals should an individual development plan contain?
Two, occasionally three. Plans with five or more goals signal that no real prioritisation happened, and effort gets diluted across all of them. Each goal should be behavioural, anchored in live work, and known to a specific witness such as the manager.
What is the 70-20-10 model and should we follow it literally?
It is a rule of thumb suggesting development comes roughly 70% from challenging work, 20% from relationships and feedback, and 10% from formal learning. Treat the ratios as directional, not literal — the real lesson is that courses alone change very little.
Who is responsible for making an IDP happen — the employee, the manager, or HR?
The employee owns the effort, the manager owns the monthly conversation and access to stretch work, and HR owns the system and data that make both possible. IDPs fail when this three-way ownership is left implicit.
Leaders you can bet the company on.
Talk to Humane Insights about your next leadership hire or challenge.
Book a conversation