Skip to content

Service · Design

UI/UX Design

Commission design on its own when your engineers, or another agency, will build the product and you need the thinking done first. We research the people and tasks, structure the flows, test a realistic prototype and hand over a design system precise enough to build without guesswork.

Prototypes tested with real users before handover

Every state designed, not only the happy path

Figma library with tokens your engineers can map

Deliverables

What a product UI/UX design engagement delivers.

01Delivered

Research summary

Findings from interviews, observation sessions, support tickets and analytics, written as the problems users actually face, each with the evidence behind it and an honest note of its limits.

02Delivered

Task flows and information architecture

The objects users work with, the actions they take, which roles may do what, and how navigation groups it all, mapped before any visual design so structure problems surface early.

03Delivered

A realistic, tested prototype

An interactive prototype using real content and data volumes, tested with representative users, with a short report on what changed as a result.

04Delivered

A component library and tokens

A Figma library of components with variants and states, plus colour, type, spacing and radius tokens named so engineers can map them straight into code.

05Delivered

Annotated screen specifications

Final screens covering empty, loading, error, partial and permission-denied states, with behaviour notes, responsive rules and accessibility annotations for focus order and labels.

Early decisions

Technical decisions we settle early in product UI/UX design.

01Decided

Which users and tasks come first

Complex products serve several roles. We agree which role and which tasks the engagement must get right, so research and testing time is not spread too thin to be useful.

02Decided

Platform conventions or a custom language

Following Apple’s Human Interface Guidelines and Material Design makes an app feel familiar. A strong brand may justify departures, but every departure costs build time and user learning.

03Decided

Accessibility target

We usually design to WCAG 2.2 level AA. Agreeing that before visual work means contrast, target sizes and focus handling are part of the design rather than fixes requested later.

04Decided

How the library maps to code

If your engineers use an existing component kit, the design library should mirror its components and props. Designing in isolation from the code creates a translation step on every screen.

05Decided

What evidence is enough

Some decisions need moderated usability sessions; others can be settled with analytics or a quick preference test. We match the method to the risk rather than running the same study for everything.

Engagement

How a product UI/UX design engagement runs.

  1. 01Phase 1

    Understand the work and the people

    Stakeholder interviews, a review of the current product and data, and sessions with users doing the real task, ending in a shared list of problems worth solving.

  2. 02Phase 2

    Structure before surface

    Flows, information architecture and low-fidelity wireframes are reviewed with your product and engineering leads, so feasibility questions are raised while changes are still cheap.

  3. 03Phase 3

    Prototype and test

    A higher-fidelity prototype is tested with users. We revise it, test again where the first round exposed real confusion, and record what each change was meant to fix.

  4. 04Phase 4

    System, specification and design QA

    The component library and annotated screens are finalised and walked through with your engineers. Where they build during the engagement, we review implemented screens against the design.

Fit

When a design-only engagement is the right choice.

01Good fit

You have engineers but no designer

Capable in-house teams building on instinct often produce screens that work but confuse. A design engagement gives them a tested blueprint to build from.

02Good fit

A complex workflow needs untangling

Back-office tools, scheduling, claims or approvals with many roles and exceptions benefit from structured flow mapping more than from a visual refresh.

03Good fit

A redesign must be justified

When leadership needs evidence that the new design is better, research and usability testing give a clear before-and-after rather than taste.

Design is a decision, not decoration

Most products that confuse their users do not suffer from ugly screens. They suffer from flows that mirror the database rather than the task, labels written by engineers for engineers, and states nobody thought about. Visual polish on top of that structure only makes the confusion look professional.

So we spend the early part of an engagement on what users are trying to get done and in what order, and we write those findings down before drawing anything that looks finished.

Designing the states people actually see

A screen with perfect sample data is a small part of real use. People meet empty lists on day one, slow connections, validation errors, half-saved drafts and features they lack permission for. Each of those needs a design, or engineers invent one under deadline. Our specifications cover them screen by screen.

Testing with people, not opinions

Stakeholder reviews are useful for catching business rules, but they rarely predict where users will stumble. A handful of sessions with people who do the real task tends to reveal the problems that matter most. We test a prototype built with realistic content, because placeholder text hides the truncation and scanning problems that real names and numbers create.

Accessibility from the first wireframe

Contrast, target size, focus order, readable error messages and labels for screen readers are cheapest to get right while shapes are still grey boxes. We design against WCAG 2.2 criteria from the start and annotate the specifics engineers need, rather than handing over pictures that fail an audit later.

A handover engineers can build from

The test of a design engagement is whether engineers can build it without a stream of questions. We name components and tokens to match the code they will become, show every variant, and walk your team through the library. When they start building, we review implemented screens against the design and log any drift.

FAQ

Questions to resolve before the build.

01What changes the cost of a design engagement?

The number of user roles and tasks in scope, how much research is needed and whether users are easy to reach, the number of usability rounds, whether a component library is built from scratch or extends an existing one, and the number of platforms and breakpoints designed.

02How long does the design work take?

It depends on access to users for research and testing, how quickly stakeholders review, the breadth of flows in scope and how many test rounds the findings call for. Recruiting participants is often the slowest step, so we start it in the first days.

03What do we get at the end?

The research summary, flow and architecture maps, the tested prototype and its test report, the Figma component library with tokens, annotated screen specifications for every agreed state, and a recorded walkthrough for engineers who join later.

04Who owns the designs and research?

You own the design files, research notes and outputs. Recordings of user sessions are handled under the consent participants gave, which we agree with you before recruiting. Third-party fonts and icon sets keep their own licences, which we list.

05How do we sign off design work?

Each stage ends with a review against the goals agreed at the start: flows are accepted before visual design, the prototype after testing, and the library and specifications once your engineers confirm they can build from them without open questions.

06What is not part of a design-only engagement?

Writing production code, building the backend, brand identity work such as logos, and copywriting beyond interface text. Design QA on implemented screens is included only when your team is building during the engagement.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Web Content Accessibility Guidelines (WCAG) 2.2

    The W3C standard used as the accessibility target for interface design.

  2. 02
    Apple Human Interface Guidelines

    Apple’s guidance on interface conventions across its platforms.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.