Primary source
Designing for How People Think (book_cube)
Summary post about John Whalen's six-component UX framework and contextual interviews.
Primary source
Designing for How People Think (book_cube)
Summary post about John Whalen's six-component UX framework and contextual interviews.
Designing for How People Think: Using Brain Science to Build Better Products
Authors: John Whalen
Publisher: O'Reilly Media; МИФ (русское издание)
Length: —
A practical framework for applying cognitive psychology in UX: from contextual interview data to testable product hypotheses.
Original
TranslationDesign / UX / Thinking / Leadership
Designing for How People Think breaks customer experience into six cognitive components and uses them as a structured discovery model. The strongest takeaway for engineering and product leaders is the pipeline from qualitative observations to measurable product decisions.
1. The six components
1. Visual perception, attention, and automatic behavior
Core question: What do users notice first, and what visual cues pull their focus?
Application focus: Validate contrast, hierarchy, affordances, and how fast users can identify the next meaningful action.
2. Navigation
Core question: How do users understand product space and build a route to their goal?
Application focus: Stress-test information architecture, wayfinding signals, and transitions across screens and states.
3. Language
Core question: Which words do users use, and what meanings do they attach to those words?
Application focus: Align labels and microcopy with user vocabulary instead of internal team jargon.
4. Memory
Core question: Which prior experiences and mental models shape user expectations?
Application focus: Design predictable interactions and avoid surprising behavior that conflicts with established patterns.
5. Decision making
Core question: Which problem do users think they are solving, and where does friction appear?
Application focus: Map user goals, uncertainty points, and intermediate tasks before the core conversion moment.
6. Emotions
Core question: Which fears, motivations, and trust signals drive behavior?
Application focus: Design confidence states through transparency, control, clear status communication, and safe defaults.
2. Why contextual interviews matter
Observe in natural context
Interviews happen where users actually perform work, so environmental constraints become visible.
Prioritize behavior over declarations
Researchers track real actions and compare them with what users initially say they do.
Probe with clarifying questions
Questions like 'why did you choose this step?' reveal motivation, risk perception, and hidden barriers.
Example from the book: SMB onboarding to PayPal
The author describes how contextual interviews with small and medium business owners informed segmentation, messaging, and landing page decisions. This turns research output into concrete product hypotheses rather than generic UX advice.
3. Pipeline from research to product changes
- Run a meaningful sample of contextual interviews and identify repeated observations.
- Classify insights across the 6 components (perception, navigation, language, memory, decisions, emotions).
- Segment users by goals, prior experience, and blockers.
- Create product and UX hypotheses grounded in observed behavior.
- Validate changes with prototypes first, then confirm effect via metrics and controlled experiments.
4. Qualitative plus quantitative: a practical blend
The book is strongest on qualitative methods. In production, teams usually need a mixed loop: contextual interviews explain behavior, while A/B tests and product metrics verify the impact at scale.
Related reading on experimentation
- How to Lie with Statistics - A practical introduction to common statistical distortions and interpretation traps.
- Understanding Statistics and Experimental Design - Core foundations for experiment design and evidence-based product decisions.
- Trustworthy Online Controlled Experiments - How to build and scale an experimentation platform across a company.
- Dark Data - How unknown and missing data can break conclusions and product choices.
5. Common anti-patterns
Relying on surveys and focus groups without direct observation in real user context.
Collecting interviews but failing to convert insights into structured hypotheses and product decisions.
Using internal terminology that does not match how customers actually describe their tasks.
Treating qualitative research as a full substitute for quantitative validation and A/B testing.
6. Recommendations for product and engineering leaders
Use the 6 components as a mandatory checklist in discovery, UX reviews, and hypothesis framing.
Review interview findings jointly across design, product, analytics, and engineering.
Plan quantitative follow-up after qualitative discovery: guardrail metrics, experiment design, and stop criteria.
Explicitly capture the chain: observation -> hypothesis -> UX change -> measurable effect.