← All notes

Same name, same meaning.

The smallest decision in a two-sided product, and the one that saves the most phone calls.

By Haleh NobarProduct structureNovember 20264 min read

Most products I work on have two sides. In Pin2Pin, the office plans orders on a web dashboard while drivers carry them out on a phone. At Elegant Menu, guests order at the table while staff and kitchens handle the same order behind the scenes. In Digesti, a patient logs meals and a specialist reads the history.

Two sides means two interfaces, often designed at different times, for very different moments. The office sits at a desk with many orders on screen. The driver stands outside with a phone in one hand and one job at a time. It would be natural to give them different words.

Pin2Pin’s design system: the dashboard and the driver app are built from the same parts and the same names.
Pin2Pin’s design system: the dashboard and the driver app are built from the same parts and the same names.

The cost of translation

In testing Pin2Pin, people looked for the same feature in different places, in the dashboard and in the app. When the two sides name the same thing differently, every conversation between them starts with a translation: “the job you see as… is the one I call…”. In a phone call from a van, that translation is where mistakes happen.

If the office and the driver can’t name the same thing the same way, the phone call becomes the product.

A structural decision

So we mapped the product around the life of a single order and fixed the vocabulary first. The dashboard has Orders, Tracking, Drivers, Vehicles, Customers, Reports and Settings. The driver app has Home, Orders, Tracking and Profile. Orders and Tracking mean exactly the same thing on both sides.

The screens are different, and they should be: the office needs four order-stage counters and a full list; the driver needs one action per screen, readable at arm’s length. But the nouns are shared. A dispatcher and a driver can talk about one order without translating.

How I apply it

  • Name the shared objects first, before designing either interface: the order, the dish, the meal.
  • Let layouts differ, never names. Each side gets the density it needs; the vocabulary stays fixed.
  • Test across the line. Ask someone on one side to describe what they see to someone on the other, and listen for translation.

It is a small decision that rarely appears in a portfolio, because it isn’t visible. But it is the kind of decision that makes a complex product feel simple to the people who use it together.