In short

Product design is the work of deciding how a digital product looks, feels and behaves, so people can get what they came for without effort. At Fat Elephant it covers UX research, user journeys, wireframes, prototypes, UI design, design systems and usability testing, and it is done alongside the engineers who will build it.

What We Do

What we do: Product Design

Six parts of the design process, used together or on their own. Most products need all six in some form, but the weight changes from one product to the next.

UX research

We find out who will use the product, what they are trying to do and where today's tools let them down. Conversations and observation come first, so the design starts from how people really behave, not from assumptions in a meeting room.

User journey mapping

We map the path a person takes from first arriving to getting what they came for, including the awkward moments in between. The map shows where to simplify, where to reassure and which steps can go altogether.

Wireframes and prototypes

Rough layouts first, then clickable prototypes you can hold in your hand. You can try the product, argue with it and change it while changes are still cheap, long before any code exists.

UI design

The visual layer: type, colour, spacing, icons and motion. We aim for screens that look good, read clearly and feel like one product, on every device people will use it on.

Design systems

A shared kit of components, styles and rules, so every new screen looks and behaves like the last one. A design system keeps a growing product consistent, and it saves your team from redrawing the same button again and again.

Usability testing

We put the prototype in front of real users, watch where they hesitate and fix what we find. It is the quickest way to learn what works, and it is far cheaper than finding out after launch.

The Process

How it works

Three phases, with engineers in the room from the start, so what we design is also what can be built.

  1. Understand

    We learn the product, the people and the problem. Research, interviews and a look at what already exists give us a clear picture of what the design has to achieve.

  2. Design

    We sketch, map and prototype, sharing work early and often. You see rough ideas before polished ones, so you can steer while it is still easy to change direction.

  3. Test and hand over

    We test the prototype with real users, refine it and hand over clean, organised design files with a design system. Our engineers can start building straight away, or your own team can.

Honest Fit

Who it's for, and who it isn't

A good fit if you are

  • Founders with a clear idea and nothing on screen yet
  • Teams whose product works but is hard to use or to explain
  • Companies that need one consistent look across many screens or products
  • Anyone who wants to test with users before committing to a build

Probably not for

  • Projects that only need a logo or brand identity, which is a different kind of work
  • Teams who want screens drawn to match a fixed opinion, with no testing
  • Anyone hoping design will rescue an idea nobody wants. We'll say so early, and strategy work may need to come first
FAQ

Questions we get asked

What is the difference between UX and UI design?

UX design is about how a product works: the flow, the structure and how easy it is to get things done. UI design is about how it looks: type, colour, spacing and detail. Good products need both, and we do them together.

Can you redesign a product that already exists?

Yes. We look at how people use it today, find where they struggle and redesign the parts that matter most. It does not have to be all or nothing.

What is a design system, and do we need one?

A design system is a shared set of components, styles and rules that keeps a product consistent as it grows. A small product can start without one, but anything that will keep growing is easier to build and maintain with one.

How do you test a design before it is built?

We build a clickable prototype and ask real users to try it while we watch. Where they hesitate or get lost shows us what to fix, and we fix it before any code is written.

Will the designers work with the engineers?

Yes, from the start. Engineers see the designs early and flag what is easy, hard or costly, so the design fits what can really be built, and nothing is lost in handover.

How long does it take, and what does it cost?

It depends on the size of the product and how much research it needs. Tell us what you are trying to build and we will suggest the right starting point, with a clear scope agreed before any work begins.

Have an idea worth building?

Tell us what you are trying to build, and we will suggest the right place to start.