Studio Matrx Monthly · Volume 1 · Issue 1 · June 2026
Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
Walkthrough testingLesson 5.1
Design Thinking/Module 5 · Test & Iterate — closing the loop

Lesson 5.1

Walkthrough testing

Moving an inhabitant through a space that doesn't exist yet

6 min Lesson 24 of 32
The hook
A software designer tests a button by letting a user click it. But you're designing a house that won't exist for a year, that can't be un-built. You can't seat Lakshmi in her finished prayer corner and ask 'does this work?' — the corner is still a rectangle on a foam model. How do you watch someone use a space that hasn't been built?

The problem unique to our field

You must test the design before the thing you'd test exists, because by the time the building is real it's too late and expensive to fix. So testing is simulation — and the core technique is the walkthrough: deliberately moving a person through your design, step by step, doing what they'd really do, watching for what fails. You can't walk an abstraction through a plan, but you can walk Lakshmi (your persona is your test subject) — each persona becomes a probe you push through the design to see where it breaks.

How a walkthrough works

Not glancing and thinking 'looks good' — a slow, cinematic re-enactment. Take one persona, one realistic scenario, and move them moment by moment, asking at each step: does the space support this or fight it? Walking Lakshmi through her morning surfaces three failures a static glance never would — the prayer dais sits too low for her knees, rising is hard, two cooks collide in the kitchen. None is visible in a floor plan; they appear only when a real person does a real thing across real time. The walkthrough also confirms successes (the path is clear, the morning light reaches the corner) — testing tells you what's working, so you know what to protect.

The two kinds of walkthrough

The imagined walkthrough you run yourself, in your head — instant, free, repeatable, but carrying your own blind spots and attachment. The real walkthrough brings the actual people to a physical prototype — the family points at the foam kitchen and says 'this feels small'; Lakshmi looks at the prayer corner and goes quiet. It catches what your imagination missed and corrects your bias, because they aren't attached to your design and know their lives better than your persona-of-them. The imagined is your fast private first pass; the real is the honest check.

Walk the year, not just the day

A single walkthrough tests one moment, but a home is lived across a whole day, year, and life. Run many, choosing the scenarios most likely to break the design: the ordinary Tuesday (does daily life flow?), the festival lunch (peak load), the monsoon evening (everyone indoors, wet shoes), ten years on (aged knees, a child moved out, a grandchild). Choose the scenarios likely to expose flaws, not the ones that flatter the design — a test you design to pass tells you nothing.

entrylivingkitchen Walk the inhabitant through the space on paper before it is built. where do they pause, bump, double back, squint?
Walkthrough testing: trace a real inhabitant's path through the unbuilt plan and watch where they pause, bump or double back.
Go deeper — for practitioners & students

Walk the spaces between the rooms, not just the rooms — a surprising share of failures live in the journeys (the awkward turn, the door that swings into the path, the corridor two can't pass). The most revealing walkthroughs follow the overlooked user — it's harder and far more valuable to walk Lakshmi, the cook, the grandchild, the aged knee, because these are exactly the users the design most likely failed. And narrate out loud and slowly — the failures hide in the small moments you'd skip: not 'she prays in the corner' but 'she walks over, lowers herself, settles, reaches for the lamp, later pushes up to stand'; slow to the granularity of physical actions and the design's hidden cruelties surface.

Try it

1. Pick your most vulnerable persona as the probe. Run a slow imagined walkthrough of one scenario, narrating each physical action and marking support or fight. Walk a hard scenario too — the festival, the monsoon, ten-years-on — chosen because it's likely to break the design. List the failures, and also what worked (to protect). Finding the failures on paper, now, is the whole point.

Check yourself

3 quick questions — pick an answer to see why.

Q1Why is the walkthrough the core testing technique in architecture, unlike a software click test?

Q2When choosing walkthrough scenarios, which should you prioritise?

Q3Where do a surprising share of walkthrough failures hide?

Key terms

Walkthrough
Deliberately and slowly moving a persona through your design step by step, doing what they'd really do, to watch whether the space supports or fights their life.
Imagined vs real walkthrough
The imagined walkthrough is the fast first pass in your head; the real walkthrough brings actual people to a physical prototype to catch what bias missed.
Overlooked user
The persona most likely to have been failed by the design — the cook, the grandchild, the ageing knee — and therefore the most revealing to walk through.
Recap
Architecture must test the design before the thing you'd test exists. The core technique is the walkthrough: slowly moving a persona through the design, moment by moment, watching whether the space supports or fights the life in it. The plan shows the room; the walkthrough shows the life in the room — and life is what fails. Run both the fast imagined and the honest real walkthrough, and walk the year, not just the day, choosing the hard scenarios likely to expose flaws. Walk the journeys between rooms, follow the overlooked user, and go slow.
Carry forward →

Your walkthroughs produce a flood of reactions — 'I love it,' 'the kitchen feels small,' 'can we have more storage,' 'hmm, I'm not sure.' Some points at real flaws; some is noise, politeness, or redesigning for you. How do you tell the signal from the noise?