# Conceptual Design: Plan How Your Product Works Before the Screens

> Learn what a conceptual model is, the three models behind every product, and the steps to build a clear one before you design the screens.

**In short:** A conceptual model plans how a product works before the screens, using three kinds of models and clear objects and operations.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/conceptual-design

## Start Here

Before you draw a single screen, you need a clear idea of how your product works. Designers call that idea a conceptual model. In this lesson you will learn what it is, the parts it has, and the steps to build one. You do not need to know how to code.

- **Conceptual model:** A simple, high-level plan of how a product works and how its parts fit together.
- **Interface:** The screens, buttons, and menus that a person sees and touches.
- **Mental model:** What a user believes about a product, based on past experience and what they see.
- **Entity:** A person, place, or thing that exists inside the product, such as a document or an event.
- **Relationship:** The way two entities connect, such as a file that can be saved or printed.
- **Constraint:** A limit on an entity or a relationship, such as a file size or a format.

## What Is a Conceptual Model?

A conceptual model is the big picture of a product. One design article describes it as a high-level plan for how the product will work and fit together.

The model comes before the interface. Two authors who write about this topic say that a designer should describe the product in terms of tasks, not clicks or screen pictures. Then the interface is built from that model. A good model keeps the number of ideas small, so people have less to learn.

The term has roots in the work of Don Norman, a well-known design researcher. One article describes his idea as a mental simulation, which is a kind of picture in the mind, of how a device works and what it can do.

The Interaction Design Foundation says there are three main types of conceptual modeling. Each one is a different view of the same thing.

### What Are the Three Kinds of Models?

- **Mental model:** What the user believes about the product. It lives in the user's head and is shaped by past experience.
- **Represented model:** What the designer plans to show, including the functions and content the system offers.
- **System image:** What the product actually presents, such as its screens, buttons, and help text.

A clear conceptual model matches what users expect, so people find the product easier to use. Ignoring the user's mental model often causes frustration.

> **Tip:** Ask yourself: if a new user guessed what this product does from its first screen, would the guess be right? If not, your system image needs work.

## What Are the Parts of a Conceptual Model?

A conceptual model has three basic parts. You can write them as short lists before you design anything.

- **Entities:** The people, places, and things that users deal with. In a word processor, these are documents, fonts, and images.
- **Relationships:** How the entities connect and what rules link them. In a word processor, a document can be saved, opened, edited, or printed.
- **Constraints:** The limits on entities and relationships. In a word processor, these might be file formats, storage space, or printing options.

### What Are Objects and Operations?

Jeff Johnson and Austin Henderson suggest a method they call object and operation analysis. You list the objects users can see, the attributes (details) each object has, and the operations (actions) users can do with each object.

Take a simple calendar app. An event is an object. Its attributes could be a name, a date, a time, and a location. Its operations could be view, print, and edit. A memory buffer or a database table is not part of the model, because users never see it. Leave those out.

## How Do You Build One?

1. **List the objects:** Write down the things users will see and handle. Skip the parts that only the computer needs.
2. **List the operations:** For each object, write what users can do with it. Look for actions many objects share, such as copy, delete, or print.
3. **Connect the parts:** Note which objects relate to each other and which ones contain others, such as a folder that holds files.
4. **Write task stories:** Describe a person doing a job using only the model's words. Do not mention buttons or clicks yet.
5. **Design the screens last:** Build the interface from the model. If the screens are hard to design, the model may need fixing.

> **Tip:** Keep it simple. Every extra idea is one more thing a user must learn. Johnson and Henderson sum up their advice as: less is more.

## A Small Model in Code

You can store a model as plain data. This sample keeps the parts of a shopping cart in one place and prints them. It uses only Python's standard library.

```python
cart = {"name": "shopping cart", "holds": "items", "actions": ["add", "remove", "checkout"]}
print("Object:", cart["name"])
print("Holds:", cart["holds"])
print("Actions:", ", ".join(cart["actions"]))

```

Output:

```text
Object: shopping cart
Holds: items
Actions: add, remove, checkout

```

## Check Your Understanding

**Quick check:** Which kind of model is what the user believes about the product, and lives in the user's head?

A. System image
B. Mental model
C. Represented model

**Answer:** B. A mental model is the user's own belief about how the product works. The represented model is the designer's plan, and the system image is what the product shows on screen.

## Sources

- [Boxes and Arrows: Conceptual Models in a Nutshell (Jeff Johnson and Austin Henderson, 2013)](https://boxesandarrows.com/conceptual-models-in-a-nutshell/)
- [Interaction Design Foundation: What are Conceptual Models?](https://ixdf.org/literature/topics/conceptual-models)
- [UX Magazine: The Secret to Designing an Intuitive UX (Match the Mental Model to the Conceptual Model)](https://uxmag.com/articles/the-secret-to-designing-an-intuitive-user-experience)
- [UX Design (Medium): Understanding mental and conceptual models in product design](https://uxdesign.cc/understanding-mental-and-conceptual-models-in-product-design-7d69de3cae26)
- [Design Bootcamp (Medium): What's a conceptual model in UX? A story of a business class passenger](https://medium.com/design-bootcamp/whats-conceptual-model-in-ux-a-story-of-a-business-class-passenger-8a0358c6f79e)
- [Medium: What UX design taught me about conceptual models](https://medium.com/@resonance.heals/what-ux-design-taught-me-about-conceptual-models-and-why-a-product-should-not-feel-like-a-box-of-5e672976bed3)
