What the Floor Remembers

A week on the floor · Field notes from a wellness hotel in northern Spain · Part 1 of 3

Study note. Five days on-site in July: observation on the floor, consented interviews, counting. Staff appear as roles only; identifying details are altered. Part 1: what the floor remembers. Part 2: the offer that never comes. Part 3: the method, and what it does not prove.

Last week I spent five days doing field research on the floor of a high-end wellness-focused hotel in the north of Spain. I spent hours behind the spa reception, in the morning briefings, at the front desk observing the service. My goal was to get immersed in the operation and analyze how knowledge flows across shifts, service areas, and technology systems. Several staff members have been in the building for over twenty years and have developed an intuition you cannot teach quickly, the service instinct a guest actually chose this hotel for.

On the first morning I sat with the woman who runs the spa and has been on the team for ten years. I asked her one of the questions I routinely include in my interviews: when you meet a guest for a treatment, what do you know about them? Does anyone who books show up with a profile, a history, a note about who they are and how they like being cared for?

"No," she answered. "Sometimes we know the guest's birthday because front desk lets us know in the morning huddle." No hesitation in her voice. Just a fact of the business.

Consider what that costs in a business whose whole product is making someone feel recognized. A guest who always wants more pressure than the massage booking says. Who would gladly pay for a glass of cava to enjoy after the treatment poolside. Who books at the last minute because that is how their life runs. Someone on the staff at some point learned this, and much more, about this guest. But all of that knowledge lives in one person's memory, or it lives nowhere. When that person is off, or busy, or has moved on, the guest arrives as a stranger. This is not a lapse of attention. It is the absence of service infrastructure no one has ever built.

Around that one reception desk I counted close to a dozen separate systems. A booking tool, a property system, a maintenance log, a messaging app, a spreadsheet for the laundry. Between the two that matter most, the only things that pass are a name, a room number, and a set of dates. Everything that would let her anticipate a guest's preferences travels the old way: an email flagged and half-remembered. A note typed into a field only she can see, after six clicks and three windows. A line written by hand onto a sheet printed the evening before, handed across at the shift handoff.

I have written before about a Japanese concept, omotenashi, for care that is already in place before you ask for it. Knowing what someone needs before they even express it. It runs on memory, and the memory in this hotel (and in most) has nowhere to live. The software these teams were handed was built for the transaction, the room, the rate, the bill. It was never built to care for the guest on the floor, or for the person actually delivering the care. The information is learned, sometimes captured, almost never coordinated.

A guest's history survives only if whoever takes the next booking finds and reopens the right file. A hurried booking under a slightly different spelling spawns a second file, and the past quietly detaches from the person. So even where the record is there, it holds by diligence and luck, not by design.

Last week I saw the gap clearly, and I heard it named, without prompting, by the people living inside it. I have a clearer picture of the shape of the memory problem and some hypotheses on how to solve it. But a problem worth solving does not equate to a business. My goal is to build a product that produces significant, quantifiable, and sustainable value for our customers. Hotels are littered with archaic technology that adds marginal value but, once implemented, is hard to rip out. Technology that becomes a sink of information that is never shared across systems, turning hotel staff into the knowledge-transfer mechanism, siphoning valuable time that could be better invested in knowing their guests deeply and serving them exactly how they want.

If you run a floor, here is the question I keep returning to. The guest standing in front of your best person right now: how much of the knowledge required to anticipate their needs is written somewhere your person can easily access in the moment? I would value your honest read.

— Carlos

Next in these notes — Part 2: the offer that never comes. Why a warm, well-run floor still lets the experiences guests would love slip past, and why that is not a sales problem.