Architecture of Course Design

System key

• Blue: cognitive
• Green: instructional
• Orange: motivational
• Purple: contextual

Forward design vs. backward design

• Forward design (how most courses are built)
• Diagram: Topics, then activities, then assessments, then hope students learned something.
• Backward design (Wiggins & McTighe)
• Diagram: Desired results, then evidence of learning, then learning experiences.
• Why forward design fails: Teaches content, not learning.
• Most courses are designed around coverage. Backward design is designed around outcomes.

The alignment triangle

• Diagram: a triangle whose three corners are learning outcomes (what students will be able to do), assessments (how you'll know they can do it), and learning activities (how they'll get there).
• Alignment = all three point at the same target
• Misalignment examples: Teaching for understanding is not assessing for recall
• If your assessment doesn't measure your outcome, your outcome is decorative.

Learning objectives that work

• Weak objectives
• “Students will understand...”
• “Students will appreciate...”
• “Students will know...”
• Strong objectives: Observable, specific, measurable verbs at appropriate cognitive level.
• Bloom's verb bank (by level)
• Create: design, construct, develop, devise, justify
• Evaluate: assess, critique, judge, defend, prioritize
• Analyze: analyze, compare, contrast, examine, infer
• Apply: apply, implement, solve, use, demonstrate
• Understand: explain, summarize, interpret, classify
• Remember: define, list, recall, identify, name
• “Understand” is not a learning objective. It is a wish.

Cognitive level alignment

• Diagram: a table pairing Bloom's levels with course design implications.
• Create: capstone, synthesis, original work
• Evaluate: judgment, critique, evidence-based decisions
• Analyze: break apart, examine relationships
• Apply: use in new contexts, solve problems
• Understand: explain ideas, make meaning
• Remember: recall facts, basic concepts
• Common misalignment: Teaching at apply is not assessing at remember
• Match the cognitive demand of your assessment to the cognitive demand of your instruction.

The assessment design sequence

• 1. What would a student who achieved this outcome be able to do in the real world?
• 2. What performance would demonstrate that?
• 3. What task elicits that performance?
• 4. What criteria distinguish strong from weak performance?
• 5. What instruction prepares them?
• Design the assessment before the activities. Let the assessment drive the instruction.

Course sequencing and scaffolding

• Learning progression (staircase)
• Diagram: a staircase rising from prior knowledge (activate it) to new learning (build it), then consolidation (make it stick), then application (use it), then transfer (new contexts).
• Scaffolding removal
• Diagram: I do (model), then we do (guide), then you do (independent).
• Common sequencing errors
• Too much too fast
• Prerequisites assumed
• No consolidation
• Learning is cumulative. Course design should be too.

The workload equation

• Carnegie unit: 1 credit = 3 hours student work/week
• Typical 3-credit course: 9 hours / week
• Diagram: 9 hours / week splits into lecture + reading + assignment prep, which lead to studying, writing and other.
• Common overload: Many syllabi assume 15–20 hours a week for a 3-credit course
• Workload as a design variable
• Overloaded students don't learn more. They learn less, faster, and forget it sooner.

Learning outcome vs. performance objective

• Course-level outcomes: Broad, enduring, transferable: what survives the semester.
• Nesting relationship
• Module-level objectives: Specific, weekly, building blocks that build toward outcomes.
• Diagram: course-level outcomes and module-level objectives are linked by a two-way arrow labelled nesting relationship.
• Why both matter
• Outcomes give direction and coherence.
• Objectives give clarity and action.
• Common confusion: Treating every weekly topic as a course outcome.
• Not every topic is an outcome. Some topics are vehicles for outcomes.

The coherence problem

• Coherence audit questions
• Does every unit connect to at least one course outcome?
• Does every assessment connect to at least one outcome?
• Do students know why they're doing each activity?
• Is there a visible through-line from week 1 to finals?
• Incoherence symptoms
• Students ask “why are we doing this?”
• Disconnected units feel like separate courses.
• Coherence is the difference between a course and a collection of topics.

Student motivation by design

• Design signals that increase motivation
• Clear outcomes lead to autonomy
• Achievable scaffolding leads to competence
• Meaningful tasks lead to purpose
• Visible progress leads to persistence
• Design choices that undermine motivation
• Opaque grading
• Front-loaded difficulty
• No low-stakes practice
• No feedback before high-stakes assessment
• Motivation is not a student characteristic. It is a design outcome.

The prep cycle audit

• Before building the course
• What are the 3–5 enduring outcomes?
• What would mastery look like?
• What do students need to unlearn?
• What's actually essential vs. merely interesting?
• Before each unit
• Does this connect to an outcome?
• Is there assessment?
• Is there practice?
• The audit takes an hour. The clarity lasts a semester.

Common course design failures

• Failure 1: Coverage as the goal (finishing content is not producing learning)
• Failure 2: Assessment as afterthought (designed last, reveals misalignment)
• Failure 3: Activities without purpose (engaging does not mean aligned)
• Failure 4: No low-stakes practice before high-stakes assessment
• Failure 5: Outcomes written after the syllabus
• Most course design failures happen before the first class meeting.

The backward design process

(Wiggins & McTighe)

• Stage 1: Identify desired results
• Enduring understandings
• Essential questions
• Knowledge and skills
• Stage 2: Determine acceptable evidence
• Performance tasks
• Other evidence
• Self-assessment
• Stage 3: Plan learning experiences and instruction
• Instruction
• Resources
• Sequence
• Differentiation

The course design ecosystem

• Diagram: student learning at the center, connected by arrows to eight parts.
• Clear outcomes: direction & purpose
• Aligned assessment: measures what matters
• Scaffolded activities: build capability
• Coherent sequence: logical progression
• Appropriate workload: sustainable for students
• Motivation design: signals that matter
• Feedback loops: improve & adjust
• Prior knowledge activation: builds connections
• A well-designed course removes the obstacles between students and learning. A poorly designed one creates them.

The feedback bank blueprint

• Conceptual issues (thesis, argument, evidence): 5–10 pre-written, numbered comments for common conceptual problems.
• Structural issues (organization, transitions, coherence): 5–10 pre-written, numbered comments for structure and flow.
• Mechanical issues (citation, formatting, sentence-level): 5–10 pre-written, numbered comments for mechanical and style issues.
• Strengths (what to preserve and amplify): 5–10 pre-written, numbered comments to reinforce strengths.
• Thirty minutes of setup can save hours per batch.

The course design checklist

• 3–5 enduring outcomes stated clearly
• Every assessment maps to an outcome
• Every unit has low-stakes practice before high-stakes assessment
• Workload is within Carnegie unit range
• Students can answer “why are we doing this?” for every major activity
• Feedback is formative before summative
• Run this audit on your next course. One check per week.

The course design equation

• Clear outcomes + aligned assessment + scaffolded activities + coherent sequence = learning by design
• Coverage is what you teach. Outcomes are what students learn. Design for outcomes.