Levinas and the Face of the User: Ethics Precedes Design

What does Levinas mean by “the face of the Other”?

For Levinas, the face is not a visual image. It is the experience of encountering another consciousness that makes a claim on you, a demand for responsibility that precedes any choice or contract. The user’s presence in your system is that face.

I remember the moment this clicked for me. I was reviewing a user flow for an account deletion process. The product team had designed 7 confirmation steps. Seven. The stated reason was “preventing accidental deletion.” The actual reason was reducing churn. I looked at the flow diagram and saw something that was not on the diagram: a person trying to leave, and an interface designed to prevent them. The user’s face was not on the wireframe. But their frustration, their trapped feeling, their vulnerability to our design choices, that was the ethical reality the wireframe concealed.

Levinas would not have been surprised. He argued that systems of thought (and wireframes are systems of thought) naturally tend to reduce the Other to a category, a user segment, a persona, a churn statistic. The ethical demand is to resist that reduction. To see the person behind the data point.

Why does Levinas say ethics precedes design?

Because the user exists before the interface does. Their vulnerability, their needs, their capacity to be harmed by your design decisions, these are not design constraints. They are the conditions that give design its moral weight.

Most design processes begin with requirements: what should the system do? Levinas would begin differently: who will this system encounter, and what claim does their existence make on us? This is not user research. User research asks what users want. Levinasian ethics asks what users deserve, regardless of whether they can articulate it, regardless of whether it serves the business.

I worked on a notification system that sent 14 push notifications per day to the average user. Engagement metrics were excellent. Click-through rates were 23% above industry average. The system was, by every quantitative measure, a success. But I had read Levinas by then. I asked: “What is the experience of receiving 14 interruptions per day from a system that knows exactly when you are most vulnerable to responding?” The ethics of attention is not about metrics. It is about the face of the person whose attention we are claiming.

How does this philosophy change design practice?

It reverses the order of operations. Instead of designing first and considering ethics second, you begin with the ethical encounter and let it constrain the design. The user’s vulnerability is not a risk to mitigate. It is the foundation of your responsibility.

• Begin with vulnerability audit: Before any design work, map the points where users are vulnerable to your system’s power. Where can the system frustrate, mislead, addict, or trap? These points are where Levinas’s face appears.
• Replace personas with encounters: Personas abstract people into categories. Instead, write encounter narratives: specific stories of specific people interacting with the system in moments of vulnerability. A 67-year-old trying to cancel a subscription they do not understand is not a “silver segment user.” They are a person whose face demands your attention.
• Design for departure: The ultimate test of Levinasian design ethics is the exit. How easy is it to leave? A system that respects the Other’s face makes departure as dignified as arrival.

What are the limits of applying Levinas to technology?

Levinas wrote about face-to-face encounters between humans. Applying his framework to mediated, scaled, asynchronous digital interactions requires adaptation, but the core insight survives: where there is vulnerability, there is ethical obligation.

Critics rightly note that Levinas’s philosophy was developed for direct human encounter, not mass-scale digital products. The user at the other end of an API is not present in the way Levinas meant. But Levinas himself acknowledged that the face is not limited to physical presence. It is any manifestation of the Other’s vulnerability. A user submitting personal data to a system they cannot inspect is vulnerable. A patient receiving an automated diagnosis they cannot challenge is vulnerable. The medium changes. The ethical structure does not.

According to Levinas’s ethical framework, responsibility for the Other is infinite and asymmetric: I am responsible for you before you are responsible for me. In design terms, this means the burden of ethical consideration falls entirely on the builder, not the user. The user is not obligated to protect themselves from your design. You are obligated to protect them. This connects to why security must be embedded rather than bolted on: the user’s vulnerability is your starting point, not their problem to solve.

“The face resists possession. It speaks to you and thereby invites you to a relation.” — Emmanuel Levinas

Every interface is a face. Not literally, but ethically. Every pixel that a user encounters is a site where your design power meets their vulnerability. Levinas asks us to feel the weight of that encounter before we write the first line of code. Not as guilt. As responsibility. The face of the user is not on your wireframe. But it is in every decision you make about what the wireframe demands of the person who will one day stand before it.