The Professional Development Administrators Actually Need to Support a Soft Skills Program

How to Teach Soft Skills  |  Guide  |  August 30, 2026

The Professional Development Administrators Actually Need to Support a Soft Skills Program

Most PD around soft skills is built for teachers, not the administrator who has to approve, fund, and defend it to a board. Here's what admin-level PD should actually cover — and what most districts skip.

By Rob Heller, Founder — The Boost Program

I've sat in enough rollout meetings to know the pattern. A district buys a soft skills or SEL program. The teachers, or in Boost's case the coaches, get trained on delivery — how to run the lessons, lead discussions, handle the kid who won't participate. Then everyone assumes the administrator's job is done: sign the contract, forward the training schedule, check in at the end of the semester.

That's the gap nobody talks about. The people teaching the program get PD. The people who have to defend it to a school board, explain it to skeptical parents, and decide whether it survives budget season next year get almost nothing.

The PD Gap No One Talks About

Here's what the national data shows. In the most recent federal survey of principals, 92% reported professional development on "supporting effective instruction" and 85% on school safety or climate. Good — those are core to the job. But only about half of principals reported PD on "social services for students" and the human-resource, relational side of leading a building. That's the exact terrain a soft skills program lives in, and it's the half of the job administrators are least equipped for.

It gets worse when you look at spending. District leaders are telling researchers that professional development is one of their fastest-growing budget lines heading into next year — roughly four in ten expect to increase PD spend, more than any other category. The money is there. But it's flowing into instructional PD and compliance training, not into helping administrators understand and defend a new soft-skills initiative. There's also a perception gap: the vast majority of principals and superintendents believe their PD adequately prepares teachers, but only about two-thirds of teachers agree. If that gap exists at the teacher level, it's wider at the administrator level, where almost nobody is measuring PD adequacy at all.

I'm not saying administrators are lazy or uninterested. The entire PD industry — a multi-billion-dollar market at this point — has built its offerings around instructional strategy and data analysis, because that's what's easy to sell and easy to measure. Nobody built a course for "how do I defend a new program to my board when a parent emails asking why we're not focused on test scores."

What Administrator-Level PD Usually Gets Wrong

Most PD that reaches administrators around a new program falls into one of two traps.

The first is that it's really just teacher PD with the volume turned down. Someone hands the principal the same slide deck the coaches got, minus the role-play. The administrator walks away knowing what the program covers but not why it matters, how to talk about it, or how to know if it's working.

The second trap is that it's all logistics — how to schedule the sessions, track attendance, file the paperwork. Useful, but it treats the administrator like a project manager instead of the person who has to make the case for why this program deserves a slot in an already packed school day.

An administrator adopting a soft skills program isn't there to teach it. They're there to protect it.

Both traps miss the actual job. An administrator adopting a soft skills program isn't there to teach it. They're there to protect it — from budget cuts, skeptical staff, and the next new initiative that will try to eat its time slot in two years. That requires a different kind of preparation entirely.

The Four Things Admins Actually Need to Know

After working with schools rolling out Boost, I've narrowed it down to four things that actually move the needle for the administrator, not the coach.

1. The why, in language that survives a board meeting. Every administrator needs to be able to say, in one sentence, why this program exists and why it's not just another initiative. At Boost, that sentence is: life is skill-based — the things that determine whether a student thrives after graduation are learnable skills, not fixed traits. That's a sentence a principal can say to a board, a skeptical teacher, or a parent, and it holds up because it's true and specific. Vague mission language doesn't survive contact with a hard question. A clear thesis does.

2. What fidelity actually looks like. Administrators don't need to know how to run every lesson. They need to know what "this program is working" looks like from the outside — attendance in sessions, whether coaches are following the framework instead of freelancing, whether students can articulate the core idea partway through. Without this, an administrator has no way to catch a program quietly drifting off track until it's already failed.

3. How to answer the three objections that come every time. "We already do SEL." "This feels like it's cutting into academic time." "How do we know this actually works." Every administrator who skips this piece ends up improvising an answer in the moment, and improvised answers to hard questions rarely land well. The strongest answer to "we already do SEL" isn't defensive — it's "you're already doing great work, and this is the next version of it, built specifically for high schoolers instead of retrofitted from elementary programs." That reframes the program as a force multiplier instead of a replacement, and it's a much easier conversation.

4. A first-year rollout plan, not just a training calendar. This is where most PD stops short. Administrators need a plan that covers the first 90 days: how the program gets introduced to staff, how it gets communicated to parents, what data gets collected and reported back to the board, and what the checkpoint looks like at the semester mark to decide whether to expand it. Without this, even a well-run program can stall simply because nobody planned past the launch.

How to Build This Into a Rollout Plan

If you're an administrator about to bring a soft skills program into your building, here's the sequence I'd recommend, based on what's worked in schools we've partnered with.

Start before the coaches start. Book two to three hours with your leadership team — not the delivery team — dedicated specifically to the why, the fidelity markers, and the objection responses. This is not the same meeting as staff onboarding.

Build your board or leadership one-pager before you need it, not after the first hard question comes in. One page: the problem, the approach, the cost, the early evidence. Boost's own pilot data — about 87% of students finishing an eight-week program with a clear understanding that these are learnable skills, compared to a small fraction going in — is the kind of concrete number that belongs on that page.

Set your semester checkpoint on the calendar now. Decide in advance what you're measuring at the halfway mark and who reviews it. If you wait until someone asks "is this working," you'll be building your evaluation criteria under pressure instead of by design.

And treat this as one hour of leadership time, not a second full-time job. A soft skills program, done well, asks for about an hour a week from the students. The administrator-level commitment is even smaller — mostly front-loaded into the setup, then a light monthly check-in. If your PD plan is asking for more than that from your leadership team, something in the design is off.