frameworkResearch & behavior

Conceptual Model

A deliberately designed explanation of a product’s main objects, relationships, actions, and rules.

Download Markdown (.md)

01What it means

A conceptual model is the coherent structure a product presents to help users form a useful mental model. It defines what kinds of things exist, how they relate, what actions are possible, and how state changes.[1][2]

The product explained as recognizable objects and rules A coherent model connects what exists, how it relates, and what can happen
Product concept
Objects
The things people recognize and reason about
Relationships
How those objects connect and contain one another
Actions
What people and the system can do
States
How objects change over time
Rules
Constraints, permissions, and consequences
Language
Names that keep the explanation consistent

A conceptual model is a deliberately simplified explanation for users and teams—not a screen map or a direct copy of database structure.

02Why it matters

A strong conceptual model makes separate screens feel like one understandable system. It guides navigation, language, permissions, workflows, and interaction patterns before visual polish begins.

03When to use it

Use a conceptual model when creating a new product, redesigning a fragmented one, aligning teams on domain language, or resolving inconsistent objects and actions.

04How it works

  1. Name the core user-facing objects and goals.
  2. Define relationships, ownership, lifecycle, and allowed actions.
  3. Choose metaphors only where they clarify rather than distort the system.
  4. Express the model consistently in navigation, labels, controls, and feedback.
  5. Test whether users can predict unseen behavior from what they have learned.

05A practical example

Example

In a collaborative editor, “workspace,” “document,” “member,” and “guest” need stable relationships. If guests belong to documents rather than the whole workspace, invitations, permissions, and navigation should all reflect that rule.

06Where it breaks

A conceptual model simplifies reality and may hide technical details users eventually need. Metaphors can become restrictive as features grow. The model should evolve deliberately rather than accumulating exceptions.

Common mistakes

  • Confusing a sitemap or data schema with the complete conceptual model.
  • Mixing competing metaphors across features.
  • Adding exceptions without updating labels, permissions, and user expectations.

07Sources

  1. Design Principles: Conceptual ModelsW3C · design standardDesign Principles: Conceptual Models
  2. The Design of Everyday Things, Revised and ExpandedBasic Books / Don Norman · bookThe Design of Everyday Things, Revised and Expanded
View saved topics

Start typing to search titles, definitions, categories, and frameworks.