Service

UX design

Research, information architecture, flows and tested prototypes that make a product understandable before it becomes expensive to change.

What it is

UX design is the work of deciding how a product should behave before deciding how it should look. It starts with understanding who uses the product and what they are trying to get done, continues with structure (what goes where, what leads to what) and ends with prototypes that real people have tried.

At Scaledex, UX design is usually the first phase of a build, but it also stands alone: a usability review of a product that is losing users, or the groundwork for a team that will build in-house. We have designed flows for learning platforms, quiz games, virtual events and logistics tools, and the same discipline applies to a marketing site with three pages.

What you get

  • Research you can act on: interviews, task analysis and a review of what your analytics and support tickets already say.
  • An information architecture for the whole product: navigation, content hierarchy and the flows between screens.
  • Wireframes and clickable prototypes, tested with users drawn from your actual audience.
  • For an existing product, a prioritised list of usability problems, each with a proposed fix and an estimate of effort.
  • Annotated designs that developers can build from without guessing, plus a walkthrough with the people who will build them.

How we work

We do not begin in a design tool. We begin with conversations: with you, with the people who answer customer questions, and with users if you can introduce us to them. Five short interviews find most of the big problems.

Structure comes next. We map every screen and state on paper or a whiteboard, agree the navigation and the vocabulary (what things are called matters more than most teams expect), and only then draw wireframes. Prototypes start low-fidelity so nobody gets attached to them, and each round is tested and revised. We stop when the core tasks succeed without help, not when the design looks finished.

Handover is a working session with the engineers, not a file drop. Where we also build the product, the designers stay on the project through launch.

Who it is for

  • Founders with a product idea who need it turned into a set of screens someone can build.
  • Teams whose product works but whose users keep getting lost, and who want evidence about why.
  • Organisations commissioning a build elsewhere who want the thinking done properly first.

If you need visual polish more than structural change, our visual design service is the right place to start.

Process

How it runs

  1. Understand

    Who uses the product, what they are trying to do, and where it fails them today.

  2. Structure

    Flows, navigation and content hierarchy agreed before any visual work starts.

  3. Prototype and test

    Low-fidelity first, then higher, with each round tested with users and revised.

  4. Hand over

    Annotated designs and a working session with the engineers who will build them.

Have a project in mind?

Tell us what you are trying to do. We reply within two working days, with questions before a quote.