Similar to the principle of “Make it Obvious“, and “Make Problems Visible“, this principle is more about delivery than content. The content must be delivered “In a Glance” – that is, the user must look at it and understand immediately what he/she is looking at, know what he/she should do with that information, by when, and who are involved.
As an example, In a Glance, this site tells us how how many dead birds, dead sea turtles, and dead mammals there are from the BP Oil Spill; how many oiled but alive and how many cleaned and released.

In a Glance,

Straightforward. Simple. Informative. Very sad.
![]() |
![]() |
![]() |
||
This post was written by Pete Abilla | ||||









Jeff Bezos and Root Cause Analysis
The Apple iPhone Supply Chain
The Toyota A3 Report
Queueing, Disneyland, and FastPass
Zipcar Customer Experience: Variability, Utilization, and Queueing
Visual Management and Self-Reliance
Process Control and Luck
Poka Yoke Example: Prevent Error Through Embarrassment and Humiliation
Quality and Continuous Improvement;
{ 2 comments… read them below or add one }
Whilst they show something visually, I’d like something that shows what action to do/where to focus next.
Perhaps they would be better if the other rows also featured scaled images to show that there is something that could be done to mitigate what has passed.
I would consider the table of numbers to be biased, showing only the negative side.
Disclaimer: this comes as someone who enjoys diving and sponsors turtles
Similar to Kevin W’s comment, although the picture does “communicate”, it falls short on the other elements of In a Glance.
1. what he/she should do with that information
2. by when
3. who are involved
I would like to see more examples of this, as I would like to apply it to my work. Very interesting.
Thanks,
Ryan