The Problem With Plans That Never Actually Get Used
Most educational plans are beautiful documents that sit on a shelf because they were designed for a hypothetical student who doesn't exist. My Plan PUSD framework exists because I spent years watching teachers and administrators build elaborate syllabi that collapsed the moment real students walked through the door. The PUSD model — Purpose, Understanding, Skill-building, and Demonstration — was my attempt to fix that disconnect between what a plan says and what actually happens in a classroom over fourteen weeks.Here's how it works in practice. You start with Purpose, which means defining exactly what a student should be able to do, not what they should know. Knowing is passive and impossible to measure. Being able to do something is the only metric that matters. Then you map Understanding by breaking that performance target into the prerequisite concepts a student needs to access it. Skill-building is where most plans fail because they assume understanding automatically translates into ability. It doesn't. You need deliberate, repeated practice with feedback on each discrete skill. Demonstration is the assessment phase where students prove they can execute the original purpose under conditions that mirror real application, not a multiple-choice test. The actual build process takes about three to four hours for a competent educator working alone on a single unit. First hour: define the purpose statement in performance language. Not "students will understand fractions." Try "students will be able to add, subtract, and compare fractions with unlike denominators in word problems involving measurement and cooking scenarios." That specificity changes everything that follows. Second hour: map understanding prerequisites backwards from that goal. What concepts block someone from doing that task? Third hour: design skill-building activities for each prerequisite. Fourth hour: create the demonstration task with a rubric. I ran into a specific problem last year that exposed a flaw in how I'd been applying PUSD. I built a complete unit for a vocational coding course where students had to build a functioning web form. The Purpose was clear. The Understanding map was solid. The Skill-building activities covered HTML, CSS, JavaScript individually. The Demonstration task required assembling all three. The problem was that thirty percent of my students hit a wall at the integration phase. They could write valid HTML, they understood basic CSS selectors, they knew individual JavaScript functions — but putting them together in a real context was a completely different cognitive load. The PUSD framework as I'd originally designed it didn't account for this integration gap between discrete skill sets.
The workaround was adding what I now call a bridge phase between Skill-building and Demonstration. This is a two-week period where students work on simplified versions of the final task that force them to connect skills in low-stakes environments before facing the full assessment. For the coding course, that meant building a form that only validated one field, then two, then all fields with progressively fewer hints. This addition usually adds ten to fifteen percent more instructional time but increases final mastery rates from around sixty-five percent to eightynine percent based on my internal data across twelve course iterations. It's not elegant but it's honest about how learning actually works. There are scenarios where My Plan PUSD simply does not work well. Standardized test prep is one. The framework assumes a reasonable degree of autonomy in pace and method, which standardized curricula don't provide. Special education populations with IEPs require heavy modification because the rigid four-phase structure doesn't flex naturally around accommodation requirements without significant upfront redesign. Large lecture-style courses with over one hundred fifty students also struggle with the demonstration phase because authentic performance assessment at that scale demands either teaching assistant support or a fundamental redesign of what counts as demonstration. In those cases, I recommend a hybrid approach where you use PUSD for the Purpose and Understanding phases only, then switch to a more traditional model for delivery and assessment. The common mistake people make is treating PUSD as a template to fill in rather than a diagnostic lens. You don't need to rebuild every plan from scratch. Take any existing curriculum document and run it through the four phases as an audit. You will find gaps immediately. Usually the biggest one is that Skill-building time is drastically understated because planners confuse exposure to a concept with development of a skill. Exposure might take twenty minutes of direct instruction. Skill development in that same area typically requires three to five hours of guided practice with feedback spread across multiple sessions before students can perform independently.
Another counter-intuitive finding from my work: the Purpose statement should be written after the Understanding map, not before it. When you start with Purpose, you tend to write vague or overly ambitious goals because you haven't yet mapped the prerequisite landscape. By reverse-engineering from the Understanding requirements, your final Purpose statement tends to be more realistic and achievable within the available instructional time. I've seen this reduce plan revisions by roughly forty percent across a semester. If you want to apply this framework to your own planning, start small. Pick one unit from your current curriculum, ideally one that has given you trouble in the past. Run it through the four phases over a couple of afternoons. Compare what emerges with your existing plan. The differences will show you what you were missing without requiring you to abandon everything you currently do. The framework is designed to be additive, not replacement-heavy. Most educators find that after six to eight weeks of use, their planning time actually decreases because they stop second-guessing whether their lessons are connected to coherent outcomes. That's the actual excellence being unlocked — not better students, but clearer thinking from the people designing the instruction.
Get the Full Details
