The 7 principles (dimensions)
- Connected Micro-Knowledge™
Mechanic: 200–500-word units linked as a network, not a linear list.
User sees: short context that always points somewhere next.
Business gets: less drop-off; knowledge sticks because it’s revisited from new angles. - Rhythm-Through-Progress™
Mechanic: visible KPIs at every step (correct/incorrect, retries, coverage, experts met).
User sees: “I’m advancing” on each micro-action.
Business gets: higher completion; steadier pace through onboarding. - Guided-by-Mind™
Mechanic: virtual experts with role, avatar, and voice steer decisions.
User sees: dialogue, not lecture.
Business gets: applied judgment (not just recall) in realistic constraints. - Context-to-Practice™
Mechanic: every concept sits inside a case or scene.
User sees: “show me, then let me try.”
Business gets: transfer to work (decisions improve in similar real tasks). - Micro-Action Learning™
Mechanic: 1 concrete action per node (choose / match / mark / drag-drop / short input).
User sees: tiny tasks with instant feedback.
Business gets: event-level evidence, not just completion. - Focus-by-Micro-Choice™
Mechanic: 2–4 meaningful options often, plus reinforcement loops.
User sees: agency without overwhelm.
Business gets: engagement + orientation in the domain (multiple good paths to mastery). - Momentum Pulse™
Mechanic: micro-rituals for start/finish of a node (framing, success, nudge).
User sees: many small wins.
Business gets: reduced fatigue; consistent progress day-to-day.
The 3 meta-principles (architecture)
A) Adaptive Complexity Flow™
Rule: each node branches “slightly harder” and “slightly easier” (+Δ/−Δ).
Engine does: balances cognitive load; avoids grind or boredom.
Effect: sustained pace; fewer stalls; better retention.
B) XYZ Interaction Lattice™
Rule: forward-only route over triples (X–Y–Z), with built-in 3-node loops.
Engine does: keeps motion forward; repeats concepts in new contexts without backtracking.
Effect: mastery through variation; scalable to any domain (EPC, HSE, Ops, PM, Sales).
C) Outcome Traceability & Verifiable Credentials™
Rule: log every event → update competency vector p(topic) → issue QR-verifiable certificate.
Engine does: turns clicks/choices/notes into a skill record HR can trust.
Effect: “proof of ability,” not just “course completed.”
What a manager notices in week one
- Learners finish more nodes per sitting (short, connected steps).
- Conversations with virtual experts surface judgment gaps early.
- KPI panel shows where people slow down (topics, experts, domains).
- Reinforcement loops close the gaps without rewinding the whole course.
Pilot KPIs we align to (and define clearly)
- Completion / Retention: % who finish the micro-route.
- Time-to-Productivity: weeks to first independent task(s) in the target project.
- Post-training Accuracy: decision quality on control micro-cases.
- Orientation Gain: improvement in navigating domains/experts/topics.
- Coverage: required topics/domains/experts achieved per learner.
- Verified Certificates: % issued with QR/hash after meeting thresholds.
Design notes (add these visuals on the page)
- Route vs Course: linear module vs node graph with 2–4 options + loop icons.
- One node card: context, expert chat (4–6 turns), 1 action, feedback, next steps.
- Evidence pipeline: Event Log → p(topic) → KPI/Coverage → QR-verifiable certificate.
- Adaptive flow sketch: split arrows +Δ/−Δ from the same node.
Business outcome in one line
Higher completion, faster time-to-productivity, less dead content, and HR-grade data for decisions—because the route and the data are the core, not an afterthought.
Innovation that makes people smarter
