Individual Development Plan

An employee wants to lead more complex customer projects, and their manager says they should develop leadership but gives no route to practise it, so an IDP can turn that vague advice into specific work and feedback. Start with the person's interests and current role, since a plan copied from someone else may target skills they do not need or want, and ask what work they hope to do.

The US Office of Personnel Management's development-planning guidance describes individual plans that identify goals and actions, though its federal context does not require every private employer to use the same template, and SHRM provides a template as one way to organise goals, activities and follow-up, but the value lies in the conversation and opportunities, not in filling boxes. Choose a few goals, because one or two meaningful capabilities can be easier to work on than a long list of generic traits, and define the difference between current and target behaviour.

Make actions concrete, since a project assignment, shadowing, course or mentor conversation can each help, and state what the employee will do and what support the manager will provide. Include practice, because attending a course does not prove a new skill, so give a chance to apply it to real work with feedback.

Set evidence: if the goal is leading a meeting, the evidence may be a planned agenda, facilitation and participant feedback, and no exact score captures all growth. Name a review date, since a plan created at an annual appraisal and never revisited is unlikely to guide work, and check-ins can adapt to the project cycle.

An illustrative action completion rate is planned development actions completed divided by actions due, so if six of eight due actions are completed, that is 75%, though it does not prove learning or readiness for promotion. Separate development from performance correction, because an IDP can include a skill gap but a formal performance process may have different rules and consequences, and discipline should not be disguised as a friendly growth plan.

Clarify resources, since training fees, time away from work and mentor access need approval and a goal with no capacity can frustrate the employee. Use role requirements: a career path or competency framework may show what the next role needs, so an IDP selects practical steps rather than promising the role, and a target month for practising a skill is a planning aid, not a promise of promotion by that date.

Keep shared ownership, as the employee brings interests and effort while the manager provides feedback and opportunities, and neither side can control every vacancy or business change. Review barriers, so if a planned project is cancelled, the action should change instead of marking the employee as failed, and the plan should allow revision by recording why an action changed and agreeing the next step.

Give feedback using examples, since general praise or criticism is difficult to act on, so state what was observed and what to try next. Protect private context, since a development goal may relate to confidence or a personal constraint, so share the plan only with those who need it under company policy, and avoid narrow stereotypes by not assuming every strong specialist should become a people manager; ask about technical, lateral and leadership routes.

Connect work and learning so a goal helps the person and the organisation where possible, with purely mandatory compliance training belonging in another plan, check fairness because some workers have easier access to stretch projects by sitting near leaders, and make progress visible with a short note after each review that need not be a lengthy report. Do not overmeasure, since a simple plan that leads to meaningful practice is better than a polished scorecard nobody uses; for owners, an IDP is a small agreement about learning work, support and review that turns career conversations into action while staying honest about what the company can offer.