Pattern directory
Patterns that can appear during account management.
Journey tags identify where a mechanism may be observable; they do not mean it appears in every product or only at that stage. Follow the detail links for two concrete comparisons, boundary cases, legal context and evidence questions.
Editorial analysisObstruction
Account deletion obstruction
Deleting an account is unavailable, disguised as another outcome or burdened by unnecessary barriers. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Account deletion obstruction→Editorial analysisForced action
Automatic attention capture
Content continues automatically or lacks meaningful stopping cues, reducing deliberate control over time and attention. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Automatic attention capture→Editorial analysisSneaking
Bait and switch
The user selects a represented action or offer but receives a materially different outcome that favours the business. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Bait and switch→Current lawObstruction
Cancellation friction
Ending an existing subscription, recurring service or permission is made difficult to find or complete through unnecessary steps or channel asymmetry. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Cancellation friction→Editorial analysisForced action
Contact harvesting and coerced referrals
The service extracts contact information, sends or prepares unwanted invitations, or ties functionality to recruiting other people. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Contact harvesting and coerced referrals→Editorial analysisObstruction
Customer-support obstruction
Access to support needed to resolve a purchase, account, charge or right is hidden or burdened by unnecessary loops and dead ends. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Customer-support obstruction→Editorial analysisObstruction
Dead end
A consumer-favourable route cannot reach its represented outcome and instead loops, stalls or loses progress. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Dead end→Editorial analysisInterface interference
Feedforward ambiguity
A control does not let the user reasonably predict its material outcome before activation. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Feedforward ambiguity→Editorial analysisForced action
Gamified or paid access coercion
Desired functionality is practically conditioned on repetitive engagement or an additional payment not sufficiently clear at acquisition. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Gamified or paid access coercion→Current lawInterface interference
Preselection and defaults
A business-favoured option with a plausible adverse consequence is active before a deliberate user choice. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Preselection and defaults→Editorial analysisObstruction
Privacy maze
Privacy controls are fragmented, inconsistently labelled or layered so that limiting collection or use is unnecessarily difficult. The label describes a recurring design mechanism; whether a particular implementation is harmful or unlawful depends on the complete journey, audience, evidence and rules within scope.
2 visual examples
See examples in context: Privacy maze→