Design Challenges¶

Strategy · All strategies
Evidence · 3 claims (2 for, 1 against) · 8 studies (5 causal, 2 quant-synthesis, 1 review), q2–q4 · 2 of 8 report an effect size

Description¶

A design challenge asks learners to produce a working artifact — a device, system, model, or solution — that must satisfy explicit criteria and constraints. Learning is driven by the iterative cycle of building, testing against requirements, and revising, with instruction positioned as a resource learners draw on when their designs fail.

Design Implications¶

Design challenges sit at the productive end of inquiry-based learning: they work when the challenge is well-scaffolded and the target concepts are surfaced through structured reflection on design decisions [~M]. Unguided versions often fail because learners optimize for "it works" rather than understanding why it works, so the challenge must be paired with Practice-like application moments and explicit concept extraction. Failure of an early prototype is pedagogically valuable only when learners are prompted to diagnose it against principles rather than trial-and-error around it.

Context¶

Requirements¶

• A challenge with authentic constraints and clear success criteria, so design decisions map onto target concepts
• Iteration time: at least one build–test–revise cycle, with testing that produces informative feedback
• Structured reflection (design journals, decision rationales) that converts design activity into articulable knowledge
• Access to needed materials, tools, and just-in-time instruction

Constraints¶

• Cognitive overload is common: open-ended challenges force learners to manage goals, constraints, and domain content simultaneously Cognitive overload degrades learning when working memory demands exceed capacity. [-S] — mitigate with Cognitive Load Management, staged constraints, and worked starter examples
• Learners can succeed at the artifact while missing the underlying science; without explicit concept extraction, transfer is poor [~M]
• Weak or delayed feedback during testing lets misconceptions persist across iterations
• Novices given fully open design tasks often flounder; effectiveness increases with more guidance for less knowledgeable learners [~S]

Implementation Variability¶

• Engineering design cycles (e.g., build-a-vehicle challenges) emphasizing test data and revision
• Software/game design challenges with runnable artifacts and rapid iteration
• Design-for-others challenges (design a playground, an app for a client) adding user-requirements reasoning
• Paper/low-fidelity design when materials or time are limited — the reasoning cycle matters more than the artifact

Target Learners¶

• Intermediate learners with enough domain knowledge to generate and evaluate design options; pure novices need substantial scaffolding first [~M]
• Learners motivated by Authentic Audiences and Purposes — real criteria and clients raise investment Authentic audiences improve the quality of student work. [+M]
• Teams with heterogeneous skills, where design roles distribute cognitive load

Target Learning Goals¶

• Applied problem solving: connecting concepts to functional requirements
• Systems thinking: understanding how components interact under constraints
• Iterative reasoning: hypothesis generation, testing, and revision from evidence
• Collaboration and project management practices

Instructions¶

1. Frame the challenge — present criteria, constraints, and the audience; activate relevant prior knowledge (Activation)
2. Analyze exemplar designs — have learners compare strong and weak prior solutions to extract design principles Comparing and contrasting cases improves learning. [+S]
3. Plan and build — teams propose, justify, and construct a first design; require a written rationale linking choices to concepts
4. Test and diagnose — run designs against criteria; require diagnosis of failures in terms of underlying principles, not surface fixes
5. Revise and re-test — iterate at least once, documenting what changed and why
6. Extract and share principles — teams present designs and articulate generalizable lessons; instructor consolidates target concepts

Related Strategies¶

• Case-Based Learning — analyzing existing designs complements creating new ones
• Project-Based Learning — design challenges are a common project type within it
• Peer Review — structured critique of design rationales sharpens criteria use

Examples¶

• Learning by Design (Kolodner's LBD curriculum) — middle-school science units where students design vehicles and containers, then run "design rules" discussions to extract science principles.
• Engineering is Elementary (Museum of Science, Boston) — elementary engineering design challenges integrated with science content.
• MIT D-Lab — university courses where students design technologies with community partners under real constraints.

Key Sources¶

• Hmelo-Silver, C. E. (2004). Problem-based learning: What and how do students learn? Educational Psychology Review, 16(3), 235–266. doi:10.1023/B:EDPR.0000034022.16470.f3
• Kolodner, J. L., Camp, P. J., Crismond, D., Fasse, B., Gray, J., Holbrook, J., Puntambekar, S., & Ryan, M. (2003). Problem-based learning meets case-based reasoning in the middle-school science classroom: Putting Learning by Design™ into practice. Journal of the Learning Sciences, 12(4), 495–547. doi:10.1207/S15327809JLS1204_2
• Jonassen, D. H. (2000). Toward a design theory of problem solving. Educational Technology Research and Development, 48(4), 63–85. doi:10.1007/BF02300500
• Kirschner, P. A., Sweller, J., & Clark, R. E. (2006). Why minimal guidance during instruction does not work: An analysis of the failure of constructivist, discovery, problem-based, experiential, and inquiry-based teaching. Educational Psychologist, 41(2), 75–86. doi:10.1207/s15326985ep4102_1