Lesson 6.2

Design Thinking/Module 6 · Capstone — a full design-thinking project

Lesson 6.2

Running the modes end-to-end

Empathise, Define, Ideate on the live brief

6 min Lesson 30 of 32

The hook
You've resisted solving. Now you have to move — through empathy, into definition, into ideation — on a real family, with no headings announcing the transitions, watching the modes blur. Watch less for what each mode does and more for how they connect: where one mode's output becomes the next mode's fuel, and where the loop quietly doubles back.

Empathise: from vague words to understood people

You see the home and run contextual interviews in the space, talking to everyone. The silences fill in: Priya, nine, has nowhere quiet to study (she does homework at the dining table amid the bustle). Meena cooks daily and feels the kitchen is cramped — and when asked to show you, three vessels slide off a shelf ('every day, see'). The grandmother prays at dawn; the grandfather's knees struggle with the low seating. 'Presentable' means something emotional: Meena's relatives will visit and judge, and she doesn't want them to think the young couple 'couldn't manage.' Then you synthesise: personas for the overlooked (Priya, the grandparents), empathy maps with their gaps. Even as you synthesise, you're already half-stepping into Define — that bleed is the method flowing.

Define: from understood people to a sharp problem

You crystallise the personas into POVs: Priya needs a space that's truly her own to study and grow; the grandparents need to live with comfort and dignity for their months here; Meena needs a home that works for her daily cooking and earns her family's respect. The POVs collide — in 650 sq ft there isn't room for separate dedicated spaces — so you write a collision HMW: 'how might one small home give Priya her own space, the grandparents comfort and dignity, and the family a presentable shared life — all within 650 sq ft and ₹8–10 lakhs?' You reframe the tightest constraint as fuel ('small + tight budget' becomes radical, dignified multi-functionality) and assemble the rewritten brief with success criteria that will become your test.

Ideate: from a sharp problem to a chosen concept

You diverge, resisting the first idea (a tiny separate room for Priya would starve every other need). You generate widely — bubble diagrams, three partis, SCAMPER on stuck points — and borrow by analogy: the boat's double-duty everything, the stepwell's work-in-section (could Priya's study be a loft, reclaiming the vertical?). You sketch ugly and fast. Then you converge — dot-vote, run the triangle, and combine rather than pick. The winning concept is a synthesis: a service spine (kitchen, bath, storage along one wall — Meena's two-cook kitchen) freeing one flexible main volume (the grandmother's dawn prayer corner, the family's presentable evening living space), with Priya's own study loft above (her private space, reclaimed from the section), and knee-friendly, rising-supportive seating that's also storage. Every need served, the collision dissolved by time and section.

Three understood people → three POVs → one collision question, framed against the constraints.

Go deeper — for practitioners & students

The transitions between modes are where you'll get stuck — and the cure is always to look backwards, not forwards: when ideation stalls, the problem is almost never in Ideate but in a fuzzy Define or a thin Empathise; step back a mode and find the weak foundation. The loop doubles back mid-stream, and that's not failure — halfway through ideating you might realise you never confirmed where the grandparents pray, so you loop back into Empathise for one targeted question, then forward again. And keep the client in the loop through the front half, not just at the reveal — check the framing before ideating heavily ('here's what I think the real problem is — does this capture your family?'), so the final reveal is a fulfilment of an agreed direction, not a surprise to be defended.

Try it

1. Empathise into the silences — for each silent inhabitant, write the real unstated need and the 'show me' question that confirms it; build one quick persona for the most overlooked. Define to a collision — a POV for each key person, then a single collision HMW within the constraints, with the tightest constraint reframed as a concept. Ideate to a combination — generate widely (force one parti and one analogy), then converge by combining the best parts into one concept. Catch the blur and the loop-back — note one moment where two modes blurred and one place you'd loop back to empathy.

Check yourself

3 quick questions — pick an answer to see why.

Q1The three POVs can't all have separate spaces in 650 sq ft. What captures this tension?

Q2When ideation stalls, what does the lesson advise?

Q3How does the winning concept dissolve the collision of competing needs?

Key terms

Collision HMW: A single How-Might-We question that holds several colliding POVs together within the project's real constraints.
Constraint-as-fuel reframe: Turning the tightest limitation ('small + tight budget') into the creative driver of the concept — here, radical, dignified multi-functionality.
Looping back: Doubling back mid-stream to an earlier mode for a targeted question — which is the method working, not failing.

Recap

This lesson ran the front half of the loop end-to-end on the live family. Empathise turned the brief's vague words and silences into understood people with real unstated needs. Define converged those into POVs that collided, held together by a collision HMW within the constraints, with 'small + tight' reframed as dignified multi-functionality. Ideate diverged with real methods and analogies, then converged by combining into one integrated concept that dissolved the collision through time and section. Throughout, the modes blurred and the loop doubled back — the method working. When stuck in a mode, step back a mode; keep the client's framing agreed before you ideate heavily.

Carry forward →

You have a chosen concept that looks right on paper — exactly the danger. Can you now run the back half of the loop — make it testable cheaply, walk the real family and the real monsoon through it, find the flaws while free, and iterate to a tested, good-enough design?