If you want to become a better instructional designer, teach middle school. Not as a side note to your career. As the thing itself. Because nothing — no certification, no graduate course, no portfolio project — will teach you more about how learning actually works than spending a year trying to hold the attention of a room full of twelve-year-olds who have absolutely no obligation to care about what you're saying.
I taught middle school before I became an instructional designer. At the time I thought of it as one chapter before another. Looking back, I understand it was the most rigorous instructional design training I ever received.
The most honest audience you will ever have
Here's the thing about middle schoolers: they cannot pretend. They don't have the social conditioning yet to sit politely through something that isn't working. When a lesson doesn't connect, they show you. Not through a post-course survey. Not through a low completion rate you'll analyze in a dashboard weeks later. Immediately. Visibly. Honestly.
If you've lost them, you'll know within four minutes. If your explanation is unclear, someone will say so out loud. If your example doesn't feel relevant, you'll watch them drift. And if something lands — if something actually works — the energy in the room shifts in a way that is unmistakable.
"You can't design around your learners in a middle school classroom. You have to design for them. Entirely. From the first sentence."
That feedback loop — immediate, unfiltered, honest — is what most professional learning environments are missing. In corporate L&D, we design in isolation, ship a course, and find out six months later through completion data whether anyone actually engaged. Middle school didn't let me wait six months. It demanded that I understand my audience before I opened my mouth.
What it taught me about relevance
The first question a middle schooler asks — silently, constantly — is: why does this matter to me? Not to you, the teacher. Not to the curriculum. To them. Right now. In their lives.
I spent the first part of my teaching career answering that question poorly, and the second part learning to answer it well. The difference showed up immediately in engagement, in retention, in the quality of work students produced. When they understood why something mattered, they worked harder at it. Every time. Without exception.
This is exactly the question most corporate training ignores. We tell learners what to know and how to do it, but we rarely tell them — specifically, concretely, in terms of their actual daily experience — why it matters to them. Why this module, on this topic, changes something real about how they work or who they can become. When that connection is made, engagement isn't something you design for. It happens naturally.
What it taught me about pacing
A forty-five minute class period feels infinite if the pacing is wrong. And in a middle school classroom, the pacing being wrong is catastrophic. You don't just lose engagement — you lose the room. Completely. And getting it back is twice as hard as never losing it in the first place.
I learned to feel pacing. To sense when an explanation had gone on thirty seconds too long. To know when it was time to shift the activity, change the energy, ask a question, move to a new idea. That instinct — which is really just deep attunement to how humans process information over time — is now one of the most valuable things I bring to eLearning design.
Most eLearning modules are too long. Not because the content is excessive, but because the pacing is uniform. Everything moves at the same speed. There are no pauses, no shifts in tempo, no moments where the learner gets to catch up. The result is a module that feels endless — even when it's only twenty minutes — because nothing changes to signal that something new is beginning.
What it taught me about psychological safety
Twelve-year-olds are acutely aware of embarrassment. They are at the precise developmental moment when being seen to fail — in front of peers, in front of an authority figure — feels genuinely dangerous. Getting something wrong in class isn't just an academic setback. It's a social one. And they protect themselves accordingly: by not trying, by not raising their hand, by not engaging with questions they aren't certain about.
Creating a classroom where students felt safe enough to be wrong — to guess, to attempt, to fail without consequence — was the most important instructional design challenge I faced. Everything else depended on it. If students didn't feel safe, they didn't engage. If they didn't engage, they didn't learn. Full stop.
"Psychological safety is not a soft concern. In both a classroom and an eLearning module, it determines whether any learning happens at all."
This matters enormously in professional learning design. Adults are often more protective of their egos than twelve-year-olds are, because they have more at stake. A scenario-based module that allows people to make wrong choices without visible shame, that frames mistakes as part of the learning rather than failures to be judged — that design decision is not cosmetic. It is structural. It determines whether the learner will engage honestly with the content or perform their way through it.
What I brought with me
When I transitioned into instructional design, I brought a classroom's worth of real experience with me. I knew what bad pacing felt like from both sides of the room. I knew how relevance changes engagement at a molecular level. I knew that the relationship between the learner and the material is not a given — it has to be earned, maintained, and protected through design.
Most importantly, I knew that learners — whether they're twelve years old or forty-five, whether they're sitting in a classroom or clicking through a module on their work laptop — are not passive. They are constantly making decisions about whether to invest their attention, and those decisions are driven by design. Your design. The structure, the pacing, the relevance, the safety.
The classroom taught me that learning design is not about content. It is about people. The content is just the vehicle. What you're really designing is an experience — one that either earns attention and trust, or doesn't. And the feedback, unlike a dashboard report, comes immediately. Whether or not you're paying attention to it.
