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 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. The honest truth is that 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 90% of what makes IDPs work. The document is just the place those things get written down.

This guide is different. It is written for small business owners and operators running 5-50 person companies who do not have a Chief People Officer building development frameworks, but who still need their team members to grow. You will get the six components every IDP needs, a six-step process for creating one, five real examples from common SMB roles, and an honest take on the check-in cadence that separates IDPs that work from IDPs that get filed and forgotten. I built FirstHR for this audience because most performance and development content assumes a level of HR sophistication small businesses neither have nor need.

What an Individual Development Plan Actually Is

The simple working description: an IDP is the answer to the 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 comes from three things together: 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, they commit to the activities, they push for resources. Manager-driven IDPs become homework assignments and produce no follow-through. Second, the manager commits real resources. Time, budget, mentor access, stretch project assignments. Without resources, the IDP becomes the employee's problem alone, and most goals require the manager to actually do something. Third, the cadence is consistent. Check-ins every 4-6 weeks, mid-cycle review at the halfway point, end-of-cycle review when the plan completes. IDPs without check-ins die within months.

Most IDP failures happen because at least one of those three things is missing. The plan was written by the manager, or no resources were committed, or the check-in calendar was never set up. 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.

Why Most IDPs Fail

Before describing how to do IDPs well, it helps to be honest about why they usually do not work. The patterns are consistent across companies of all sizes, and recognizing them is the first step toward avoiding them.

The pattern across these failures: treating 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 their 12-person team has different constraints, different advantages, and needs a different approach.

Three implications for SMB IDPs. First, the formality should match the scale. A 12-person company does not need a 4-page templated form; a one-page shared doc captures everything important. The format does not produce development; the practice does. 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, internal teaching opportunities. OPM's career development framework covers the broader principles of structured development at the federal level, but the SMB-specific application is finding development opportunities that fit small business resource constraints.

The 6 Components of an Effective IDP

Every effective IDP contains six components, working together. Missing any one weakens the plan; including all six in coherent form produces a plan that actually 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 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 interpret vague goals into specific actions, the plan is not concrete enough yet and needs more specificity before it goes into effect.

A 6-Step Process for Creating an IDP

The process below produces IDPs that actually drive development. The total time investment is 2-3 hours over 1-2 weeks, including the career conversation, drafting, and refinement. Skipping steps produces lower-quality plans, regardless of how good the template is.

Two failure modes to avoid during creation. First, do not skip Step 1 (the career conversation). Most IDPs fail because the manager writes the plan alone and skips the conversation that creates ownership. Without ownership, no plan moves. Second, do not commit to Step 5 (timeline and check-in cadence) without actually scheduling the check-ins. 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. The difference produces 80% of the variance in IDP outcomes.

The conversation runs 45-60 minutes and covers four 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?

The conversation should produce a 1-page summary of conclusions: career direction, energizers, drainers, skill gaps, and asks from the manager. This summary becomes the input to drafting the IDP. Gallup research on managers consistently finds that the manager-employee relationship is the strongest predictor of engagement; the career conversation is one of the highest-leverage applications of that relationship.

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. Most IDP failures happen 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 actually moves over the IDP cycle.

For broader practice on writing measurable performance goals, the OKR guide covers a goal-setting framework that complements IDP goal-writing, especially when the development goals connect to team-level objectives.

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 small business context.

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 Real IDP Examples for SMB Roles

Below are 5 IDP examples drawn from common SMB roles. Each shows current state, career direction, and 3-4 development goals. The examples are intentionally short to fit the format; real IDPs would include activities, timelines, and resources for each goal.

Three patterns across these examples worth noticing. First, none of the goals say "become more strategic" or "develop leadership." Every goal includes the specific activity, scope, and timing. Second, most goals span 4-9 months, which is the typical range for development goals at this scope. 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. Time off for courses, budget for training, time on stretch projects, mentor introductions, opportunity to present to leadership. Without manager-side resources, the activity becomes the employee's problem alone, and most goals stall. SHRM's research on organizational employee development consistently shows that resource commitment is the strongest predictor of whether development plans actually produce development.

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 is the highest-leverage practice in the entire 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 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 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.

For the broader practice of running effective 1:1 meetings (which is where most IDP check-ins happen), the 1:1 meeting guide covers the agenda structure that makes IDP integration possible without bloating the meeting.

IDP vs Other Development and Performance Tools

IDPs are often confused with other development and performance tools. The confusion produces both bad IDPs and bad versions of the other tools. Below is the clarification: each tool has a distinct purpose, and they work together rather than substituting for each other.

Two clarifications worth emphasizing. First, IDP and 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. The PIP guide covers when and how to use performance improvement plans correctly.

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. The performance review guide covers how to structure reviews that complement, rather than entangle with, IDPs.

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.

The pattern across these mistakes: treating IDP as a deliverable rather than as a living planning practice. A deliverable gets produced once and filed away. A practice gets revisited, adjusted, resourced, and held accountable. The fix for most IDP failures is not a better template; it is more honest treatment of what makes IDPs actually work. Work Institute research on retention consistently finds that lack of career development is among the top reasons employees leave; IDPs are the most concrete tool for addressing this, but only when run as practice rather than paperwork.

IDPs for Managers and Senior Employees

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

Two principles for manager IDPs. First, the goals should disproportionately involve developing other people, not just developing themselves. 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. The leadership development guide covers the broader practice that supports manager IDPs.

IDPs for Remote and Distributed Teams

Remote IDPs work, but 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.

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 accessible to the employee, plus calendar holds for check-ins, plus the IDP saved in a shared folder is enough. The tooling does not produce development; the practice does. Gallup research on engagement consistently finds that the manager-employee development relationship matters more than the systems that support it.

How FirstHR Fits

The honest disclosure: FirstHR is not a dedicated IDP or career development platform. We do not have a built-in IDP template, goal-tracking workflow, or career-pathing software. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. IDPs, when you adopt them, will live in your shared docs, internal wiki, or eventually in dedicated performance management software once you have grown into needing that.

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 actually drive development. FirstHR exists to handle the operational HR foundation at flat-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), 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.

For the foundation that makes development possible, the onboarding best practices guide covers what determines whether someone is set up to grow in their role.

For the broader management foundation that IDPs sit on top of, the people management guide covers running a small team without enterprise overhead.

Frequently Asked Questions