Coaching Plans That Managers Actually Run (Not Docs That Die in a Drive)

Somewhere in your shared drive there's a document called "Development Plan — Q1." It has three bullet points, one aspirational goal, and a last-edited date that stopped moving the week after it was written. Everyone meant well. The manager sat down with the report, they talked honestly for forty-five minutes, they typed something up. And then the quarter happened — the fires, the deadlines, the actual job — and the plan quietly became an artifact. Proof that a conversation once occurred, not a thing anyone is running.

That's the good case. At most small companies, manager coaching isn't a doc that died; it never got written at all. Coaching happens in the hallway, in the moment, when someone remembers — which means it happens for the squeaky wheels and the people the manager naturally likes, and not for anyone else. There's no structure, no cadence, no record. When someone asks "how is this person developing," the honest answer is a shrug and a vibe.

Here's the thing worth saying out loud: the problem was never the manager's intentions. Managers at small companies genuinely want their people to grow. The problem is that coaching, as most SMBs practice it, has no operating system. A one-time conversation isn't a development plan any more than a single workout is a fitness program. Good intentions die in week one because nothing was built to carry them past it.

So stop treating a coaching plan as a document you produce and file. Treat it as a living plan you run — something with a goal, a few concrete moves, a review rhythm, and a trail of evidence. Built that way, it survives the quarter. Built the old way, it becomes the thing you feel guilty about in the drive.

What a coaching plan actually needs

A plan that gets run has four parts, and skipping any one of them is how you end up back in the drive. Here they are, in order.

1. One development goal, stated as a behavior

Not "improve communication." Not "be more strategic." Those are wishes, and you can't run a wish. A goal you can run names a specific thing this person will be able to do that they can't reliably do today. "Run a client status call without the account lead in the room." "Write a project update that a stakeholder can act on without a follow-up meeting." "Push back on an unrealistic deadline with a counter-proposal instead of just absorbing it."

The test is the same one good instructional design uses: if you can't picture what "done" looks like on the job, you don't have a goal yet — you have a topic. One goal per plan. A report developing five things at once is developing none of them.

2. A few concrete actions — small enough to actually happen

This is where most plans overreach. Someone gets ambitious and lists eight development activities, and the sheer weight of it guarantees none get done. A coaching plan needs two or three actions, each small and specific enough to fit inside a normal week: shadow a particular meeting, draft the thing and get feedback before it goes out, take the lead on one low-stakes call. Actions, not aspirations. "Get better at presenting" is not an action. "Present the Tuesday numbers to the team, then debrief with me for ten minutes after" is.

The bar is this: could the person start the action this week without asking anyone for permission or resources they don't have? If yes, it's a real action. If it needs a budget approval and a course enrollment and a stars-align moment, it's a someday, and somedays don't get run.

3. A review rhythm you commit to before you need it

This is the part that separates a plan that lives from a doc that dies, and it's the part everyone skips. A coaching plan needs a cadence — a recurring, already-scheduled moment where the manager and report look at the plan together. Not "we'll check in when things calm down," because things never calm down. Fifteen minutes, every two weeks, on the calendar, treated like a real meeting instead of the first thing that gets bumped.

The rhythm doesn't have to be heavy. Most of these reviews are three questions: What moved since last time? What got in the way? What's the next action? But the fact that the review is scheduled is what keeps the plan alive. A plan reviewed on a cadence is a plan. A plan you'll "revisit eventually" is a memory.

4. Evidence of progress — so growth is visible, not vibes

The last piece is a trail. Every review, you note what actually happened: the call got run, the update landed without a follow-up, the pushback was attempted and it went okay. This does two things. It makes progress visible — to the report, who can see they're moving, and to you, when someone asks how this person is developing and you can point to a record instead of a feeling. And it makes the plan honest: if three reviews go by and the evidence column is empty, that's information. Either the actions were wrong or the cadence isn't holding, and now you can fix it instead of pretending.

Evidence is also what turns a coaching plan into something a manager can defend — in a promotion case, a performance conversation, a raise discussion. "I think they've grown" is a vibe. "Here's the plan, here's what they took on, here's what changed" is a case.

Why this dies without a structure to hold it

Notice that none of the four parts is complicated. A manager reading this could build one on a napkin. So why doesn't it happen?

That's the gap a tool can close — not by coaching for you (it can't, and shouldn't), but by giving the plan a shape that survives a busy week.

Where LearningByDesign fits

This is the specific thing LearningByDesign generates: a structured coaching plan a manager and report can actually run and revisit. You describe the person and what they need to develop, and it produces the plan in the shape that holds — one behavioral development goal, a few concrete actions sized to a real week, a review cadence, and a place for the evidence to accumulate as you go.

The point isn't the document. It's that the plan comes out already structured to be run instead of filed — the goal is a behavior, the actions are small, the cadence is built in, the record has somewhere to live. You still do the coaching; that's yours and always will be. What you don't do is start from a blank page every time and hope you remember the parts that make it stick. If you want a manager coaching plan template that's built to survive past week one, this is what it's for.

We're early and honest about it: LearningByDesign is a small, pre-revenue product, not a decade-old suite with a case-study library. What it does is take the structure good managers already know they should use and make it the path of least resistance instead of the thing they keep meaning to set up.

The bottom line

Manager coaching at a small company fails in a predictable way: a well-meant conversation becomes a document, the document becomes an artifact, and the artifact dies in a drive. The fix isn't more sincerity or a better template file. It's treating a coaching plan as a living thing with four working parts — one behavioral goal, a few concrete actions, a review rhythm you schedule before you need it, and a trail of evidence that makes growth visible. Build it that way and it survives the quarter. Build it the old way and you'll find it next January, last edited in week one, right where you left it.