Week 6 Studio: Ranking alerts by ear alone
Students listen blind to a set of real dashboard alert sounds and try to rank them by intended urgency using only what they hear
29 March 2027
Before the studio#
No preparation required. Come as you are; the exercise depends on hearing these sounds without context, so don’t look up dashboard alert clips beforehand.
In the studio#
Idris plays a set of real dashboard alert sounds back to back, stripped of any visual context — a seatbelt chime, a low-fuel ding, a lane-departure warning, and park-assist proximity beeping among them, unlabelled and in a shuffled order. Working alone first, everyone writes down a guessed ranking from “can wait” to “respond now,” plus one sentence per sound describing what about it produced that ranking. Only after rankings are locked in does the group compare notes and the sounds are named. The interesting disagreements aren’t about which sound is loudest — they’re about which sounds two people ranked in opposite orders, and why one person heard “insistent” where another heard merely “repetitive.”
Afterwards#
Pick one alert from the set that your ranking got wrong relative to its real-world stakes, and write down what specifically misled you: was it too calm for what it signals, or too frantic? Keep that note — Idris returns to it when we look at alarm fatigue and false alarms later in the course.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you can justify your urgency ranking using specific sound properties (pitch, tempo, repetition, timbre), not just gut feeling
- you can name at least one alert whose sound felt more or less urgent than the situation it signals actually warrants
- you can describe, in words, the difference between two alerts a non-designer would call "basically the same beeping"
Teaching team
- Idris Fenn — tutor