Crit found a warning icon louder than the problem it flags. On severity as a volume knob, and what happens when a designer calls out her constraint.
Silent crit this week took up a warning state on the calendar our users spend time with day in and day out. The brief is sound: clinicians need to know about a problem with a client’s setup before the session starts, so the design surfaces a warning when something is off and stays quiet when everything is fine. Silence for the healthy state is the right instinct. The trouble was the voice it used when it spoke. (things got loud)
The room’s verdict was unanimous, which is rare for us: the warning icon was louder than the problem. This kind of flag is a problem for this week, and the icon said the building was on fire. Severity is a designed variable, a volume knob, and most of us only ship it at ten. Our users know the failure mode better than we do; in clinical settings it’s called alarm fatigue, and the outcome is always the same. When everything shouts, people stop hearing all of it, including the one alarm that mattered.
Severity is a volume knob, and most of us only ship it at ten.
The better lesson was how the designer took it. No defense, no explanation of intent. She agreed the treatment was too strong, and then she called out her constraint: rebuilding the surface would be ideal, it isn’t on the timeline, and the team is working within what exists. Most crits die of unspoken constraints; feedback piles up against a version of the problem the designer isn’t allowed to solve. Drawing the box converts the room from wishing to helping.
And the room changed on the spot. Rebuild proposals stopped, treatment proposals started: quieter iconography, reserved color, warning states that scale with the consequence. Revisions go to the design channel next. The icon will get quieter. The move worth stealing is the sentence that made the feedback useful.
The teachable part
Treat severity as a designed variable: match the alarm to the consequence and reserve the loudest treatment for the rarest state. In crit, call out your constraints before feedback starts; the room can only help with the problem it’s allowed to solve.