Nexux Labs

Interfaces people understand without being trained

Product Design & UX

Research, prototypes and design systems that turn a complicated product into something a new user can finish a task in, on the first try.

Typical timeline
2-6 weeks
Best for
Teams whose product works but nobody finds it easy

The short version

What this service actually involves

Good design is not decoration added at the end. It is the decision about what goes on the screen, in what order, and what gets left off entirely. Those decisions are cheap to change in a prototype and expensive to change in production code.

We work in the open: research notes you can read, prototypes you can click, and a design system handed over as real components rather than a static file. If a screen tests badly, we would rather find out in week two than after launch.

Scope

What is included in a product design engagement

Every item below is in the written scope before work starts, so nothing on this list is an upsell later.

01

User and stakeholder research

Interviews with the people who will actually use the product, plus a review of what your current flow already tells you.

02

Information architecture

The structure of the product: navigation, hierarchy and naming that matches how your users think about their work.

03

Wireframes and clickable prototypes

Low fidelity first to settle the flow, then an interactive prototype in Figma you can hand to a real user.

04

Visual design and UI kit

Type scale, colour, spacing, states and components, documented so two developers build the same button the same way.

05

Design system handover

Tokens and components mapped to code, so the design survives the next three features instead of drifting.

06

Accessibility review

Contrast, focus order, keyboard paths, labels and touch targets checked against WCAG, not left to chance.

How it runs

From first call to live and supported

Five stages, each with something you can see or review at the end of it.

  1. 1

    Understand the job

    What is the user trying to finish, how often, and what currently gets in the way.

  2. 2

    Structure before pixels

    Flows and wireframes reviewed together, so the expensive decisions are made in the cheap medium.

  3. 3

    Design the system, not the page

    Components and tokens defined once and reused, so the twentieth screen costs less than the second.

  4. 4

    Test with real users

    Five sessions on the prototype catch most of what a launch would have caught the hard way.

  5. 5

    Hand over to engineering

    Specs, states and edge cases documented, with us available while the build happens.

Questions

What clients ask before starting

If your question is not here, ask it directly. We answer the awkward ones too.

All frequently asked questions

Yes. Plenty of clients bring us in for research, UX and a design system, then build with their own in-house team. We write the handover for developers we will never meet, which tends to make it better documentation.

Also relevant

Services that usually go with this one

Need product design done properly?

Send us the situation as it is, including the parts that are messy. We will tell you what we would do first and what it would cost.

whatsapp-icon Nexux