Designing Interactions

In one sentence

Design is not about the appearance of an object; it is about the choreography of the interaction between a human and a system over time.

Why read this (and who it's for)

Most people approach design as "how does this look?" or "where do I put this button?" Moggridge argues that these are superficial concerns. This book solves the problem of friction—the moments where a user feels confused, lost, or frustrated because the system didn't behave as expected.

This is for product designers, software engineers, and anyone building tools (from apps to physical products). After reading this, you will stop thinking about "screens" and start thinking about "conversations." You will be able to audit any interface to see where the dialogue breaks down and design systems that feel like natural extensions of human intent.

The big idea

The central thesis of Designing Interactions is that interaction is a dialogue. When you use a tool, you are engaging in a conversation with it. You perform an action (a question), and the system provides a reaction (an answer). If the response is delayed, ambiguous, or unexpected, the conversation breaks down, and the user becomes frustrated.

Moggridge argues that we must design for the temporal experience. Most design focuses on the "static" state—the screen at rest. Interaction design focuses on the "dynamic" state—what happens between two moments of stillness. It is about the transition, the feedback, and the evolution of the user's mental model as they navigate a system.

To succeed, you must account for Context. A tool used in a crowded, noisy subway station must behave differently than one used in a quiet office. Interaction design requires us to consider the physical environment, the user’s emotional state, and their immediate goals. If you ignore context, your design will fail because it won't respect the reality of how humans actually live and work.

Key ideas

The Conversational Model

What it is — Interaction is a loop: Action $\rightarrow$ Reaction $\rightarrow$ Interpretation $\rightarrow$ New Action. Every time a user interacts with a system, they are looking for a specific response that confirms their action was understood. Why it matters — If the "Reaction" doesn't match the user's "Interpretation," the interaction fails. You must ensure the system speaks the same language as the human. In the book — Moggridge uses the metaphor of a conversation to explain why buttons need to change state (e.g., depressing, changing color) to acknowledge they have been "heard."

Context of Use

What it is — Design cannot happen in a vacuum; you must define who is using the tool, where they are, and what they are trying to achieve at that exact moment. Why it matters — A great design in a lab can be a terrible design in the real world. Context dictates constraints like lighting, noise, hand-held stability, and attention span. In the book — He emphasizes that a mobile device (or any portable tool) must account for "distracted" use—users who are walking, holding bags, or dealing with changing light conditions.

Feedback and Response

What it is — Feedback is the system's way of saying, "I heard you, and here is what I did." It can be visual (a loading spinner), auditory (a click), or haptic (a vibration). Why it matters — Without feedback, the user is left in a state of uncertainty. Uncertainty leads to repeated actions (clicking a button five times because nothing happened) which can lead to system errors. In the book — Moggridge argues for "immediate" feedback. The reaction must happen fast enough to maintain the flow of the conversation.

Affordances and Signifiers

What it is — An affordance is what an object can do (a chair affords sitting); a signifier is the signal that tells you how to use it (the flat surface of the seat). Why it matters — If the signifier is missing, the user won't know the affordance exists. You must design "clues" into your interface. In the book — He discusses how a button should look like it can be pressed (shadows, depth) so that its function is obvious before the user even touches it.

Error Prevention and Recovery

What it is — Good design anticipates human fallibility. It tries to prevent errors from happening in the first place but provides clear paths for recovery when they do. Why it matters — Errors are a breakdown of the conversation. A system that allows a user to "break" easily without a way back creates anxiety and frustration. In the book — He advocates for "constraints"—designing the system so that certain actions are physically or logically impossible (e.g., graying out a button until a form is filled).

Frameworks & tools

The Interaction Loop Audit

Use this to evaluate any existing interface. For every primary action a user takes, ask:

1. Action: What did the user intend to do?
2. Reaction: What did the system actually do?
3. Interpretation: Did the system's reaction match the user's expectation?
4. Next Step: Is the path forward clear, or is there a "dead end"?

The Contextual Design Checklist

Before starting any design project, answer these four questions to define the boundaries of the interaction:

1. Who? (Age, experience level, physical abilities, and cognitive load).
2. Where? (Physical environment, lighting, noise, and social context).
3. When? (Is this a high-speed "on-the-go" task or a slow "deep work" task?)
4. Why? (What is the singular primary goal of this specific interaction?)

The Feedback Hierarchy

When designing responses, prioritize based on the urgency of the information:

1. Immediate (System Status): Did the click register? (Visual/Haptic)
2. Intermediate (Process Progress): Is the system still working? (Progress bars, animations)
3. Final (Outcome): Was the action successful? (Success messages, new screens)

Memorable examples & stories

The "Door" Problem

Moggridge references the classic "Norman Door"—a door that looks like it should be pulled but is actually pushed. The Lesson: If the signifiers (the handle shape) contradict the affordances (how the door opens), the design has failed, regardless of how beautiful the door looks.

The ATM Experience

Moggridge analyzes the interaction of an Automated Teller Machine as a complex series of nested conversations. The Lesson: Because high-stakes actions (withdrawing money) happen here, the system must provide extremely clear feedback and "guardrails" to prevent errors.

Mobile Contextual Awareness

He discusses how portable devices must be designed for "one-handed" use or "glanceable" information. The Lesson: Design is not just about what fits on a screen; it's about what a human can process while their attention is divided by the physical world.

Key quotes

"Interaction design is the design of the experience of using a product over time." (Paraphrased) Why it matters: It shifts the focus from static objects to dynamic experiences.

"The system must respond to the user's actions in a way that confirms the action was understood." (Paraphrased) Why it matters: This is the core of the conversational metaphor—acknowledgment is required for trust.

"Design is not just about how things look, but how they behave and how they feel." (Paraphrased) Why it matters: It elevates interaction from aesthetics to behavior and emotion.

How to apply it

This week

• The "Click Audit": Open your favorite app. Perform 5 actions. For each action, notice the reaction. Did the app tell you it was working? Was the reaction immediate? Write down one place where the "conversation" felt awkward or delayed.
• Signifier Hunt: Look at three physical objects in your house (a kettle, a remote, a door). Identify the signifiers that tell you how to use them. If you had to guess how to use them without any labels, would you succeed?

Ongoing

• The "What Happens Next?" Rule: Every time you design a screen or a feature, ask: "Once the user does X, what is the very next thing they need to know?" Never leave a user in a state of "What happened?"
• Contextual Review: Before finalizing any UI, walk through the "Where" and "Who." Ask: "Would this still work if the user was holding a grocery bag in a bright sunlit parking lot?"

Common pitfalls

• The Aesthetic Trap: Focusing on "clean" UI (minimalism) to the point where signifiers are removed. If a button is so minimal that it doesn't look like a button, you have sacrificed usability for style.
• Ignoring Latency: Designers often design for "instant" responses, but backend systems have delays. You must design for the waiting period (loading states) as much as the active state.
• Over-Engineering the Conversation: Sometimes, a simple "Success" message is better than a complex animation. Don't add interaction for the sake of interaction; only add it if it clarifies the conversation.

Connects to

• The Design of Everyday Things by Don Norman: Provides the foundational theory on affordances and mental models that Moggridge applies to digital interaction.
• Don't Make Me Think by Steve Krug: A more practical, usability-focused companion that complements Moggridge’s philosophical approach to interaction flow.

If you remember only three things

• Interaction is a conversation: Every action needs a reaction.
• Design for the temporal experience, not just the static screen.
• Context (who, where, when) dictates how an interface must behave.

Internalize it

• Reflection questions

  1. Think of a time you felt frustrated by a piece of technology. Was it because the button was ugly, or because the system didn't respond the way you expected?
  2. How does your current project handle "waiting" states? Is the user left in a vacuum when the system is processing?
  3. If you removed all text from your app/website, would the signifiers alone tell the user what to do next?

• Flashcards Q: What is the core metaphor for interaction design? A: Interaction is a conversation between a human and a machine.

Q: What is the difference between an affordance and a signifier? A: An affordance is what an object can do; a signifier is the signal that tells you how to do it.

Q: Why is "Context of Use" critical in design? A: Because physical environments (noise, light, movement) dictate how a user can interact with a tool.

Q: What are the three components of the Interaction Loop? A: Action $\rightarrow$ Reaction $\rightarrow$ Interpretation.

Q: What is the primary goal of "Feedback" in an interface? A: To eliminate uncertainty and confirm that the system has understood the user's action.

Fidelity note

I have a high level of confidence in the core principles of this summary (the conversational model, context, feedback, and signifiers). These are the pillars of Moggridge’s work and his contributions to the field of Interaction Design. However, because I am summarizing from memory, specific minor anecdotes or secondary examples might be generalized. Readers should verify the specific "Context" examples if they require a deep academic citation for a professional paper.