Skip to main content

Strictly necessary · always on

Remembers this choice in your browser. No tracking.

Design

Design for the person on the other side of the screen.

A nurse between two patients. A driver in the snow. A customer halfway through opening a bank account. We study what they do, design for it, and build what we designed.

Measure behavior, not opinions.

Where it starts

It starts with empathy.

Our design practice has one founding question. Dragana Krtinic, our Chief Design Officer, first asked it in a talk to a room of engineers.

The answer shaped how we work. Designers sit in the research sessions. Engineers watch the recordings. Nobody gets to design for a user they have not met.

Doesn’t user experience mean knowing how users feel? And to know how people feel, don’t you need intuition? To grow your intuition, don’t you need empathy?

Dragana Krtinic, Chief Design Officer, in “Empathy-Driven Design: What Engineers Need to Hear”
Read the talk
Illustrated designer looking doubtfulThe same character raising a hand with an ideaThe same character smiling and making a peace signThe same character with a heart where the thought was

Does any of this matter here?

But wait.

Knowing how people feel is the job.

Keep it humane.

What we believe

Four lines we keep coming back to.

Each one is a line from something we published. They still settle arguments here.

  1. 01
    Keep it humane!

    User experience means knowing how people feel. A product that is kind to a tired, distracted, or anxious person is a product that works.

    From: Empathy-Driven Design: What Engineers Need to Hear
  2. 02
    Measure behavior, not opinions.

    People describe one product and use another. We watch the session, read the heatmap, and count who finishes. Approval in a meeting is not validation.

    From: Prototyping is About Validation
  3. 03
    Never leave your users in the dark.

    Empty screens, slow connections, and errors are part of the product. Each one tells the person what is happening and what to do next.

    From: Embracing the State of Emptiness
  4. 04
    A confusing interface is formally a hazard.

    In a clinic, a vehicle, or a bank, usability is a safety and compliance matter. The required field and the regulator's disclosure are designed, not bolted on.

    From: Key UX Considerations When Designing for IoT
What we look for

Four questions about the people who use your product.

  1. 01

    What motivates them?

    Interviews, personas, jobs to be done

    What the person is trying to get done, and what they would do if your product did not exist.

  2. 02

    How do they behave in the product?

    Usability sessions, heatmaps, analytics

    Where they look, what they tap, and what they never find. Recorded, so the whole team sees it.

  3. 03

    Where do they drop off, and why?

    Journey maps across every channel

    The step where a customer gives up is usually a step nobody on the team owns.

  4. 04

    What makes them use more of it?

    Prototypes tested each iteration

    The change that earns trust is tested with real users before anyone builds it.

The UX audit

Find what is in the way. Then remove it.

An audit is an outside read of your product, grounded in evidence from the people who use it. There is no single right way to run one. This is what ours contains.

An illustration of the four patterns from the banking redesign, not the bank's screens.

Findings

  1. Progressive disclosureBefore: Twelve fields at once, before the customer knows why.After: One question at a time. Only what this step needs.
  2. Progress indicatorsBefore: No sign of how much is left, or what happens next.After: The customer always knows where they are and what is next.
  3. Inline validationBefore: An error count after submit, and no word on how to fix any of them.After: Each answer is checked as it is given.
  4. Smart defaultsBefore: The customer retypes what the bank already knows.After: Known answers are filled in, and stay editable.

  1. 01

    Research

    User research aligned with what the business needs: who the users are, what they came to do, and where the product fails them.

  2. 02

    Heuristic review

    Every key screen and flow read against established usability principles, accessibility included.

  3. 03

    Usability testing

    Representative users work through real tasks, in person or remote. We watch what they do.

  4. 04

    Benchmarking

    Your product next to the ones your customers compare it with.

  5. 05

    The report

    The issues, the evidence behind each, and recommendations that were tested. Presented in the room, not mailed over.

When teams ask for one

  • Before a redesign

  • A new product is not performing

  • The user base has to grow

Then we design it, and build it

An audit ends with a report. Most of our partners keep going: user journeys, wireframes, prototypes tested at each iteration, and a design system the next product can start from. The team that designed it ships it.

Société Générale Expressbank

From a UX audit to a design system the bank runs on.

30% of customers were abandoning account opening. The bank asked for a complete audit of its website, online banking, and mobile banking, and then for the redesign.

  1. Existing banking screens laid out for the audit, page by page
    Attention heatmaps of the loan page before and after optimization

    01Audit

    Every screen, annotated.

    We audited the website, online banking, and mobile banking page by page, then put representative customers in front of them. In testing, 60% of participants could not find the loan calculator on the homepage.

  2. Persona card for the Digital Native group with a quote from testing

    02People

    Three groups of customers, tested separately.

    Digital Native, Stratum, and Top Affluent customers use a bank differently and trust it differently. Each design iteration was tested with all three.

  3. Journey map of a transfer flow with an emotion curve dipping at the form steps and rising at confirmation

    03Journey

    The drop-off, mapped across channels.

    Journey maps followed customers across web, mobile, and branch, and marked the steps where they lost confidence and left.

  4. Prototype iterations of the redesigned banking screens across desktop and tablet

    04Prototypes

    Wireframes and prototypes, tested each round.

    Progressive disclosure shows only what each step needs. Smart defaults fill in what the bank already knows. Progress is always visible, and errors are caught before submission.

  5. Redesigned Société Générale Expressbank home, insurance, and account screens

    05System

    One design system for every channel.

    A component library with documentation and accessibility built in, interaction patterns, and content standards for voice, tone, and microcopy. Regulatory fields and disclosures are part of the design.

What changed

For customers

The redesign removed the steps that lost them, and more customers now finish account opening. The experience is consistent across web, mobile, and branch.

For the business

More completed account openings from the same traffic, and fewer support calls caused by confusion.

For the bank's teams

Design standards and a reusable component library that every later digital property starts from.

In their words

“Users already have a mental model for car remotes. We designed around the fob they already know—not some novel interface.”
Geoff, VP at Viper
Field notes

What we have written down.

The practice, in our own words. Start anywhere.

Questions

Before you ask.

What do we get from a UX audit?

A report that names the main issues, shows the evidence behind each one, and gives recommendations that were tested with users. We present it to your team in person and agree what to fix first.

Do you only audit, or do you also design and build?

Both, and for most partners all three. At Société Générale Expressbank the work ran from the audit through tested prototypes to a design system. On the products we run for years, the team that designs a screen also ships it and answers for what it does in production.

Our product is regulated. Does that limit the design?

It shapes it. Required fields, disclosures, consent, and audit trails are design inputs from the first wireframe, and accessibility is built into every component. The banking redesign met its regulatory requirements without making account opening harder.

Who do you test with?

People who represent your real users, recruited for each group that uses the product differently. We include people who have never used it, because existing users have already learned to live with its problems.

How does it start?

With a conversation about what the business needs to win and who owns it on your side. The first engagement is a First Build with a fixed price. How we partner explains the shapes that follow.

Let's talk

Whose day should your product make easier?

Tell us what you are building, what the business needs to win, and who owns it on your side. A founder reads every message and answers within two working days, including when the answer is no.