Every January, a 400-person company asks employees to complete an individual development plan. People fill in a template with 3 goals, a manager signs it, HR files it and the form is never opened again. In October, an engineer who wanted to learn architecture hears that the budget is gone, a finance analyst who wanted a stretch project has been assigned to month-end close, and both start answering recruiters’ messages, while the plan sits in a folder and nobody remembers what it said.
This guide explains why development plans fail in that way and what the plans that survive have in common. It covers the research on manager support and career conversations, a structure that ties plans to real work, how to choose development activities that build skill, the manager’s role and time budget, a 90-day sprint calendar, ways to adapt plans for different employees, measures that show whether plans work and mistakes to avoid. Evidence on plan effectiveness is thinner than the confidence of many vendors suggests, so figures are attributed and the guidance is practical rather than proven.
TL;DR
- Plans fail because nothing in the week-to-week work points back to them. LinkedIn’s 2025 Workplace Learning Report found that only 15% of employees said their manager helped them build a career plan in the past 6 months, and a plan that lives in a form instead of in 1:1 meetings, project assignments and calendars has no mechanism to survive the first busy quarter. Build the plan into the meetings and calendars people already use.
- Small, specific and time-boxed beats are exhaustive. A working plan has 1 to 3 goals, each linked to a project or role the employee can really get, with a named sponsor, a next action within 2 weeks and a 90-day review, so the plan becomes a sequence of short sprints instead of an annual aspiration that nobody can see. Review each goal at 90 days and then set the next first action.
- Measure behaviors, then outcomes, and fund the time. Count active plans, 1:1 discussions, completed stretch assignments and internal moves, protect development hours on the calendar and train managers for the conversation, because Gallup research links manager involvement in goal setting to engagement and shows that most employees don’t experience it. Ask managers to report each quarter’s development actions so senior leaders can see where support is missing across all of the teams.
Why Development Plans End Up in a Drawer
The most reliable finding in the research is that managers are the weak link. LinkedIn’s 2025 report says only 15% of employees reported that their manager helped them build a career plan in the past 6 months, a drop of 5 points from the year before, and it describes the intent as present and the structure as missing. The same report found that just 36% of organizations qualify as career development champions, that another 31% have programs with limited adoption and that half of organizations say managers lack the support they need.
Gallup’s work points the same way. It reports that employees whose manager involved them in setting goals were nearly 4 times more likely to be engaged, yet only about 30% experience that basic expectation, and that 47% of employees received feedback from their manager a few times or less in the past year. A summary of Gallup data also notes that 41% of employees named time as their top development obstacle and that 39% of chief human resources officers named direct-manager support as an organizational obstacle.
These findings suggest a pattern rather than a villain. Plans are usually completed once a year, in a separate system, with goals disconnected from the actual work, by managers who weren’t taught how to hold a career conversation and who face competing priorities. Nothing in the next 50 weeks reminds anyone of the plan, so it loses every contest for attention. The fixes that follow therefore concentrate on structure, time and routine instead of better templates.
7 Failure Patterns at a Glance
| Failure Pattern | What It Looks Like | Why It Happens | Fix |
| The annual form | Plan written in January, reviewed in December | Process designed around HR calendars | Quarterly sprints and 1:1 check-ins |
| Goals disconnected from work | Courses and certificates with no use on the job | Plan treated as a learning wish list | Link each goal to a project, role or stakeholder |
| Too many goals | 6 to 10 aspirations, none finished | Fear of leaving something out | Cap at 3 and sequence them |
| No manager skill | Conversation feels awkward and short | Managers weren’t trained | Provide scripts, practice and coaching |
| No time or budget | Plan approved, calendar full | Development isn’t scheduled like delivery | Protect hours and publish a small budget |
| No sponsor | Employee needs access the manager lacks | Plan owned by 1 person | Name a sponsor with influence over assignments |
| No visible follow-up | Nobody asks about progress | No metric, no rhythm | Add a standing agenda item and a 90-day review |
Most organizations will recognize several rows. The table is more useful as a diagnostic than a to-do list, so ask a sample of employees and managers which failures they’ve seen, and fix the 2 or 3 that appear most often. Trying to repair all 7 at once repeats the mistake of too many goals, while a focused fix on time, managers and follow-up usually works faster than a new template.
Principle 1: Tie the Plan to Real Work
Start With the Work the Employee Does or Wants to Do A plan that begins with a course catalog produces learning with no destination, while a plan that begins with work produces skills with immediate use. Ask what the employee will be doing in the next 6 to 12 months, which projects or roles they want and which skills those require. Then pick activities that put them near that work, such as shadowing, a smaller version of the project or a rotation, so every action has a practical payoff.
Use Business Priorities as the Source of Stretch Opportunities Managers hold a supply of development opportunities in the form of upcoming projects, presentations, vendor negotiations, incident reviews and customer visits. Map those to employees’ goals during planning, and record them in the plan as committed assignments with dates. LinkedIn’s report says career development champions are 88% more likely to use project-based learning, which suggests that work-based experiences are a practical lever instead of an extra. Keep that list current each quarter.
Link the Plan to Skills the Organization Needs Employees are more likely to get support when their goals connect to skills the business needs. Share a short list of priority skills for each function and have employees pick goals that sit inside or near them, while leaving room for personal interests that build adaptability. This keeps the plan from becoming either a purely personal wish list or a narrow corporate directive, and it gives managers a basis for approving time and money.
Write the Plan Where the Work Is Planned Keep the plan in the tool, document or meeting where work is already tracked, such as the 1:1 agenda, team planning board or project staffing process. A plan that lives in a separate human resources system is visible only during review season. A plan that appears in staffing decisions, sprint planning and 1:1 notes is visible every week, which is what keeps it alive when deadlines and priorities compete for attention.
Principle 2: Keep It Small, Specific and Time-Boxed
- Limit each plan to 1 to 3 goals. People who list a dozen intentions usually complete none, so ask which 1 or 2 goals would matter most over the next 12 months, sequence the rest for later and write the deferred items in a parking list so nothing is lost, which reduces anxiety about leaving things out while keeping attention on a few outcomes. Review the parking list at each 90-day check-in.
- State each goal as a visible outcome, not a topic. Learn data analysis is a topic, while build the weekly sales dashboard and present it to the regional director by June is an outcome, and the second form tells the employee, the manager and the sponsor what success looks like and when to review it, which makes follow-up natural. Ask the employee to describe what the finished result will look like in 1 sentence.
- Set a first action within 2 weeks. Plans stall when the first step is vague, so end the planning conversation with an action small enough to do soon, such as booking time with a mentor, drafting a project proposal or requesting access to a dataset, and put the date in the calendar before the meeting ends. Share the date with the manager so the first check-in can ask about it directly.
- Break the year into 90-day sprints. A 12-month plan feels distant, and a 90-day sprint feels real, so define what progress should look like at the end of each quarter, hold a short review and adjust, because work changes quickly and a plan that can’t change is the one that ends up in a drawer. Write down what changed between sprints, so the plan reflects the work the employee actually did.
- Name the sponsor and the support needed. Many development actions depend on someone other than the manager, such as a project lead, a department head or a mentor, so list the person, the request and the date it will be made, since a plan that depends on goodwill without a named ask rarely produces access. Follow up on each request at the next 1:1 meeting until it’s answered or declined with a reason.
What a Working Plan Contains
| Section | Content | Example | Owner |
| Direction | The role or contribution the employee wants in 12 to 24 months | Move from analyst to senior analyst with ownership of pricing models | Employee |
| Strengths and gaps | 2 or 3 strengths to build on and 1 to 3 skills to develop | Strong in SQL, needs stakeholder presentation skills | Employee and manager |
| Goals | 1 to 3 outcomes with dates | Present the pricing review to leadership by June | Employee |
| Actions | Mix of experience, relationships and learning | Co-lead a pricing project, monthly sessions with a mentor, 1 course on storytelling | Employee |
| Support | Sponsor, budget, time and access | Director sponsor, 4 hours a month protected, course budget | Manager |
| Measures | Evidence of progress | Delivered presentation, feedback from 3 stakeholders | Employee and manager |
| Review dates | 90-day checkpoints | Quarterly review in 1:1 | Manager |
A plan this size fits on 1 page, which is a feature. Plans that run to 6 pages with competency ratings are completed once and rarely reread. The most important rows are goals, actions and support, since they turn intent into commitments by named people on specific dates. If the template has more fields than a manager can discuss in 45 minutes, remove fields until it fits, and keep extra detail in optional guidance.
The Conversation That Creates the Plan
The planning conversation matters more than the document. It works best when the employee prepares in advance by reflecting on what energizes them, what they want to learn and where they see themselves in 1 to 2 years, and when the manager prepares by thinking about the employee’s strengths, upcoming work and opportunities the team can offer. Sending a short preparation sheet a week ahead lets both sides arrive with ideas, which makes a 45-minute conversation productive.
During the meeting, the manager’s job is to ask and listen before suggesting. Useful questions include what part of your work gives you the most energy, which skills would open the next opportunity you want, what would make you consider leaving and what would make you stay longer. Gallup data summarized in 1 source says that among leavers who had a manager conversation, only 29% discussed their future career with the organization, so asking directly about the future is itself a retention practice.
Close the conversation with specifics. Agree on the 1 to 3 goals, the first action and its date, who will sponsor each goal, what support the manager will provide and when the next check-in will happen. The manager should write a short summary within 24 hours and send it to the employee for correction, which turns spoken intentions into a shared record. This summary becomes the plan, and it takes less time than completing a form in a separate system.
Choosing Development Activities That Build Skill
Experience Carries the Most Weight The widely quoted 70-20-10 model says about 70% of development comes from on-the-job experience, 20% from relationships and 10% from formal learning. The numbers are a rule of thumb from leadership research rather than a precise measurement, so treat them as a prompt to favor experience, not as a target. Practical experiences include stretch assignments, leading a small project, covering for a manager, presenting to senior leaders and working on a cross-functional team.
Relationships Provide Feedback and Access Mentors, sponsors, peer groups and coaches give employees feedback, perspective and introductions that courses can’t provide. Structure these relationships by naming a purpose and a cadence, such as a monthly 45-minute session for 6 months, and by giving the employee a question to bring each time. For employees who want to move into new areas, a sponsor with influence over staffing decisions is more valuable than a friendly mentor with no power to open doors.
Formal Learning Works When It Supports a Real Need Courses, certifications and workshops help when they fill a gap that blocks a goal, and they work best when the employee will apply the learning within weeks. Pair each course with a practice assignment, a short presentation to the team or a project that uses the new skill. Ask the employee to share what they learned with colleagues, because teaching reinforces learning and spreads value beyond 1 person. Keep the practice task small.
Short Gigs and Rotations Create Mobility Short assignments in other teams, such as a 4 to 8 week project or a 10% time allocation, let employees test new areas and build relationships without a permanent move. LinkedIn’s report says career development champions are more likely to use gigs and to prioritize internal mobility. To make this work, publish opportunities in 1 place, set rules for backfill and time commitment, and let managers know that releasing people for development is expected and recognized.
The Manager’s Role and the Time It Takes
- The manager is the plan’s operating system. Employees rarely reread a document, though they do respond to a manager who asks about progress, adjusts assignments and removes obstacles, so the manager’s job is to keep the plan visible in 1:1 meetings, projects and staffing decisions, and to notice when work has changed and the plan needs updating. When priorities shift, the manager is the person who updates the plan and tells the employee why.
- A realistic time budget is about 5 hours per employee per year. As an illustration, a 45-minute development conversation each quarter totals 180 minutes, and a 10-minute plan check in each monthly 1:1 adds 120 minutes, which makes 300 minutes or 5 hours per employee, so a manager with 8 direct reports spends about 40 hours a year, roughly 2% of a 2,000-hour work year. Adjust the cadence to your own team.
- Managers need skills and scripts, not only expectations. LinkedIn’s data shows manager support declining and Gallup reports that coaching-trained managers see higher engagement, so provide short training, question guides and practice sessions with feedback, because asking people to hold career conversations without preparing them produces awkward meetings and little follow-through. Short practice sessions with role-play and feedback help managers get comfortable with the first conversation before they hold it for real.
- Give managers a menu of opportunities they can offer. Many managers say they don’t know what to offer, so compile a list of stretch projects, rotations, shadowing options, presentation slots and stakeholder introductions available in the function, and update it quarterly, which turns a vague intention to develop people into a set of concrete choices. Share the list with employees as well, so they can ask for the specific experiences they want.
- Hold managers accountable in a way they can meet. Measure whether each manager has held development conversations and updated plans, review the results in leadership meetings and recognize managers who build strong bench strength, though avoid turning the process into a compliance exercise, since rushed forms completed to satisfy a metric produce exactly the drawer problem the program is meant to solve. Ask managers what gets in the way, then remove those obstacles where you can.
A 90-Day IDP Sprint Calendar
| Timing | Activity | Participants | Output |
| Week 0 | Preparation: employee reflection and manager input | Employee and manager | Short preparation notes on both sides |
| Week 1 | Planning conversation and 1-page plan | Employee and manager | 1 to 3 goals, first action, sponsor and review date |
| Week 2 | First action completed and sponsor request made | Employee, sponsor | Booked mentor session or project proposal |
| Weeks 3 to 6 | Work on the goal through a project or assignment | Employee and team | Visible progress on the work product |
| Week 6 | Mid-sprint check in the regular 1:1 | Employee and manager | Adjustment or additional support |
| Weeks 7 to 11 | Continue the assignment, gather feedback | Employee and stakeholders | Feedback from at least 2 people |
| Week 12 | 90-day review and next sprint plan | Employee and manager | Updated goals, lessons and next first action |
This calendar fits a single goal and repeats 4 times a year, and it should be adapted to the rhythm of each function. A sales team might align sprints with quarters and a project team might align them with release cycles. What matters is the repetition, because each review is a chance to refresh the plan and show the employee that it affects real decisions. A plan that appears only at annual review has 1 chance a year to matter, while a sprint plan has 4.
Making Time and Budget Real
Development fails when it competes with delivery work and loses, so make it explicit. Set a default allowance, such as 2 to 4 hours a month protected on the calendar, and tell managers that using it isn’t optional. Treat the time like a client meeting, with a booked slot and an agenda, because unscheduled development time disappears in the first busy week. Gallup’s summary notes that 41% of employees named time as their biggest obstacle, which makes calendar protection a direct response to the stated barrier.
Budget needs the same clarity. Publish a simple policy that lists what’s covered, such as courses, certifications, conferences, books and coaching, what approval is needed and a default amount per person. A small, predictable budget that employees can use without a long approval chain is more effective than a large budget that is hard to access. Where money is tight, favor low-cost experience-based activities such as shadowing, rotations and mentoring, which often produce more growth per dollar than formal courses.
Capacity planning is the part many organizations skip. If a manager releases an employee for a 6-week rotation or a 4-hour weekly project, someone has to cover the work. Build backfill rules into staffing, and let managers adjust deadlines or priorities when they release people for development. Otherwise the plan creates a conflict between the manager’s delivery targets and the employee’s growth, and the manager will rationally choose delivery, which is what happens in most organizations today.
Adapting Plans for Different Employees
Early-Career Employees Need Structure and Exposure Employees in their first 2 years benefit from clear skill ladders, regular feedback and exposure to different parts of the business. Plans should cover technical fundamentals, communication skills and relationships, and they should include a buddy or mentor. Short rotations and shadowing help early-career staff discover where they want to grow, and frequent check-ins, perhaps monthly, help catch confusion before it turns into disengagement or an early exit. Keep the cadence short.
Specialists and Individual Contributors Need Paths Beyond Management Many strong specialists don’t want to manage people, and plans that assume promotion means management lose them. Offer growth through deeper expertise, technical leadership, mentoring, cross-team influence and bigger scope. Define what progress looks like on an expert track, and show examples of senior individual contributors who have grown without managing, so employees see that the organization values their path and can plan goals around it. Publish the expert-track criteria in plain language.
Aspiring Managers Need Practice Before the Title Employees who want to lead should practice leadership tasks before a promotion, such as running a project, mentoring a new hire, facilitating meetings or leading a small initiative. Pair them with a sponsor who can create these opportunities and give honest feedback. A management training course can help, but supervised practice with real stakes teaches more, and it gives the organization evidence about readiness before it makes a high-stakes appointment.
Experienced and Senior Staff Need Fresh Challenges Long-tenured employees may not want promotion, but they still need growth to stay engaged. Plans might include new domains, cross-functional leadership, mentoring roles, external learning or sabbatical-style projects. Ask what would make the next 2 years feel meaningful, and design experiences around that. Skipping development conversations with experienced staff because they seem settled is a common mistake that leads to disengagement and quiet exits. Ask them to mentor others as part of their plan.
Measuring Whether Plans Work
| Metric | What It Tells You | Caution |
| Share of employees with an active plan reviewed in the last 90 days | Whether the process is alive | A reviewed plan isn’t the same as a useful plan |
| Development discussions logged in 1:1s | Manager behavior | Count quality through surveys, not only logs |
| Completed stretch assignments and rotations | Real development activity | Track by function to find gaps |
| Employee survey items on growth and manager support | Employee experience | Use consistent wording and watch trends |
| Internal mobility and promotion rates | Career movement | Many factors affect mobility |
| Retention of employees with and without active plans | Possible link to retention | Correlation may reflect who engages with plans |
| Skills added against priority skill list | Capability growth | Needs credible assessment, not self-report alone |
Measure behaviors first, because they’re the leading indicators that managers can influence. Outcomes such as retention and promotion matter, though they respond slowly and have many causes, so avoid claiming that plans alone caused any change. Gallup reports that organizations investing strategically in development reported 11% greater profitability in earlier research, and LinkedIn associates career development champions with stronger results, but both are correlational. Use your own data over time, with consistent definitions, to see whether the program is shifting what people do and how they feel.
Tools, Templates and AI Support
- Choose the simplest tool that fits the workflow. A shared document, a section in the 1:1 template or a module in the human resources system can all work, and the best choice is the 1 that managers and employees already open every week, since a sophisticated platform that people visit twice a year recreates the drawer in digital form. Ask a few managers to test the tool before a wider launch.
- Integrate with skills data and learning content where possible. LinkedIn reports that champions use internal data to track skill gaps, and tools that connect plan goals to skills profiles, learning libraries and open gigs can reduce friction, though integration should follow a working process instead of replacing one, because software doesn’t create manager conversations. Start with the data you already have and add integrations only where managers ask for them in practice.
- Use AI as a preparation aid, not as the planner. AI tools can suggest goals, draft summaries, recommend learning resources and match skills to opportunities, and LinkedIn says 71% of learning professionals are experimenting with or integrating AI, but a generic suggestion can’t know the employee’s context, so use it to draft and prepare and keep the human conversation central. Review every AI draft with the employee before it becomes part of the plan.
- Protect privacy and trust. Development plans contain career intentions that employees may not want shared widely, so define who can see them, how long they’re kept and how they’re used in decisions, and state clearly that plan content, such as interest in other teams, won’t be used against the employee, since fear of exposure leads people to write safe, empty goals. Publish the policy in plain language where employees can find it.
Common Mistakes
Treating the plan as a form to complete is the most common mistake. When the goal is 100% completed by a deadline, people produce plans quickly and carelessly, and the organization reports success with little changes. Measure activity that follows the form, such as 1:1 discussions and stretch assignments, and treat completion as the first step. A plan used every month is worth far more than a perfect plan nobody reads.
Making the plan solely the employee’s responsibility is the second mistake. Employee ownership is valuable, though many development actions need a manager’s time, a sponsor’s influence or the organization’s money, and employees can’t supply those alone. A plan that lists what the manager and sponsor will do, with dates, creates mutual accountability. A plan that lists only what the employee will do, often on their own time, signals that the organization isn’t investing.
Launching the program without preparing managers is the third mistake. Organizations announce a new template and expect managers to improvise, which produces uneven results and cynicism. Give managers training, scripts, a menu of opportunities and time on the calendar, and ask them for feedback on what makes the process hard. A modest program with prepared managers outperforms an ambitious program that depends on every manager discovering how to hold the conversation alone.
FAQs
What is an individual development plan?
An individual development plan is a short, shared document that records an employee’s direction, a few development goals, the actions that will build the needed skills, the support from the manager and sponsors, and the dates for review. The most effective plans are 1 page, focus on 1 to 3 goals, link to real work and are revisited in regular 1:1 meetings. Keep it in a place both people see.
Why do most development plans fail?
They live in a form instead of in the work. LinkedIn’s 2025 report found that only 15% of employees said their manager helped them build a career plan in the past 6 months, and Gallup found that most employees don’t experience involvement in goal setting. Plans fail when there’s no manager skill, no time, no sponsor and no routine that brings the plan back into view.
How many goals should a plan have?
Between 1 and 3. Fewer goals allow focus and follow-through, and a parking list can hold ideas for later. State each goal as an outcome with a date, such as build and present a dashboard to a director by June, so the employee, manager and sponsor can recognize success and review progress at 90 days. Keep the parking list visible so deferred ideas aren’t forgotten, and review it at each quarterly check-in.
How often should we review development plans?
At least quarterly, with a short check in monthly 1:1 meetings. A 90-day sprint structure keeps goals current and gives each review a clear purpose: look at what changed, learn from feedback, adjust the goal and set the next first action. Annual-only reviews give the plan 1 chance a year to affect decisions. Put the review dates on the calendar when the plan is written, since unscheduled reviews are the first to slip.
How much time do development conversations take?
As an illustration, a 45-minute conversation each quarter plus a 10-minute check in each monthly 1:1 is 5 hours per employee per year, or about 40 hours for a manager with 8 direct reports. That’s roughly 2% of a 2,000-hour year. Adjust the numbers to your cadence, and treat the time as a core management responsibility. Compare the estimate with the time your managers spend today and adjust where the gap is large.
Does the 70-20-10 model really work?
It’s a useful rule of thumb that emphasizes learning from experience, relationships and formal learning in that order, but the exact ratio is only a rough guide. Use it as a reminder to favor on-the-job experience, such as stretch assignments and projects, and to support experience with feedback from mentors and targeted courses, instead of treating the percentages as a budget formula. Test what works in your own teams by asking employees which experiences taught them most.
How do we measure whether development plans improve retention?
Track behaviors first, such as active plans and development discussions, then outcomes such as internal mobility and retention. Compare people with and without active plans, though bear in mind that engaged employees may be the ones who complete plans, so the result is correlation. Use consistent definitions, survey employees about growth and manager support, and look at trends over several quarters. Share the findings with leaders as hypotheses to test, with the caveats stated plainly.
What should we do about employees who don’t want promotion? Treat growth as broader than promotion. Offer deeper expertise, technical leadership, mentoring, cross-team projects, new domains or bigger scope, and ask what would make the next 2 years meaningful. Show examples of senior individual contributors who have grown without managing people. Employees who feel stretched and valued tend to stay engaged even when a title change isn’t their goal. Revisit the plan each quarter.
