English:Design Thinking
Design Thinking
Introduction
Design Thinking is a human-centered and iterative approach to solving complex problems. Instead of jumping directly from a problem to one preferred solution, you investigate the people and context involved, frame the challenge carefully, generate several possibilities, make ideas tangible, test them, and learn from evidence. For learners in Grades 11–13, design thinking is especially useful because it connects Creativity, Problem solving, Communication, Technology, Business, Engineering, and Social sciences.
Design thinking is not a single universal recipe. Different institutions use different terms and diagrams. The Stanford d.school, for example, teaches five common modes: empathize, define, ideate, prototype, and test. The Design Council's Double Diamond uses discover, define, develop, and deliver. Both frameworks emphasize that real projects involve iteration: you may return to earlier questions when new evidence changes your understanding.
By the end of this aiMOOC, you should be able to explain major design-thinking ideas, conduct basic user research, synthesize evidence into a useful problem statement, generate and evaluate ideas, build low-cost prototypes, test them responsibly, and reflect on the limits and ethical consequences of proposed solutions.
Why Design Thinking Matters
Many school, workplace, and community problems are not purely technical. A technically impressive solution can still fail if it does not fit people's needs, routines, resources, abilities, values, or environment. Design thinking therefore asks you to study the situation before deciding what should be built or changed.
The approach is especially useful for open problems with uncertainty. Examples include improving a school library experience, reducing food waste, redesigning a digital learning tool, making public information easier to understand, improving access for people with different abilities, or creating a service that works for several stakeholder groups.
A strong design team moves between divergent thinking and convergent thinking. During divergence, you deliberately expand the range of observations, questions, or possible solutions. During convergence, you select, combine, prioritize, and justify. Creativity and critical judgment are both necessary, but they are often most effective at different moments.
Foundations of Human-Centered Design
People, Context, and Evidence
Human-centered design begins with people, but it should not reduce people to stereotypes. A designer needs evidence from observation, interviews, participation, existing research, and feedback. You should distinguish what a person actually said or did from your interpretation of why it happened.
Useful evidence can include recurring frustrations, workarounds, unmet goals, emotional reactions, environmental constraints, conflicting stakeholder needs, and moments where an existing process breaks down. One interview can inspire a question, but it rarely proves that a need is universal. Whenever possible, compare several sources and look for patterns as well as differences.
Good research also requires ethics. Ask permission before recording people, protect personal data, avoid pressuring participants, and explain how information will be used. When working with minors or sensitive situations, follow school rules and applicable consent procedures.
Desirability, Feasibility, and Viability
A promising design should be examined from several perspectives. Desirability asks whether the solution creates value for the people affected. Feasibility asks whether it can be built or delivered with available technology, knowledge, time, and resources. Viability asks whether it can continue to function within financial, organizational, legal, and operational constraints.
For school and community projects, you can broaden this analysis. Ask whether the idea is accessible, sustainable, fair, safe, maintainable, and understandable. A concept that works for one user group may create new barriers for another. Design quality therefore includes both performance and consequences.
Iteration and Learning from Failure
Iteration means repeating parts of the process in response to evidence. A prototype that performs poorly is not automatically a failed project. It may be a useful experiment if it reveals a wrong assumption early and cheaply. The important question is what you learned and how that learning changes the next version.
This mindset differs from defending the first idea. In design thinking, attachment to one solution can create confirmation bias. Teams should make assumptions visible, seek disconfirming feedback, and treat criticism of a prototype as information about the design rather than as a personal judgment.
The Design Thinking Cycle
Empathize: Understand People in Context
The empathy mode aims to understand experiences from the perspective of people affected by a challenge. You can observe, interview, shadow a process, examine artifacts people use, or ask participants to describe specific recent situations. Open questions such as "Tell me about the last time this happened" usually produce richer evidence than questions that invite only yes or no.
Empathy is not the same as assuming you know how another person feels. It requires curiosity and disciplined listening. Record exact observations, meaningful quotations, needs, contradictions, and uncertainties. Then compare accounts across participants.
An empathy map can help organize research into what a person says, thinks, does, and feels. Treat the map as a hypothesis based on evidence, not as a psychological diagnosis.
A useful research note separates observation from interpretation. For example, "three students photographed the timetable" is an observation. "the timetable is confusing" is an interpretation that should be tested with follow-up questions or additional evidence.
Define: Frame the Right Problem
The define mode turns raw research into a clear design challenge. You look for patterns, tensions, causes, and unmet needs. A useful problem statement is specific enough to guide action but open enough to allow different solutions.
One common structure is a point-of-view statement: identify a user or stakeholder, a meaningful need, and an insight explaining why that need matters. From there, a team can form a How might we question. For example: "How might we help new students find quiet study areas without requiring them to learn the entire building layout first?"
Avoid embedding a favorite solution in the question. "How might we build an app for..." already assumes that an app is the answer. A stronger framing keeps the underlying need visible so that digital, physical, social, or organizational solutions can compete.
Ideate: Generate Possibilities
Ideation expands the solution space. The goal is not to find one perfect idea immediately but to create enough variety that the team can compare alternatives. Methods include brainstorming, brainwriting, sketching, mind mapping, analogies, worst-possible-idea exercises, and combining partial ideas.
During early divergence, defer judgment long enough for unusual ideas to emerge. Encourage quantity, build on other people's contributions, and make ideas visible. During convergence, apply criteria such as user value, feasibility, cost, accessibility, sustainability, risk, and evidence from research.
Idea selection should be transparent. A decision matrix can help a team compare concepts, but numerical scores do not remove judgment. Explain why criteria matter and who may be disadvantaged by the selected option.
Prototype: Make Ideas Testable
A prototype is a representation created to learn something. It can be a paper interface, storyboard, cardboard model, role-play, clickable mock-up, service script, process diagram, or physical model. Its fidelity should match the question you want to test.
Early prototypes should usually be quick and inexpensive. If the main question is whether users understand a screen flow, a paper sketch may be more useful than a polished application. If the question is whether an object fits comfortably in a hand, a rough physical model may be more informative than a detailed rendering.
A good prototype isolates uncertainty. Before building, write the assumption you want to test, the evidence you will collect, and what result would make you revise the concept.
Test: Learn with Users
Testing puts a prototype in front of relevant users or stakeholders so that you can observe what happens. Ask participants to perform realistic tasks. Avoid explaining every feature in advance because that can hide usability problems. Watch where people hesitate, misunderstand, improvise, or succeed.
Feedback should be specific. "I like it" is less useful than an observation such as "I could not tell which button moved me to the next step." Combine what participants say with what they do. After the test, decide whether to refine the solution, change the problem framing, gather more research, or explore another concept.
Testing is not permission to expose people to unnecessary risk. For potentially harmful, expensive, or sensitive ideas, use simulations, expert review, controlled environments, and ethical safeguards before any real-world trial.
Alternative Process Models
The Double Diamond
The Design Council's Double Diamond is another widely used way to represent design and innovation. Its four phases are Discover, Define, Develop, and Deliver. The two diamond shapes visualize repeated divergence and convergence: first to understand and frame the problem, then to explore and refine solutions.
The model is valuable because it reminds you that designing the right thing and designing the thing right are different challenges. If a team rushes through discovery, it may optimize a solution to the wrong problem. If it explores ideas but never converges, it may fail to create something testable and usable.
The Double Diamond is a model, not an instruction manual. Complex projects can move backward, repeat phases, or run several lines of inquiry at the same time.
Comparing Frameworks
The five-mode d.school model and the Double Diamond use different labels, but they share important principles: understand people and context, define the challenge, expand the range of possibilities, make ideas tangible, test them, and iterate.
You should therefore learn the purpose of each activity rather than memorizing one diagram as the only correct process. In professional practice, teams often adapt methods to project risk, available time, organizational culture, regulation, and the type of product or service being designed.
Working as a Design Team
Collaboration and Creative Confidence
Design thinking is usually collaborative because complex problems involve different forms of knowledge. A balanced team may include people who understand users, technology, business constraints, visual communication, data, policy, or implementation.
Useful team routines include assigning a facilitator, documenting decisions, rotating speaking order, inviting quieter voices, making disagreements visible, and separating idea generation from evaluation. Psychological safety matters because participants need to propose unfinished ideas and admit uncertainty.
Creative confidence does not mean believing every idea is good. It means being willing to generate, show, test, revise, and sometimes abandon ideas without treating uncertainty as a reason to stop.
Bias, Inclusion, and Accessibility
Human-centered methods can still reproduce bias. A team may interview only convenient participants, treat one person as representative of an entire group, or design around its own habits. Counter these risks by recruiting diverse participants, checking whose perspective is missing, and making assumptions explicit.
Accessibility should be considered from the beginning rather than added after a design is finished. Depending on the project, this can involve visual contrast, readable language, keyboard access, captions, physical reach, sensory needs, language differences, cognitive load, and alternative ways to complete a task.
Inclusion also concerns power. Ask who defines the problem, who benefits, who carries the cost, who can refuse participation, and who is responsible if the solution causes harm.
Sustainability and Systems Thinking
A design exists inside a larger system. A new product can solve one problem while increasing waste, energy use, maintenance burden, or inequality elsewhere. Systems thinking helps you examine connections, feedback loops, incentives, resources, and long-term effects.
For a physical prototype, consider materials, repairability, reuse, and end-of-life. For a digital service, consider energy use, hardware requirements, data collection, privacy, moderation, and unequal access. For a school process, consider staff workload, training, schedules, and whether the solution remains useful after the project team leaves.
Applying Design Thinking in School
Example Challenge: Improve the Study Experience
Imagine that your school wants to improve independent study spaces. A weak start would be to decide immediately that the answer is new furniture. A design-thinking approach begins by asking who uses the spaces, when, for what purposes, and what currently helps or prevents productive study.
You might observe several study areas, interview students and staff, map noise and movement, document existing workarounds, and compare different times of day. You could then define a focused challenge such as helping students switch quickly between quiet individual work and small-group collaboration without creating conflict between users.
Ideation could produce physical, digital, and organizational concepts. Prototypes might include movable paper floor plans, signage, a booking flow, cardboard dividers, or a short role-play of a new room-use procedure. Tests would reveal what users understand, what breaks down, and which assumptions need revision.
A Practical Project Workflow
A useful project record contains a challenge statement, stakeholder map, research plan, consent considerations, observation notes, interview evidence, synthesized insights, a problem statement, several concept sketches, selection criteria, prototype versions, test protocols, feedback, revisions, and a final reflection.
Do not hide dead ends. A strong design portfolio shows how evidence changed your thinking. Teachers and assessors can then judge the quality of your reasoning rather than only the visual polish of the final product.
Questions to Ask at Every Stage
Research: What do we know, what are we assuming, and whose experience is missing?
Define: Are we solving a cause, a symptom, or a convenient version of the problem?
Ideate: Have we generated genuinely different approaches, or only variations of one concept?
Prototype: What uncertainty is this prototype designed to reduce?
Test: What evidence would make us change our mind?
Implement: Who will maintain the solution, what could go wrong, and how will we know whether it works over time?
Sources and Further Exploration
The following resources are useful for checking terminology, comparing models, and extending your project work:
- Stanford d.school Design Thinking Bootleg: A collection of tools organized around empathize, define, ideate, prototype, and test.
- IDEO Design Thinking: A human-centered introduction connecting desirability, feasibility, and viability.
- Design Council Double Diamond: An overview of discover, define, develop, and deliver.
- MIT Open Learning Library: An open course on design thinking for leading and learning.
- Wikipedia Design thinking: A general reference article with historical and conceptual background.
Interactive Tasks
Quiz: Test Your Knowledge
Why is user research important at the beginning of a design-thinking project? (It helps the team understand people and context before choosing a solution) (!It guarantees that every participant has the same opinion) (!It removes the need to test prototypes later) (!It proves that the first problem statement is correct)
What is the main purpose of divergent thinking? (To expand the range of observations questions or possible ideas) (!To select one final idea as early as possible) (!To calculate the exact cost of implementation) (!To eliminate disagreement within the team)
What makes a useful design problem statement? (It is focused on a meaningful need but still allows different solutions) (!It names the technology that must be used) (!It contains the final answer chosen by the team) (!It avoids reference to users or stakeholders)
What is the main purpose of an early prototype? (To make an idea testable so the team can learn) (!To prove that the project is already finished) (!To impress users with maximum visual polish) (!To replace the need for research evidence)
What is a strong testing practice? (Observe users attempting realistic tasks with the prototype) (!Explain every feature before users can interact) (!Ask only whether users like the idea) (!Ignore behavior that conflicts with interview answers)
What does iteration mean in design thinking? (Revisiting and revising work in response to new evidence) (!Repeating the same solution without changes) (!Following every phase exactly once) (!Avoiding feedback until the final presentation)
Which question best addresses feasibility? (Can this solution be built or delivered with available resources and capabilities) (!Do users find the solution meaningful and useful) (!Can the organization sustain the solution economically) (!Does the team personally prefer the visual style)
What does the Double Diamond mainly visualize? (Repeated divergence and convergence around problems and solutions) (!A fixed sequence that never allows returning to earlier work) (!A ranking of designers from beginners to experts) (!A financial model for calculating product prices)
Which practice helps reduce bias in user research? (Include varied participants and check whose perspective is missing) (!Interview only people who are easiest to reach) (!Treat one participant as representative of everyone) (!Remove observations that challenge the first idea)
Why should a design team consider sustainability and systems effects? (A solution can create new costs or harms elsewhere in the system) (!Sustainability matters only after a product reaches the market) (!Systems thinking removes the need for user research) (!Environmental effects are unrelated to design decisions)
Memory Game
| Empathy | Evidence-based understanding of people and their context |
| Problemstatement | A focused description of the user need or challenge |
| Ideation | Deliberate generation of multiple possible solutions |
| Prototype | A tangible representation built to answer a design question |
| Testing | Observation of how users interact with a proposed solution |
| Iteration | Revision of a concept in response to new evidence |
| Divergence | Expansion of the range of possibilities |
| Convergence | Selection and refinement using relevant criteria |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Empathize | Learn about people and context through research |
| Define | Turn evidence into a focused design challenge |
| Ideate | Generate a broad range of possible solutions |
| Prototype | Make an idea tangible enough to investigate |
| Test | Observe interaction and collect evidence for revision |
...
Crossword Puzzle
| Empathy | What concept describes evidence-based understanding of another person's experience and context? |
| Ideation | What process generates many possible responses to a design challenge? |
| Prototype | What testable representation makes an idea tangible? |
| Iteration | What repeated process improves a design through evidence and revision? |
| Divergence | What thinking mode deliberately expands the range of possibilities? |
| Convergence | What thinking mode narrows options using criteria and judgment? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Observation study: Observe one everyday school activity for fifteen minutes, record only what you can directly see or hear, and separate these observations from your interpretations.
- Empathy interview: Conduct a short interview about one recent user experience, ask open follow-up questions, and summarize two needs supported by specific evidence.
- Idea sketching: Choose a small school challenge and create six visibly different solution sketches before deciding which one you prefer.
- Prototype photo story: Build a low-cost paper or cardboard prototype, photograph three stages of its use, and add short English captions explaining what each image tests.
Standard
- Stakeholder map: Map the people affected by a school or community problem, identify competing needs, and explain whose perspective is hardest to include.
- Design interview video: Record a short interview with a willing participant about a real problem, obtain appropriate permission, edit the material into a two-minute evidence summary, and explain what surprised you.
- Prototype experiment: Build two versions of the same concept, define one question that distinguishes them, test both with users, and compare the resulting evidence.
- Design observation walk: Visit a suitable public place such as a library transit stop school entrance or service desk, document how people navigate the setting without collecting personal data, and propose one evidence-based design opportunity.
Advanced
- Inclusive design audit: Evaluate an existing product service or school process for accessibility and inclusion, identify at least three barriers, and create a revised prototype that addresses them.
- Systems map: Investigate a complex issue such as food waste mobility or digital distraction, create a systems map showing stakeholders incentives resources and feedback loops, and identify one leverage point for design intervention.
- Community co-design project: Work with a small stakeholder group to define a challenge generate alternatives prototype one concept and document how participant feedback changes the design.
- Design case study film: Produce a five-minute video case study that presents the problem research evidence ideation prototype testing ethical considerations and final reflection, including at least one limitation or unresolved question.
Learning Assessment
- Problem framing assessment: Given a vague challenge, analyze the available evidence, distinguish symptoms from underlying needs, and justify a focused problem statement that does not assume a solution.
- Research quality assessment: Compare two user-research plans and explain which one is more likely to produce trustworthy and ethically collected evidence, including at least two limitations.
- Concept selection assessment: Evaluate three proposed solutions using user value feasibility accessibility sustainability and implementation constraints, then defend a selection while acknowledging trade-offs.
- Prototype strategy assessment: For a proposed service or product, identify the largest uncertainty and design a low-cost prototype and test procedure that could reduce that uncertainty.
- Evidence interpretation assessment: Analyze conflicting feedback from several test participants and decide whether the team should refine the prototype gather more research or reframe the problem.
- Transfer assessment: Apply design-thinking principles to a new field such as public health education business or environmental action and explain which methods would need adaptation and why.
Evidence of Learning
| Dimension | Evidence |
|---|---|
| Knowledge | You can explain human-centered design, divergence and convergence, problem framing, prototyping, testing, iteration, and the relationship between desirability, feasibility, and viability. |
| Research skills | You can plan ethical observations or interviews, distinguish evidence from interpretation, synthesize patterns, and identify missing perspectives. |
| Creative skills | You can generate genuinely different concepts, visualize ideas quickly, and use criteria to move from divergence to justified convergence. |
| Making and testing | You can choose an appropriate prototype fidelity, state the uncertainty being tested, observe user interaction, and revise the design from evidence. |
| Products | Your portfolio can include research notes, empathy maps, problem statements, sketches, decision criteria, prototype versions, test records, and a final case study. |
| Transfer | You can apply design-thinking reasoning to unfamiliar school, community, technical, social, or business challenges while considering ethics, accessibility, sustainability, and systems effects. |
| Reflection | You can explain what changed during the project, why it changed, which assumptions were disproved, and what remains uncertain. |
OERs on the Topic
Linked Learning Areas
Design thinking connects naturally with English through interviewing, argumentation, documentation, presentation, and reflection; with Design and Art through visual communication and prototyping; with Technology and Engineering through feasibility and implementation; with Business through value creation and viability; and with Social sciences through research, ethics, stakeholder analysis, and systems thinking.
