This one turned into an argument about org charts about twenty minutes in, which is exactly what a systems book should do. Meadows's core claim : that behavior comes from structure, not from the people caught inside it : is uncomfortable for a field that likes to blame "learner motivation" for problems that are really feedback-loop problems.
"We keep training people to work around a broken handoff instead of fixing the handoff. That's not a training problem. Meadows would say we found the wrong leverage point."
: from the discussion, paraphrased by Andy
What stuck with the group
- 01Meadows's leverage-points hierarchy became a working checklist: before shipping a course, ask whether the real fix is upstream : a policy, an incentive, a piece of missing information : rather than a training module.
- 02"Shifting the burden to the intervener" was the line that hit hardest : several designers recognized their org's dependence on last-minute compliance training as exactly that trap.
- 03A useful reframe: a Learning Systems Mapper isn't a diagram exercise, it's leverage-point hunting. Where in this system does the smallest nudge produce the biggest change?
What it means for practice
Before the next stakeholder request for "a course on X," a few of us are now asking one systems question first: is X a knowledge gap, or a structural one wearing a knowledge gap's clothes? It's a five-minute conversation that has already killed two unnecessary courses this quarter.
Marginalia™