Mental Model
The internal picture people form of how a product works—what objects exist, what they can do, and what happens next.
A mental model is the story a user carries in their head about a product: what the main objects are, how they relate, and what actions feel natural. Design succeeds when the interface matches that story—or gently teaches a better one.
Why it matters
When the UI organizes around chat history, people think in questions and answers. When it organizes around persistent agents, people start thinking in roles, ownership, and delegation. Same technology; different mental model.
Mismatch shows up as confusion, not as a missing feature: users keep asking “where did that go?” or “am I supposed to watch this or leave it alone?”
Common design moves
- Name the primary object — chats, bots, projects, files—pick one spine for the product
- Hide extra vocabulary until someone needs it
- Show state in human terms — idle, working, waiting—not only system logs
- Test the story — ask users to explain how the product works after five minutes
Beginner tip
Before adding another panel or setting, ask: does this help someone build a clearer model, or does it give them one more thing to manage?