Instructional Design & Course Architecture
Parent: Technical Instruction & Engineering Education · Published reference · snapshot 2026-09-08 · skill technical-instruction/references/instructional-design-course-architecture.md
↓ Facts as markdownall context files
The discipline of designing multi-lesson courses and curricula: the layer between learning science (mechanisms of how people learn) and single-tutorial craft (how to write one how-to guide). This skil
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Instructional Design & Course Architecture
- The discipline of designing multi-lesson courses and curricula: the layer between learning science (mechanisms of how people learn) and single-tutorial craft (how to write one how-to guide). This skill covers process models, curriculum architecture tools, objective-writing frameworks, and course-format decisions for technical and engineering training contexts. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Boundary contracts: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Learning science mechanisms (cognitive load, retrieval practice, spacing, deliberate practice) → applied-psychology [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Tutorial / how-to / reference writing craft → technical-writing-craft [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Certification exam design and psychometrics → assessment-certification-design [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Training delivery craft, facilitation, live lab instruction → technical-training-delivery [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Program evaluation, ROI, Kirkpatrick → not yet a separate skill; out of scope here [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Teaching troubleshooting as a pedagogy → teaching-troubleshooting-diagnostic-reasoning [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
- Typical invocation outputs: when asked to design a course from scratch, produce a course design document (TO/EO hierarchy, scope-and-sequence, format decision, prerequisite map). When asked to audit an existing course, produce an alignment audit table (ILO verb | TLA description | AT type | match Y/N) plus a findings list. When asked for a lesson plan, produce a Gagné event map for the module. Format adapts to the scope of the request; ask for clarification only when the target audience and learning objective are both absent. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#instructional-design-course-architecture]
Contents
- Process Models: ADDIE, SAM, Dick & Carey [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Backward Design / Understanding by Design [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Curriculum Architecture: Scope, Sequence, Prerequisite Mapping [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Chunking and Sequencing Technical Content [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Writing Learning Objectives as a Design Tool [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Bloom's Taxonomy as a Design Tool [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Terminal vs. Enabling Objective Hierarchies [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Constructive Alignment: ILOs → TLAs → ATs [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Gagné's Nine Events of Instruction [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Merrill's First Principles and the Pebble-in-the-Pond Model [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Course Format Decisions: Self-Paced vs. Cohort vs. Blended [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Anti-Patterns [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
- Quick Reference [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#contents]
1. Process Models: ADDIE, SAM, Dick & Carey
- Three process models dominate instructional design practice. They differ on sequencing, iteration, documentation, and stakeholder involvement - not on underlying learning science. Choose based on content stability, timeline, documentation requirements, and team structure. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#1-process-models-addie-sam-dick-carey]
ADDIE
- ADDIE (Analysis–Design–Development–Implementation–Evaluation) originated in 1975 at Florida State University under U.S. Army contract. It functions as a meta-framework describing what must happen in any instructional design project without prescribing how to do it. Most other models are recognizable as ADDIE variants. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Analysis - identify the instructional problem, learner characteristics, existing skill gaps, delivery constraints [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Design - map learning objectives to assessment strategies; select instructional approach [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Development - create content assets (modules, simulations, facilitator guides); pilot test [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Implementation - deliver instruction; train facilitators [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Evaluation - formative (ongoing quality checks within phases) + summative (outcome assessment post-delivery) [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- The "ADDIE is a waterfall" characterization is partially a myth: the model never prohibited iteration or mid-phase revision; that rigidity was an implementation choice, not a structural constraint. Contemporary ADDIE explicitly accommodates rapid prototyping as formative feedback within phases. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
- Best fit for technical/engineering training: compliance-mandated curricula, safety certification, regulatory onboarding, content with a long shelf-life, contexts requiring documentation trails. Weakest fit: fast-changing technical content (new platform releases, agile workflows); tight timelines. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#addie]
SAM (Successive Approximation Model)
- Introduced by Michael Allen (Allen Interactions) in Leaving ADDIE for SAM (Allen & Sites, ASTD Press, 2012), explicitly as a response to waterfall-ADDIE dynamics. Draws from agile software development, prioritizing rapid prototyping and continuous stakeholder feedback over upfront planning. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#sam-successive-approximation-model]
- SAM1 (smaller projects): Preparation (rapid info gathering + "Savvy Start" brainstorm) → Iterative Design (rapid prototyping + stakeholder review) → Iterative Development (alpha/beta/gold with embedded testing) [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#sam-successive-approximation-model]
- SAM2 (larger projects): same core with added project management scaffolding [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#sam-successive-approximation-model]
- Core differentiator: produce something usable at every stage so stakeholders interact with real artifacts, not abstract specs. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#sam-successive-approximation-model]
- Best fit: evolving technical content; eLearning for new tooling; agile development contexts; tight timelines. Weakest fit: certification-track programs requiring audit trails, regulatory compliance documentation, or large-scale replicability. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#sam-successive-approximation-model]
Dick & Carey Systems Model
- Published by Walter Dick and Lou Carey in The Systematic Design of Instruction (1978). A fully elaborated ten-component procedural model grounded in systems theory: instructor, learners, materials, delivery, activities, and environment are treated as interdependent components of a coherent system. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#dick-carey-systems-model]
- Ten components (abbreviated): Identify instructional goals → conduct instructional analysis → analyze learners and contexts → write performance objectives → develop assessment instruments → develop instructional strategy → develop/select materials → design and conduct formative evaluation (1:1, small group, field trial) → revise instruction → design summative evaluation. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#dick-carey-systems-model]
- Components 1–9 are explicitly iterative and parallel; formative evaluation feeds back into earlier steps continuously. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#dick-carey-systems-model]
- Best fit: complex competency-based programs; technical certification requiring rigorous performance-objective alignment; blended learning with multiple modalities. Weakest fit: small-scale or time-constrained projects; teams without dedicated instructional design expertise. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#dick-carey-systems-model]
2. Backward Design / Understanding by Design
- Understanding by Design (UbD) - Wiggins & McTighe (ASCD, 1998) - inverts conventional planning: define what students must ultimately do first, then design evidence of that performance, and only then plan instruction. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#2-backward-design-understanding-by-design]
Three Stages
- Stage 1 - Desired Results: Establish specific measurable learning objectives and, deeper, "enduring understandings" (transferable big ideas expressed as declarative sentences, e.g., "Systems have emergent properties their components do not") and "essential questions" (open-ended, recurring, thought-provoking questions that anchor the course). The six facets of understanding - explain, interpret, apply, have perspective, empathize, have self-knowledge - inform what evidence of understanding looks like. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Stage 2 - Acceptable Evidence: Determine how learners will demonstrate understanding before designing any instruction. Distinguishes performance tasks (authentic applications) from other evidence (quizzes, reflections). Sequencing this before Stage 3 prevents "teaching to the activity." [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Stage 3 - Learning Plan: Design instruction last, in service of Stage 2 evidence requirements. The WHERETO heuristic guides design: Where and Why, Hook, Equip and Explore, Rethink and Revise, Evaluate, Tailor, Organize. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Scaling UbD to curriculum: the backward design logic applies recursively - program-level transfer goals are established first, then courses are designed to build toward them, then units within courses. McTighe and Wiggins explicitly frame UbD as a "unit-planning process" that scales to full curriculum design. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Requires upfront commitment to fixed objectives, which can crowd out emergent or personalized learning pathways [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Highly dependent on the designer's disciplinary grasp - if you cannot distinguish enduring understandings from topic coverage, the output is misaligned curricula [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
- Expensive to adopt institutionally - working backward against content-first instincts requires significant professional development [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#three-stages]
Scope and Sequence
- Scope defines breadth and depth of coverage. Sequence determines the order of content presentation, ensuring learning is cumulative and builds systematically. A well-designed scope and sequence ensures prerequisite skills appear before courses that require them. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#scope-and-sequence]
Prerequisite Mapping as a Directed Graph
- A curriculum is a directed acyclic graph (DAG): courses are nodes, prerequisite relationships are directed edges. Three structural roles emerge from this framing: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#prerequisite-mapping-as-a-directed-graph]
- Hub courses - connect many subsequent topics; single point of failure if poorly taught [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#prerequisite-mapping-as-a-directed-graph]
- Bridge courses - connect otherwise isolated clusters [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#prerequisite-mapping-as-a-directed-graph]
- Source courses - foundational material with no prerequisites but many dependents [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#prerequisite-mapping-as-a-directed-graph]
- Mapping the prerequisite graph explicitly surfaces structural bottlenecks before the curriculum is built. A hub course whose prerequisites are unclear or inconsistently enforced creates cascade failures in all downstream courses. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#prerequisite-mapping-as-a-directed-graph]
Curriculum Mapping
- A curriculum map is a visual matrix: courses vs. learning outcomes, marked at Introduction / Reinforcement / Mastery (I/R/M) levels. It verifies that critical competencies are: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#curriculum-mapping]
- Introduced early in the sequence [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#curriculum-mapping]
- Reinforced across multiple courses [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#curriculum-mapping]
- Demonstrated at mastery level before program completion [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#curriculum-mapping]
- Missing or misplaced coverage is visible as matrix gaps. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#curriculum-mapping]
4. Chunking and Sequencing Technical Content
- Chunking groups content into manageable units grounded in working memory limits. Practical guidance: target 1–3 learning objectives per module; end each chunk with a practice activity (knowledge check, scenario, reflection) to facilitate transfer to long-term memory. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#4-chunking-and-sequencing-technical-content]
- Sequencing approaches for technical content: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#4-chunking-and-sequencing-technical-content]
- Standard pattern for technical/engineering content: Declarative (what it is) → Procedural (how to do it) → Situated (when and why to apply it). [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#4-chunking-and-sequencing-technical-content]
- Key failure mode: over-loading declarative knowledge before procedural application - the "front-loaded lecture" where learners process concepts they cannot yet connect to practice. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#4-chunking-and-sequencing-technical-content]
The ABCD Format (Mager)
- Robert F. Mager's Preparing Instructional Objectives (1962) established behavioral objectives as a design tool. The ABCD expansion makes all four design elements explicit: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#the-abcd-format-mager]
- Each component constrains a downstream decision. Once Condition is fixed ("without reference materials"), instructional practice must mirror that constraint. Once Degree is fixed ("with no more than one error"), the rubric writes itself. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#the-abcd-format-mager]
- Well-formed technical example: Given access to the Atlas UI and current index configurations [C], database administrators [A] will identify the three indexes most likely causing collection scan warnings [B] by selecting all three correctly from a provided list of ten candidates [D]. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#the-abcd-format-mager]
- Conditions opener patterns: Given a… / Without reference to… / Using the standard operating procedure… / Given access to the cluster dashboard… [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#the-abcd-format-mager]
When to simplify
- Not every objective requires all four components spelled out. Explicitly state Condition when the performance constraint differs from daily work context; explicitly state Degree when a pass/fail line must be drawn for certification or safety-critical outcomes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#when-to-simplify]
6. Bloom's Taxonomy as a Design Tool
- Bloom's Revised Taxonomy (Anderson & Krathwohl, 2001) is, for course designers, a verb selection and objective leveling tool - use it when writing learning objectives and sequencing lessons, not as a theory of cognition (that belongs in applied-psychology). The 2001 revision replaced nouns with action verbs, making it directly actionable for objective writing. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
- Taxonomy as a dependency chain: a learner who cannot remember configuration syntax cannot apply it; one who cannot analyze a failure trace cannot evaluate whether an architectural change is warranted. This chain is a curriculum pacing heuristic. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
- Sequencing rule: lesson-level verbs must be at or below the course-level verb's Bloom's level - never higher. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
- Verb table for technical training: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
- Common design defect: training assessments test at Remember or Understand when the job demands Apply or Analyze. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
- Assessment alignment note: objective-to-assessment alignment (ILO verb → AT demand) is covered in Section 8 (Constructive Alignment). Psychometrics, item writing, and IRT analysis belong in assessment-certification-design. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#6-blooms-taxonomy-as-a-design-tool]
7. Terminal vs. Enabling Objective Hierarchies
- Terminal Objective (TO): the capstone performance the learner must achieve by module/course end. One TO per module scope is a practical limit (5–9 TOs per full course). TOs describe outcomes, not activities. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
- Enabling Objectives (EOs): prerequisite sub-skills derived by asking recursively: "What must the learner already be able to do to achieve this?" The result is a directed graph of prerequisites - not a flat list. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
- Design payoff: once the hierarchy is drawn, the instructional sequence is largely determined. EOs that are prerequisites for other EOs come first; EOs with no dependents can be taught in any order; the TO is assessed last. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
- Derivation method (subordinate skills analysis): Start with the TO. Ask "What must they know/do to achieve this?" for each answer. Continue recursively. Validate the resulting graph with subject-matter experts. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
- Worked example - Atlas slow-query diagnosis: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
- EO1–EO3 have no dependencies on each other and can be taught in any order. EO4 requires EO1–EO3 before it can be practiced. The TO is assessed only after EO4 is demonstrated. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#7-terminal-vs-enabling-objective-hierarchies]
8. Constructive Alignment: ILOs → TLAs → ATs
- John Biggs' constructive alignment (1996) coordinates three components so they address the same learning agenda: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#8-constructive-alignment-ilos-tlas-ats]
- Design sequence: ILO first → TLA that practices the ILO verb → AT that measures the same verb under the ILO conditions. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#8-constructive-alignment-ilos-tlas-ats]
- Backwash mechanism: learners tend to learn what they believe will be assessed. A misaligned course (objective says analyze, assessment tests recall) produces learners who study for recall and never practice analysis. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#8-constructive-alignment-ilos-tlas-ats]
- Alignment audit: map ILO verbs → TLA activities → AT demands. Mismatches at cognitive demand levels are the primary finding. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#8-constructive-alignment-ilos-tlas-ats]
- Limitations: When mandated top-down as a quality-assurance tool, constructive alignment can become a paperwork exercise disconnected from actual learning; it specifies the architecture but offers limited guidance on which specific TLAs to select. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#8-constructive-alignment-ilos-tlas-ats]
9. Gagné's Nine Events of Instruction
- Robert Gagné's framework pairs nine external instructional events with internal cognitive processes. Operates as both a lesson design scaffold and a lesson audit tool. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#9-gagnés-nine-events-of-instruction]
- Three-phase structure: Preparation (Events 1–3) → Acquisition (Events 4–6) → Transfer (Events 7–9). [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#9-gagnés-nine-events-of-instruction]
- Most commonly skipped - and an anti-pattern when absent: Event 9 (Retention and Transfer). The framework provides a structural reminder to design for transfer, not just comprehension; skipping it is listed as an explicit anti-pattern in Section 12. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#9-gagnés-nine-events-of-instruction]
- Sequence guidance: for short modules, several events can be compressed into a single activity. Events should not be permanently omitted; if an event is absent, the designer should document an explicit reason. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#9-gagnés-nine-events-of-instruction]
- Key limitation: the framework does not include a motivation principle; Keller's ARCS model (Attention, Relevance, Confidence, Satisfaction) was developed explicitly to fill this gap. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#9-gagnés-nine-events-of-instruction]
10. Merrill's First Principles and the Pebble-in-the-Pond Model
- M. David Merrill (2002) synthesized five invariant principles from a review of major ID theories. All five are simultaneously necessary - no single principle is sufficient without the others. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#10-merrills-first-principles-and-the-pebble-in-the-pond-model]
- Pebble-in-the-Pond model: Merrill's practical design process radiates outward from a real-world problem: design problem sequences first, then component skills, then demonstrations and practice, then integration activities, then assessments - in that order. Inverts the conventional outline-first approach. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#10-merrills-first-principles-and-the-pebble-in-the-pond-model]
- Design reorientation: the first question shifts from "What content must I cover?" to "What real-world problem must learners be able to solve?" [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#10-merrills-first-principles-and-the-pebble-in-the-pond-model]
- Limitations: resource-intensive to implement; presupposes design autonomy to restructure course around problem sequences (not always available in institutional/compliance contexts); less explicit about how to select specific activities than what principles to honor. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#10-merrills-first-principles-and-the-pebble-in-the-pond-model]
11. Course Format Decisions: Self-Paced vs. Cohort vs. Blended
- Course format is an architectural decision that determines which learning activities are feasible and what learner behaviors the design can depend on. ILT = Instructor-Led Training (synchronous, cohort-based delivery). [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#11-course-format-decisions-self-paced-vs-cohort-vs-blended]
- Design principle for blended: use self-paced for declarative knowledge and easily codified procedural knowledge; reserve synchronous for situated knowledge and procedural content requiring real-time instructor correction. [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#11-course-format-decisions-self-paced-vs-cohort-vs-blended]
13. Quick Reference
- When to use which process model: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Stable content, compliance required, documentation trail needed → ADDIE [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Fast-changing content, agile context, tight timeline, iterative stakeholder feedback → SAM [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Complex competency-based program, rigorous performance-objective alignment, blended learning → Dick & Carey [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Typical course design deliverables: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Course design document - TO/EO hierarchy, scope-and-sequence, format decision, assessment strategy, prerequisite map [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Module blueprint - objectives (ABCD), Gagné event mapping, activity type per objective, alignment audit table [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Alignment audit table - ILO verb | TLA description | AT type | match? (Y/N) [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Prerequisite graph - DAG diagram with hub/bridge/source roles labeled [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Design from scratch: start with transfer goals → TO/EO hierarchy → process model selection → scope-and-sequence → module blueprints [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Audit an existing course: run the alignment audit table; flag ILO/TLA/AT mismatches; apply Gagné event check per module; compare against Merrill's five principles [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Single-module design: write the TO first; derive EOs via subordinate skills analysis; map Gagné events; confirm format matches stakes [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Objective quality checklist: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Written from learner's perspective (not "the lesson will cover") [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Behavior verb is observable (not vague state verbs) [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Condition specified when it differs from daily work context [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Degree stated when a pass/fail line is required [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Bloom's level matches actual job performance demand [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Alignment audit steps: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- For each, identify the TLA that practices that verb [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- For each, identify the AT that requires that verb [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Flag any ILO with no TLA and/or no AT → gap in the design [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Curriculum architecture checklist: [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Transfer goals defined at program level before course design begins [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Prerequisite graph drawn as a DAG; hub courses identified [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] I/R/M levels mapped across courses for each critical competency [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Chunking targets 1–3 objectives per module [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- [ ] Sequencing follows declarative → procedural → situated pattern [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
- Full source citations: references/instructional-design-course-architecture.md (28 sources). [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#13-quick-reference]
Routing Detail
- Measuring whether the training you designed actually worked (Kirkpatrick levels, Phillips ROI, training transfer, L&D dashboards) → learning-measurement-evaluation [archived source: https://llms-explorer.com/sources/mdb-context-hub/instructional-design-course-architecture/#routing-detail]
Where this helps
- Designing a technical certification program or engineering onboarding curriculum where content must be sequenced so prerequisite skills are taught before the skills that depend on them (prerequisite mapping as a DAG). [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Choosing a process model for a training project — ADDIE for stable, compliance-driven content with a documentation trail; SAM for fast-changing content under a tight, iterative timeline; Dick & Carey for complex, competency-based programs needing rigorous performance-objective alignment. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Auditing an existing course for backwash — checking whether its objectives (ILOs), activities (TLAs), and assessments (ATs) actually test what was taught, since learners tend to study for whatever they believe will be assessed. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Writing a well-formed learning objective for a technical skill using Mager's ABCD format (Audience, Behavior, Condition, Degree) so the objective is observable and gradeable rather than vague. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
How to apply this
- Draw the curriculum as a prerequisite DAG first, identifying hub courses (many downstream dependents), bridge courses (connecting otherwise isolated clusters), and source courses (no prerequisites) before deciding on a teaching sequence. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Apply backward design: define the terminal objective and how learners will demonstrate it (the assessment) before designing any instructional activities, instead of starting from "what content should I cover." [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Use Gagné's Nine Events as a lesson-audit checklist, checking specifically for Event 9 (retention and transfer) — the most commonly skipped event, and treated as an anti-pattern when it's dropped without an explicit rationale. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Match course format to knowledge type: use self-paced delivery for declarative and easily codified procedural knowledge, and reserve synchronous cohort time for situated knowledge and procedures that need real-time feedback. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Antipatterns
- Front-loading declarative knowledge before any procedural application — the named "front-loaded lecture" failure mode, where learners process concepts they can't yet connect to practice. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Writing a lesson-level objective verb above the course-level objective's Bloom's-taxonomy level — the sequencing rule requires lesson verbs to sit at or below the course-level verb, never higher. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Permanently skipping Gagné's Event 9 (retention and transfer) instead of documenting an explicit rationale for omitting it — the framework treats this omission as a structural warning sign, not a neutral shortcut. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Misaligning ILOs, TLAs, and ATs — for example, an objective that says "analyze" but an assessment that only tests recall — which produces learners who study for recall and never practice the actual target skill. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Limitations
- Merrill's First Principles model is resource-intensive to implement and presupposes design autonomy to restructure a course around real-world problem sequences, autonomy that isn't always available in institutional or compliance-bound contexts. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- ADDIE's stage-gated documentation trail suits stable, compliance-driven content but is a poor fit for fast-changing content or tight timelines, which is exactly the gap SAM's iterative, prototype-first process was built to fill. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A curriculum DAG makes hub courses a single point of failure — if a hub course (one with many downstream dependents) is poorly taught, every course that depends on it inherits the gap. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- The ABCD objective format doesn't require every objective to spell out all four components; over-specifying Condition and Degree for objectives that don't need them adds documentation overhead without a matching design benefit. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Children
- ADDIE (frontier)
- SAM (Allen) (frontier)
- Dick & Carey systems model (frontier)
- Backward Design / UbD (frontier)
- Scope-and-Sequence & Prerequisite DAGs (frontier)
- Learning Objectives (ABCD / Mager, Bloom's verbs) (frontier)
- Constructive Alignment (Biggs) (frontier)
- Gagné's Nine Events (frontier)
- Merrill's First Principles (frontier)
- Course Format Decisions (frontier)
Frontier under this node: ADDIE, Backward Design / UbD, Constructive Alignment (Biggs), Course Format Decisions, Dick & Carey systems model, Gagné's Nine Events, Learning Objectives (ABCD / Mager, Bloom's verbs), Merrill's First Principles, SAM (Allen), Scope-and-Sequence & Prerequisite DAGs