Skip to main content

Warning Priority Lab

Allocate seven warning types across scarce visual and audio resources, across three driving scenarios.

A dashboard has a small number of ways to demand attention: one primary visual zone large enough to dominate the driver's view, a strict cap on how many sounds can play at once before they blur into noise, and one slot for a full-screen interrupt that takes over the whole cluster. It has seven warnings that might all want one of those at the same time.

Below, allocate a visual zone, colour tier, sound, persistence, and (where you think it's warranted) the full-screen interrupt to each warning that's active in the current scenario. The scarce resources are enforced live — claiming the primary zone or the interrupt for one warning takes it away from whichever warning held it before, and only two warnings may sound at once. Switch scenarios to see which warnings are even active, and how urgently.

When you're satisfied with an allocation, compare it against a reference design for that scenario. The comparison isn't a score: it's a rationale for a different set of choices, so you can decide where you agree and where you don't.

Scarce resources
  • Primary visual zone: 0 / 1 in use
  • Concurrent sounds: 0 / 2 in use
  • Full-screen interrupt: 0 / 1 in use
Instrument cluster preview

No active warning has been given the primary zone yet.

Closing reflection

Pick one warning where your allocation still disagrees with the reference design after reading its rationale, in any scenario. Write two or three sentences defending your choice — not restating the reference's reasoning, but arguing against it.