Forced Consent
Forced consent occurs when agreement is required for access, without offering meaningful alternatives. People consent not because they agree, but because exclusion is the only other option.
This turns consent from a conscious choice into a gatekeeping mechanism. Legally, consent may exist; psychologically, it is hollow. The user becomes a pass-through entity.
UX that respects choice separates functionality from consent. Systems that do not confuse agreement with surrender.
Compact overview
What this page covers
A machine-readable overview with context, audiences, suitability and the most common questions.
Forced Consent is a Mitterberger:Lab knowledge article about UX, digital products, software engineering, or AI. It helps teams understand a relevant concept, problem, or pattern in complex digital systems.
Best fit for
- Product teams
- UX leads
- decision-makers in digital organizations
Contexts
- Anti-Patterns
Useful when
- a concept, pattern, or decision problem needs clarification
- UX, product, or AI topics need to be placed in system context
Less suitable when
- only a surface-level definition without practical context is needed
Relevant signals
- Part of the Mitterberger:Lab knowledge collection.
- Topic grouping: Anti-Patterns.
Common questions
- What is Forced Consent about?
- Forced Consent explains a relevant concept or pattern in the context of UX, digital products, systems, or AI.