Professional Development Plan: A Small Business Playbook

A professional development plan in a six-person business is not a career ladder. There is usually no rung above the person you are trying to develop, and everyone involved can see that. What there is, in every small business, is a list of jobs only the owner can currently do.

So write the plan as the thing it actually is: a dated transfer of ownership. One piece of work moves off your desk onto someone else’s, on a specific date, with whatever training makes that transfer safe attached to it. Nearly everything else that usually fills a development plan is decoration around that one sentence.

The pressure behind this is ordinary rather than dramatic. In May 2026, 3.065 million people in the United States quit a job, a figure the Bureau of Labor Statistics publishes monthly through its Job Openings and Labor Turnover Survey (fred.stlouisfed.org). Most of them did not leave over a single bad week.

What most owners write down, and why it stalls

The typical plan is a list of qualities. Improve leadership skills. Get more confident with the numbers. Take more initiative. None of that is wrong, and none of it can be owned. There is no date on it, no artifact at the end, and no way for either of you to say in eight weeks whether it happened.

The failure is structural rather than motivational. The document describes a person when it should be naming work that changes hands.

Write the last line first

Take the sentence you would normally arrive at last and put it at the top: on this date, this person owns this task, without checking with me.

Everything else derives backwards from that sentence. Ask what would have to be true for it to be safe, and the skills fall out on their own, in the order the work needs them rather than the order they sound impressive.

Four lines carry the whole plan:

1. The handoff. The task, the person, the date.
2. What has to be true first. Two or three capabilities, not qualities: can quote a standard job without calling you, can close out the week’s invoices, can run the Monday order.
3. Where each one gets learned, with its own date.
4. The stop condition. What you do if line one is not true on the date. Reschedule, shrink, or drop it, decided now rather than in the moment.

As a hypothetical, and it is only a hypothetical: a two-van HVAC shop wants its senior technician to own scheduling by October 1. What has to be true first is that he can quote a standard replacement without a phone call, and that he can read the week’s remaining capacity before promising a slot. Those are two learnable things with dates on them. “Grow into a leadership role” is neither.

Writing down how the task is currently done is usually the real first step, and it is worth doing properly. Our playbook on turning a task into standard work instructions covers the capture-and-test method for exactly this.

The coverage question that kills most plans

Here is the line almost no development plan contains, and it is the one that decides whether the plan survives: who does this person’s current job during the hours the learning takes.

In a large company the question answers itself. There is slack in the system, a backfill, a team that absorbs it. In a six-person business none of that exists. The hours have to come from somewhere, and when nobody names where, they come out of the person’s existing week, which is already full.

So add the line nobody adds. For each learning block: the hours, and who covers. If the honest answer is that they will fit it in around the work, the plan is already over and has simply not admitted it, because you have scheduled development into the only hours that person uses to keep up.

The fix is almost always to shrink the plan rather than to find the hours. One capability, learned in blocks you can genuinely cover, beats four capabilities that exist only on the page. This is also the quiet reason development plans and burnout are the same conversation, which we worked through separately in reducing employee turnover by tackling burnout.

Where the training actually comes from

Three real options. The honest split between them is not quality, it is which resource you are spending.

SCORE mentoring is free. The wording on its own site is unambiguous: “SCORE mentoring is a free service offered to any aspiring or established owners of a U.S.-based business”, delivered one to one, virtually or in person (score.org). It suits the judgment-shaped skills that courses handle badly, such as holding a pricing conversation or managing someone who was a peer last month.

MySBA Learning is the Small Business Administration’s free platform, built as topic journeys made of shorter excursions, each carrying a time estimate (learning.sba.gov). Those time estimates are the useful part here, because the coverage line above needs a number of hours and this hands you one before you commit to anything.

Coursera Plus is the paid option, at $59 per month or $399 per year, with a 7-day free trial and a 14-day money-back guarantee on the annual plan (coursera.org). It earns the money when the gap is a specific technical skill with a credential attached, rather than a judgment call.

The free options are not the cheap options. They cost time, and time is the scarcer of the two things you are spending.

If a blank page is the obstacle on the employee’s side, the Professional Development Plan prompt at BusinessPrompter is written for an individual mapping their own career goals rather than for the manager, which makes it a reasonable fit for the half of this the employee should be drafting. It sits behind that site’s Pro membership, and the wider library is at businessprompter.com.

The part I would argue for hardest

Everything above this heading is documented or checkable. What follows is judgment.

The reason to build a development plan is not to make the business less dependent on any one person. That is the version owners are usually sold, and it produces a predictable result. People can tell when they are being made replaceable, and they take the training somewhere that wants them for longer than the handoff.

The version that works points the other way. A handoff creates a second person who can carry the thing, and a second person who can carry the thing is how a small business accepts work it currently turns down. That makes the plan an argument for growth rather than a cost-reduction exercise with a friendlier name. Here is the test: if the payoff on your plan is written as hours saved, you have built the first kind. If it is written as work you can now say yes to, you have built the second.

It is also why the target should be capacity rather than a title you are not in a position to award. The same argument runs at a longer horizon in our piece on setting three-year goals as capacity rather than revenue.

Frequently Asked Questions

What actually goes on a one-page development plan?
Four lines. The handoff, written as a task, a person and a date. The two or three capabilities that have to be true before that date. Where each one gets learned, with its own date. And a stop condition saying what you will do if the handoff is not ready on the day. Anything beyond those four lines is commentary.

How do I run a development plan with no training budget?
Use the free options and pay in time instead. SCORE offers free one to one mentoring to owners of U.S.-based businesses (score.org), and MySBA Learning is the SBA’s free platform, with a time estimate attached to each excursion so you can schedule around cover (learning.sba.gov). The binding constraint is rarely money. It is who holds the person’s current work during the learning hours.

What if there is no promotion to offer at the end?
Then do not offer one. In a small business the honest reward is ownership rather than a title: a piece of work that is now genuinely theirs, decisions included, without checking back with you. Name that specific piece of work in the plan. A title you cannot award is worse than no title, because the plan quietly becomes a promise you will have to break.

How long should a development plan run?
Let the handoff date set the length instead of picking a round number first. One handoff usually needs 60 to 90 days, which is long enough to schedule real learning hours with cover and short enough that the date still feels real. When a plan needs a year, it is normally several handoffs stacked together and should be written as several plans.

Before you write a single goal, write the one sentence: the task, the person, the date. Then answer the second question out loud. Who covers their current work during those hours. If that answer does not exist yet, what you have is not a development plan. It is a wish with a deadline attached.