Oblique Personalization Safety Check
Personalize enough to delight without revealing how much you know
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 98%
Sutherland and Bartlett distinguish welcome personalization from personalization that exposes the machinery behind it. Bartlett appreciated a hotel placing his company logo on a small welcome gift, but felt unsettled when a gym chief executive emailed his manager shortly after registration because he did not understand how the details had travelled. Sutherland recommends using personalization judiciously and sometimes obliquely: saying a person “may be the kind of person who” did something can feel less invasive than declaring exactly what they did. The safety check evaluates expectation, visibility, cultural context, and possible negative interpretations before sending. It also asks whether someone else—such as a housemate or local postman—could see the message. Oblique wording can soften legitimate use, but it does not make unauthorised collection acceptable; privacy, consent, and security remain separate requirements.
Origin
Extracted from The Diary of a CEO. Rory Sutherland and Steven Bartlett contrast a welcome gift with an unexpectedly informed email and a publicly visible “final reminder” envelope.
Core principles
- 01Personal relevance can delight or feel invasive
- 02The recipient judges not only the message but how the sender obtained the knowledge
- 03Indirect language can reduce the sense of surveillance
- 04Cultural and situational context change privacy expectations
How to run it
- 1
Map the Revealed Knowledge
List every personal fact the recipient can infer from the message and how recently it was collected. Include facts revealed indirectly by timing or channel.
Pro tip Read the message as if you did not know how the data moved internally.
- 2
Test Expected Possession
Ask whether a reasonable recipient would expect this sender, team, and channel to know the fact. Treat surprising access as a trust risk even when the data is technically available.
Watch out Internal access does not automatically equal customer permission.
- 3
Check the Audience Around Them
Consider who else can see the envelope, screen, gift, or message. Account for shared homes, workplaces, local communities, and cultural expectations.
Pro tip Review exposed subject lines and packaging, not only message bodies.
- 4
Reduce Explicitness
When personalization is legitimate but direct wording feels intrusive, use a less declarative formulation or a contextual gesture. Preserve relevance without displaying unnecessary surveillance.
Pro tip Personalize the experience rather than reciting the customer's data back to them.
Watch out Indirect phrasing cannot cure unlawful or deceptive data use.
- 5
Run a Negative-Interpretation Review
Ask people outside the campaign team how the message could be misread or cause embarrassment. Remove or redesign elements whose downside outweighs the delight.
Pro tip Include reviewers from the markets and living contexts where the message will appear.
In the wild
Bartlett says a gym chief executive emailed his manager shortly after he entered details on a front-desk tablet. Although the message offered help, the unexplained data path made him wonder what else the organisation could see.
→ A service gesture reduced trust because it revealed unexpected access to personal information.
Illustrative example: a service has permission to use account activity for retention. Instead of stating a sensitive behavioural detail in the email subject, it places a general renewal note there and shows relevant guidance only after secure login.
→ The message remains useful without exposing private behaviour to bystanders.
Common mistakes
Equating Available Data With Permission
A customer may be alarmed when information crosses teams or channels they did not expect.
Reviewing Only the Intended Meaning
Campaign teams can miss embarrassment, surveillance, or status interpretations obvious to recipients.
Ignoring the Public Surface
Envelope text, notifications, and subject lines may reveal information to people other than the customer.
Is it for you?
Best for
It is best for marketers and service teams using customer data to tailor messages, gifts, or experiences.
Not ideal for
It is not ideal as a workaround for unlawful data use, missing consent, or inadequate security controls.
From the transcript
“it's best done obliquely”
“you may be the kind of person who recently did this”
“possible negative interpretations of what they're doing”
From the episode
The Marketing Secrets Apple & Tesla Always Use: Rory Sutherland