Omni Core · Object

Personalization

Changing what a customer sees based on what is known about them — deliberately, within limits, and only where it demonstrably helps them rather than only the organisation.

The term

What it is

Personalisation is usually adopted as a capability and then applied wherever it is technically possible, which produces experiences that are more tailored and not more useful.

The line between helpful and unsettling is drawn by the customer rather than by the organisation, and it is crossed when the personalisation reveals more knowledge than the relationship justifies.

Most personalisation is unmeasured. It feels sophisticated, it is expensive to build and maintain, and whether it improves anything is frequently never established.

Why it earns a place

What goes wrong without it

01

Relevance and surveillance are the same mechanism

The same data that makes a recommendation useful makes it uncomfortable when the customer had not realised it was held.

02

Personalisation has a maintenance cost that never ends

Every variant has to be built, tested and kept current. A dozen personalised paths is a dozen things that can be wrong.

03

Untested personalisation is expensive decoration

It should be held to the same evidential standard as any other change, and it usually is not because it is assumed to be obviously better.

One level in

The modules within personalization

Four working areas: what is varied, what it varies on, where the line is, and whether any of it works.

  1. What is personalised

    Which parts of the experience change by person, and what the customer gains from each. The inventory that makes the maintenance cost visible.

    Learn
  2. The signals

    What the personalisation is based on — stated preferences, observed behaviour, inferred attributes — and how reliable each is.

    Learn
  3. The limits

    Where the organisation chooses not to personalise, and why. The boundary that keeps relevance from becoming intrusion.

    Learn
  4. Whether it works

    Evidence that the personalisation improves something for the customer as well as for the organisation, tested rather than assumed.

    Learn

Across the framework

What it touches

  • Data CorePersonalisation runs on collected data, and the purpose it was collected for constrains this use.
  • Brand CorePersonalisation that misjudges someone damages perception more than a generic experience would.
  • Market CoreSegments are defined there; personalisation is what is done differently for each.
  • Business CoreEvery personalised variant is something to build, maintain and get wrong.

Beyond the framework

Models worth knowing here

The Omnigoal says where this belongs and what it touches. It does not tell you how to think about it — other people have done that, and done it well. These are theirs.

  1. RFM analysis

    Direct marketing practice, formalised in the 1990s · 1990s

    Sort customers by how recently they bought, how often, and for how much — three fields that predict a great deal.

    It long predates machine learning and remains an unreasonably strong baseline. Recency does most of the work: how long ago someone last bought predicts whether they will buy again better than almost anything else on file, and all three fields are already in every order table.

    Reach for it when
    As the first personalisation anyone builds, and as the baseline any more sophisticated model must beat.
    Where it stops
    It describes what someone did, not what they want. It cannot help with a new customer, and it will keep recommending more of what they already bought.

    Long-standing direct marketing practice; formalised in Jan Roelf Bult & Tom Wansbeek, “Optimal Selection for Direct Mail”, Marketing Science, 1995.

  2. Collaborative filtering

    Goldberg, Nichols, Oki & Terry · 1992

    Recommend to someone what people who behaved like them went on to choose, without needing to know anything about the item.

    The insight is that similarity of behaviour carries more information than description of content, and it needs no understanding of what is being recommended at all. Two problems have followed it ever since: it has nothing to say about a new user or a new item, and it narrows what people are shown to a reflection of what they already did.

    Reach for it when
    Where there is enough behavioural data for patterns to be real, and as the standard against which content-based approaches are judged.
    Where it stops
    It amplifies the popular and the already-chosen. Left alone it will recommend a company’s catalogue into a small corner of itself.

    David Goldberg, David Nichols, Brian M. Oki & Douglas Terry, “Using Collaborative Filtering to Weave an Information Tapestry”, Communications of the ACM, 1992.

These are other people’s models, named here so you can go to the source and use them properly. The Omnigoal is not affiliated with their authors and is not endorsed by them; nothing of theirs is reproduced here — no canvas, no diagram, no wording. Each is described in our own words, with the originator credited, because the framework is a place to put thinking, not a replacement for the people who did it. Model names and trademarks belong to their respective owners and are used here only to refer to the work itself.

Every model in the framework, and where each one belongs

The line between helpful and unsettling is drawn by the customer, and it is crossed by revealing knowledge they did not know you had.

The other objects in the Omni Core

Back to the Omni Core