What product UI/UX design includes
From user tasks to layouts, interface states and development handover.
UI/UX design covers journeys, structure, prototypes, the visual system and screen states. The result should explain how the product behaves as well as how it looks.
01. Tasks and context
First, establish what the product helps people do and where they will use it. Interviews, existing analytics and a review of the current product help form working assumptions.
This stage should produce a list of tasks and constraints, not just a presentation. In a customer portal, people might need to download an invoice, check an order and find their account manager. Establish where the data comes from, which roles can see it and what happens when it is delayed. If research is unavailable, label assumptions as assumptions so they can be tested rather than presented as universal customer needs.
02. Structure and prototype
Journeys become a sequence of screens. A prototype lets you review navigation, action labels and information placement before refining the visual style.
Review a prototype through tasks rather than a tour of screens. Ask someone to find an invoice for a particular month or change a contact detail. Observe whether labels and next steps make sense. Reordering actions is easier here than after implementation. Check going back, cancelling and finding that a document is unavailable. A prototype demonstrates interaction logic; it does not establish the speed or reliability of the finished system.
03. Layouts and important states
The main screen is only part of the work. Show loading, errors and empty data states too. Responsive behaviour and accessibility also belong in the design process.
Consider an invoice list. Besides its normal state, it needs loading, an empty list, a retrieval error and restricted access. A long list also needs defined search, filters and pagination. Forms need field labels, relevant error messages and confirmation after saving. Similar-looking situations may require different actions: “no documents yet” and “documents could not be loaded” should not use the same explanation. State design makes those distinctions clear.
- Loading, success, error and empty states.
- Interactive elements, focus and keyboard operation.
- Mobile and desktop journeys.
04. Development handover
We accompany layouts with components, behaviour rules and responsive guidance. Reviewing the implementation with developers helps keep the code aligned with the agreed experience.
Before handoff, check that developers understand reusable components, long-text behaviour and server data requirements. Agree on the design version being implemented; comments scattered across files can conflict. The deliverable is an agreed set of screens, components and behaviour rules, not simply a Figma link. Review the implemented interactions afterwards. Correct layouts do not automatically mean the browser behaviour matches the agreed design, especially around errors and responsive states.
05. Check the journey with users
Choose participants resembling the intended audience and give them a specific task without telling them where to click. Record completion, pauses and questions. A small session can reveal journey problems but cannot prove that an interface works for everyone. Separate navigation difficulties from visual preferences. After changes, repeat the relevant task. This makes decisions depend on observed behaviour rather than votes for a particular colour or layout.
06. Agree the design scope before starting
Roles, journeys, languages, mobile states and integration complexity all affect scope. Ten screens without error handling and ten screens with complete behaviour are different deliverables. Ask whether research, prototyping, components, usability checks and implementation review are included. Agree who writes the copy as well. This lets you compare proposals against the same outcome and understand what the development team will receive and which work remains outside the design engagement.
What to check in a UI/UX handoff
| Deliverable | Readiness check |
|---|---|
| Journeys and prototype | The core task can be followed from start to finish. |
| Interface states | Loading, errors, empty data and permissions are defined. |
| Responsive rules and components | Behaviour across screen sizes and long text is clear. |
| Handoff and review | The version, rules and clarification owner are agreed. |
