If Your Development Plan Doesn’t Change What You Do Monday, It Isn’t a Plan

Ray got promoted to foreman on a Thursday and was asked for a development plan the following Monday.

He'd been a journeyman electrician for 11 years at a commercial contractor, and he was good at it. Good enough that when the previous foreman left, nobody debated who should take the crew. Ray knew the details of the work through and through. What he didn't know was how to lead 12 people, manage a schedule he didn't build, or handle a general contractor who wanted to know why the panel schedule slipped.

His manager asked him to put together a learning and development plan. Ray had never made one. He looked at a blank page for a while and wrote down 3 things.

1. 1. 1. 1. Read a leadership book.
         2. Take an online course on construction management.
         3. Improve communication.

He sent it over. His manager wrote back the same afternoon: "Looks good."

6 months later, Ray was struggling with exactly the things he'd been struggling with when he was promoted. He'd read most of the book. He'd started the course and stopped around the third module. Communication had not improved, mostly because he'd never figured out what "improve communication" was supposed to mean in practice.

The plan wasn't the problem. The plan barely existed.

 

Why Most Development Plans Do Nothing

Ray's plan failed for the same 3 reasons most of them do.

It listed activities instead of outcomes. A book, a course, and a vague aspiration. None of them said what Ray would be able to do differently when he was done, which means there was no way to know if any of it worked.

Nobody else was involved. Ray wrote it alone, and his manager approved it in 4 words. No one was checking, supporting, or expecting anything. Development that happens in isolation quietly stops happening.

And it had no connection to what Ray actually needed. He was drowning in scheduling and general contractor conversations. His plan addressed neither.

But somehow the plan got approved. Approval and usefulness are different things. A plan nobody questioned is usually a plan nobody read.

 

What a Real L&D Plan Does

A learning and development plan connects a person's growth to a specific business need, defines what success looks like in measurable terms, names the people who will support and check on it, and gets pressure-tested before anyone starts executing.

It is not a training list. A list of courses is an input, not a plan.

It is not a performance improvement plan (PIP) either. This distinction matters, because people hear "development plan" and assume something went wrong.

A PIP is corrective and addresses a gap between expectations and performance.

An L&D plan is forward-looking and builds capability someone doesn't have yet. Ray wasn't failing. He'd been handed a job that required skills nobody had taught him.

 

The Seven Parts of a Plan That Works

1. 1. 1. 1. Context: why this plan, why now. Anchor the plan to a real situation, not a general desire to grow.
            • Ineffective: "To support my professional development."
            • Effective: "I was promoted to foreman in March after 11 years as a journeyman. I'm strong technically but new to leading a crew, managing schedules, and handling general contractor relationships. This plan covers my first year in the role."
              • The second version tells anyone reading it exactly what problem the plan exists to solve.

1. 1. 1. 2. Main objectives: what this will accomplish. 2 or 3 focused objectives. Not 10. A plan with 10 objectives is a wish list, and wish lists don't survive a busy quarter.
            • Ineffective: "Become a better leader."
            • Effective: "Run a crew of 12 without escalating routine scheduling conflicts. Hold a productive weekly planning conversation with the GC. Give clear direction and feedback to my crew, including the 2 guys I used to work alongside."
         3. Target development programs: the specific capabilities. What are you actually building? Name the skills specifically.
            • For Ray: crew scheduling and sequencing, delivering feedback to former peers, and running a jobsite meeting that produces decisions.
         4. Methods: how the learning happens. Coaching, mentorship, stretch assignments, courses, reading, shadowing.
            • One caution. Most development is work, not coursework. Courses and books have their place, but capability gets built by doing the thing with support, not by reading about it. If your methods column is entirely books and online modules, you've built a study plan.
            • Effective: "Weekly thirty-minute sit-down with the senior foreman on the adjacent job for my first quarter. Shadow him on 2 GC coordination meetings. Own the 3-week look-ahead schedule starting in month 2, with his review before I submit it."
         5. Expected outcomes: what gets hit, by when, and how success is measured.
            • Ineffective: "Improved leadership skills."
            • Effective: "By month 3, I'm building the 3-week look ahead without review. By month 6, GC coordination meetings run without my manager attending. By month 6, I've given direct feedback to each crew member at least twice, and my manager has heard about it from them rather than from me."
              • If you can't tell whether an outcome happened, it isn't an outcome.

1. 1. 1. 6. Stakeholders: who's involved and how often you sync. Name people and put the syncs on a calendar. This is the accountability structure.
            • Effective: "Meet with my manager monthly for thirty minutes. Meet with the senior foreman on the adjacent job, weekly for the first quarter. Meet with my crew weekly, who feel the difference if this works."

That last one matters more than it looks. Development plans that only benefit the individual tend to lose to urgent work. Plans where other people feel the impact tend to survive.

1. 1. 1. 7. Other: constraints and reality. Winter shutdown, a major project running through Q3, a certification with a fixed exam date. Anything that will impact timing. Better to name it now than to have the plan quietly collapse against it later.

Don’t Skip This Step

Once the plan is drafted, share it with people who can poke holes in it. Your manager, a coach, a peer who's done the job, ideally with commenting access so you get real feedback rather than a verbal "looks fine."

Ask them directly: what's missing?

2 things happen. The plan gets better, because someone who's already done what you're trying to do will see the gap you can't. And the plan gets witnesses. Now other people know what you committed to, which changes the odds you'll follow through.

A plan that survives someone else's questions is a plan worth executing.

 

Keep It Alive

Put a review on the calendar. Quarterly at a minimum.

Plans go stale because businesses change and documents don't. 6 months in, Ray might discover that scheduling clicked faster than expected, and the harder problem is something he didn't anticipate. That's a signal to evolve the plan, not to abandon it.

 

Where These Go Wrong

The course list. A collection of training with no outcome attached. Easy to write, easy to approve, produces nothing you can point to.

The plan for the wrong job. Someone builds a plan for a role they're not actually moving toward, usually because it sounded impressive. Development aimed at a job that isn't coming is wasted effort.

The plan with no stakeholders. Written alone, executed alone, forgotten alone. Nothing reinforces it, and nobody notices when it starts and stops.

 

Back to Ray

9 months after his promotion, Ray rebuilt the plan. It took him about an hour, which is roughly 55 minutes longer than the first one.

 

His updated context was specific:

• • • • A technically strong journeyman running a crew for the first time
      • Weakest on scheduling and GC coordination
      • Objectives came down to three
      • Methods were mostly weekly time with a senior foreman on the next job over and progressively owning the lookahead schedule
      • Outcomes had dates attached
      • His manager and the senior foreman were named, with syncs on the calendar.

He shared it before he started. His manager added one thing he'd missed: the crew conversation about being promoted over people he used to work next to, which Ray had been avoiding.

6 months after that, Ray built the 3-week look-ahead without review. He runs GC coordination meetings alone. He had the awkward conversation with his crew twice, and both went better than he expected.

The difference wasn't effort. Ray worked hard on the first plan's book and course too. The difference was that the second plan named what he needed to be able to do, when, and who was going to help.

Development plans don't fail because people lack discipline. They fail because they were never specific enough to execute.

 

How we can help

Most leaders are handed a bigger job and left to figure out the new skills on their own. That works occasionally. Mostly, it produces capable people who struggle longer than they need to.

Our Executive Performance Coaches work with leaders at every level to build development plans that connect to real business needs, define measurable outcomes, and come with the support structure that makes them stick.

If your newly promoted leaders are figuring it out alone, we can help. Reach out through our contact form, and we'll share our Learning and Development Plan Template as a resource you can put to use immediately.