Author: Marc Ferrer, Ph.D, Founder Engram Kinetics
Marc Ferrer, Ph.D., is the founder of Engram Kinetics (engramkinetics.com), where he designs branched decision-training scenarios for exercise-certification candidates. His training spans four fields united by one problem — reasoning from incomplete evidence: a Ph.D. in geology (EPFL) and an M.Sc. in computer science for earth sciences (UPMC, Paris), then an M.Sc. in education (HEPL) and an M.Sc. in kinesiology (University of Lausanne). He spent a decade authoring high-stakes school-leaving examinations and years researching educational assessment. His work on training clinical decision-making appeared in the NSCA’s Strength & Conditioning Journal (2026), and a companion framework is forthcoming in ACSM’s Health & Fitness Journal (2027). Reach him at admin@engramkinetics.com.
Every instructor has met this student. She can recite the thresholds, she aced the flashcards, her notes are immaculate — and then a case-based question lands in front of her and she picks the wrong option with total confidence. Test anxiety? A careless slip? Sometimes. More often, I’ve come to believe, it’s something else entirely: a decision problem wearing a knowledge costume.
We spend most of our teaching time building content — definitions, mechanisms, values, protocols. Certification exams, and the applied and coaching settings they stand in for, put much of their scored weight somewhere else: on what a student does with that content when a specific person’s data is on the table. Recognition and decision are different cognitive acts. A student can know perfectly well that systolic pressure should rise with workload during a graded test, and still sail past a stem where it keeps falling as the load climbs. The item isn’t asking her to recall the fact. It’s asking her to notice that a sustained fall against rising workload is a red flag, and to weigh what to do next. Knowing the number and making the right call for the person in front of you are two different skills. We tend to grade the first. The exam quietly tests the second.
Give the error a name
Here’s a small shift that changes how students study: when they miss an applied question, don’t mark it “wrong.” Name the reasoning trap that produced it.
Years of writing high-stakes examinations — and of sifting through the response data afterward — convinced me that wrong answers on decision-heavy items are rarely random. They cluster. The same few patterns return again and again: over-reading a single impressive data point, confusing the expected direction of a physiological response, anchoring on the first plausible option, stretching a rule past the edge of the situation it was built for. Left unnamed, each of these just feels like a bad day. Named, it becomes a pattern the student can watch for. A student who can say “I let one dramatic number drive a decision the client wasn’t ready for” has something to catch next time. A student who only knows she got it wrong has nothing to catch at all.
This is really just metacognition with better labels — but the labels do a lot of work. They turn a vague sense of failure into a specific, portable diagnosis.
Four moves you can steal on Monday
Little of this requires new tools or a redesigned syllabus. Mostly, it’s a change in what we ask.
Turn practice questions into diagnostics. After a missed item, resist “what’s the right answer?” and try “what pulled you toward the wrong one?” The answer is more often a reasoning pattern than a content gap — which means it’s fixable in a way that re-reading the chapter is not.
Teach decision rules, not just facts. Every threshold carries an implicit “so what?” When you hand students a loading range or a cutoff, ask what would have to be true about the person in front of them before they’d act on it. The fact is the easy part; the conditions that govern its use are the exam.
Let choices change the data. A branched scenario — one where each decision reveals the next piece of information — is hard to pattern-match against a memorized answer. Students have to reason forward instead of backward from the option that “looks right.”
Explain the error before the fix. Students learn more from seeing why an attractive wrong answer was attractive than from simply being handed the correct one. Feedback that opens with the trap, then resolves it, sticks.
Why it counts as active learning
What these four moves share is that they put the student’s own reasoning on the table as the object of study. Instead of absorbing content and hoping it transfers, students build a personal catalog of the traps they actually fall into — and start recognizing those traps in novel cases. That transfer, from a labeled error on a classroom item to a real decision under uncertainty, is exactly what we want applied reasoning to do.
It also tends to be more engaging, for an unglamorous reason: students are genuinely curious about their own mistakes in a way they rarely are about a list of correct answers. If we’re honest, so are we.
The half that’s hardest to teach
Content gets students to the door of the exam — and of the work waiting beyond it. Decisions get them through. Both matter, but the second half is the harder one to teach, precisely because it’s harder to put on a slide. Naming cognitive errors is one small, portable way to start closing that gap, and it costs nothing but a change of habit in how we give feedback.
I’d genuinely like to hear how others in this group build decision-making into their courses. The field feels wide open, and most of the good ideas I’ve encountered have come from comparing notes.


