Intuitive Design Explained: Interfaces as Conversations

Everyone wants an intuitive interface. Almost nobody can define one. UI is Communication offers the best definition we know: an interface is intuitive when it conducts a conversation the user already knows how to have.

What does intuition actually mean?

Users call something intuitive when nothing surprises them. They never ask what this screen is for, what they can do here, whether their action worked, or where to go next, because the interface answers each question the moment it forms. Intuition is not a visual style. It is the absence of unanswered questions.

This explains why minimalist redesigns sometimes backfire. Removing elements can remove answers. A clean screen that leaves users wondering what happened after they clicked is a beautiful failure of communication.

How do you design an intuitive conversation?

1. Script the conversation before the screen. For each step of a flow, write the questions the user will have, in order. Then check that the design answers them in that order.

2. Use vocabulary the user already owns. Words, icons, and patterns from the user’s world, not your org chart.

3. Answer the silent questions. Confirmations, progress indicators, empty states: these answer “did it work” and “what now” before users have to ask.

4. Test comprehension directly. Show a screen and ask users to explain it. If they cannot tell you what it is for, the conversation broke down.

What do designers take away?

A definition of quality they can test. “Is it intuitive?” stops being a matter of taste and becomes an observable question: did the user’s questions get answered?

Why does Tremoloo share this book?

Because “make it intuitive” is the most common and least useful brief clients receive, and this book turns it into a method. We use its question-mapping approach in our own design process, and it works.

Want interfaces your users understand on the first try? Our product design team designs conversations, not just screens.