UX & Product Design

Products people can use, and that move the business forward.

Situations

When this service helps

Design is often reduced to how things look, but most product failures are failures of understanding. The workflow doesn't match how people work, or the interface needs explaining, or the experience suits the organisation better than the people using it.

What it can look like from the inside

  1. The workflows don't match how people actually work.
  2. The interface needs explaining before anyone can use it.
  3. The experience is built around internal convenience rather than what users are trying to achieve.
  4. The product has grown feature by feature without a coherent structure, so new capabilities get bolted on and navigation keeps getting deeper.
  5. Research points one way and commercial pressure another, with no process that holds both in view.

Who it suits

  • New digital productsOrganisations building something new.
  • Platform redesignsOrganisations redesigning an existing platform.
  • Adoption and satisfactionProducts that work technically but not well enough for the people who use them.

We work with product teams who want design embedded in decision-making rather than delivered as a layer at the end.

People leave not because the technology failed, but because the product became too hard to understand.

Deliverables

What we deliver

We design intuitive, human-centred products that balance what users need with what the business is trying to achieve.

What we do

  1. Map journeys and friction

    Before we draw screens, we map journeys, identify friction and work out what users are trying to accomplish at each step.

  2. Hold business and user needs together

    Business objectives and user needs are treated as paired constraints rather than a compromise, and together they shape better solutions.

  3. Simplify

    Every element on a screen should earn its place. We remove what confuses, consolidate what fragments and make the primary action obvious without explanation.

  4. Prototype to think

    Early prototypes exist to test assumptions with real users and stakeholders, quickly, cheaply and honestly, rather than to impress.

  5. Stay involved through implementation

    Design decisions lose their meaning when they're handed over as static files. We work alongside engineering to preserve intent, adapt when reality intervenes and make the pragmatic calls that protect the experience.

What you leave with

The aim is a team that can evolve the product with confidence.

  • Prototypes that test assumptions

    Early artefacts, tested with real users and stakeholders.

  • Clear patterns

  • Documented decisions

  • A design system that scales

    Built to scale rather than fragment.

  • Design intent carried into delivery

    Preserved alongside engineering through implementation.

Client work

Design in practice

One Vasco

Visa applications guided from start to finish, so travellers know they've done it correctly and haven't just submitted the form.

One Vasco's experience was designed around reassurance rather than forms, answering the questions applicants naturally ask: what happens next, whether everything has been done and where their application is now.

Industry
Travel Technology
Role
Product definition, user experience design and digital platform design.
Engagement
  • Product Strategy
  • UX Strategy
  • Product Design
  • Mobile Experience
Outcome
A digital visa platform that simplified the application experience while combining automation with expert human support.
Read the One Vasco case study

Collaboration

How we work together

Design works best when it's part of decision-making from the start.

Our part

We design from understanding rather than from a blank screen, and we're willing to recommend removing features that add complexity without proportional value. We also resist the kind of perfectionism that delays learning.

Together

We test assumptions with real users and stakeholders, and we work alongside engineering through implementation. Keeping the same people involved from problem to prototype to production means the product reflects a single line of reasoning.

Decisions along the way

Every design choice favours some users and behaviours over others, so we make those choices visible and let you own them deliberately. We also help decide what to remove or consolidate, and which pragmatic calls protect the experience when reality intervenes.

A good product in users' hands beats an ideal product in a design file.

Outcomes

  1. Products users adopt.
  2. Patterns and a design system that scale.
  3. Decisions documented, not forgotten.
  4. Measurable improvement where it matters.

What clients leave with

Clients end up with products that users adopt because they are easier to understand and easier to use. Teams can evolve the product with confidence, with clear patterns, documented decisions and a design system that scales rather than fragments.

The improvement we look for is measurable in the outcomes that matter: completion rates, time to task and support burden, along with the qualitative signal that users trust the product.

Questions

Practical questions

Is design just how a product looks?

No. Design is often reduced to appearance, but most product failures are failures of understanding. The real measure of good product design isn't aesthetic approval but whether someone can accomplish what they came to do without needing help.

Who is this work for?

Organisations building a new digital product, redesigning an existing platform, or trying to improve adoption and satisfaction on something that works technically but not well enough for the people who use it.

Where does the design process start?

With understanding rather than screens. Before we design anything, we map journeys, identify friction and work out what users are trying to accomplish at each step.

Do you hand designs over to engineering?

Not as static files. Design decisions lose their meaning when they're handed off, so we stay involved through implementation, working alongside engineering to preserve intent, adapting when reality intervenes and making the pragmatic calls that protect the experience.

How will we know it worked?

We look for measurable improvement in the outcomes that matter, such as completion rates, time to task and support burden, along with the qualitative signal that users trust the product.

Will you recommend removing features?

Yes, where they add complexity without proportional value. We'll also resist the kind of perfectionism that delays learning.

The measure of good product design isn't aesthetic approval. It's whether someone can accomplish what they came to do without needing help.

When design and engineering share context, and the same people stay in the room from problem to prototype to production, the product reflects a single thread of reasoning. That continuity is where design creates the most value.

Ready to move on this?