The redesign that looked better and performed worse
It's a familiar story: a product gets a redesign, everyone on the team agrees it looks cleaner, and conversion quietly drops. Nobody planned for that outcome — it happened because "looks better" and "performs better" aren't the same claim, and only one of them was ever actually tested.
Why skipping research feels efficient (and isn't)
Research takes time upfront, which makes skipping it feel like progress. But a redesign without research isn't actually faster — it just moves the cost from "before shipping" to "after shipping," where it's more expensive to fix. A UX mistake that isn't caught in testing gets caught in production, where reversing it means another redesign cycle, more engineering time, and weeks or months of lost conversion in the meantime.
What research actually buys you
The value of research isn't validation of what the team already believes — it's the ability to catch a wrong assumption while it's still cheap. A five-user testing round on a prototype costs a few days. Discovering the same problem after launch costs a quarter.
Research also protects against a subtler risk: designing for the loudest internal opinion rather than the actual user. Without evidence, decisions default to whoever argues most convincingly in the room — which has no necessary relationship to what real users need.
The minimum viable version
Full research programs aren't always necessary. Even a lightweight pass — a funnel audit to find where users actually drop off, five user testing sessions on the current experience, a quick competitor benchmark — is usually enough to separate real problems from assumed ones before committing to a redesign.
The takeaway
A redesign is only as good as the assumption it's built on. If that assumption hasn't been tested against real user behavior, "looks better" is a coin flip, not a plan — and the cost of being wrong only grows the longer it goes unchecked.
