A mental model is the internal representation a person uses to understand how a system works. It is their working theory — often incomplete, sometimes wrong, but always the lens through which they interpret interface behaviour and decide on actions. When a design aligns with users' mental models, it feels intuitive. When it contradicts them, every interaction requires conscious effort. Understanding the mental models your users bring to a product is foundational to designing for intuition rather than merely for function.
What It Is
Mental model research, as a method, involves eliciting and documenting the implicit theories users hold about a system, service, or domain. Indi Young's mental model diagram technique produces a structured visual map that aligns user tasks and thoughts with organisational capabilities, revealing gaps and opportunities for design. The output is less a deliverable and more a research lens: a framework for interpreting everything else you learn about how users relate to a product.
How to Run It
- Conduct a series of task-based interviews asking users to describe what they are trying to accomplish and what they expect to happen at each step.
- Capture the tasks, feelings, and philosophies users articulate, not the interface features they describe.
- Organise tasks into clusters representing coherent behavioural spaces — each cluster represents a mental space.
- Build a diagram with mental spaces arranged horizontally across the top, aligned with organisational capabilities on the bottom half.
- Identify gaps where user tasks have no corresponding organisational support.
- Use gaps to prioritise feature development, content strategy, and service design decisions.
Design for the mental model users have, not the one you wish they had.
When to Use It
Mental model research is most valuable for complex, task-rich applications where the gap between how users think about a domain and how the product is organised is a primary source of confusion. It is particularly powerful for redesign projects where accumulated UI debt has produced a product that reflects its own development history rather than any user's mental model of the task.
Tips for Success
- Focus on tasks and goals, not features — the mental model lives at the task level, not the UI level.
- Conduct at least twelve to fifteen interviews before attempting to build the diagram: pattern recognition requires volume.
- Involve the whole team in building the diagram collaboratively — shared understanding is as important as the artefact.
- Revisit the diagram when the product domain evolves: mental models shift as technology and behaviour change.
