Field Notes

Serving up a nourishing meal

Customer recognition, seen from a restaurant table: menus are for strangers, regulars want to be known, and scale quietly removes the difference. A field note.

Table of contents
  1. Menus are for strangers
  2. Two design problems, not one
  3. Filling versus nourishing
  4. Two habits worth stealing

There is a small test for whether a restaurant knows you, and it is the simplest form of customer recognition there is. It is whether they still bring the menu.

The first few visits, you need it. You do not know the kitchen, which dishes they are proud of, or which ones are only there because somebody expects them. The menu is a kindness to the stranger. It says: here is everything, take your time, nobody will judge. Customer recognition has not started yet, and it should not have.

Then, if the place is good and you keep coming back, the menu stops arriving. Someone nods at you on the way in, asks whether you want the usual, and mentions that the dish you liked last time is back. You have not been handed a document. You have been recognized.

That moment is the whole point of a relationship, and it is exactly what scale tends to remove.

A business grows, and the first thing it does is write down the menu. That is sensible: you cannot run forty locations on the memory of one head waiter. So the offer gets standardized, the script gets written, and every customer, on every visit, gets the same well-designed menu.

The trouble is that the same menu treats the regular like a stranger. The person who has bought from you for six years fills in the same form and gets the same “welcome, here is how it works” email as someone who arrived this morning. Nothing in the experience says: we know you are here, and we know what you like.

Are you standardizing yourself out of business? is the longer argument; this is the quiet version. Nobody complains. The regular just stops feeling like a regular, and one day they try the place across the street, which also has a menu.

Two design problems, not one

Most businesses design for one customer. Good restaurants design for two.

The first-timer needs the menu. Guidance, a safe choice, and permission to ask questions. The first visit is about lowering the risk of being wrong.

The regular needs recognition and the freedom to skip the ritual. They do not want to be walked through the specials. They want the shortcut: the usual, the reorder button, the person who remembers that they do not eat mushrooms. Sending the regular through the first-timer’s flow is a small insult, repeated, and regulars are usually the best customers a business hears from least, so the insult goes unreported.

The same person is both of these customers at different times (the many sides of me is a longer look at that), so if your experience has one path, it is the wrong path for about half the people on it.

Filling versus nourishing

Restaurants understand a second thing too. A plate can be full and still leave you feeling worse than when you sat down.

Features and offers pile the plate high. Another module, another loyalty tier, another banner, another “you might also like”. From the customer’s side of the table it often feels like being fed things you did not order while the one dish you came for is late.

A nourishing experience gives the customer what they came for and lets them leave. It does not offer dessert to someone who asked for the check, or keep them at the table to hit a session-length target. The measure is whether the person walks out satisfied and comes back hungry for the same thing.

That takes a restraint that is hard to defend in a planning meeting, because restraint does not look like work. It is the same discipline as in tennis and the art of effective customer experience: the winning shot is usually the one you did not overhit.

Two habits worth stealing

Two habits, one for each customer, and neither needs a reservation book.

For first-timers: name the safe choice. Somewhere in the first experience, tell new customers what most people like them pick, and why. On a menu it is the house special. On a pricing page it is the plan marked “most teams start here”. A stranger handed a good default stops feeling like a stranger a little sooner.

For regulars: remember one thing and show it. Pick one fact about a returning customer that your systems already hold (their last order, their plan, the problem they called about last time) and put it in front of them, unprompted, at the start of the next interaction. Not a dashboard of everything you know. One thing, said plainly, the way a good waiter mentions that the fish you liked is back.

Neither habit needs a budget line. Both need someone to decide that being known is part of what you serve, and to check, this week, whether the regulars are still being handed the menu.

Related articles