Information displays should be annotated, combining words, images, graphics, whatever it takes to describe and explain something. Annotation calls out and explains information and, at the same time, explains to viewers how to read data displays. Good annotation is like a knowledgeable expert/teacher at the viewer's side pointing and saying, "Now see how this works with that, how this might explain that..."
Yehudi Menuhin, a great violinist, marked up a score for Bach's Sonata No. 2 for Solo Violin. Penciled annotations show real-time performance strategies. To outsiders, insider markups appear chaotic and cryptic, but these personal annotations are for Menuhin's eyes, the only eyes that matter. All can learn from this useful workaday grid strategy: a relevant and intense data layer can become a coherent substrate scaffold upon which to overlay additional information. Maps do this all day long.
The Agile founders had it right, one size doesn't fit all. What the founders perhaps didn’t foresee, or couldn’t agree on, is that in order for the world to scale and consume their wisdom, it had to be packaged as concrete practices, not as abstract classes with virtual methods to be defined in context. And to the proponents of Agile Scrum, give them their due, for their part, they made it concrete – Agile Scrum has been packaged and delivered. Yet much work remains to realize the promise of Agile, which in summary is, the realization of wise use of lightweight development practices and workflows that flexibly adapt to the changing and evolving needs of customers.