When Calm Designers Meet Crisis Users: The Mental‑Health App That Missed the Moment
A real-world example of Empathy gap in action
Context
A mid‑stage startup built a mobile app to help users manage acute anxiety and depressive episodes with quick exercises, safety plans, and peer support chat. The product team—largely composed of engineers and designers working in stable, low‑stress conditions—relied on short usability tests and analytics from beta users to finalize the launch.
Situation
At launch the team prioritized a clean interface, minimal friction for signups, and a single 'report a problem' button routed to email. They assumed users would behave rationally: read onboarding, select coping strategies, and reach out for help if needed. The team did not run extended studies with users in highly distressed states, nor did they include real‑time crisis telephony or immediate escalation flows.
The bias in action
Team members, calm and composed during design sessions, underestimated how differently people behave under acute emotional distress (the empathy gap). They assumed users would follow menus and toggles patiently instead of needing immediate, low‑cognitive‑load support. Risky design decisions—placing critical help links behind two screens, requiring a password to access emergency contacts, and sending only asynchronous email reports for safety incidents—reflect a failure to predict user behavior under emotional duress. Internal metrics that looked healthy in calm test sessions masked how the app performed when users were panicked or overwhelmed.
Outcome
Within weeks of release, support logs and user feedback revealed multiple instances where users couldn't find or act on emergency options quickly. Several users reported escalating crises because they hesitated navigating the interface. The startup faced public criticism, a liability review, and user trust eroded as social media posts described the app as 'unhelpful during a breakdown.'



