Why Your K–12 Staff Training Isn't Changing Practice (And How Backward Design Fixes That)

By Kalin Schoephoerster | KShep Creative

You've been there. A training that went well by every visible measure. The facilitator was strong. The content was solid. People were engaged, asked good questions, and filled out the feedback form with positive ratings.

And then nothing changed.

Staff went back to doing what they'd always done. The new procedure wasn't followed. The tool wasn't used. The framework wasn't implemented. Three weeks later, you're wondering whether the training happened at all.

This isn't a facilitator problem or a staff motivation problem. It's a design problem. And it's one of the most common issues in K–12 professional development. The good news is that it's fixable, and the fix has a name: backward design.

Why most training doesn't change practice

Most staff training is built content-first. Someone identifies a topic that needs to be covered, builds a slide deck around that content, delivers it, and measures success by whether people showed up and seemed engaged. The implicit assumption is that exposure to information leads to behavior change.

That assumption is almost always wrong.

There are three reasons training typically fails to transfer to practice.

No clear outcome was defined upfront. If you don't know what you want staff to do differently on Monday morning, you can't design a training that gets them there. "Staff will understand the new framework" is not an outcome. It's a hope. Outcomes describe observable behavior, not internal states.

Content is mistaken for learning. Delivering information and producing learning are two different things. A training that covers all the right content but gives no time for practice, application, or reflection rarely produces lasting change. People need to do something with information before it sticks.

Success is measured by completion, not behavior. If the only question you ask after a training is "did people attend," you'll never know whether it worked. Attendance and learning are not the same metric, and treating them as equivalent is how ineffective training keeps getting scheduled year after year.

What backward design is

Backward design is a planning framework developed by Grant Wiggins and Jay McTighe in their work on Understanding by Design. It was originally developed for curriculum planning, but the core logic applies directly to professional development and staff training. The idea is straightforward: start with the end in mind, then build backward to get there.

The framework has three stages.

Stage 1: Identify the desired results. What should staff be able to do, understand, or decide differently after this training? This question comes before anything else. Not "what do we need to cover" but "what do we need staff to be able to do." The answer should be specific and observable. "Staff will be able to use the program's progress monitoring tool to adjust instruction by the end of the first week" is a desired result. "Staff will have learned about progress monitoring" is not.

Stage 2: Determine acceptable evidence. How will you know the training worked? What would you actually see staff doing on the job if the training was successful? This stage is where most training design skips ahead too quickly. People move straight from defining the topic to building slides, without ever stopping to ask what evidence would tell them the training achieved its goal. Defining that evidence before building anything changes what you build.

Stage 3: Plan the learning experience. Only after stages one and two do you design the actual training. The content, activities, format, and length are all chosen because they serve the outcome you defined in stage one and will produce the evidence you identified in stage two. If a section of content doesn't connect to those answers, it probably doesn't belong in the training.

That last point is worth sitting with. Backward design gives you a principled way to cut content that feels important but doesn't serve the actual goal. And in professional development, where time is always scarce, that's one of its most practical benefits.

What backward design looks like in K–12 staff training

Here's a concrete before-and-after comparison using a scenario most K–12 leaders will recognize.

The content-first version:

A district is rolling out a new behavior support framework. Someone builds a two-hour training covering the framework's philosophy, its key components, the research behind it, and examples from other districts that have implemented it. The session is informative. Staff rate it positively. Three weeks later, almost none of them are using the framework differently in their classrooms or hallways.

The training covered everything it was supposed to cover. It just didn't change anything.

The backward design version:

Start by asking: what do we want staff to do differently next week? Get specific. "Staff will use the three-step de-escalation protocol when a student is dysregulated, without waiting to consult with a specialist first."

Then ask: how will we know they can do it? Maybe staff practice the protocol through a scenario during the training itself. Maybe a coach observes two weeks later and gives structured feedback. Define the evidence before you build the session.

Then build backward from those answers. What do staff need to know to execute the protocol confidently? What practice will build the skill during the training? What job aid will help them remember the steps when they're standing in a hallway and a student is escalating?

The resulting training is shorter, more focused, and far more likely to produce the change the district actually needed. It may cover less content. But it will achieve more.

Three questions to ask before you build any training

You don't need to implement the full Understanding by Design framework to start applying backward design thinking to your professional development. These three questions will get you most of the way there.

1. What should staff be able to do differently after this training? Be specific and behavioral. "Understand the new policy" is not an outcome. "Complete the new referral form correctly without asking for help" is. If you can't answer this question clearly, the training isn't ready to be designed yet.

2. How will you know it worked? Define what success looks like before you build anything. Would you see staff using a new tool? Following a new procedure? Making a different kind of decision? If you can't describe what you'd observe if the training succeeded, you don't yet have a clear enough outcome.

3. Does every part of this training serve those answers? Once you have the training drafted, go back through it section by section. If a piece of content doesn't connect to what staff need to do or how you'll know it worked, ask whether it belongs. In most cases, cutting it makes the training stronger, not weaker.

Where instructional design fits in

Backward design isn't a tool that gets applied after a training is built. It's a lens that shapes the whole process from the first conversation.

When I work with a K–12 district on professional development, the discovery and scoping stage is essentially stages one and two of backward design: what do people need to do differently, and how will we know they can? Every decision after that point — format, length, activities, job aids, assessment — is made in service of those answers.

This is what separates instructional design from content development. A content developer builds what you ask for. An instructional designer asks whether what you're asking for will actually achieve what you need, and designs accordingly. For districts that have invested in training that didn't transfer, that distinction tends to matter.

For more on what instructional designers actually do in a K–12 context, see What Does an Instructional Designer Do? A Guide for K–12 Districts →

The training didn't fail. The design did.

If your district has staff training that isn't changing practice, the problem usually isn't the content, the facilitator, or the staff. It's that the outcome wasn't defined before the content was built. That's a design problem, and it has a straightforward solution.

Start with the end. Define what you want staff to be able to do. Decide how you'll know they can do it. Then build everything else to serve those answers.

That's backward design. And it's one of the most reliable ways to build professional development that actually changes what happens in classrooms and hallways.

Book a free 30-minute intro call →

Or explore K–12 staff training and eLearning services → to see what outcome-focused training design looks like in practice.

Kalin Schoephoerster is a CPACC-certified instructional designer and accessibility consultant based in St. Paul, MN. KShep Creative partners with K–12 districts, higher education institutions, and EdTech organizations to develop accessible eLearning, instructor-led training, curriculum, SOPs, and website accessibility audits aligned with WCAG 2.2 and ADA Title II requirements.