The CAIRN Learning Model™ keeps the loop that makes games compelling — clear goals, instant feedback, visible progress, calibrated challenge — and loses the game skin. Learners move forward when they've demonstrated mastery, not when the calendar says so.
Think about a typical new-hire program. Six to eight weeks, everyone in the same room, everyone on the same schedule. The completion criterion is attendance, not ability.
Everyone sits through week four because it is week four. Fast learners idle; struggling learners are swept forward before they're ready.
Curricula are linear because documents and calendars are linear — not because the knowledge is. Most of the line is an artifact of the delivery medium.
Sitting-and-listening produces boredom and poor retention. Meanwhile, well-designed games get people to voluntarily pour hours of focused effort into getting better at something.
The design question behind CAIRN: what would workplace training look like if it kept the engagement mechanics that make games compelling, discarded the game skin that makes them unpresentable in a corporate environment, and replaced schedule-based progression with mastery-based progression?
Every mastery unit is cleared the same way — fundamentals to automaticity, judgment in private, then the real thing with graduated autonomy.
Adaptive retrieval practice until the fundamentals are automatic. Misses surge in frequency; mastered items retire and return spaced. Speed counts — fluency is fast and accurate. A learner who has to think about the mechanics has no attention left for the work itself.
Realistic practice with an AI partner and a scored debrief — specific, immediate, private, judgment-free. The rehearsal room that used to require a scarce human role-player, now available on demand, as many reps as it takes.
Real work with graduated autonomy — observed first, coached next, then released with exception-based review, one unit at a time. The reward for mastering something isn't a badge. It's being trusted with the real thing.
The loop feeds the stack: evidence from all three loops assembles the case, and a human signs the clearance. Fast learners reach real work in a fraction of the scheduled time; struggling learners get what they currently never get — a facilitator with time to coach.
A cairn is a hand-stacked pile of stones that marks a route across open terrain where no trail exists. The metaphor carries the whole model:
Cairns stand at the points that matter; how you travel between them is your choice. Gate the true prerequisites — free everything else.
Mastery accumulates in small, discrete, verifiable units — each cleared unit a stone added to the stack.
Learners see each other, help each other, and reach the facilitator from anywhere. The social layer is in the name.
CAIRN borrows game mechanics, never game aesthetics. Outdoors and wayfinding — not arcade.
An implementation that violates them is not CAIRN, whatever it looks like.
CAIRN verifies recall, recognition, and fluency, and structures the path to demonstrated readiness. Judgment, soft skills, and applied performance need scenarios, practice, and human evaluation — and the release decision is always signed by a human. A deployment that quietly substitutes for those is an oversold deployment.
Both run entirely in your browser — nothing to install, nothing tracked, no sign-up.
Walk the territory as a learner: a navigable map of mastery units, the three-loop cycle inside a unit, the mini-map, scoped chat with facilitator reach, and a clearance moment. Five minutes tells you more than any deck.
Open the Prototype →The adaptive retrieval-practice engine with a generic content pack: miss-driven weighting, mastery retirement, targeted remediation of your personal trouble spots, and optional time pressure. Feel the loop for yourself.
Start the Drill →These demos show the model's mechanics with deliberately generic content. Real deployments pair the same engine and cycle with subject-matter content designed by the people who know the domain.
CAIRN is being developed in the open. Leave your email for occasional updates — design notes, demos, and pilot results as they land. If you lead L&D, onboarding, or enablement and this resonates — or you think it's wrong somewhere — I'd like to hear it.