Design Thinking¶

Strategy · All strategies
Evidence · 4 claims (3 for, 1 against) · 12 studies (4 causal, 4 quant-synthesis, 3 review, 1 theoretical), q1–q4 · 3 of 12 report an effect size

Not the design process. This page is design thinking as a learning strategy — students running the cycle on an authentic problem. The designer's process of the same name is Design Thinking, a process. This page was briefly deprecated in favour of that one; it is restored, because they are two objects and only the shared slug ever made them look like one. Ids are unique per kind, so each resolves in its own namespace.

Description¶

Design Thinking organizes learning around a structured innovation process: empathizing with users, defining a problem, ideating solutions, prototyping, and testing. Learners work on authentic, open-ended problems where user needs — not textbook answers — drive the solution. The process is carried out in teams through rapid, iterative cycles in which early ideas are externalized as sketches or prototypes and revised based on user feedback.

Design Implications¶

Design Thinking situates learning in ill-structured, authentic problems, which supports transfer better than well-structured exercises when learners have adequate support [~M]. Its power comes from iteration: prototypes function as externalized thinking that can be critiqued and revised, converting abstract concepts into concrete artifacts. Because the problem space is open-ended, learning depends on encountering multiple cases and perspectives rather than a single correct path Multiple varied cases support learning in ill-structured domains. [+M].

Context¶

Requirements¶

• A real or realistic problem with identifiable users whose needs can be investigated
• Time and materials for rapid prototyping and at least one full test-and-revise cycle
• Structured empathy activities (interviews, observation) so the "define" stage rests on evidence, not assumption
• Critique protocols that make feedback specific and actionable Feedback is most effective when directed at the task and process rather than the self. [+S]

Constraints¶

• Weak for novices in the underlying domain: open-ended exploration without domain knowledge imposes heavy search costs Guidance becomes more necessary as task complexity and learner inexperience increase. [-S] — minimally guided versions of design tasks can overload novices
• The "empathize" stage often produces shallow user insight when learners lack interview and observation skills
• Process can become ritualized: teams follow the five stages superficially without genuine iteration, yielding engaging activity but little conceptual learning [-M]
• Time-intensive; the full cycle rarely fits a single lesson and is often truncated to ideation-only, which removes the testing feedback loop where most learning occurs

Implementation Variability¶

• Full cycle vs. sprint: multi-week projects vs. compressed design sprints (e.g., a 90-minute "wallet exercise"); sprints trade depth of empathy work for exposure to the whole process
• Domain-embedded vs. process-focused: using design thinking to teach engineering or biology content vs. teaching the design process itself as the learning goal
• Physical vs. digital prototyping: paper mockups, role-played services, or clickable wireframes depending on the problem
• Depth of user contact: direct field interviews vs. personas and secondary research

Target Learners¶

• Intermediate learners who have enough domain knowledge to generate and evaluate ideas meaningfully; pure novices need more structure first Expertise reversal: guidance that helps novices can hinder more knowledgeable learners. [~M]
• Learners developing collaboration, communication, and tolerance for ambiguity
• Students who benefit from seeing knowledge applied to human situations rather than abstract exercises

Target Learning Goals¶

• Ill-structured problem solving: framing problems before solving them
• Empathy and perspective-taking: understanding stakeholder needs Empathy-building activities improve understanding of others' perspectives. [+M]
• Iterative improvement: learning from failure and revision
• Creative confidence and collaboration

Instructions¶

1. Frame the challenge — present an authentic problem and audience; use Advance Organizers to map the process stages before beginning
2. Empathize — learners conduct user interviews or observations; provide interview protocols and model questioning through Coaching
3. Define — synthesize findings into a point-of-view statement; use Case Studies to compare how experts frame similar problems
4. Ideate — brainstorm with deferred judgment; encourage Analogical Reasoning by asking "where else is this problem solved?"
5. Prototype and test — build low-fidelity artifacts, gather user feedback, iterate; structure critique with task- and process-level feedback prompts
6. Reflect — debrief on both the solution and the process, connecting experience to underlying concepts

Related Strategies¶

• Case-Based Learning — like design thinking, grounds learning in authentic problems, but analyzes existing cases rather than generating new solutions
• Project-Based Learning — design thinking supplies a repeatable process structure for the open-ended inquiry at the heart of project work
• Engage users and community members in the design process to make learning tools more attractive, useful, and effective
• Conduct empathy interviews to understand user experiences with technology
• Use a design thinking process with Empathize, Define, Ideate, Prototype, and Test stages to reimagine school safety
• User-centered R&D with A/B tests and rapid prototyping to tailor interventions to a target population

Examples¶

• Stanford d.school K12 Lab (https://dschool.stanford.edu) — publishes design challenge curricula and the "wallet project" sprint used widely in schools and universities
• IDEO design kits (https://www.designkit.org) — Field Guide to Human-Centered Design used in classrooms and community programs to structure empathy and prototyping activities
• Engineering capstone courses — Dym et al. describe design thinking as the organizing framework for undergraduate engineering education, with students iterating on client-driven projects

Key Sources¶

• Dym, C. L., Agogino, A. M., Eris, O., Frey, D. D., & Leifer, L. J. (2005). Engineering design thinking, teaching, and learning. Journal of Engineering Education, 94(1), 103–120. doi:10.1002/j.2168-9830.2005.tb00832.x
• Razzouk, R., & Shute, V. (2012). What is design thinking and why is it important? Review of Educational Research, 82(3), 330–348. doi:10.3102/0034654312457429
• Dorst, K. (2011). The core of 'design thinking' and its application. Design Studies, 32(6), 521–532. doi:10.1016/j.destud.2011.07.006
• Hmelo, C. E., Holton, D. L., & Kolodner, J. L. (2000). Designing to learn about complex systems. Journal of the Learning Sciences, 9(3), 247–298. doi:10.1207/s15327809jls0903_2