UI Is Communication: The Mindset That Fixes Confusing Interfaces

Look at a confusing interface and you will usually find the same root cause: it is not saying what the user needs to hear. Everett McKay’s UI is Communication built an entire design philosophy on that observation, and once you adopt it, you cannot unsee it.

What is the core lesson of the book?

A user interface is a conversation. The user arrives with questions: What is this? What can I do here? What just happened? What happens next? Every element on the screen is either answering those questions or making noise. McKay’s radical claim is that communication quality, not aesthetics, determines whether an interface is intuitive. Pretty screens that answer the wrong questions still fail. Plain screens that answer the right ones succeed.

This reframes the designer’s job. You are not arranging rectangles. You are composing answers, in the user’s vocabulary, at the moment they need them.

What do designers take away from it?

• Design the answers first. Before layout, list the questions users bring to each screen. Then make sure the screen answers them in priority order.

• Cut the jargon. If users need a manual to parse your labels, you are speaking the system’s language, not theirs.

• Silence is a failure too. A missing confirmation is a broken conversation: the user asked “did that work?” and got nothing.

• Evaluate by comprehension. Test whether users can say what a screen is for. That is the metric that matters.

Why does Tremoloo share this book?

Because it gives teams a razor for design debates. When stakeholders argue about layouts, we ask the book’s question: what is this screen saying, and to whom? The argument usually resolves itself. It is the fastest lens we know for spotting why an interface confuses people.

Is your interface saying what users need to hear? A UX audit will tell you.