Skip to main content

Designing for Sad Paths, Not Just Happy Ones

The happy path is what designers and PMs spec. The sad paths — errors, timeouts, empty states, partial successes — are what users actually hit on bad days.Spend 20% of design time …

March 8, 2026 Product chris 1 min read Accessibility

Article takeaway

The happy path is what designers and PMs spec. The sad paths — errors, timeouts, empty states, partial successes — are what users actually hit on bad days.Spend 20% of design time …

The happy path is what designers and PMs spec. The sad paths — errors, timeouts, empty states, partial successes — are what users actually hit on bad days.

Spend 20% of design time on sad paths. The investment shows up in support tickets, retention, and trust.

The simplest sad-path test: kill the network mid-flow. What does the UI do? What does the user know? What can they do next?

Share X / Twitter LinkedIn

Leave a comment

Related Posts