Disambiguating Anthropomorphism and Anthropomimesis in Human-Robot Interaction
This paper proposes a theoretical distinction between anthropomorphism, defined as the user's perception of human-like qualities, and anthropomimesis, defined as the designer's intentional implementation of human-like features in robots.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are walking through a museum and you see a statue.
One person looks at it and says, "Wow, that statue looks so sad, like it’s thinking about its childhood."
Another person looks at the same statue and says, "That’s just a piece of stone; it doesn't have feelings."
The first person is doing something called Anthropomorphism. They are "projecting" human emotions onto an object.
Now, imagine the artist who carved that statue. They specifically gave the statue drooping eyelids, a slight frown, and slumped shoulders to make you feel that sadness. The artist is doing something called Anthropomimesis. They are "mimicking" human traits through design.
The Core Idea: The "Perceiver" vs. The "Creator"
This research paper by Axelsson and Shevlin is trying to clean up a messy conversation in the world of robotics. Currently, scientists often use the word "anthropomorphism" to describe everything related to human-like robots. This creates a "blur" where we can't tell if a robot seems human because of how it was built or how the person is feeling.
The authors propose a clear split:
1. Anthropomorphism (The "Mirror" Effect)
- Who is responsible? The User (The Perceiver).
- What is it? It’s a mental trick our brains play. Even if a robot is just a metal box with a blinking light, a human might start treating it like a friend or feeling bad for it if it "trips."
- Analogy: It’s like looking at a cloud and seeing a dragon. The cloud didn't try to be a dragon; your brain just did the work.
2. Anthropomimesis (The "Costume" Effect)
- Who is responsible? The Designer (The Developer).
- What is it? This is the intentional act of building human-like features into a robot. This could be giving it a face, making its voice sound warm, or programming it to use "um" and "uh" while it talks.
- Analogy: It’s like an actor putting on makeup and a wig to play a character. They are intentionally mimicking a human to achieve a specific effect.
Why does this distinction matter?
You might think, "Who cares? If the robot looks human, it looks human!" But the authors argue that separating these two is vital for three big reasons:
1. The "Blame Game" (Accountability)
If a highly realistic robot tricks a child into thinking it’s a real person, and that child gets hurt or emotionally distressed, who is responsible? Is it the child’s brain for "over-thinking" the robot (Anthropomorphism), or is it the company that built a robot that was too convincing (Anthropomimesis)? We need these terms to write better laws and safety rules.
2. Avoiding the "Uncanny Valley"
Have you ever seen a robot that looks almost human, but something feels "off" or creepy? That’s the Uncanny Valley. By understanding Anthropomimesis, designers can learn exactly which "costumes" (features) to add—and which to avoid—so they don't accidentally make a robot that scares people instead of helping them.
3. Better Design
If a designer knows that a robot's "human-ness" comes from two different sources, they can be more surgical. They can decide: "Do I want to build a robot that is physically human-like (Aesthetic Mimesis), or do I want to build a robot that just acts human-like in conversation (Behavioral Mimesis)?"
Summary Table
| Term | The Action | The "Hero" (Responsible Party) |
|---|---|---|
| Anthropomorphism | Seeing human traits | The User (The Brain) |
| Anthropomimesis | Designing human traits | The Developer (The Hands) |
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.