The UI/UX design process, and the states most handovers forget
A UI/UX process runs research, information architecture, user flows, wireframes, a design system, then screens in every state — default, empty, loading and error. Its purpose is to reduce the number of decisions made during engineering, which is where the speed gain comes from.
Key takeaways
- Five users surface most serious usability problems; you do not need a large study.
- Every screen needs four states drawn, not one. Missing states are where handovers break.
- Build tokens before components, and components before screens.
- Design QA after the build is what stops the shipped product drifting from the file.
Most design handovers fail quietly. The screens look finished, an engineer opens the file, and three quarters of the states they need are missing — empty, loading, error, long name, no permission. The design was a picture of the product working.
The process, stage by stage
- 01Research. Interviews with real users, a read of what your analytics and support tickets already say, and a competitive teardown that is honest about what competitors do well.
- 02Information architecture. Navigation, hierarchy and naming. What things are called is a design decision people consistently underestimate.
- 03User flows. The paths through the product, including the ones where something goes wrong — which is where most of the real work lives.
- 04Wireframes. Structure before styling, so the argument about what goes on the page happens before anyone has fallen in love with a colour.
- 05Design system. Tokens first — type scale, colour, spacing, radius — then the eight or nine components used on every screen.
- 06Screens. Every one, mobile and desktop, in four states.
- 07Test and hand over. Five users, revisions, specs, then a design QA pass against what was built.
Why a design system is an engineering investment
It is usually sold as a consistency benefit, which undersells it. Its real return is decisions not made twice: when spacing, type and components are defined, an engineer implements rather than interprets. Changing a button in a system is one change; changing it across forty hand-drawn screens is forty changes and at least one you will miss. What to build first is in design system development.
Testing at the scale that is worth doing
Nielsen Norman Group's long-standing finding is that a small number of participants surfaces the majority of usability problems, which is why waiting for a large study is usually a way of never testing. Five people from the target audience, on the devices they actually use, with the findings written down and prioritised.
For Indian products that means testing on a mid-range Android on a throttled connection rather than in a desktop simulator, because that is what most of your users are holding.
Design for conversion, not for the portfolio
On commercial pages, clarity beats decoration and message match beats layout. If the ad promised a specific thing, the H1 should say close to it — every gap between the promise and the page is a moment where some visitors leave. The structure that works is in conversion-focused web design.