Skip to main content

Diffuseness

Adapted from the Cognitive Dimensions of Notations framework (Green & Petre, 1996; Blackwell & Green, 2003). See About the Dimensions for framework references.

Diffuseness describes how many actions, symbols, or how much screen space is required to express a meaning or accomplish an operation. Green and Petre note that "some notations can be annoyingly long-winded, or occupy too much valuable real-estate within a display area." In professional software where screen space is precious and common operations are performed hundreds of times a day, diffuseness directly impacts productivity.

Diffuseness sits on a spectrum. At one extreme, operations are so verbose that common tasks require excessive clicking, scrolling, or navigation — a colour change requiring five clicks through nested menus, or a parameter adjustment requiring opening a modal dialog. At the other extreme, operations are so terse that they become cryptic — single-character shortcuts with no discoverability, or compressed notations that require memorisation.

The sweet spot for professional software is terse for the expert, discoverable for the learner. Common operations should be achievable in minimal interactions (keyboard shortcuts, direct manipulation) while remaining accessible through more verbose but more discoverable paths (menus, toolbars, search).

Screen Real Estate​

In information-dense professional interfaces, visual diffuseness is a constant tension. Large icons, long labels, generous padding, and spacious layouts all improve clarity at the cost of screen real estate. Dense, compact layouts maximise the working area but can feel overwhelming. The right balance depends on the frequency and importance of the controls: frequently used tools deserve prime, compact placement; rarely used features can accept more diffuse presentation behind progressive disclosure.

The Cross-Application Workaround​

One of the worst forms of diffuseness is the cross-application workaround — when accomplishing a single analytical goal requires exporting data from one tool, transforming it in another, and importing it into a third. Barbara Mirel documents cases where analysts spent 75% of their time on data conditioning across multiple applications, performing what should have been a single integrated operation.1 This is diffuseness at the workflow level, not just the interface level.

The antidote is Mirel's "analysis in a keystroke"1 principle: domain-conventional operations should be directly available, not constructed from lower-level primitives across multiple tools.

Transient UI as a Diffuseness Strategy​

Research on transient user interfaces suggests a productive middle ground for managing visual diffuseness: controls that appear when contextually relevant and hide when not needed.2 This preserves screen real estate for the primary workspace while reducing the interaction cost of accessing features. However, transient UI must be user-controllable — users need the ability to pin frequently used controls and dismiss irrelevant ones.

Testing​

  1. Time the most common operations. How many clicks, keystrokes, or navigation steps are required? Are there faster paths available for expert users?
  2. Evaluate screen space usage: Is the primary content area maximised? Are controls proportionally sized to their frequency of use?
  3. Look for cross-application workarounds: Are there operations that force users to leave the application to accomplish their goal? Could these be integrated?
  4. Test for the terse/discoverable balance: Can experts achieve common tasks quickly? Can new users find the same operations through more verbose but more discoverable paths?
  5. Check for excessive modal dialogs or multi-step wizards for operations that could be performed inline.

Conclusion​

Diffuseness is about respecting the user's time and screen space. Every unnecessary click, every excessive dialog, every bloated layout is a small tax on productivity that compounds across hundreds of daily operations. The goal is not minimal interface at all costs, but proportional interface — where the effort to accomplish something matches its importance and frequency.

Check After Improvement​

  • Hard Mental Operations
  • Visibility

Footnotes​

  1. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. ↩ ↩2

  2. Patterson, D., & Costain, G. (2015). The effectiveness of transient user interface components. In Proc. 16th Australasian User Interface Conference (AUIC 2015), CRPIT 162. ↩