Allyse Appel

This module landed on a blind spot in my own work --> I've built strong exit points and almost no entry points. The credentials allow a student to step out at multiple levels with something that holds value, and the module showed me the on-ramps deserve that same attention: the ways a student can enter a pathway at different levels, or earn credit for prior learning and training they already bring. Naming the stacking types -- progressive, supplemental, independent (we have been calling these primary, secondary, and tertiary)-- sharpened that further. I intend to apply it by building the entry… >>>

What I learned from this module is a stronger standard for judging a credential's worth. The push I hear from district leadership is that a credential has to be industry-recognized and industry-validated, and my pushback has always been that recognition depends on who's doing the recognizing -- the entity that cares most about a Microsoft credential is usually Microsoft. This module gave me clearer metrics to grade against: industry-recognized, stackable, portable, and accredited. I intend to apply it by grading candidate certifications against all four criteria and using that as the language to argue for the ones that genuinely hold… >>>

Most of my work sits in vertical alignment: making sure each course builds on the last so students keep stacking skills instead of repeating them.

What shifted for me in this module was seeing two gaps more clearly (1) I underuse university partners in the high-school-to-college handoff, and (2) I’ve treated alignment mostly as a college-readiness issue when many of my students go straight into trades.

The result is a sharper sense that the core of my sequence is solid inside my own programs, and the real leakage happens at system transitions; which is where I need to focus next.

This module provided the vocabulary for my existing design process. Program progression is a deliberate choice, not an accident of scheduling. I use backward scaffolding, gradual release, and non-duplication to ensure students move from foundational skills to mastery, preventing repetitive, disconnected coursework.

My next focus is visibility. A sequence can look sound on paper but feel disjointed to a student. I intend to make the program’s arc explicit, ensuring students understand where they are, what they have built, and what comes next. Scaffolding must serve as a roadmap for them, not just an architecture for myself.

This module helped me think about a Program of Study as more than a required planning document or a basic course sequence. At its best, it shows how a student actually moves through a pathway: what they take, what they earn, how the learning builds, and what options open up after high school. The biggest takeaway for me is the importance of making that pathway visible. A lot of students and families do not automatically know how high school courses connect to college credit, industry credentials, career options, or future training. If that information is not clearly mapped, access depends… >>>

This module reframed our curriculum work as a continuous improvement cycle operating at the program level rather than the classroom level. The structure I have been supporting to build (the cohort-based revision of a backwards-mapped scope and sequence) is essentially a teacher inquiry cycle scaled up to collect evidence, analyze it, share it with stakeholders, identify changes, implement, and return to evidence. Recognizing this equipped me both a vocabulary for what we are doing and a sensation of validation, because I can locate our current work precisely within that cycle.
The module's central argument is essentially that curriculum must not… >>>

What I learned: transparency is not the same as having standards. I have the standards. What the module pushed on is whether anyone outside the building can actually see them, and whether I'm honest about how well students are mastering them.
That second part is the real lesson. Posting standards is the easy half. Posting outcomes is the hard half. Telling stakeholders how many students actually hit the standard, and where we fall short, is a different level of transparency than most programs offer.
The other reframe: stakeholders are contributors, not an audience. Transparency runs both ways. You share the… >>>

What I learned: authentic application is a spectrum, not a project type. I'd been treating it as "do a big project." The module sorts it by depth. Everyday scenarios, project-based challenges, simulated workplace, full work-based learning. Naming the rungs showed me where I have them and where I have gaps.
The gap it exposed: simulated workplace. The structured version, where students clock in, get hired, run as a company, and file reports, is a real method, not a vibe. I'd been skipping the middle and jumping straight from project to placement.
The line that stuck: reflection equals retention. The doing… >>>

What I learned: I have the structure but not always the method. The IAC puts the right people in the room. This module gave me names for what to do once they're there — DACUM, Critical Incident, modified Delphi.
The one that stuck: modified Delphi. Iterative survey rounds, starting from existing standards, until the input actually converges. My current model can still let one loud voice in a single meeting steer a pathway. Iteration guards against that. A meeting is a snapshot. Delphi is a signal.
The other: Critical Incident Technique. Employers documenting real cases of behavior that got a… >>>

What stood out to me the most was the quote: “Employability skills may not get a student hired, but lack of them could get a student fired.”
We often over-index on technical certification hours while treating professional behavior like a footnote—or worse, isolating it into its own separate, abstract unit. If a student can pass a credential exam but can't handle team friction or conflict resolution, that credential becomes deadweight. Especially in the trades, your reputation is everything. Unless these behaviors are practiced as daily habits during core technical courses, they don't sharpen into an applied way of living, which… >>>