Studio Matrx Monthly · Volume 1 · Issue 2 · July 2026
Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
A design-thinking process presentation pinned across a studio wall — research photos, an empathy map, concept sketches, a mood board, scale-model photos and a final interior render arranged left to right as one story, no people, no legible text.
Unit VDesign Thinking

The Final Project

Presenting a whole design-thinking process as a portfolio story.

The final project carries one chosen interior problem through all five modes and presents it as a coherent process story — and it is the process and reasoning that are graded, not just the final render. Learn the deliverables, what a strong story looks like, and the weak submissions to avoid.

Learning objectives

By the end of this lesson, you will be able to — mapped to the course outcomes for Design Thinking:

1
CO6 · Create

Carry an interior problem through all five modes and document each.

2
CO6 · Create

Assemble the stage-by-stage deliverables into a coherent process story.

3
CO6 · Evaluate

Show iteration and pivots — traceable from Test back to Empathize.

4
CO6 · Evaluate

Avoid the weak-submission traps (empathy-washing, loop-free march, shallow testing).

Stage by stage

The deliverables

Map the evidence to each mode — research and empathy map, POV and HMW, ideation, prototypes, test feedback, iteration narrative, resolved design and reflection.[1]

A traceable process story Empathize Define Ideate Prototype Test finaldesign traceable back — the design is justified BY the process The process and reasoning are graded — not just the final render.
DiagramA strong process story is traceable — the final design links back through test, prototype, ideate, define and empathize

Start with real users

Present the chosen space and problem, the users, and why it matters — then the EMPATHIZE evidence: interview notes and direct quotes, photos of the space in use, observation findings, and an empathy map, a persona and/or a user journey map. The evidence must show real people, not 'I think a family would like…'.[1]

Process over polish

Strong vs weak — and how it is graded

What a strong process story looks like, the weak-submission traps, and the grading cues that reward process over polish.[1, 2]

Strong vs weak process story Strong ✓ grounded in real users✓ shows a PIVOT✓ iteration & cheap failure shown✓ right-fidelity prototypes✓ honest testing + a response✓ traceable, reflective Weak ✗ 'empathy-washing'✗ a loop-free, tidy march✗ prototypes = render drafts✗ 'testing' = asking a friend✗ a pretty render, no process✗ defensive, not reflective A suspiciously tidy process usually means shallow research. Process over polish.
DiagramA strong submission is grounded in real users and shows iteration; a weak one bolts design-thinking vocabulary onto a pretty render

What good looks like

Grounded in real users (quotes and observed behaviour, not assumptions); shows THE PIVOT (a visible moment where research changed the direction); shows iteration and cheap failure (abandoned concepts shown, not hidden); uses right-fidelity prototypes each with a learning goal; tests honestly (real feedback including criticism, and a documented response); and is coherent — the final design is traceable back through Test → Prototype → Ideate → Define → Empathize.[1, 2]

Myth vs reality

At a glance

AspectCommon beliefThe reality
What is gradedMyth: the final renderReality: the process, evidence and reasoning
Process shapeMyth: a clean, loop-free marchReality: visible iteration and pivots
TestingMyth: asking if people like itReality: observing users + documented change
EmpathyEmpathy-washing (bolted on)Grounded in real user evidence
PrototypesEarly drafts of the renderBuilt to learn, each with a question
Vocabulary

Key terms

Process story

The traceable account of how a design was arrived at, across the five modes.

The pivot

A visible moment where user research changed the design direction.

Iteration narrative

An explicit account of the loops — what was tried, abandoned and why.

Empathy-washing

Bolting design-thinking vocabulary onto a pre-decided solution.

Right-fidelity

Prototypes matched to the question — low-fi to explore, higher-fi to resolve.

Reflection

A candid account of what was learned about the method and the users.

Apply it

Studio task

Assemble a one-page storyboard of your process for a small interior problem: one artefact per mode (a quote, a POV, a sketch sheet, a prototype photo, a feedback note) plus one visible pivot where testing changed your direction. Then write two sentences of honest reflection on what you would do differently.

Check your understanding

Self-assessment

1. In the final project, what is primarily graded?

2. A suspiciously tidy, loop-free process usually signals —

3. 'Empathy-washing' means —

In a nutshell

Recap

The final project carries one interior problem through all five modes — and the PROCESS is what is graded.
Deliverables map to the stages: research + empathy/journey map → POV + HMW → ideation → prototypes → test feedback → iteration → resolved design + reflection.
A strong process story is grounded in real users, shows a pivot, and is traceable from Test back to Empathize.
Avoid empathy-washing, the loop-free march, prototypes that are just render drafts, and 'testing' that is asking a friend.
Process over polish: a gorgeous render with no visible process scores below an honest, well-evidenced one.
The evidence

References & further reading

  1. [1]Jeanne Liedtka, Andrew King & Kevin Bennett, Solving Problems with Design Thinking: Ten Stories of What Works, Columbia, 2013 (model process narratives).
  2. [2]Eli Woolery, Design Thinking Handbook, InVision; Stanford d.school, Bootcamp Bootleg (structuring deliverables).
  3. [3]NPTEL, Innovation by Design, B. K. Chakravarthy, IIT Bombay (project-based Indian reference).

Further reading

  • Liedtka, King & Bennett — Solving Problems with Design Thinking.
  • Eli Woolery — Design Thinking Handbook.
  • Stanford d.school — Bootcamp Bootleg.

Sources gathered and fact-checked June 2026. Published values vary by source, sample and method — treat as indicative and confirm against the cited standard before structural use.

A

The author

Amogh N P

Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.

More about Amogh →