Prioritize redesign of late, back-to-back, and spanning Course Walls, where momentum recovery is least likely¶
Strategy · All strategies
Evidence · no claims cited
Description¶
The authors recommend that when Course Walls are identified, designers prioritize the walls latest in the course. They argue students who pass one wall regain momentum only to hit the next with diminished momentum, and that "Late Course Walls are perhaps the worst situation for course providers, course designers, and students" because students give up after substantial course work. For spanning walls, they advise focusing on the group of lessons where the wall occurs, giving initial priority to the last few lessons.
Design Implications¶
Context¶
Requirements¶
- Identification of Course Walls through graphing the Student Momentum Indicator on a lesson-by-lesson basis
Constraints¶
- The authors caution a course should not be redesigned for the sole purpose of reducing Course Walls, since making a course easy would eliminate walls at the cost of pedagogical and academic integrity
Target Learners¶
- instructional designers of university-level online courses
Target Learning Goals¶
- reducing dropout rates through targeted course revision
Affordances¶
Related Strategies¶
Examples¶
-
Key Sources¶
- Steven S. Christensen & Jonathan S. Spackman. (2016). Dropout Rates, Student Momentum, and Course Walls: A New Tool for Distance Education Designers. Journal of Educators Online. https://eric.ed.gov/?id=EJ1150708
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
prioritize-late-and-spanning-course-walls |
title |
Prioritize redesign of late, back-to-back, and spanning Course Walls, where momentum recovery is least likely |
description |
The authors recommend that when Course Walls are identified, designers prioritize the walls latest in the course. |
status |
review |
generated |
by process:wiki-ingest on 2026-09-27 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — steven-s-christensen-jonathan-s-spackman-2016 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.