From hotels to digital: why personalisation is the Achilles heel of truly personalised experiences

Imagine you've booked the holiday of a lifetime. A surprise for someone you love. First class, beautiful hotel, all the trimmings.

It starts at the airport, where the assistant greets you warmly, learns you're celebrating something, and wishes you a wonderful trip. It continues at the hotel: the security guard at the gate takes your name and waves you through. The bag attendant addresses you by name before you've said a word. The concierge already knows who you are, and whisks you up to a room that's been upgraded, with a handwritten note and a bottle of wine waiting.

This feels different. It feels personal.

And here's the thing worth pausing on: almost none of that was personalisation. It was a team communicating with each other.

Personalised and personal are not the same word

This is the distinction that I think the whole industry has quietly muddled, and Mark Schaefer put it better than I could. Personalised is cut and paste. Personal is unique and custom. Personalised requires no real knowledge of the customer. Personal reflects an understanding of a human being. Personalised doesn't elicit an emotion. Personal creates an emotional bond.

Go back to the hotel. What made it land wasn't that your name appeared on something. It was that the staff had told each other you were coming, and why. The name was a symptom of the care. Most digital personalisation is the name without the care.

Personalised is cut and paste. Personal is unique and custom. Most digital personalisation gives you the name without the care.

The digital personalisation trap

I'll grant the obvious objection straight away: it's a bit unfair to hold up a five-star hotel as the benchmark. They have fourteen days to impress a guest who is already relaxed and predisposed to enjoy themselves. Most digital businesses measure session duration in minutes and are competing with a notification from someone else.

So we turn to what's affordable. Capture a bit of data, drop a first name into an email subject line, serve a recommendation based on what they looked at last. It's cheap, it's scalable, and it does move the numbers a little. I'm not going to pretend otherwise.

But somewhere along the way "personalisation" got promoted from tactic to strategy. The logic runs: the more we know about you, the better we can serve you - therefore, if we know a great deal about you and mention it back at you, you will feel served.

That's the bit I think is wide of the mark. Knowing someone's name and using it is not the same as knowing what they need and giving it to them. One is data. The other is design.

Why it backfires

There's a failure mode here that gets underplayed. Personalisation without the underlying care doesn't just fall flat - it can actively irritate. An email that uses your first name three times while clearly having no idea what you were trying to do reads as a performance of intimacy, and people are very good at spotting that. It's the digital equivalent of a shop assistant reading your name off your card and using it in every sentence.

Worse, it consumes the budget and attention that could have gone into fixing the actual friction. It is much easier to add a merge field than to redesign a broken journey, and one of those gets celebrated in a marketing meeting.

What to do instead

Ask a different question. Not what do we know about this person that we could mention? but what does this person need right now that we could quietly do for them?

The hotel's magic was operational: the information travelled ahead of the guest, so nobody had to ask twice. That's translatable. It means a client not having to re-explain their situation to the third person they speak to. It means the system knowing they raised an issue last week, so the next interaction starts from there. It means removing the moment where they have to work, rather than adding a moment where they're addressed by name.

That is harder than personalisation. It's also the thing people actually remember.

So the question I'd put to your team: if you switched off every first-name merge field tomorrow, would your customers notice? And if the honest answer is no - what does that tell you about what you've been calling personal?

Worth a conversation. Book a short discovery call with the team at Distinction - no pitch, just an honest look at where your experience feels human and where it doesn't.