The Fear Rationale
It arrives as a rationale. "I'm afraid that if we do it this way, people won’t..." or "I'm afraid not having it will cause..." The concern sounds considered. It sounds like user advocacy.
It isn't.
It's a decision-maker managing their own discomfort and presenting it as strategy.
The phrase
When "I'm afraid that..." becomes the rationale for a design decision, the conversation has moved away from the user. Fear-based decisions are, by definition, about the person experiencing the fear. The user's actual behavior, the evidence of how people navigate similar contexts, the structure of what the product needs to do: none of it enters the frame. The feeling does.
I've sat in enough of these conversations to recognize the pattern. The project is going well. The work is holding. Then fear enters the room. And it enters not as a risk to be evaluated, but as a reason to undo what was already established. Because it's framed as caution, it's difficult to name for what it really is.
What it produces
Design built from fear is additive by construction. The navigation gets overloaded because someone was afraid a user wouldn't find something. More buttons appear, more options surface, more pathways open. Each one added to manage a specific anxiety about what might be missed.
Every one of those decisions protects the person making it. The person using the product is an afterthought.
The result is decision fatigue. The user arrives with too many directions to go and no clear signal about which one matters. The friction shows up in behavior: the task that takes longer than it should, the drop-off that nobody in the meeting anticipated. The product doesn't fail dramatically. It just doesn't quite work, and people move on.
What the work requires
Good design decisions are made from clarity about two things: what the product needs to do, and who it needs to do it for. That kind of clarity isn’t comfortable either. It requires commitment to a position. It means some people will encounter the work and it won't be for them.
That discomfort is structural. A product designed specifically enough to serve its actual users will not work equally well for everyone.
Fear tries to design around that. To produce something no one will object to. The result is something no one particularly needs.
The products that hold were built from a clear answer to a harder question than "What are we afraid of?"
Alex Corvin
I'm a strategic brand designer building identities for established ventures, mission-driven non-profits, and luxury labels who treat design as structural, not decorative. My work is rooted in the Swiss design tradition of clarity and precision — brand as infrastructure, built to carry load.
If your brand is starting to feel like a collection rather than a system, start a project.
