Teaching is harder than it looks
I spent years designing training programs for enterprise software rollouts. We had instructional designers, L&D teams, budgets that made sense. And still, half the people who went through our programs couldn't do the actual job a week later. That's when I started digging into the older pedagogical frameworks instead of whatever modern corporate training manual was sitting on my desk. The Seven Laws Of Teaching came up in a footnote somewhere and I figured, why not test them against the worst part of my job: getting adults to actually retain skills they've been shown once. Here's what I found. They hold up.
The Seven Laws Of Teaching
The framework is old enough to be basically invisible now. It traces back to William Hamilton in the early 1800s and got formalized later by Herbart and others. Seven laws, not rules with punishments attached but more like observable conditions that, when ignored, make learning quietly impossible. You'll see different versions depending on who's compiling them, but the core seven are consistent enough. 1. The Law of the Teacher The instructor must genuinely understand what they're teaching. This sounds stupidly obvious until you watch someone try to teach a process they only half-learned themselves three weeks ago. I ran into this hard with a senior engineer who was brilliant at the work but had never actually decoded it into steps. He'd teach a debugging workflow by doing it while the team watched. Nobody learned it because he couldn't explain the branching logic out loud. The fix wasn't better training materials. It was giving him two weeks to write down his own decision tree before he was allowed to run another session.
2. The Law of the Learner Learning doesn't happen in a vacuum. The student's prior knowledge, motivation, cognitive load, and even their physical state matter. Most corporate training ignores this completely. You put everyone in the same room regardless of experience level and wonder why the juniors are lost and the seniors are bored. I learned to split sessions by baseline competency and skip the "introductory" material entirely for people who'd already demonstrated it. Cuts session time in half and actually keeps the advanced people engaged. 3. The Law of the Teaching Act
Get the Full Details
The method of delivery matters. Not in a fluffy "find your teaching style" way. The law is saying that the mechanism you use to transfer knowledge has to match the kind of knowledge you're transferring. You can't teach procedural skills purely through lecture. You can't teach conceptual understanding purely through rote drills. I used to run coding workshops where I'd walk through a full build step by step. Nobody retained it. Switched to having them build alongside me with deliberate pauses for them to predict the next move. Retention jumped from roughly 20% to maybe 60% on follow-up assessments. Big difference. 4. The Law of Learning This one is about the actual mechanics of how learning occurs. Practice, repetition, reinforcement, spaced review. The brain doesn't lock in information on first exposure. Period. Every training program I've ever seen treats first exposure as sufficient. It's not. I started building mandatory recall intervals into my sessions: 10 minutes after the lesson, 2 days later, 1 week later. Each interval was five minutes of unguided recall, no notes. People who hit all four intervals retained things at a noticeably higher rate three months out. The ones who skipped the later intervals forgot most of it by week two.
5. The Law of the Object or Motive There has to be a clear, understandable purpose behind the learning. Not "this is required for your job" but "here's what you'll be able to do differently after this." I've seen training fail because the instructor led with compliance. "We're doing this because headquarters says so." That's not a motive. That's a threat wrapped in paperwork. When I reframed everything around what the person would gain — less firefighting, faster deployments, fewer late nights — participation and effort changed immediately. The content was identical. The framing was everything. 6. The Law of Self-Education
The learner has to do work. Not busy work. Actual cognitive work. This is the one most training programs violate the hardest. They make the instructor do all the thinking and hand the student a completed artifact. I remember running a session where I spent 45 minutes demonstrating a configuration process and the participants took detailed notes. Follow-up quiz: most of them couldn't reproduce the process from memory. Next time, I did the demo in half the time and spent the rest having them configure it themselves while I watched and corrected. Same content. Completely different outcome. 7. The Law of Application Knowledge that isn't used dies. This isn't profound. It's just something people keep forgetting. I used to treat the end of a training session as the end. Wrong. Now I build in an application requirement: something the learner has to do with the material within 48 hours of the session, in their actual work environment. Not a simulation. Real work. I track completion rates. Sessions where application is required and followed up on show measurably better retention. Sessions where it's just mentioned and never checked have the same drop-off as sessions with no application at all.
How I actually use this framework
When I design a training program now, I start with law 5. What's the actual purpose? Then law 2. Who am I teaching and what do they already know? Then law 1. Do I or someone else actually know this well enough to teach it? If any of those come back wrong, nothing else matters. I've watched people build beautiful slide decks and perfect LMS modules and still have zero effective learning because those first three laws were violated. The laws aren't sequential. They're conditional. All of them need to be true simultaneously for learning to happen reliably. Miss one and you're gambling.
Where the framework breaks down
It's not universal. It assumes a context where the instructor has time to prepare, the learner has capacity to engage, and there's an environment where application is actually possible. Military basic training, surgical residency, and skilled trade apprenticeships fit well. Two-hour compliance webinars with 200 people logged in do not. The Seven Laws Of Teaching doesn't fix structural problems like insufficient time, lack of practice environment, or learners who aren't allowed to apply anything back on the job. If you're dealing with those constraints, the framework will tell you what's missing but it won't solve it. You need management involvement, schedule changes, or tool access before pedagogy matters at all.
One edge case that still bugs me
I once had a learner who passed every assessment, scored top marks on application exercises, and then completely failed to perform the skill on the actual job. Turned out the training environment had sanitized variables — predictable inputs, no edge cases, error states that never occurred. The Seven Laws were all technically satisfied. The learning happened in a controlled setting. But the real job had chaotic conditions the training never exposed them to. I solved it by injecting failure modes into practice sessions: network timeouts, bad data, corrupted files, conflicting priorities. It made the training harder and people complained. Performance on the actual job improved dramatically. The law of application was satisfied in the abstract but not in the specific. That distinction costs people who don't watch for it. There are older print editions of materials that compile these laws with examples. Educational publishers kept reissuing them through the 1900s and 1910s. You can find digital copies through the Internet Archive or HathiTrust if you want the original formulations. The Herbartian versions tend to be more detailed but also more tangled. The Hamilton originals are cleaner.
I don't recommend starting with the primary sources. They're dense and full of language that hasn't aged well. Start with applying the laws to your own training problems and circle back to the originals when you hit a concept that doesn't seem to fit what you're seeing in practice.
