Design thinking steps through one practical example
Use a studio-induction problem to practice understanding people, framing an obstacle, exploring options, prototyping, and learning, while treating the sequence as iterative rather than a rigid formula.
Treat process activities as revisitable
Design thinking is often introduced through a sequence of understanding people, defining a problem, generating ideas, prototyping, and testing. Use that sequence as a set of activities to revisit, not a guarantee of a good solution. A studio-induction example makes the activities concrete without pretending that a short exercise replaces research.
Frame the preparation obstacle
Start with a question about how newcomers prepare for their first studio visit. Keep observations separate from assumptions, frame one obstacle, and explore several responses before choosing a prototype. The Stanford d.school offers introductory process resources, while the exercise here uses an original arts-service scenario rather than reproducing its workshop material. Write the decision the artifact is meant to support at the top of the working document. Keep the people, task, and practical constraints visible beside it. This gives contributors a common reference when the discussion drifts toward tools or presentation. The artifact should expose uncertainty rather than quietly settle it through confident formatting. Assign unresolved questions to a person who can investigate or decide them, and keep their status explicit.
Explore three induction-support options
Practice with a hypothetical newcomer who cannot tell which tools to bring. Draft questions you would investigate, write a provisional problem statement, and sketch three options: a checklist, a sample kit, and a guided preparation call. Prototype one option and identify the task you would ask a participant to attempt. Give a colleague the working artifact and a clear purpose, then ask them to explain what they would do next. Compare their interpretation with the intended use. A mismatch may come from missing context, ambiguous language, or a decision that the team has not actually made. Repair the source of the mismatch rather than adding a verbal explanation that will disappear as soon as the artifact leaves the meeting.
Challenge a premature app solution
If the team jumps straight to an app, return to the underlying obstacle. If the problem statement merely repeats an invented persona, mark its assumptions and plan real investigation. If testing asks only whether someone likes the idea, replace that question with an observable task that can reveal misunderstanding or a missing capability. Keep feedback proportionate to what the artifact can show. A rehearsal may expose confusing instructions, while a diagram may reveal missing ownership; neither automatically establishes how frequently the problem occurs in the real service. State the observation precisely and separate its interpretation. This preserves the value of the issue without attaching a larger claim that the activity was not designed to support.
Record learning without inventing evidence
Review which activity changed your understanding and what remains unsupported. Do not report the hypothetical exercise as participant research or claim an improvement that has not been observed. A practical process leaves a record of questions, options, decisions, and learning. Revisiting an earlier activity is useful when new evidence changes the problem or exposes a weak assumption.
Worked decision
A checklist, sample kit, and preparation call address the same provisional induction obstacle through different mechanisms; compare them before selecting a prototype.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
