[sagichmal]

Dashboards should not "loop" — that totally defeats the purpose of communal screens as information radiators! Screens should always display the same dashboard continuously, so that viewers can passively detect and identify changes.

[jasonv]

Not practical in all circumstances.

For instance, Really Big Enterprises don't always have consensus among teams on what tools to use, and so.. for war/peace rooms, collecting all the dashboards relevant for an operations event is the vital requirement.

[sagichmal]

Incident- or event-based war rooms are special cases, but in those cases, static information radiators are even more important. Saying "Hey everyone, look at what <metric> is doing right now" and having it rotate away is totally destructive to coherence.

If you want more information than can be displayed on available information radiators, they belong on individuals' computers.

[jasonv]

Says you, and probably me, but not the VP for the last event I participated in, which had hundreds of participants across the globe.

Instead the project coordinator used a Chrome plugin to rotate the various dashboards, which were used, if not optimal, for the event.

This tool serves a purpose, and if it does it better than the Chrome plugins that are out there, it'll could provide a lift.

[sagichmal]

This whole comment chain distills down to "some people, who are wrong, don't agree" which is 100% noise, 0% signal. I'm not sure why you bothered replying.