Applying Design Thinking to a Real School Problem

Design Thinking (Stanford d.school, 2004) is a structured problem-solving process: (1) Empathise — observe and interview the user to understand their real needs without assumptions. (2) Define — synthesise observations into a clear problem statement (Point of View: 'User X needs Y because Z'). (3) Ideate — generate 5+ ideas before committing to any one. (4) Prototype — build the simplest version that tests your core assumption. (5) Test — put the prototype in front of the real user and collect feedback.

A Point of View statement converts observations into a design challenge. Format: '[User] needs [specific need] because [surprising insight from research].' Example: 'Grade 6 students who use both a ruler and a pencil case need a way to keep the ruler accessible without it taking up desk space, because rulers fall off desks when placed on top of the pencil case.' POV must be specific, human, and insight-driven — not a solution description.

Most students stop at their first idea. Professional designers generate a minimum of 5 ideas before evaluating. Ideation rules: (1) No evaluation during generation — all ideas are valid. (2) Quantity over quality. (3) Build on each other's ideas. (4) Use 'How Might We' questions to trigger ideas: 'How might we keep a ruler accessible without taking desk space?' Then apply a decision matrix (criteria × ideas) to select the best idea to prototype.

A decision matrix scores each idea against the same criteria. Format: rows = ideas, columns = criteria (feasibility, cost, impact, time to make), each cell scored 1–5. The highest total score is the recommended prototype. The matrix also documents WHY an idea was selected — which is as important as the selection itself. Never select an idea without documented justification.