Individual Development Plan: A Guide for Small Business

The first time I tried to write an individual development plan for a direct report, I sat alone in front of a Google Doc and produced four pages of goals organized by competency framework, complete with SMART criteria and quarterly milestones. I sent it to the employee, they nodded politely, and three months later I realized none of the goals had moved. The plan was technically perfect and practically useless because I had written it alone, which meant nothing in it was actually theirs.

Most articles about individual development plans (IDPs) treat them as a documentation exercise: here is the template, here are the components, fill in the blanks. The result is plans that satisfy HR but do not produce development, because the document is the smallest part of an IDP. The conversations that produce the goals, the resources committed to support them, and the check-in cadence that maintains them are nearly all of what makes one work.

This guide is built around those three things, and it is written for small business owners and operators who do not have a Chief People Officer building development frameworks, but who still need their team members to grow. I built FirstHR for this audience because most performance and development content assumes a level of HR sophistication small businesses neither have nor need.

You will get the six components every IDP needs, a six-step process for creating one, five examples from roles common at small and midsize businesses (SMBs), and an honest take on the check-in cadence that separates IDPs that work from IDPs that get filed and forgotten.

What an Individual Development Plan Actually Is

Put simply, an IDP answers one question: "what does this employee need to do over the next 6-12 months to get closer to where they want to be in their career?" The answer combines an honest assessment of where they are now, a clear sense of where they want to go, and a specific set of activities that close the gap between the two.

Three things are true about every IDP that actually works. First, the employee owns it: they drive the goals, commit to the activities, and push for resources. Manager-driven IDPs become homework assignments and produce no follow-through.

Second, the manager commits real resources: time, budget, mentor access, and stretch project assignments. Most goals require the manager to do something, so without resources the IDP becomes the employee's problem alone. Third, the cadence is consistent: check-ins every 4-6 weeks, a mid-cycle review at the halfway point, and an end-of-cycle review when the plan completes. IDPs without check-ins die within months.

Why Most IDPs Fail

Most IDPs fail because at least one of three things is missing: employee ownership of the plan, resources committed by the manager, or a check-in calendar. Each missing piece reduces the probability of actual development. Missing all three is the norm, not the exception, which is why most IDPs in most organizations produce nothing.

The table below lists those three failure modes and five more. The patterns are consistent across companies of all sizes, and recognizing them is the first step toward avoiding them.

The pattern across these failures is treating the IDP as a document rather than as a practice. A document gets written once and filed. A practice gets revisited regularly, adjusted as reality changes, and held accountable through consistent attention. The fix for most IDP failures is not a better template; it is more honest treatment of what makes IDPs actually work.

Why SMB IDPs Need to Be Different

Most IDP frameworks are written for mid-market and enterprise companies with formal competency models, calibrated rating scales, and HR business partners coaching managers through the process. None of that applies at small business scale. The owner-operator running IDPs for a small team has different constraints and different advantages, and needs a different approach.

Three implications follow for SMB IDPs. First, the formality should match the scale. A small company does not need a 4-page templated form; a one-page shared doc captures everything important. Use the lightest format that works for your team.

Second, the manager is much closer to the employee than at enterprise scale. The founder or COO running an IDP knows the employee's actual work, has direct context on their performance, and can spot stretch opportunities personally. This is a significant advantage that most enterprise IDPs do not have. Use it: write goals based on real observation, not on competency framework abstractions.

Third, resource constraints are tighter. A small business cannot commit unlimited training budget or hire a mentor for every goal. The constraint forces creativity: stretch projects within existing work, mentor relationships with senior team members or external advisors, free or low-cost online courses, and internal teaching opportunities.

That list is less improvised than it looks. The federal Office of Personnel Management (OPM) names rotational assignments, shadowing assignments, on-the-job training, and self-study programs alongside formal classroom and web-based training as development activities, which covers most of what a small team can afford.

The 6 Components of an Effective IDP

