Concept — The Five Roles and Their Flows

← tree index · overview

Five roles, each with a verbatim v3 goal, each with a flow through the Applied Learning Cycle. Flows cross-reference each other: one role’s action is another’s trigger.

1. Participant — “Understands learning priorities and applies learning faster”

The behavioral subject. Their flow is where the payoff lives.

Onboarding: invited by Learning Admin → welcome email (branded, role-aware) → first-time users build a Learner Profile [F1] (grade, experience, content area, role) + platform tutorial; returning users sign in → Participant Dashboard.

Prepare: watch IS intro video [A2] (≤30s) → read workshop intro text [B1] (focus points + reminders, with TTS) → pulse check [C1, C2] (Likert + 3 MCQs, “diagnostic — not a test”) → pre-engagement handout. Post-workshop resources visible but locked/greyed [D1]. A pre-work readiness gate at 24h: if incomplete, auto-nudge fires and the participant is flagged on IS + LA dashboards.

Engage: attend (in-person / virtual / async) + engage with content.

Practice: practice during session (role-play / modeling / planning) → commit to an action plan (what / when / with whom).

Apply: decision gate — applied within 48h? - within 24h / 24–48h → on-time application logged → extension resources unlocked - delayed (>48h) → triggered nudge [G2] (microlearning + reminder) - attempted but failed → targeted support [G3] (microlearning + IS office hours)

Reflect: post-application reflection (evidence + obstacles + next try) → workshop survey → gate: survey complete? No → reminder + flag to LA; Yes → certificate unlocked + visible.

Adjust: IS releases locked resources [D2] → gate: continue applying over 5d / 4–6 wk? Yes → log additional applications toward mastery → profile updated with demonstrated competencies → next-engagement suggestions surfaced. Drifting → IS-scheduled follow-up nudges [G2] + LA reinforcement. End: cycle complete — faster time-to-apply.

Flow images: image2.png (Part 1), image3.png (Part 2), image4.png (Part 3).

2. Learning Administrator — “Reinforces learnings and realizes school impact sooner”

The single biggest role expansion in v3. The LA becomes a structured signal source, not just an attendance tracker. See the dedicated context layer concept.

Onboarding / Prepare: gate — School Context Profile exists? No → build it [A1–A5] (readiness 1–5, change-pressure tags, top-3 priorities, narrative note), save in <5 min, reusable; Yes → edit if needed (timestamped). Then per engagement, add a Cohort Snapshot [B1, B2] (attendee group, cohort note, expected participant count).

Monitor: logins + engagement indicators, pulse-check aggregates [C3] (patterns only, no names, no scores), gaps in participation.

Adjust (now first-class): reinforcement prompts, encourage survey completion, reinforce application expectations. Cohort outcomes view: completion, application rate + speed, repeat-application rate, school-impact evidence — exportable, shown to leadership to justify the investment.

Guardrails: entire context entry < 5 min; narrative note warns against names/confidential personnel details; UI carries “This helps tailor the experience. This is not evaluative.”

Flow images: image9.png–image12.png (Parts 1–4).

3. Instructional Strategist (IS) — “Prepares more precisely and guides Participant Learning Path”

Onboarding: gate — intro video on file? No → record intro video [A1] (≤30s, max 45s) → submit to PM for approval → once approved, auto-associates to assigned schools/workshops.

Prepare — the Context Brief [C1] (visible ≥3 days before engagement) surfaces: - LA School Context Profile (readiness, change tags, top-3 priorities, narrative note) - Cohort Snapshot (attendee group, count) - Strategist Insights [E2–E4]: % logged in, % watched intro, pulse aggregates, notable outliers - cohort profile summary [F2]

This is the difference between a generic workshop and a responsive one.

Engage / Practice: deliver responsive to signals; facilitate practice + commitment-to-action.

Apply / Reflect / Adjust: “Mark complete” is a system action with three downstream effects — triggers (a) participant survey, (b) certificate eligibility, (c) the application-tracking window. Stuck-participant detection drives targeted intervention [G1/G2/G3]: respond async to reflections, schedule 1–3 follow-up nudges, recommend microlearning. Dashboard exposes time-to-first-application and the 24h/48h/5d thresholds directly. Release locked resources [D2].

Next-engagement signal feeds three places: the LA dashboard (LA champions the renewal), the PM queue (renewal/expansion surfaces in HubSpot), the Content Creator backlog (new microlearning gets prioritized).

Flow images: image5.png–image8.png (Parts 1–4).

4. Platform Manager (PM) — “Enables coherence” (NEW flow in v3)

Referenced in user stories but absent from prior flowcharts.

Flow images: image13.png–image16.png (Parts 1–4).

5. Content Creator — “Designs for application and reinforcement, not consumption” (NEW role, flow TBD)

v3 introduces the role but does not specify the day-to-day workflow. Recommended four responsibilities:

  1. Pre-engagement assets — workshop intro text (focus points + reminders) per B1, incl. TTS variants.
  2. Pulse-check authoring — the 3 MCQs per workshop, mapped to focus points, per C2.
  3. Microlearning library — reusable items the IS can recommend per G3, designed for application + reinforcement, not consumption.
  4. Gap-driven backlog — receive cohort-gap signals from PM + IS; prioritize new microlearning by observed patterns.

Before drafting a flow, answer two questions (see content-creator-role.md): 1. What signals from PM and IS would actually change what you build next? 2. What does “designed for application” mean in practice vs. “consumption-oriented”?