Acceptability is a person's or society's willingness to embrace a solution: not just "does it work?", but "is it tolerable, legitimate, and aligned with my values and practices?".

At the individual level, Fred Davis (TAM model, 1989) demonstrated that technology adoption relies on two key perceptions: perceived usefulness and perceived ease of use. Yet acceptability extends far beyond the individual: a solution can be highly useful, simple, and desirable, and still be socially rejected because it clashes with a norm, a fear, or a specific relationship to the body, privacy, or work.

This is the definitive tension in innovation: just because something is possible does not make it acceptable. Facial recognition, tracking, and certain forms of automation are technically feasible—and sometimes desirable for those deploying them—but they cross a line for those experiencing them. Confusing feasibility with acceptability is the ultimate path to rejection: creating a brilliant project that no one wants, not because it is poorly made, but because it simply is not acceptable.

Acceptability must be addressed at the outset, not as an afterthought in customer service. It is tested with the very people who will experience the solution, and is built on transparency, user control, reversibility, and sometimes the conscious choice to step back from what is technically possible.

Our conviction is clear: a solution is only successful when it is truly accepted, not just adopted under constraint. We treat acceptability as a core design criterion in its own right, on par with desirability and feasibility. Designing for acceptability means honoring and respecting the people who will live with the final result.

What is at play elsewhere: desirability, design ethics, dark patterns, artificial intelligence and its limitations, and human-centered design.

References: F. Davis, Technology Acceptance Model (1989); distinction between feasibility, desirability, and acceptability.