Every effective IDP contains six components that work together. Missing any one weakens the plan; including all six in coherent form produces a plan that drives development.

The order matters. Career direction (component 2) shapes goal selection (component 3). Goals shape activities (component 4). Activities require timelines (component 5) and success measures (component 6) to be meaningful. Skipping component 2 (career direction) is the most common drafting error: without it, goals are arbitrary and may pull the employee in a direction they do not want to go.

The single most useful test for any IDP: would the employee, reading it six months from now, know exactly what they should be working on this week? If yes, the plan is concrete enough to drive behavior. If they would have to translate vague goals into specific actions, the plan needs more specificity before it goes into effect.

A 6-Step Process for Creating an IDP

Creating an IDP takes six steps and 2-3 hours of total time over 1-2 weeks, including the career conversation, drafting, and refinement. Skipping steps produces lower-quality plans, however good the template is.

Two failure modes are worth guarding against during creation. First, do not skip Step 1 (the career conversation). A manager who writes the plan alone skips the conversation that creates ownership, and without ownership, no plan moves.

Second, do not treat Step 5 (timeline and check-in cadence) as done until the check-ins are actually scheduled. A check-in plan that is not on the calendar is a check-in plan that does not exist. Schedule them immediately, in both calendars, before the IDP is considered complete.

The Career Conversation That Precedes the IDP

The career conversation is the single most important part of the IDP process and the most commonly skipped. Without it, the IDP becomes a document the manager wrote about the employee. With it, the IDP becomes a plan the employee created with manager support. That difference is what separates a plan that moves from one that gets filed.

The conversation runs 45-60 minutes and covers five areas. First, where does the employee want to be in 1-3 years? Specific role, specific scope, specific level of responsibility. "I want to grow" is not an answer; "I want to be leading a team of 3-5 people on customer-facing projects" is.

Second, what energizes them in their current work? The activities they enjoy reveal what to lean into. Third, what drains them? The activities they avoid reveal what to either build skills around or design out of their role over time. Fourth, what skills, experiences, or relationships do they need to acquire to move toward where they want to be? Fifth, what support do they need from you?

Regular manager time is what makes that conversation land. According to Gallup, employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not, and the career conversation is the most valuable version of that meeting.

The conversation should produce a 1-page summary of conclusions: career direction, energizers, drainers, skill gaps, and what the employee is asking the manager for.

Write the summary within a day, while the phrasing is still theirs rather than yours. This is the page the goals get drafted from, so if it is vague here, no amount of care at the goal-writing stage recovers it.

Writing Goals That Actually Drive Development

The goals are the engine of the IDP. Vague goals produce vague results; specific goals produce specific behavior change. Many plans go wrong at the goal-writing stage, where good intentions get expressed as fuzzy aspirations that nobody can act on.

The pattern: vague goals describe a wish; specific goals describe a path. The specific goal includes the activity (lead, develop, deliver), the scope (3 projects, 4 presentations), and the success signal (feedback collected, knowledge demonstrated). The investment to make a goal specific is 2-3 minutes per goal; the payoff is a goal that moves over the IDP cycle.

Types of Development Goals

Most IDPs have a mix of goal types, not just skill-building. Below are the seven most useful categories for SMB IDPs, with examples calibrated for a small business.

The mix matters. An IDP with 5 skill-development goals produces a person with new skills but no new experiences. An IDP with 5 stretch experiences produces a person with new experiences but no deeper skills. The strongest IDPs typically include 1-2 skill-development goals, 1-2 stretch experiences, and 1 visibility or relationship goal. The combination produces both depth and breadth.

5 IDP Examples for SMB Roles

Below are 5 IDP examples drawn from common SMB roles. Each shows the current state, a career direction, and four development goals, each with an activity and a timeline. The examples are intentionally short to fit the format; a full IDP would also name the resources and success measures for each goal.

