DEV Community

Cover image for UX Design Myths That Sound Sensible Until You Ship
Foundry 5
Foundry 5

Posted on

UX Design Myths That Sound Sensible Until You Ship

Ask a room of founders what UX design is for and you will hear a version of the same answer: making the product look good so people trust it. That answer is not wrong, exactly. It is just small enough to cause real damage when it becomes the basis for how a team spends its design budget.

Here are four beliefs that sound reasonable in a planning meeting and turn expensive later.

Myth: Design is what happens after the requirements are settled

The tidy version of a product build goes: decide what to build, then design it, then engineer it. Design sits in the middle as a translation step, turning a spec into screens.

The problem is that requirements are usually guesses. Someone believes users will want a particular flow, and the design job becomes making that flow look convincing. Nobody has watched a real person attempt it. By the time the flow is built and tested, the guess has hardened into code, and changing it means a sprint rather than a sketch.

Design that earns its keep sits earlier than that. Research and journey mapping are not extras bolted on before the visuals; they are the part that tells you whether the thing you are about to build is the right thing. Teams that treat design as decoration discover the answer in production, where it costs the most.

Myth: A beautiful mockup is a finished design

A polished screen in a design tool creates a strong sense of progress. Stakeholders approve it, the meeting ends well, and everyone assumes the design is done.

What the mockup does not answer: what happens when the field is empty, when the network drops, when the text is twice as long in German, when the user is on a small phone in bright sunlight. Those states are where products actually break, and they are rarely in the picture.

A design that is genuinely ready for engineering carries interaction detail, responsive behaviour and the awkward edge cases. Without them, developers fill the gaps with assumptions. The build drifts from the design, and both sides end up frustrated with the other.

Myth: Consistency is a nice-to-have for later

Early on, every screen gets designed on its own terms. It feels faster. There is no system to think about, just the next page.

The cost arrives quietly. Spacing shifts by a few pixels between screens. Buttons behave differently in different places. Users cannot say what is wrong, but the product starts to feel like several apps stitched together, and trust erodes with each inconsistency.

A shared set of components, spacing rules and type scales is cheaper to build early than to retrofit. The interesting part is that it also speeds up development, because engineers map tokens to code instead of guessing at values.

Myth: User testing is a luxury for big budgets

Testing has a reputation as a formal, expensive phase involving a lab and a report nobody reads. So it gets deferred until there is time, which is to say never.

In practice the useful version is small and early: watching a handful of people try the flows that matter, before a line of code exists. The findings are rarely subtle. What matters is that they arrive while changes are still cheap.

The belief that design is about making things attractive is not so much false as incomplete. Attractive is a side effect of clarity, and clarity comes from evidence. Teams that skip the evidence do not save money; they move the spend to a later, more painful stage.

There is a fuller version of this argument, with the specific methods behind each of these points, on the UX UI design services in London page.

Top comments (0)