Learning Loop & Chapter Build Workflow
Program learning loop
LEARN
Build a clear mental model: terminology, purpose, relationships, processes, roles, artifacts, tools, implementation concerns, metrics, and examples.
RECALL
Retrieve without looking using short-answer prompts, blank diagrams, fill-the-structure exercises, and teach-back.
COMPARE
Place similar concepts side by side and identify the deciding distinction.
APPLY
Use business scenarios: identify the problem, leading Knowledge Area, involved role, and appropriate activity/process/artifact.
TEST
Use realistic original multiple-choice questions with strong distractors and later timed sets.
DIAGNOSE
Record what went wrong: knowledge gap, terminology confusion, role confusion, sequence error, missed qualifier, elimination problem, overthinking, time pressure, lookup failure, etc.
REVISIT
Schedule the concept to return through spaced and mixed practice until performance is stable.
Master workflow for every chapter
- Read the complete controlling DMBOK chapter.
- Create an internal chapter blueprint before drafting.
- Map the chapter to Fundamentals weighting and relevant specialist context.
- Identify prerequisite knowledge.
- Identify confusion pairs/clusters.
- Build the Guided Learning Guide first.
- Build retrieval/comparison artifacts from the guide and source, not memory alone.
- Build scenarios requiring diagnosis and best-action reasoning.
- Build original MCQs spanning recall, understanding, application, role, sequence, comparison, and best-answer reasoning.
- Run chapter QC against the source and blueprint.
- After learner use, update future drills based on actual mistakes.
Build sequence for the whole program
- Infrastructure — dashboard, error taxonomy, review schedule, question-bank schema, naming conventions, control system.
- Chapter 1 prototype — build and validate the complete Chapter 1 package.
- Fundamentals core — build Chapters 2–14 with extra depth for the high-weight domains.
- Supporting chapters — Chapters 15–17 with targeted role, maturity, change, and cross-domain work.
- Cross-domain/confusion layer — Confusion Book, battle rounds, mixed scenarios, integrated cases.
- Exam conditioning — timed sprints, mixed mocks, lookup drills, full-length simulations.
- Personalized repair — shift from content production to error-driven remediation.
- Final rapid review — generated from weighted mastery and actual error history.
Operational prompt
Use the New Chapter Build Prompt when a chapter has not yet been built, and the Existing Chapter Audit Prompt when improving an existing package.
Source: 00A-01, Sections 3, 4, 14, and 15.