Who gets the last slice of cake? Who speaks first in a group? Whose idea moves forward in a meeting? Jan-ken<\/em> decides. <\/p>\n\n\n\n Unlike in the West, where Rock, Paper, Scissors is mostly playful, in Japan it\u2019s a serious (yet friendly) tool for resolving small-scale conflicts, eliminating bias, or simply moving things along without debate. No hard feelings, no hierarchy, just a simple hand game and mutual agreement. <\/p>\n\n\n\n It\u2019s a game everyone knows, and few have ever thought deeply about it. But if you do, it turns out jan-ken<\/em> has a lot to say about interaction, shared understanding, and the very nature of UX (user experience).<\/span> <\/p>\n\n\n\n At its core, jan-ken<\/em> is a game of three hand gestures: rock (guu<\/em>), paper (paa<\/em>), and scissors (choki<\/em>). Each beats one and loses to another in a perfect loop. Rock crushes scissors, scissors cuts paper, paper covers rock. <\/p>\n\n\n\n This structure, known as a three-way deadlock, isn\u2019t unique to Japan, but in Japanese culture, it resonates with traditional patterns of balance and cyclical relationships. Folk beliefs, for instance, include sayings like: \u201cThe snake defeats the frog, the frog defeats the slug, and the slug defeats the snake.\u201d <\/p>\n\n\n\n The modern form of jan-ken<\/em> evolved from a hand game imported from China during the Edo period. Known as shou-shou<\/em> or ken<\/em>, the early versions featured entirely different characters, like tiger, soldier, and gun. Over time, Japan simplified the format into something accessible to all ages: rock, paper, scissors. <\/p>\n\n\n\n What\u2019s particularly striking is how universally intuitive this structure became, despite its symbolic roots. With just three shapes and no language, the game resolves disputes, prompts laughter, and creates agreement. <\/p>\n\n\n\n Another fascinating feature of jan-ken<\/em> is how deeply it\u2019s rooted in local culture while still adaptable across regions. Even within Japan, the game sounds different depending on where you are: <\/p>\n\n\n\n The hand signs are the same, but the rhythm, chants, and tie-breaker rules vary. Yet somehow, every child instinctively knows how to play without needing explanation. <\/p>\n\n\n\n Beyond Japan, jan-ken<\/em> has spread to the rest of the world as Rock, Paper, Scissors. In some countries, the elements change\u2014Elephant, Man, Ant<\/em> or Stone, Cloth, Scissors<\/em>\u2014but the underlying loop remains intact. <\/p>\n\n\n\n It\u2019s a brilliant example of a core structure<\/strong> traveling through local expression<\/strong>. This is where UX thinking starts to kick in,<\/span> and, yes, where it gets exciting (at least for us). <\/p>\n\n\n\n Let\u2019s start here: jan-ken<\/em> has a shared structure, but it\u2019s not rigid. <\/p>\n\n\n\n Good UX doesn\u2019t enforce uniformity. It enables consistent outcomes across diverse contexts. <\/p>\n\n\n\n Jan-ken<\/em> also requires no instructions. No onboarding. No tooltip. No tutorial. And yet, even a five-year-old can learn it, use it, and trust the outcome. That\u2019s the gold standard of natural interaction<\/strong>.<\/span> <\/p>\n\n\n\n It\u2019s worth asking: <\/p>\n\n\n\n These all comes down to how humans create shared meaning. And for that, we need to bring in a little philosophy. <\/p>\n\n\n\n This brings us to someone who, while not a game designer or UX expert, had a lot to say about how meaning works in human interactions: Ludwig Wittgenstein<\/strong>. <\/p>\n\n\n\n Regarded as one of the most influential philosophers of the 20th century, Wittgenstein, also known as the \u201cfather of conceptual analysis,\u201d argued that we understand words through their use in specific situations. His ideas helped shape modern thinking in linguistics, psychology, and education. <\/p>\n\n\n\n In Philosophical Investigations<\/em> (1953), he famously wrote: \u201cThe meaning of a word is its use in the language.<\/strong>\u201d He challenged the idea that words have fixed meanings, and argued that meaning is defined by use<\/strong>, by how words are actually employed in everyday life.<\/span> He also introduced the concept of language games<\/strong>: social activities where meaning arises from shared understanding, implicit rules, and patterns of behavior, not from dictionary definitions. <\/p>\n\n\n\n Think about the word rock<\/em>. It could mean a geological object, a music genre, or a verb. But in jan-ken<\/em>, rock<\/em> means \u201cthis gesture, in this moment, which beats scissors and loses to paper.\u201d That\u2019s not a definition, it\u2019s a function. And it only makes sense within the context of the game<\/strong>. <\/p>\n\n\n\n Jan-ken<\/em>, in this way, is a nonverbal language game<\/strong>. There are no words, but there are rules. So what does all of this have to do with UX? A lot. <\/p>\n\n\n\n In UX research, we constantly face the challenge of ambiguous language<\/strong>. <\/p>\n\n\n\n Users say things like: <\/p>\n\n\n\n \u201cThis app is easy to use.\u201d These phrases sound positive, but they\u2019re vague. \u201cSafe\u201d in a banking app might mean encryption. In a medical device, it might mean clear alerts. That\u2019s the Wittgenstein lens. It\u2019s not just about what people say, it\u2019s about what they\u2019re doing when they say it<\/strong>. <\/p>\n\n\n\n Here\u2019s how this perspective plays out in our research practice at Uism: <\/p>\n\n\n\n Ultimately, good UX isn\u2019t about designing for what people say. It\u2019s about designing for how people make meaning in real situations<\/strong>.<\/span> Jan-ken<\/em> might be the simplest possible system for resolving disagreements. But beneath its simplicity lies a miniature model of how we interact, collaborate, and create shared understanding. <\/p>\n\n\n\n It\u2019s not flashy, but it works because it meets people where they are, not where instructions want them to be. And that\u2019s the heart of great UX. <\/p>\n\n\n\n At Uism, we spend our time observing how people interact with systems, services, and each other, and uncovering the meanings they often don\u2019t say out loud. Sometimes, that means analyzing digital products. Sometimes, it means watching behavior in physical environments. The best design insights don\u2019t always come from cutting-edge tech. They often come from everyday habits so embedded, we forget they\u2019re designed at all. Jan-ken<\/em> reminds us that when something feels intuitive, it\u2019s not because it\u2019s simple. It\u2019s because it\u2019s culturally embedded<\/strong>, contextually flexible<\/strong>, and socially negotiated<\/strong>. And maybe that\u2019s the ultimate UX challenge: We\u2019re a team of curious UX researchers at Uism, always exploring how people create meaning through design and interaction. If this perspective resonates with you or sparks a new question, let\u2019s talk! <\/p>\n","protected":false},"excerpt":{"rendered":" Explore why Japan\u2019s Rock, Paper, Scissors (jan-ken) is more than a game\u2014it\u2019s a powerful UX model rooted in cultural context, shared meaning, and intuitive interaction.<\/p>\n","protected":false},"author":16,"featured_media":4692,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_locale":"en_US","_original_post":"https:\/\/uism.co.jp\/?p=4703","footnotes":"","wp-seo-meta-description":"Explore why Japan\u2019s Rock, Paper, Scissors (jan-ken) is more than a game\u2014it\u2019s a powerful UX model rooted in cultural context, shared meaning, and intuitive interaction.","wp-seo-meta-robots":[]},"categories":[374],"tags":[],"class_list":{"0":"post-4704","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ux-thinking","8":"en-US","9":"c-entry"},"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/posts\/4704","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/comments?post=4704"}],"version-history":[{"count":7,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/posts\/4704\/revisions"}],"predecessor-version":[{"id":9386,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/posts\/4704\/revisions\/9386"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/media\/4692"}],"wp:attachment":[{"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/media?parent=4704"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/categories?post=4704"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/uism.co.jp\/wp-json\/wp\/v2\/tags?post=4704"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The Roots <\/span><\/h2>\n\n\n\n
Different Voices, Same Game <\/span><\/h2>\n\n\n\n
\n
\n
\n
\n
Why Jan-Ken Feels So UX <\/span><\/h2>\n\n\n\n
It allows for variation. Different chants. Different styles. Even different meanings depending on the setting. But the core loop stays the same, and everyone intuitively \u201cgets it.\u201d That\u2019s what we call contextual flexibility<\/strong> in UX. <\/span><\/p>\n\n\n\n\n
\n
\n
The Philosophy Behind Shared Meaning <\/span><\/h2>\n\n\n\n
![\"\"](\"https:\/\/uism.co.jp\/wp-content\/uploads\/2025\/05\/image-852x1024.jpeg\")
<\/figure>\n\n\n\n
There\u2019s no explanation, but there is shared understanding. And meaning flows naturally from how people play.<\/span> <\/p>\n\n\n\nWhat This Means for UX Research <\/span><\/h2>\n\n\n\n
\u201cIt feels safe.\u201d
\u201cI like how clean it looks.\u201d <\/p>\n\n\n\n
Easy because there are fewer steps? Because the layout is familiar? Because nothing broke? <\/p>\n\n\n\n
In a car interface, it might mean physical buttons instead of touchscreens. The words alone don\u2019t tell us enough. We need to explore how<\/strong> users use those words, what they\u2019re responding to, what they expect, and the context they\u2019re in.<\/span> <\/p>\n\n\n\nPractical Takeaways <\/span><\/h2>\n\n\n\n
\n
We intentionally use open-ended, fuzzy words like \u201cconvenient\u201d or \u201ctrustworthy\u201d\u2014not because we\u2019re unclear, but because we want to hear what those words mean to each user. <\/li>\n\n\n\n
We don\u2019t just count keywords\u2014we consider what the user was doing, feeling, or trying to solve when they said it. <\/li>\n\n\n\n
We check whether users are interpreting the interface the way designers intended. If there\u2019s a mismatch, we look for context gaps\u2014not just copy issues. <\/li>\n<\/ul>\n\n\n\n\n
Final Thoughts: When Meaning Feels Effortless <\/span><\/h2>\n\n\n\n
And sometimes, it starts with a question as innocent as: \u201cWhy is it rock, paper, and scissors?\u201d <\/p>\n\n\n\n
Designing things that feel obvious without ever needing to be explained.<\/span><\/strong> <\/p>\n\n\n\n