Comparing Design Metaphors and User-Driven Metaphors for Interaction Design

Why Read This from an HCI Perspective

This article shows how different the metaphors a platform presents can be from the metaphors users actually use to describe their lived experience. In HCI/UX practice, it becomes a powerful lens for checking whether the experience we intended is truly being communicated. By combining qualitative metaphor elicitation, quantitative ratings, and analyses of differences across groups, it’s possible to quickly diagnose mismatches among product messaging, onboarding, branding, and feature design.

CIT's Commentary

What’s especially interesting is that the study treats metaphors not merely as copywriting or branding language, but as a unit for validating experience design. In particular, the way it separates and compares design metaphors and user metaphors reveals more directly how users read a feature—not just what it looks like, but what sense of everyday life it evokes for them. That said, the current approach relies on explicit wording and archived web pages, so it’s difficult to fully capture metaphors at the level of internal decision-making and actual interaction. Even so, in products like AI services—where expectations and perceived experience can diverge quickly—the metaphor gap itself can be an important signal of user experience. In subsequent design work, the practical value will grow further if we also examine how this difference varies by culture, language, and usage context.

Questions to Consider While Reading

• Q.How can we distinguish whether a mismatch between a design metaphor and a user metaphor is a problem with the feature itself, a problem with shaping expectations, or a problem with communication?
• Q.When analyzing only the explicitly revealed metaphors, how much do we end up missing the implicit metaphors that actually shape real product experience?
• Q.What analytical framework would be most useful for connecting group-level differences—where metaphors are interpreted differently across platforms—to product improvement priorities?