First UX, then UI: research-led product design
Beautiful screens built on the wrong assumptions are expensive to unwind. Why we resolve the workflow before we style the pixels.
There’s a seductive order of operations in product work: open the design tool, make something gorgeous, then figure out whether it solves the problem. It feels productive because you have artifacts to show. It’s also how teams end up polishing the wrong thing.
Resolve the workflow first
Good product design front-loads the cheap questions before the expensive ones:
- Who is this for, and what are they actually trying to accomplish? Not the feature, but the underlying job.
- What’s the real workflow? The sequence, the edge cases, the moments people get stuck. Complex domains like payments, healthcare, and logistics live and die here.
- What’s the simplest thing that could work? Structure and flow before color and type.
Get these right and the interface almost designs itself. Get them wrong and no amount of visual craft will save it.
UI is where trust is earned
None of this means visual design is optional. Quite the opposite. Once the workflow is sound, the interface is where credibility is built: clarity, hierarchy, responsiveness, the small interactions that make software feel considered. But UI is an amplifier. It multiplies whatever the underlying UX is worth, positive or negative.
Research doesn’t have to be heavy
“Research-led” scares people who imagine months of studies. In practice it’s often a handful of user conversations, a walk through the real workflow, and a prototype tested with actual users before a line of production code is written. Cheap insurance against building the wrong thing.
The teams that turn complex workflows into interfaces people enjoy using are the ones that earned the right to draw the pixels, by understanding the problem first.