Instructional Design & Course Architecture
Parent: Technical Instruction & Engineering Education · researched 2026-06-16T22:31:20.823Z· 28 sources · 10 concepts · skill 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 skil
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. [source]
- Boundary contracts: [source]
- Learning science mechanisms (cognitive load, retrieval practice, spacing, deliberate practice) → applied-psychology [source]
- Tutorial / how-to / reference writing craft → technical-writing-craft [source]
- Certification exam design and psychometrics → assessment-certification-design [source]
- Training delivery craft, facilitation, live lab instruction → technical-training-delivery [source]
- Program evaluation, ROI, Kirkpatrick → not yet a separate skill; out of scope here [source]
- Teaching troubleshooting as a pedagogy → teaching-troubleshooting-diagnostic-reasoning [source]
- 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. [source]
Contents
- Process Models: ADDIE, SAM, Dick & Carey [source]
- Backward Design / Understanding by Design [source]
- Curriculum Architecture: Scope, Sequence, Prerequisite Mapping [source]
- Chunking and Sequencing Technical Content [source]
- Writing Learning Objectives as a Design Tool [source]
- Bloom's Taxonomy as a Design Tool [source]
- Terminal vs. Enabling Objective Hierarchies [source]
- Constructive Alignment: ILOs → TLAs → ATs [source]
- Gagné's Nine Events of Instruction [source]
- Merrill's First Principles and the Pebble-in-the-Pond Model [source]
- Course Format Decisions: Self-Paced vs. Cohort vs. Blended [source]
- Anti-Patterns [source]
- Quick Reference [source]
- Full source citations: references/instructional-design-course-architecture.md (28 sources). [source]
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. [source]
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. [source]
- Analysis - identify the instructional problem, learner characteristics, existing skill gaps, delivery constraints [source]
- Design - map learning objectives to assessment strategies; select instructional approach [source]
- Development - create content assets (modules, simulations, facilitator guides); pilot test [source]
- Implementation - deliver instruction; train facilitators [source]
- Evaluation - formative (ongoing quality checks within phases) + summative (outcome assessment post-delivery) [source]
- 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. [source]
- Best fit for technical/engineering training: compliance-mandated curricula, safety certification, regulatory onboarding, content with a long shelf-life, contexts requiring documentation trails. [source]
- Weakest fit: fast-changing technical content (new platform releases, agile workflows); tight timelines. [source]
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. [source]
- SAM1 (smaller projects): Preparation (rapid info gathering + "Savvy Start" brainstorm) → Iterative Design (rapid prototyping + stakeholder review) → Iterative Development (alpha/beta/gold with embedded testing) [source]
- SAM2 (larger projects): same core with added project management scaffolding [source]
- Core differentiator: produce something usable at every stage so stakeholders interact with real artifacts, not abstract specs. [source]
- Best fit: evolving technical content; eLearning for new tooling; agile development contexts; tight timelines. [source]
- Weakest fit: certification-track programs requiring audit trails, regulatory compliance documentation, or large-scale replicability. [source]
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. [source]
- 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. [source]
- Components 1–9 are explicitly iterative and parallel; formative evaluation feeds back into earlier steps continuously. [source]
- Best fit: complex competency-based programs; technical certification requiring rigorous performance-objective alignment; blended learning with multiple modalities. [source]
- Weakest fit: small-scale or time-constrained projects; teams without dedicated instructional design expertise. [source]
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. [source]
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. [source]
- 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." [source]
- 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. [source]
- 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. [source]
- Requires upfront commitment to fixed objectives, which can crowd out emergent or personalized learning pathways [source]
- Highly dependent on the designer's disciplinary grasp - if you cannot distinguish enduring understandings from topic coverage, the output is misaligned curricula [source]
- Expensive to adopt institutionally - working backward against content-first instincts requires significant professional development [source]
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. [source]
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: [source]
- Hub courses - connect many subsequent topics; single point of failure if poorly taught [source]
- Bridge courses - connect otherwise isolated clusters [source]
- Source courses - foundational material with no prerequisites but many dependents [source]
- 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. [source]
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: [source]
- Introduced early in the sequence [source]
- Reinforced across multiple courses [source]
- Demonstrated at mastery level before program completion [source]
- Missing or misplaced coverage is visible as matrix gaps. [source]
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. [source]
- Sequencing approaches for technical content: [source]
- Standard pattern for technical/engineering content: Declarative (what it is) → Procedural (how to do it) → Situated (when and why to apply it). [source]
- Key failure mode: over-loading declarative knowledge before procedural application - the "front-loaded lecture" where learners process concepts they cannot yet connect to practice. [source]
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: [source]
- 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. [source]
- 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]. [source]
- Conditions opener patterns: Given a… / Without reference to… / Using the standard operating procedure… / Given access to the cluster dashboard… [source]
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. [source]
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. [source]
- 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. [source]
- Sequencing rule: lesson-level verbs must be at or below the course-level verb's Bloom's level - never higher. [source]
- Verb table for technical training: [source]
- Common design defect: training assessments test at Remember or Understand when the job demands Apply or Analyze. [source]
- 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. [source]
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. [source]
- 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. [source]
- 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. [source]
- 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. [source]
- Worked example - Atlas slow-query diagnosis: [source]
- 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. [source]
8. Constructive Alignment: ILOs → TLAs → ATs
- John Biggs' constructive alignment (1996) coordinates three components so they address the same learning agenda: [source]
- Design sequence: ILO first → TLA that practices the ILO verb → AT that measures the same verb under the ILO conditions. [source]
- 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. [source]
- Alignment audit: map ILO verbs → TLA activities → AT demands. Mismatches at cognitive demand levels are the primary finding. [source]
- 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. [source]
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. [source]
- Three-phase structure: Preparation (Events 1–3) → Acquisition (Events 4–6) → Transfer (Events 7–9). [source]
- 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. [source]
- 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. [source]
- 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. [source]
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. [source]
- 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. [source]
- Design reorientation: the first question shifts from "What content must I cover?" to "What real-world problem must learners be able to solve?" [source]
- 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. [source]
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). [source]
- 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. [source]
13. Quick Reference
- When to use which process model: [source]
- Stable content, compliance required, documentation trail needed → ADDIE [source]
- Fast-changing content, agile context, tight timeline, iterative stakeholder feedback → SAM [source]
- Complex competency-based program, rigorous performance-objective alignment, blended learning → Dick & Carey [source]
- Typical course design deliverables: [source]
- Course design document - TO/EO hierarchy, scope-and-sequence, format decision, assessment strategy, prerequisite map [source]
- Module blueprint - objectives (ABCD), Gagné event mapping, activity type per objective, alignment audit table [source]
- Alignment audit table - ILO verb | TLA description | AT type | match? (Y/N) [source]
- Prerequisite graph - DAG diagram with hub/bridge/source roles labeled [source]
- Design from scratch: start with transfer goals → TO/EO hierarchy → process model selection → scope-and-sequence → module blueprints [source]
- 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 [source]
- Single-module design: write the TO first; derive EOs via subordinate skills analysis; map Gagné events; confirm format matches stakes [source]
- Objective quality checklist: [source]
- [ ] Written from learner's perspective (not "the lesson will cover") [source]
- [ ] Behavior verb is observable (not vague state verbs) [source]
- [ ] Condition specified when it differs from daily work context [source]
- [ ] Degree stated when a pass/fail line is required [source]
- [ ] Bloom's level matches actual job performance demand [source]
- Alignment audit steps: [source]
- List all ILO verbs [source]
- For each, identify the TLA that practices that verb [source]
- For each, identify the AT that requires that verb [source]
- Flag any ILO with no TLA and/or no AT → gap in the design [source]
- Curriculum architecture checklist: [source]
- [ ] Transfer goals defined at program level before course design begins [source]
- [ ] Prerequisite graph drawn as a DAG; hub courses identified [source]
- [ ] I/R/M levels mapped across courses for each critical competency [source]
- [ ] Chunking targets 1–3 objectives per module [source]
- [ ] Sequencing follows declarative → procedural → situated pattern [source]
- Full source citations: references/instructional-design-course-architecture.md (28 sources). [source]
Routing Detail
- Measuring whether the training you designed actually worked (Kirkpatrick levels, Phillips ROI, training transfer, L&D dashboards) → learning-measurement-evaluation [source]
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