Three patterns in these examples are worth noticing. First, no goal stops at "become more strategic" or "develop leadership." Even where a goal's label is broad, its activity names the specific work, scope, and timing. Second, most goals span 4-9 months and overlap, so they run side by side rather than one after another.

Third, goals often connect to real business projects rather than abstract skill-building. The IDP and the work calendar are not separate; the IDP is partly about choosing which work assignments will produce growth.

Activities and Resources for Each Goal

Goals without activities are wishes. Activities are the concrete work that closes the gap between current state and the goal. Each goal in the IDP should have 1-2 specific activities, with the resources required explicitly named.

The single most important rule: every activity needs a resource commitment from the manager, not just the employee. That means time off for courses, budget for training, time on stretch projects, mentor introductions, and the opportunity to present to leadership.

Without manager-side resources, the activity becomes the employee's problem alone, and most goals stall. In my experience the resources line is the honest signal: a manager who will not name a number there has not really agreed to the goal.

The Check-In Cadence That Makes IDPs Work

If the goals are the engine, the check-in cadence is the fuel. Without consistent check-ins, the best IDP becomes a forgotten document by month two. With consistent check-ins, even average IDPs produce real development. The cadence matters more than any other practice in the IDP process.

The pattern: short check-ins integrated with existing 1:1 meetings, plus longer milestone reviews at the halfway point and end of the cycle. Total time investment: about 3-4.5 hours per direct report per year. The investment is modest, but the cadence is what produces the development. Skipping any of these check-ins is the single largest risk to the IDP working.

Three rules for productive check-ins. First, always start with progress: what has the employee done since the last check-in? Second, surface blockers: what resources or support do they need to keep moving? Third, adjust if reality has changed: a new business priority, a shifted role, a goal that turned out to be wrong. The check-in is short but real; treat it as live planning, not status reporting.

Whose agenda the check-in follows matters too. Writing in Harvard Business Review (2022), Steven Rogelberg found that one-on-ones work best when the meeting is dominated by topics that matter to the direct report rather than what is top of mind for the manager. The same holds for an IDP check-in.

IDP vs Other Development and Performance Tools

IDPs are often confused with other development and performance tools, and the confusion produces both bad IDPs and bad versions of the other tools. Each tool in the table below has a distinct purpose, and they work together rather than substituting for each other.

Two of these distinctions matter most. First, an IDP and a PIP are completely different tools. An IDP is forward-looking development for someone performing well; a PIP is corrective documentation for someone underperforming. Mixing them produces both bad development planning and weak corrective documentation. People who need a PIP are not yet ready for an IDP; people on an IDP should not be receiving formal performance corrections at the same time.

Second, the IDP is loosely connected to the performance review but should not be tightly tied to it. Performance reviews are backward-looking; IDPs are forward-looking. Insights from the review can inform the next IDP cycle, but IDP progress should not directly affect performance ratings, because that turns development into compliance and reduces honest goal-setting.

Professional Development Plan, Performance Development Plan, and IDP

A professional development plan (PDP) is the same document as an individual development plan under a different name. Same six components, same cycle length, same test for whether a goal is real. If the template you found is labeled PDP, you can use it unchanged, and the six-step process above applies to creating one.

The label mostly tells you which sector the document came from. Professional development plan is the common term in education, healthcare, and licensed trades, where continuing education credits are part of the job. Individual development plan is what federal agencies and most US corporate HR use. Neither name implies a different structure, and PDP goals are written to the same standard: activity, scope, success signal.

Performance development plan is the one that causes real trouble, because two very different documents share the name. Some companies use it for development. Others use it as a gentler label for a performance improvement plan. Establish which one you are holding before you sign it or hand it to somebody, because the consequences are not remotely the same.

Common Mistakes in Writing and Running IDPs

The mistakes below appear consistently across small businesses running IDPs for the first time. All are avoidable once you understand the underlying patterns.

