Concept — The Applied Learning Cycle (6 stages)

← tree index · overview

The unifying spine. Every revised flow uses the same 6 phases. Naming them on every dashboard, email, and screen header gives engineering, design, content, and the Instructional Strategist one shared vocabulary — and a precise way to ask “where did we lose this cohort?”

The six phases

# Phase What’s happening What every role must produce here
1 Prepare Build readiness + context Participant pre-work submitted; IS has read it; LA context profile updated
2 Engage Introduce + model learning Attendance + active-engagement signal; IS tailors to cohort
3 Practice Low-stakes try in session Written action plan (what / when / with whom); observable practice in role-play, modeling, or planning
4 Apply First real-world attempt within 48 hrs Evidence of application (artifact, observation, self-report); time-to-first-application logged
5 Reflect What worked / didn’t Post-application reflection + survey + identified gap
6 Adjust Refine + plan next cycle Repeat applications toward mastery; supplemental resources released; next-engagement signal surfaced

Why these names (the v2 → v3 change)

The design principle this enforces

Every phase, on every role’s dashboard, must answer: “What’s the next behavior I expect from this user — and what triggers fire if it doesn’t happen?”

Each phase therefore pairs a produced behavior with an intervention trigger (the absence of that behavior). The pairing is the contract between this concept and the intervention layer.

The loop-back (this is the business model)

Adjust loops back to Prepare. The next-engagement signal surfaced in Adjust is what converts each cycle into a renewal/expansion opportunity. See business loop.

Cross-role view

In the master swimlane (Figure 1), columns are phases, rows are roles, and each cell is what that role does in that phase. Key properties: