liveBook · Manning

Communication pattern

As explained in Everyday Data Visualization

An interaction pattern is a recurring way that an interface responds to user actions and presents controls or information.

A communication pattern is a recurring way an interface presents controls, responds to actions, and lets people explore information. Familiar patterns reduce the time users spend decoding the interface, leaving more attention for the task at hand. Novelty can be charming; making essential tools feel like a scavenger hunt is less charming. section 7.1.2 section 7.5

Use simple, recognizable controls for important actions, and make the result of every interaction clear through timely feedback. Keep essential information visible without requiring interaction, place error messages near the problem, and let people easily correct mistakes. Patterns should also work beyond a mouse: support focusable elements, alt text, and ARIA labels, and account for mobile use. section 7.5

Choose and shape patterns by considering how people already approach the task:

  • Start with familiar affordances and controls rather than hiding core actions behind unusual gestures or nested menus. section 7.1.2 section 7.5
  • Match the degree of exploration to users’ needs; freedom to investigate can matter more than a polished visual style. section 8.2.1
  • Test assumptions about input devices, since a pattern that depends on a particular right-click behavior may exclude trackpad users. section 7.1.2 section 7.5
  • Learn users’ mental models through interviews, then use what they value and find comfortable to guide interaction decisions. section 7.5 section 8.2.1

When a hidden tool becomes the task

A virtual tabletop placed key tools such as distance measurement and map drawing inside right-click radial menus, including submenus. Even experienced, technically confident players struggled to discover and remember the pattern, searched for help repeatedly, and some could not access a dice feature with their laptop trackpads. Important actions buried in an unfamiliar pattern can turn setup into the main event. section 7.1.2

How Everyday Data Visualization covers it

How deep it goes
Explains practical design rationale through failures, accessibility guidance, and user interviews rather than implementation details.
Examples
Uses a virtual tabletop’s radial right-click menus and contrasts a bank website with a fitness-tracker app.
What you can do after
Apply familiar, simple controls and timely feedback while accommodating exploration, errors, and non-mouse interaction.
How it connects
Connects interaction patterns with affordances, feedback, error messages, mental models, accessibility, and data exploration.

Also explained in

Compare how 2 books explain communication pattern →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Everyday Data Visualization. The section links point to the parts of the book it draws on.