View Single Post
Quote:
Originally Posted by intranation View Post
You've both been very rude
No, it is neither rude nor irrelevant to suggest the reading of something like Tufte.

Quote:
Originally Posted by intranation View Post
the contrast is out of whack
Indeed - shouting lozenges and frame edges, and useful but over-insistent new labels.

Omni has, alas, a bit of a track record of inadvertent regressions in graphic design. Quite understandable (and helpful) to hear a range of irritated voices whenever this occurs - distracting design (a bad signal-to-noise ratio in the management of contrasting edges) wastes attention, which is a scarce and jealously guarded resource for any professional.

The fact that these regressions continue to occur suggests two things to me:
  1. The company culture has yet to acquire a pervasive awareness of the need to carefully manage levels of visual stimuli (contrast levels at edges), and align them closely with information hierarchies. Visual signal-to-noise ratios do not seem to figure very prominently or explicitly in discussions of software design goals.
  2. Project coordination does not seem to explicitly manage the issue of visual contrasts created inadvertently at the borders between sub-projects. For example: edge-detection in the retinal system is particularly sensitive to vertical and horizontal edges, so some of the strongest visual stimuli in the 1.7 default screen are generated at the two high-contrast edges between the filter area and its gray neighbours. Do these very strong visual signals convey correspondingly significant information ? No, they are virtually information-free, (dispensable, in fact), yielding an appalling ratio of cognitive processing cost to cognitive benefit. Did anyone advisedly decide to place strong visual stimuli at these positions ? No, I would guess that they didn't - these look like inadvertent and unmanaged artefacts of adjacent subprojects. Cognitively costly spandrels.

Quote:
Originally Posted by intranation View Post
not to wave the pedant flag too much, but Tufte is generally aiming his work at the presentation of information, rather than interface design.
As for particular reading material, these matters are not discipline-specific: they emerge from the structure of the retinal system, and from the general balance between information acquisition and cognitive processing cost. Tufte happens to have a particular interest in software design, and states the basics of visual communication in good non-technical terms ('minimum effective difference' is a very useful formulation, for example), One could, of course, learn the same lessons from completely general accounts of communication, such as relevance theory.

No need to plumb the depths of communication theory or retinal physiology, however, when the basics of visual signal-to-noise ratios are so easily grasped, and so central to software quality and customer satisfaction.

There is clearly room for them in Omni's design culture, and Tufte is an excellent place to begin.


RobTrew

--

Last edited by RobTrew; 2009-08-29 at 08:00 AM..