Customer-Day Design Loop
Turn observed customer journeys into testable product solutions
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 97%
The Customer-Day Design Loop begins with several real, deliberately diverse customers rather than one synthetic average persona. The team observes these people, learns their environments and imagines each person moving through a representative day. Problems encountered along those journeys become the inputs for small solution sketches, allowing the product’s form to emerge from use rather than styling convention. Promising ideas then move quickly into immersive or full-scale prototypes. Those prototypes should be usable, hackable and easy to modify so that the team can learn through physical interaction. The output is a product architecture grounded in observed needs, with variation or modularity added where different customers require genuinely different solutions.
Origin
Paul Raith described how Ford reshaped its normal development process around five real Bronco customers, journey sketches, virtual reality and a full-size prototype made from packing material.
Core principles
- 01Design for real people rather than statistical averages
- 02Learn before committing to polished concepts
- 03Discover opportunities by following customers through real situations
- 04Use prototypes that invite interaction and modification
- 05Adapt the standard development process when learning demands it
How to run it
- 1
Choose diverse real customers
Recruit several representative people whose environments, ages, behaviors and desired outcomes differ meaningfully. Avoid reducing them to a single averaged persona.
Pro tip Choose differences that are likely to create conflicting product requirements.
Watch out Demographic variety alone is insufficient if everyone uses the product in essentially the same way.
- 2
Observe their worlds
Spend time with each customer and examine the physical, cultural and practical circumstances surrounding product use. Record actions, constraints, workarounds and aspirations.
Pro tip Look for needs customers demonstrate but do not explicitly articulate.
Watch out Do not treat social-media comments as a substitute for direct observation.
- 3
Map a day in the life
Walk through a realistic day for each customer and identify moments where the existing experience becomes difficult, unsafe or limiting. Treat each problem as a design prompt.
Pro tip Use small sequential sketches rather than polished presentation art.
Watch out Do not start with a preferred feature and reverse-engineer a customer problem to justify it.
- 4
Design against the problems
Generate solutions for the specific friction points found in the journey. Let recurring solutions and requirements gradually determine the product’s form and architecture.
Pro tip Preserve competing ideas until testing reveals which one serves customers best.
Watch out Premature visual polish can make weak concepts feel more resolved than they are.
- 5
Enter an immersive prototype
Move the emerging design into virtual reality or another spatial simulation to assess scale, visibility, reach and interaction. Correct obvious failures before investing in a physical model.
Pro tip Evaluate the design from every target customer’s perspective.
Watch out A visually convincing virtual model can still hide tactile or mechanical problems.
- 6
Build something hackable
Create a full-size prototype that people can enter, operate and modify immediately. Use observations from hands-on interaction to drive repeated changes.
Pro tip Prefer inexpensive, easily altered materials during the learning phase.
Watch out Do not make the prototype so precious that the team becomes reluctant to cut it apart.
In the wild
Ford’s team worked with five real customers ranging from an urban 21-year-old to an older, highly adventurous off-road user. Designers sketched their daily journeys on scraps of paper, identified problems along the way and developed corresponding solutions. They skipped conventional scale clay models, moved into virtual reality and then built a full-size model from packing material that the team could enter, stand on and modify.
→ The process produced a customer-led, highly modular vehicle with configurations and features serving markedly different users.
A tool company could observe an electrician, a hospital technician and a remote-site mechanic through representative workdays. Journey mapping might reveal shared mobility needs but very different storage, sanitation and terrain constraints. The team could prototype one cart chassis with interchangeable modules, test its dimensions in VR and then build a full-size foam-board model for workers to rearrange.
→ The company develops a common platform that serves distinct workflows without forcing every customer into an averaged configuration.
Common mistakes
Designing for an average person
An amalgamated persona can conceal meaningful conflicts between real customers and produce a superficially universal product that serves nobody particularly well.
Starting with glamour sketches
Polished images encourage the team to defend a visual answer before it has mapped the customer problems that answer must solve.
Protecting the prototype
A prototype that is expensive or difficult to alter undermines experimentation because the team hesitates to modify it when new evidence appears.
Is it for you?
Best for
It is best for teams designing complex products for several distinct customer types or usage environments.
Not ideal for
It is not ideal when the product is already tightly specified and the team has no access to representative users.
From the transcript
“we need to go through a heavy period of learning and absorbing information before we then start to to start really start putting our pen…”
“The design of the vehicle emerged from Chinese doodles on post it notes and on scraps of paper that was pinned to a wall, where…”
“We made something out of packing material that we could all get in and out of and stand on and play with an open closed…”
From the episode
Paul Wraith on the Design Business (Podcast)