What these mistakes share is treating the IDP as a deliverable rather than a living planning practice. A deliverable gets produced once and filed away; a practice gets revisited, adjusted, resourced, and held accountable.

Career development is where these mistakes show up. According to SHRM, 72% of workers call career advancement opportunities very or extremely important, while only 43% are very or extremely satisfied with what their employer offers. An IDP is the most concrete tool for closing that career development gap, but only when it is run as a practice.

IDPs for Managers and Senior Employees

Managers and senior individual contributors often have IDPs that look different from those of junior employees. The structure is identical, but the goal types shift toward leadership, scope expansion, and external impact rather than skill-building.

Skipping development for the people who manage others is expensive. According to a 2023 survey of 2,066 employees reported by SHRM, 34% of workers who had a negative experience with a poor manager wanted to leave the organization, and 41% said they were stressed or anxious about reporting to work. A manager IDP is not a perk; it is the cheapest retention insurance available.

Two principles shape a manager's IDP. First, the goals should disproportionately involve developing other people, not just developing the manager. A manager whose IDP is entirely about their own skills is missing the point of being a manager.

Second, the manager should have their own IDP run by their manager (the founder, COO, or whoever is one level up). Skipping IDPs for senior people is one of the most common failures in SMB development practice; senior people often need development as much as junior ones, just in different areas.

A Worked Leadership IDP Example

Here is what that looks like written down, for a first-time team lead about a year into the job. Three of the four goals point at the people around them rather than at their own skill set, which is the main way a leadership IDP differs from the five examples above.

Notice what is missing: no course, no certification, no reading list. Almost everything a new manager needs to learn is learned by doing the manager job slightly ahead of where they are comfortable, with someone debriefing them afterward. Training has its place, but it is not the engine here.

IDPs for Remote and Distributed Teams

Remote IDPs work, but they require some adjustments to the standard process. The structure is identical to in-person IDPs; the execution requires more intentional planning around mentorship, visibility, and on-the-job stretch experiences that in-person environments produce naturally.

Remote work magnifies a feedback gap that is already wide. According to Gallup, only 22% of employees overall strongly agree they received meaningful feedback in the past week, and the fix Gallup recommends is one meaningful conversation a week. On a distributed team the IDP check-in is a good candidate for that conversation.

The single largest risk for remote IDPs: the in-person things that just happen (mentor relationships, visibility, exposure to leadership) need to be created intentionally in remote environments. Without explicit goals around these areas, remote employees can complete every formal IDP goal and still feel disconnected from career growth opportunities.

Tools and Templates for IDPs

The tooling for IDPs at SMB scale should be lightweight. Most teams over-engineer the format and under-engineer the practice. A simple, accessible format used consistently produces better results than a sophisticated format used inconsistently.

For most SMBs, a shared document the employee can open, saved in a shared folder, plus calendar holds for the check-ins, is enough. The tooling does not produce development; the practice does. I have seen better plans run out of a two-column doc than out of software nobody opens.

A One-Page Individual Development Plan Template

Copy this into whatever document your team already uses. The six components sit in the order they get filled in, and there is nothing in it that exists only to look thorough. One page is the target; if it runs to three, the goals are carrying too much explanation.

How FirstHR Fits

FirstHR handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. The IDP template, goal tracking, and career pathing run in the tools you pair it with.

Your IDPs will live in one of those tools: a shared doc, an internal wiki, or eventually dedicated performance management software once you have grown into needing it. None of those choices matters as much as whether the check-ins actually happen.

That said, IDPs work better when the underlying people operations are working. A team running IDPs on top of broken onboarding will spend most of the IDP cycle explaining basic role expectations rather than developing existing employees. A team running IDPs on top of consistent onboarding, structured 1:1s, and clear performance reviews will produce IDPs that drive development.

FirstHR exists to handle the operational HR foundation at flat, predictable pricing, so that owners and operators can focus on the higher-impact work of running good IDPs and committing to the check-ins that make them work.

Frequently Asked Questions