Personalization · The limits · Component
The reasoning
Why each limit exists, so it is not eroded by the next capability that makes crossing it easy.
The deliverable
What it is
A limit with no recorded reason is overruled by whoever has a business case. The reason is what makes it arguable rather than arbitrary.
Limits should be reviewed, because some are inherited from a context that has changed. Reviewing is different from eroding.
One level in
What it is made of
Each element is a constituent part of the component. Follow one to see the attributes it carries.
Reviewing a limit when someone wants to cross it produces predictable outcomes. Review them on a schedule instead.
The other components in the limits
The exclusions
What the organisation will not personalise on — written down, because otherwise each new capability is applied because it is available.
LearnThe visibility
Whether the customer can see why they are seeing this — because unexplained relevance is unsettling and explained relevance is not.
Learn