<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Consilient Design - Medium]]></title>
        <description><![CDATA[Consilience is the proposition that evidence from independent sources can be converged to create better ideas. This publication brings together divergent theories and techniques in the practice of experience technology design to better support business and social values. - Medium]]></description>
        <link>https://medium.com/consilient-design?source=rss----62c5e8c2a510---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Consilient Design - Medium</title>
            <link>https://medium.com/consilient-design?source=rss----62c5e8c2a510---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:50:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/consilient-design" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Idiot Lights]]></title>
            <link>https://medium.com/consilient-design/idiot-lights-5c87ef0e6201?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/5c87ef0e6201</guid>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Thu, 26 Oct 2023 20:02:24 GMT</pubDate>
            <atom:updated>2023-10-26T20:01:38.504Z</atom:updated>
            <content:encoded><![CDATA[<p><em>You figure it out.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jGEiQBdXn1512Ni054lfLw.png" /></figure><p>The little red triangle and the red ring around the knob labelled with the brand mark OXO constitute the idiot light on my drip coffee maker. When lit, it could mean, “clean me”, “put the carafe under the coffee filter station”, or “you forgot to add water, you moron.” It could mean other things but I’d have to consult the owner’s manual to find out what. As if I would ever do such a thing.</p><p>As a card-carrying idiot, it isn’t obvious to me which idiot the light is being referred to. Is it</p><p>· Me, the user, as a virtual dope-slap?<em> you broke me, you idiot</em></p><p>· The device itself, as a cry for help? <em>I’m stuck, I don’t know what to do.</em></p><p>· The designer, oblivious to the user? <em>There are many things that can go wrong with this gadget. A single indication will suffice for all of them.</em></p><p>In the case of my coffee maker, it must have sensors for at least “no water in tank”, “lime build up in heating element”, and one for “carafe not detected”. It may have others. It knows what is wrong. But it isn’t going to let me in on the secret.</p><p>It this age of intelligent everything, why did the designer choose to make such a tight-lipped device? Was it to save the expense of a few more LEDs for more diagnostic icons? Maybe there was no room behind the bezel for additional LEDs. I like to think it was in the spirit of minimalism. The OXO knob is the <strong>only control</strong> on the device. Rotate to the left if you are making 2–4 cups or to the right if you are making 5–8 cups (You have to discover this or read the instructions). Then press to start brewing. So, in the spirit of less is more, maybe the designer felt a single trouble light harmonized perfectly with a single control. Weirder design decisions have been made, trust me. <br> <br> The coffee maker makes excellent coffee by the way. I’m not complaining. <br> <br> As far as the device is concerned, the function of its idiot light is to elicit troubleshooting behavior from the meat-based thing attempting to use it. Sometimes the troubleshooting will be within the scope of the meat’s capabilities. Sometimes not. If not, then there is always the owner’s manual or Google. Or a more capable bit of meat can be consulted. Soon, generative AI will render more capable meat extinct.</p><p>Idiot lights surround us. They were first discovered in cars. Early in their evolution, they consisted of a single red indicator. This was used to signal that something unfortunate and expensive had happened to the vehicle. More recently, they have become more informative. The check engine light signals that something has gone bad under the hood. Some of these have a vocabulary. Yellow means that you might make it to a mechanic before it blows up. Red means you should seek shelter. You need to read the manual to know this.</p><p>Somewhat more informative idiot lights are now common. I once had a car with a single low tire pressure indicator — <em>one of your tires needs air but you are going to need to check all of them. Ha-ha. </em>But my current car helpfully lets me know which tire is low. Progress.</p><p>Some idiot lights aren’t lights at all. Personal computers made great leaps in idiot light evolution. Microsoft’s <em>Blue Screen of Death</em>, cleverly indicated that the user needed to perform the three fingered salute or alternatively, take a trip to CompUSA [1]. The “See your System Administrator” message on <em>personal</em> computers meant “I’m broke — lots of luck”. “Function not supported” meant “I don’t understand”.</p><p>As technology continues to evolve, so do idiotic indicators. Semi-pseudo-intelligent features such as spell checkers, voice response systems, human language translators and <em>Generative Artificial Idiocy Language</em> solutions all provide ways of signaling that that technology can’t deal with humans. Amazingly, semi-intelligent tech usually often does this <em>without even detecting</em> that human input has driven it off the rails. It’s still up to you, the idiot, to figure out how to get it to say what you want it to say. I’d provide an axe handle but you get the IKEA.</p><p>Idiot indicators don’t even have to involve technology. Consider those idiot lights that are the product of biological evolution. <br> <br> Some landscaping plants cleverly use yellow leaves to indicate both that they have been overwatered and underwatered.</p><p>My dog makes this huffing noise that means “play with me”, “feed me “, or “If you don’t let me out, I’ll crap on the floor”. A wagging tail can either mean “I’m thrilled to see you” or “I’m going to bite you.”</p><p>Last of all, humans have an idiot indicator called the <em>cold shoulder.</em> It means, “You have done something that really pisses me off, but I’ll be damned if I’m going to let know what it was”. Commonly used for signaling deep dissatisfaction to significant others, it often elicits an attempt to debug the relationship, such as “Is something the matter, dear?”. This is inevitably followed by another warning indication such as, “Oh, nothing. Why do you ask?”</p><h3>Notes</h3><p>[1] There are various kinds of three fingered salutes but this one refers to the act of simultaneously pressing the CTRL, ALT, and DEL keys on a Microsoft Windows computer. CompUSA was a retail establishment for selling personal computers and accessories.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c87ef0e6201" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/idiot-lights-5c87ef0e6201">Idiot Lights</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a design ethical?]]></title>
            <link>https://medium.com/consilient-design/what-makes-a-design-ethical-ac251ac3765d?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/ac251ac3765d</guid>
            <category><![CDATA[design-ethics]]></category>
            <category><![CDATA[ethical-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Mark Marrara]]></dc:creator>
            <pubDate>Thu, 23 Feb 2023 20:13:22 GMT</pubDate>
            <atom:updated>2023-02-27T14:54:52.169Z</atom:updated>
            <content:encoded><![CDATA[<p>Many people are interested in and write about ethical design. Increasing focus on the topic likely arises from public concerns related to developments in digital technologies such as social media, internet security, digital privacy, automation, deep fakes, facial recognition, and artificial intelligence in general. Although a few of these articles clearly are based on careful thinking about ethics in design, many appear to be mere opinion pieces. Some list the author’s gripes about popular software such as Facebook (Somos, 2020). Others have suggested that usable design is ethical design or that ethical design requires that designers put the needs of the user above business considerations (Vinny, 2021). Yet another has proposed a hierarchy of ethical concerns inspired by Maslow’s hierarchy of needs. The hierarchy has human rights as the base, the mid-section as the reduction of human effort and the apex as “delightful” human experience (Balkan, 2022). Finally, a more thoughtful theme is the notion of “dark design patterns” that cause users to act contrary to their best interests (Launder, 2016).</p><p>We have found much of the web content to be lacking in depth and usefulness. Design ethics goes well beyond ease of use, yet there isn’t a commonly shared way of considering what makes some design decisions ethical and others unethical. We need a firmer philisophical foundation on which to base our evaluation and discussion of design ethics. Determining what is ethical should be based on more than the opinions of the designer, author, or product development team. We hope to build on existing ideas and provide a fuller discussion of the ethical concerns that result from a designer’s work as well as those that arise as part of a designer practicing their craft.</p><p>Let’s start by defining the moral and ethical concerns related to design. Design Ethics will include different concerns when focusing on the user of a product compared to the designer of the product. The former focuses on impacts and consequences for the user of a product whereas the latter focuses more on how designers behave when applying their craft to produce the design for the product.</p><h4>Ethics and Morality</h4><p>In this article, we use “ethics” and “morals” interchangeably although subtle distinctions are often made between the two terms. Both deal with “right” versus “wrong” behavior. Some interpret ethics as dealing with rules that may be associated with specific domains or roles such as medical ethics or legal ethics. Some see morals as dealing more with personal principles that may be less dependent on context. Ethics may be viewed as more secular while morals may have a religious connotation. <br> <br>In any event, the two notions are tightly interconnected and different people make different distinctions. It is interesting to note that philosophers, those people whose job is to understand the meanings of things, variously refer to the same topic as either <em>philosophy of ethics</em> or <em>moral philosophy</em>.</p><h4><strong>Philosophical Foundations</strong></h4><p>The basis of ethics and morality is avoiding harm and doing good for others. Moral philosophers have come up two ways to define ethics. One is based on rules and goes by the name, “deontology”. This approach claims that certain <em>actions</em> are inherently good or bad. Adherents may argue for example, that it is always wrong to steal, lie, or kill. The competing idea is sometimes called “utilitarianism”. It holds that <em>consequences </em>are what we should be concerned with. A consequentialist, for example, might say that telling a white lie to protect another’s feelings or stealing to feed starving children can be considered to be moral acts.</p><p>Many ethical issues are vexing and require the weighing of both rules and consequences. For example, an ethical designer should be aware of rules of the craft (best practices and guidelines) but they should also seriously consider the ultimate consequences of the applying the practices. Using utilitarianism as a lens for our analysis, we’ll first focus on design ethics issues that arise from the impacts that a design (interaction, experience, product) has on a person. How the design functions, interacts with its users, and reports on its users, creates the consequences or impacts of its use. These consequences, or impacts, can be both negative and positive with a range of magnitude in either direction. They can also be non-reversable.</p><p>We should note that design intention matters here. In our analyses of products and experiences, we focus on the intended use of the product versus the myriad of its unintended uses. We would not say that a magnifying glass has design ethics issues because it can be used to start deadly fires. However, designers have a <em>responsibility</em> to consider ethical issues and potential harm from their choices when a consumer uses a product in its intended use.</p><p>How a design interacts with its users provides many opportunities for unethical and harmful consequences to surface. Negative outcomes of an experience can include destruction, deception, manipulation, addiction, and discrimination. We’ll start here, though more outcomes may deserve additional attention and discussion in the future.</p><h4><strong>Destruction</strong></h4><p>Outside of weapons and construction equipment, few products create destruction as their intended outcome. Consider construction equipment as an example. For many pieces of equipment, the intended user outcome is destruction in preparation of building something new.</p><p>Let’s turn our attention to weapons for a moment. One could argue that weapons are also performing their ethically necessary duty when used for purposes such as hunting and protection of civil society. However, marketing weaponry to children, as is frequently done in gaming and with some brands of guns, opens many ethical issues.</p><p>We are also purposely not delving into the arena of government policy, which many folks, depending on their political leanings, tend to view as destructive. One could debate the intent of laws passed that ban books to keep people uneducated as ethically challenged. We will avoid debates of this sort and instead focus on product design issues.</p><p>Another form of destruction can be caused by the planned obsolecence of a product, since it essentially stops a product from operating as intended. Planned obsolescence is the planning of a product or service to become obsolete. While improvements in technology will frequently require some products to become obsolete (e.g., VHS tapes were replaced by DVDs for higher quality and convenience), many products are now engineered to last only a short time when existing technology enables them to last decades. Is it ethical to design an appliance to fail within 5 years so that its users are required to buy new or upgrade? When leveraging existing technologies can enable the product to last much longer, we consider this practice to be ethically concerning due to the impacts on the environment and costs required to replace the product that should not have failed in the first place.</p><h4><strong>Deception</strong></h4><p>Deception can surface in many ways. An obvious example can be found in advertising and marketing loans in which consumers are told that they would save money by refinancing to a new mortgage that will take longer to pay off than their original loan. While users may not pay as much monthly compared to their current loan, the extra months (or years) of additional payments will actually cost more in the long-term. This illustrates a common form of deception by not providing complete disclosure of the facts. Deceiving consumers in any way is unethical, and designers have a duty to understand how their work is being interpreted by users and the value proposition (or lack thereof in this case) offered.</p><p>Not understanding how your product usage data is leveraged to influence you at every opportunity also represents a form of digital deception. Many people don’t realize how much of their data is shared with others, including the product development team to improve the product, business teams to understand their investment, and on the extreme side, other companies that can benefit from knowing more about you. It’s not a coincidence that people are served ads for products that they were previously browsing and event chatting about on a different site, app, and device.</p><p>Sharing your data is legal and you likely authorized it when you read and agreed to the multiple pages of Terms and Conditions for an app or service. Oh, you didn’t actually read the Terms and Conditions? You are certainly not alone in this behavior. For instance, a recent ProPrivacy study showed that only 1 percent of users in their study actually read the terms and conditions, although 70% of the participants lied and claimed they fully read the agreement (Sandle, 2020). While it is legally sound to provide extensive Terms and Conditions for users to agree with prior to using a product, is this behavior ethical given that we know most users don’t read the document before agreeing? A more ethically sound design would ensure that users understand and can articulate what they are signing up for versus quickly dismissing the materials faster than they can actually read the document. Enabling this to happen is ethically questionable, albeit legally sound.</p><h4><strong>Manipulation and behavior modification</strong></h4><p>Products and services will occasionally cause us to change our behaviors, both positively and negatively. Positive behavior changes have us doing positive things for ourselves, society, the planet, etc, whereas negative behavior changes have us doing things that negatively impact ourselves, society, and the planet. As a general heuristic, positive behavior changes, as the intended outcome of a design, are ethically desirable outcomes for designers to craft. Negative behavior changes should in most cases be avoided.</p><p>Behavior can be nudged positively and negatively through product design, and designers need to understand the longer-term impact of their designs. Positive nudges can be as simple as setting the positive as the default option for users. Since people will frequently stick with the default option, selecting the most positive desired behavior as the defalut will lead to the desired user behavior.</p><p><strong>Addiction</strong></p><p>Many products currently provide negative outcomes as part of their use. Consider nicotine addiction and the adverse health affects caused from a product like tobacco and e-cigarettes. Decades of research has confirmed the inherent health dangers, yet many designer continue to work in the industry. This is ethically questionable from a design craft perspective. Knowing that your work contributes to the addiction and adverse health affects for your users should serve as a warning that you are operating in an ethically questionable manner.</p><p>While tobacco and alcohol addiction are the most straightforward to discuss, addiction can also result from gambling and social media, both of which have rich digital product offerings. When a company, like Facebook, ignores (and hides) data that shows harmful outcomes to its users, including teenagers, it becomes ethically questionable for designers to contribute additional work that continues these outcomes. Are we saying that all designers currently employed by Facebook should quit and walk away? No, but their designers have a duty to ensure that their work isn’t further contributing to negative outcomes, and if so, push for change. Acting like the known data doesn’t exist or ignoring the outcomes being created is equally unethical.</p><p><strong>Discrimination</strong></p><p>There are various types of discrimination to consider when discussing the impacts of design. As an example, consider the following types of discrimination:</p><ul><li>Age</li><li>Disability</li><li>Sexual Orientation</li><li>Status as a Parent</li><li>Religious</li><li>National Origin</li><li>Pregnancy</li><li>Sexual Harassment</li></ul><p>Disability discrimination provides a popular starting point for discussing the outcome of discrimination caused by design. Not accounting for people with disabilities — both situational and permanent — represents an area of ethical concern. Many digital products work for folks with disabilities, yet most do not. Even with the risk of experiencing a lawsuit, many companies still offer digital products that do not work for disabled audiences.</p><p>Designers have a duty to ensure that they are practicing inclusive design as much as possible. This ensures that more folks will be able to use and enjoy a product. Not practicing inclusive design leads to negative outcomes for a large part of your audience, and as a result, doing so is ethically questionable.</p><h4>Borderline ethical issues</h4><p>Interestingly, we haven’t focused deeply on ease of use as a primary source of design ethical issues. That, in part, is due to the designer’s intentions. While distraction within a User Interface and ambiguity in an error message, as examples, lead to confusion, churn, and possibly lower product usage, these become a design ethics issue only when designers knowingly provide these experiences with the intent to distract or confuse. Similarly, a design that intentionally takes control away from the user is not only unethical but also unprofessional. It’s simply bad design if confusion, deception, taking away control, etc is the intended consequence. However, that is a far different intent than maturing a product to reach product-market-fit over time. Providing a Minimally Viable Product to market and then improving the ease of use and value over time is a typical product delivery method. This becomes ethically questionable only when the product and design team knowingly ignore ethically concerning problems that surface as their improving the product.</p><h4>Conclusion</h4><p>Design Ethics goes well beyond ease of use, yet there isn’t a commonly shared way of considering what makes some design decisions ethical and others unethical. We’ve used utilitarianism as a lens for our analysis, which has us focusing on the consequences or impacts that result from the designer’s (or product development team’s, more generally) design decisions. From this perspective, decisions that cause negative impacts to the user should be viewed as unethical, regardless of whether the impact is temporary or reversible. This includes the products designed by a product designer, interfaces and experiences designed by UI and UX designers, as well as designers working within marketing and advertising. Encouraging behaviors with harmful impacts through advertising is comparable ethically to designing the products that cause the harm.</p><p>In our next article, we will shift our focus of analysis to the designer applying their craft to solve a problem. How does the Design field, generally speaking, determine what behaviors are ethical and unethical? Is there a governing body for designers that provides standards and guidelines for designers to follow? Should there by? We’ll address these questions and many more.</p><h4>Sources</h4><p><em>7 Ethical Design Ideas That Would Make Facebook A Better Place.</em> (2020, April 13). <em>UX Studio</em>. <a href="https://uxstudioteam.com/ux-blog/ethical-design/">https://uxstudioteam.com/ux-blog/ethical-design/</a></p><p>Launder, M. <em>The ethics of UX: when is it good design and when are you just tricking people? </em>(2016, April 20). Digital Arts. <a href="https://www.digitalartsonline.co.uk/features/interactive-design/ethics-of-ux-when-is-it-good-design-when-are-you-just-tricking-people/">https://www.digitalartsonline.co.uk/features/interactive-design/ethics-of-ux-when-is-it-good-design-when-are-you-just-tricking-people/</a></p><p>Sandle, Tim. <em>Report finds only 1 percent reads ‘Terms &amp; Condidtions.’</em> Digital Journal, from <a href="https://www.digitaljournal.com/business/report-finds-only-1-percent-reads-terms-conditions/article/566127">https://www.digitaljournal.com/business/report-finds-only-1-percent-reads-terms-conditions/article/566127</a></p><p>Vinny, Cynthia.<em> Ethical Design: How to Be a More Considerate Designer</em>. (n.d.). (2021, November 16). From <a href="https://careerfoundry.com/en/blog/ux-design/what-is-ethical-design/">https://careerfoundry.com/en/blog/ux-design/what-is-ethical-design/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac251ac3765d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/what-makes-a-design-ethical-ac251ac3765d">What makes a design ethical?</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overloading and Mental Models]]></title>
            <link>https://medium.com/consilient-design/overloading-and-mental-models-12d84a748edf?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/12d84a748edf</guid>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[overloading]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Mon, 06 Jun 2022 01:15:43 GMT</pubDate>
            <atom:updated>2022-06-06T01:14:55.689Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A house key being used to open a letter." src="https://cdn-images-1.medium.com/max/876/1*qEW6dF3CRYNa6TSEHc3sMg.png" /></figure><p>User research and design has made much ado about mental models since at least the early 1980s. It is a compelling concept. If we understand how users think a device works we should be able to use to that knowledge to design a better experience. However, much advice on how to exploit user mental models seems to boil down to an obvious tactic — discover mental models and design to them. There must be more to glean from this apparently powerful idea.</p><p>One possible tool in the mental model design toolkit is be the concept of <em>overloading. </em>Overloading is a software engineering concept most easily understood using the example of the arithmetic operator, “+”. Some programming languages <em>overload</em> “+” by using it for both addition: 5+3=8 and concatenating (joining) strings: “bed”+”room” = “bedroom”. The symbol “+” is <em>overloaded </em>because it now has two functions — addition and concatenation.</p><p>To those unfamiliar with coding, this seems like a perfectly reasonable way for a language to behave. In English, ‘five and three make eight’ and ‘the room with a bed is a bedroom’. In fact, in programming language design, the practice of overloading has been controversial. Consequently some languages allow it, others don’t.</p><p>The problem is that while people understand what to do with these symbols based on meaning and context, computers don’t. They are finicky about data formats. Programming software has a very limited ability to interpret symbols in very constrained contexts. When handed expressions like “5+3”, it identifies “5” and “3” as integers because they are each one or more symbols in the set {0, 1, 2, … 9}. It identifies “+” as command for addition. If handed “five plus 3” it falls on its face.</p><p>The easiest way of handling this issue is to disallow overloading by implementing “+” to only call for the addition operation, full stop. This does mean however, that if the language is to support concatenation it is going to require some other symbol. Some have done this by using “&amp;” : “bed” &amp; “room” = “bedroom”. Others by using a blank space as the operator: “bed” “room” = “bedroom”.</p><p>This means that a beginning programmer will need to quickly learn data formats and symbols for operations. Above all she will need to learn to be very careful with syntax.</p><p>Alternatively, we might want to implement a language that allows some overloading. As the “bedroom” example suggests, we humans don’t think or communicate quite as rigidly as computers do. It is perfectly reasonable to think “bed” + “room” refers to a bedroom, “poison ivy” plus “bare leg” equals rash and so on. Our brains are beautifully adept at applying context and loose meanings of words to arrive at meaningful results. This fuzzy, meaning-dependent feature of human languages saves us from having to come up with a lot more words. It also gives us poetry and evocative prose. Words can be repurposed to good effect.</p><p>A similar kind of overloading phenomena is characteristic of physical tool use. Anthropologists call this <em>expedient tool use.</em> This is when, for reasons of convenience, you use a tool designed for one purpose for a different purpose. Using a house key to open a letter is an instance of expedient tool use.</p><p>By now you may be wondering what all this has to do with mental models. Read on.</p><p>Jacob Nielsen provides an <a href="https://www.nngroup.com/articles/mental-models/">excellent overloading example</a> in how Google Chrome solved a mental model issue with web browser design. Once upon a time, web browsers had a single long text field for entering the URL of a web page that the user wished to see. Entering the URL took you to that page. If you typed a simple word without “http://…” you would get an error. When search engines were invented, a search field was added. You would type web addresses in the URL field and search strings in the similar looking search field. Many users found this confusing. Their mental models presumably contained something like the rule:</p><blockquote>when I want to find something, I type it in the long text field</blockquote><p>The trouble was that this required the user to form slightly more complex mental models including both direct navigation by URL and navigation by search keywords.</p><blockquote>when I have a URL, I type it in the URL field.<br>when I only have a search term, I type it in the search field.</blockquote><p>This worked at the expense of user errors and an unnecessarily cluttered UI.</p><p>The problem was solved by overloading. Now most, if not all browsers, have URL fields that can recognize search keyword inputs. If the text input starts with “http://” or “https://” a URL lookup is performed. If the text input lacks the weird Universal Resource Identifier syntax itis treated as a search string. The users’ old simple mental model rule now works:</p><blockquote>when I want to find something, I type it in the long text field</blockquote><h4>Other examples of user interface overloading</h4><p>Similar to Google’s URL/search overloading, Apple’s Spotlight Search now overloads filesystem search with integrated web search capability.</p><p>Overloading isn’t limited to search capabilities. Imagine a draw program that could inspect free form line drawings, polylines, for patterns that a human would recognize as letter forms and then ‘reads’ the drawing as text. This ability to overload sketch input with text input is found in the note taking product, the r<a href="https://remarkable.com/?gclid=CjwKCAjwx46TBhBhEiwArA_DjNlWVq9bCWiAUrMBiRvFcTsjVMSYZASpSo2XQ0U8n5KEB0KxpavVjxoCFwcQAvD_BwE">eMarkable tablet</a>.</p><p>Finally, another case of UI overloading is provided by input fields that recognize phone numbers, addresses, dates and URLs embedded in free form text.</p><p>These examples suggest that smart interfaces that tolerate flexible, fuzzy mental models can provide opportunities for creating simpler, more intuitive user experiences.</p><h4>Making use of overloading</h4><p>The capability to be overloaded usually must be designed in, especially when it comes to software. The software engineer must enable the tool to detect an alternate usage and then supply the necessary function for “off-label” use.</p><p>For this to work successfully, two conditions must be met. Users must recognize what kinds of input might work. Software must anticipate the range of possible inputs and provide responses that align with user intentions.</p><p>The nature of the input usually gives the software a clues about user intention. Sometimes user intent can also be inferred by the context of a user interaction. When it fails, it should do so gracefully.</p><p>The interface itself should suggest to the user the various kinds of input that will be accepted. Ideally, visual affordances will be visually integrated into the design instead of relying on fall backs such as embedded user assistance or “show-me” tutorials.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12d84a748edf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/overloading-and-mental-models-12d84a748edf">Overloading and Mental Models</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Habits versus Mental Models]]></title>
            <link>https://medium.com/consilient-design/habits-versus-mental-models-96cba15d100d?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/96cba15d100d</guid>
            <category><![CDATA[habits]]></category>
            <category><![CDATA[mental-models]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Thu, 02 Jun 2022 19:40:29 GMT</pubDate>
            <atom:updated>2022-06-05T20:35:53.915Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Mental models become necessary when designs fail us.</em></p><p>Although it may seem like our conscious self is always in control, much of our behavior is automatic. When we repeat actions frequently in similar situations they come to be invoked independently of conscious thought. These automatic behaviors or habits are an important feature of our cognitive machinery they because consume less mental (and metabolic) energy than deliberate conscious thought.</p><p>This mental feature explains why we sometimes may drive a familiar route and then are subsequently unable to recall details of the trip. It also explains how musical artists can play guitar and sing at the same time. It explains why, at least some of us, can walk and chew gum simultaneously. It is a superpower.</p><p>In contrast to habits, we also behave consciously, deliberatively and intentionally. This mode gives us the power to solve problems and think creatively. It also gives us the power to modify or break habits. The conscious mode of thought is also a superpower.</p><p>The Nobel Prize winning psychologist Daniel Kahneman and his colleague David Tversky as well as others made huge advances in cognitive psychology through their research and theorizing about the unconscious automatic and conscious deliberative modes of cognition. Although he didn’t coin the terms, Kahneman popularized the terms “System 1” as the standard way of referring to fast, low-cost, automatic behavior and decision making and “System 2” for the slow, effortful, deliberate behavior and decision making in his book “Thinking Fast and Slow”.</p><p>When we operate devices, we use both System 1 and System 2. Yet it may be that that when mental models are accessed we are mostly talking about system 2 behavior.</p><p>I’ll illustrate why with an example that I discovered in my backyard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*d43JIOdGl8ISot4lMkpW2w.png" /><figcaption>An overly complicated system for supplying water to a garden</figcaption></figure><p>To connect a water faucet to both a garden hose and a DIY drip irrigation timer valve, I attached a hose splitter to the faucet. One side of the splitter goes to the hose and the other to the timer valve for the system that waters my flowers. Figure 1 is a conceptual model of this system.</p><p>The splitter has valves for both sides. For this system to work, the faucet valve and the splitter valve to the drip system both need to be left open and the splitter valve for the hose needs to be closed at until the hose is used.</p><p>An issue with this system is that my fast , unthinking System 1 causes me to make mistakes with this simple arrangement. When I want to supply water to the hose, my first impulse (a System 1 impulse) is to turn the faucet valve. I then notice that it is already open. The mild surprise causes System 2 to kick in and I consult my mental model of the two valves on the splitter. So I open valve 1.</p><p>When I finish using the hose, I need to turn off the water. Again my first, and often only, impulse is to shut off the faucet valve. If I do so this, it shuts off the hose but also the water supply to my drip system. If I don’t catch my error my flowers soon wither in the 100 degree Texas heat.</p><p>The faucet looks like any other external water faucet that I turn on or off without much thought. Because I have used conventional faucet spigots over untold years this act of getting water to flow has become habitual. It is under the control of System 1. The valves on the splitter are less familiar and less salient. They require the operation of System 2 to suppress my System 1 tendency to use the faucet valve. I need to consciously consult my mental model of the system to achieve the desired results.</p><p>The optimal solution this problem is simple — split the water supply before a hose valve and the irrigation timer so that each operates independently. This would leave the faucet valve for the hose and the timer would work on its own supply. Unfortunately in my case, that would require a plumber. Once again cost defeats usability.</p><p>I have two other examples that show how poor design can cause errors by ignoring habit and how procedural knowledge is bound up in mental models.</p><p>Figure 2 shows the gas gauge in a rental van. It has two design flaws. First, the orientation of Full and Empty markers is flipped from the normal convention of Empty on the left and Full on the right. Second, The needle covers the bottom of the E in Empty making it appear to read “Full”. It is easy for a hapless driver to hop in, glance at the gauge and surmise that the tank is full when in fact it is empty. Repeated experiences with gas gauges produces the decision habit:</p><blockquote>if the needle points to the right, I’m good to go.</blockquote><p>If the driver doesn’t engage in the System 2 behavior of carefully studying the instrument panel before driving off, he or she will get a rude surprise when the gas soon runs out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*vJp3RD8ccY1i9ZmdMyRT3Q.jpeg" /><figcaption>Figure 2, Gas gauge in a rental van,</figcaption></figure><p>Figure 3 illustrates yet another case of a poor design in which habits conflict with a user’s expectations. Many elevator controls (and controls in general), now integrate labels with buttons, using a principle known as stimulus-response contiguity. This convention relies on an evolutionarily fundamental aspect of behavior called stimulus substitution. The stimulus (the symbol for the number 2) comes to stand for the behavior (tell the machine to take me to the second floor):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pgqUfPap2XhcJFlLdUGS-w.jpeg" /></figure><blockquote>locate the control representing your goal. <br>activate that control.</blockquote><p>Stimulus substitution is a very natural way to interact with the world. It is a bit unnatural to direct actions to a stimulus that is separated from the goal. This is why babies learn to eat with their fingers before they learn how to use cutlery. Indirect action requires the additional cognitive machinery of System 2 until a habit is formed and System 1 can bypass a bit of mental effort.</p><p>This control panel is in an elevator in the medical clinic that I visit once a year for my physical. To get to the second floor, I invariably press the high contrast, round label “2” to the left of the lower contrast round actual buttons. The round label doesn’t depress, I dope-slap myself to activate System 2 and then press the button to the right. When habit fails, I must fall back on a mental model rules:</p><blockquote>locate the label representing your goal. <br>locate the control nearest to the label.<br>activate that control.</blockquote><p>If I took the elevator daily, I might learn to press the silver button first. However without repetition, my more primitive stimulus-substitution behavior continues to dominate so once a year I repeat my mistake.</p><p>These and other examples lead me to think of mental models as stopgap measures that are used when intuition and habit fail us. You don’t need much of a mental model for controls that follow pervasive conventions and map goals directly to stimuli. You don’t need to build much of a mental model when there is a high degree of stimulus-response contiguity.</p><p>These are admittedly trivial examples. Of course absolute simplicity is rarely achievable and designers will continue to need to anticipate the formation of user mental models and design to accommodate them. On the other hand, how often do we as designers intentionally strive for the development of habits to lessen the need for users to build and rely on mental models of how things work?</p><p>___</p><p>Kahneman, Daniel. (2011) <strong>Thinking, Fast and Slow</strong>, Farrar, Straus and Giroux.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96cba15d100d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/habits-versus-mental-models-96cba15d100d">Habits versus Mental Models</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Mental Models]]></title>
            <link>https://medium.com/consilient-design/understanding-mental-models-b08c2bbd10c5?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/b08c2bbd10c5</guid>
            <category><![CDATA[design-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[cd-mental-models]]></category>
            <category><![CDATA[mental-models]]></category>
            <dc:creator><![CDATA[Mark Marrara]]></dc:creator>
            <pubDate>Thu, 02 Jun 2022 13:29:29 GMT</pubDate>
            <atom:updated>2022-06-02T19:39:32.186Z</atom:updated>
            <content:encoded><![CDATA[<p>What they are, what they are not, and how they are relevant for designers.</p><p>Designers frequently refer to the mental models of their users in casual and imprecise ways. For example, they frequently talk about supporting or designing for a user’s mental model, assuming that they fully understand it. It follows that this understanding will enable them to better align their designs with user expectations. Designers often obtain their understanding of mental models through user research that attempts to directly elicit model descriptions from users asked to verbally describe or draw their understanding of the inner workings of a design.</p><p>The mental model concept, which has existed in psychological theory for over 50 years, has become very popular and has been applied to a wide variety of fields. A quick Google search on Mental Models reveals a staggering 2,530,000,000 results. While some of these results accurately point to the earlier psychological research into mental models, many or even most are based on popularized notions of the mental model concept as synonymous with simple ideas, beliefs or theories. Furthermore, some make expansive and extravagant claims about how applying the concept will change your life through better insights and decision making.</p><p>We hold that, because many of these attempts to capitalize on the concept are based on slipshod thinking, they run the risk of polluting and poisoning some very valuable insights about our cognitive machinery, and more specifically, how we should design things to accommodate it. Clarity is needed.</p><h3>Basics of mental models</h3><p>For well more than half a century,<strong> </strong>cognitive psychologists have used a variety of concepts to explain behavioral phenomena that hint at hidden organizing structures used by the mind. These include mental representations, cognitive maps, schemas, frames of reference, analogical reasoning and mental models. These structures aren’t directly observable at present and may never be.</p><p>Mental model theory and research has engendered many controversies such as whether or not they are based on logical propositions or images and whether they reside in long-term or working memory. Furthermore, because different researchers have approached this problem from different theoretical orientations using different techniques we find ourselves in the familiar role of the blind men regarding different parts of an elephant. Or as Phillip Johnson-Laird (1989) said,</p><blockquote>It is as if explorers keep reporting the existence of a hitherto unknown animal, but their fragmentary glimpses of it convince them that they are observing different creatures.</blockquote><p>At the end of the day, these are likely different metaphors that capture some part of the evidence that suggest particular kinds of mental organization. We aim to add clarity rather than an additional metaphor. In short, Mental Models are structural analogues of our complex environment (Johnson-Laird 1983). They are thought to be cognitive structures (some have described these as <em>internal representations</em> of external reality) that form the basis of reasoning, decision making, and behavior. They are constructed by individuals based on their personal life experiences, perceptions, and understandings of the world. They provide the mechanism through which new information is filtered and stored. This definition builds upon decades of psychological research that started with Craik (1943) and was heavily influenced by Johnson-Laird (1983).</p><p>Don Norman in <em>Psychology of Everyday Things</em> (1986) gave an early and succinct description of mental models<em> </em>of <em>devices</em> that we use to complete tasks (We use “device” here as shorthand for things that a person can use to complete a task — devices can be physical such as a rock, a mechanical watch, or a car, digital such as a software application, or even procedural such a business process). He described two kinds of models: a design model — the designer’s or developer’s mental model of how a device works and a user model — the user’s mental model of how the thing works. The user model is a mental representation that <em>the user creates </em>in order to know or predict how to operate the device. The model provides a frame of reference for understanding interactions with technology and building expectations of machine behavior. Mental models set our expectations of experience for interacting with various types of devices and experiences.</p><p>While Norman uses the term <em>mental representation</em>, we’re not suggesting that all mental models are equivalent to pictures that users create in their minds while imagining something. A mental model can influence what you imagine, draw, and remember, yet mental models are more than simple memories.</p><p>They cannot be directly captured by verbalization or sketching. This is because like memories, they are fragmentary. When asked to describe the model being used in a given scenario or situation, a person will recall some parts and infer others on demand, typically to produce a cogent answer for the researcher. In short, they will come up with a model or story to explain their behavior as best they can recall it rather than describing every detail in their mind that led to each behavioral decision.</p><p>As an aside, there is plenty of psychological evidence of people being able to create mental representations of objects and spaces. For example, humans can imagine what an object looks like rotated in space or from a different point of view and mentally construct a map that lays out objects in a space. For clarity, we’re separating this work as <em>mental imagery (</em>and<em> mental mapping) </em>that you consciously create and think about to solve a problem. Regarding mental models, we’re referring more to the mental <em>frameworks</em> of procedural knowledge that enable us to understand the world around us as we interacct with it and predict the behaviors of animals, objects, and systems around us.</p><h4>How mental models are created</h4><p>Mental models need not be the product of conscious deliberation by users. People usually don’t go about consciously and deliberately building mental models of the world. Instead, they typically arise implicitly with minimal conscious engagement as a byproduct of interacting with our environments. They save us time and energy by enabling us to focus on the critical parts of an experience rather than needing to pay attention and remember all of the world around us. People may not be fully aware of content in their mental model until their expectations are violated.</p><p>Norman (1983) made some additional observations about mental models focusing on their parsimoniousness and fuzzy nature. They only provide the gist of understanding and are unstable. People tend to forget their details. Furthermore, people resist enriching them, preferring instead that they remain simple. This leads people to perform inefficiently and even superstitiously. Because they are incomplete they have predictive value and cause people to guess wrongly about device behavior. Finally, because they are so ephemeral, they have weak boundaries. People can mash up mental models of similar appearing devices and make invalid generalizations.</p><p>We create and refine our mental models as we experience the world. They are dynamically reinforced through direct experience with the world. For example, consider purchasing gasoline. Many years ago, these purchases were handled through a process called “full-service”. The steps consisted of pulling up to a pump and waiting for an attendant to ask you which kind and amount of gasoline you wanted. He (usually it was a male) then checked your oil and told you whether or not you needed more and cleaned your windshield. He then orchestrated the payment process and you drove off.</p><p>When the full-service model was replaced by “self-service”, there was a model mismatch. Now, no one comes out to your car when you pull up to the pump. Initially, this new process resulted in confusion until drivers learned and adjusted their mental models to account for the new procedural knowledge and tasks demanded from a different type of purchase experience. This same scenario can operate in both directions. Now imagine a person that has only experienced self-service stations pulls into a full-service station. They will experience confusion that requires adjusting their mental model accordingly.</p><h4>Assessing a person’s mental model</h4><p>It’s important for designers and user researchers to realize that mental models are not directly observable. As noted earlier, asking a person to describe their mental model or what they were thinking during a task may provide you with a story or description of the device or its behaviors, but researchers need to realize that this output is post hoc — rather than describing the non-conscious intent driving their actual behavior, users are consciously and purposely generating stories afterwards to explain their behavior along with the devices actions. While these descriptions and stories can produce some insights into confusing areas of their experience, they should not be taken as the default rules or structures inherent to a person’s mental model.</p><p>Additionally, asking a person how they think something works will typically provide interesting (and possibly useful) stories, yet these don’t necessarily reflect how a person behaves with the product or what triggers their behaviors during an experience. People can generate explanations on the fly regarding how they think something works under the hood, but these are stories made to answer the researcher’s questions rather than conscious intent driving their behavior. Researchers have repeatedly demonstrated the inaccuracies between what people say they do and actions they actually take. While these inaccuracies typically reflect people not accurately remembering all the actions they completed, it’s also natural for people to reflect more positively on their behavior to build a better story for the researcher.</p><p>Similarly, think aloud protocols (TAP) are useful but also incomplete. TAP are best if the user is echoing what they are doing as they do it as opposed to being asked after task completion (when they have a chance to generate a self-consistent narrative explanation of their recalled behavior). TAP can provide an idea of the <em>why</em> behind some of the behaviors witnessed, yet this includes people reflecting on what they are seeing and what they think it means to them and to the researcher. While useful for understanding confusing areas of an experience, TAP is not reflecting the procedural knowledge that builds a mental model. It will help identify scenarios in which people become confused, but additional testing is needed to better understand one’s mental model.</p><p>To get at the procedural knowledge in a mental model, use a method or set of methods that have users predicting device behavior to answer questions. For example, have users select and describe a device action that will result from the question posed by the researcher. Providing opportunities for people to make predictions or estimations of how something will unfold and why gives some deeper understanding of how they are framing the device behaviors along with the user behaviors that trigger and result from the device. This will help frame what device assumptions are being made and what behaviors are expected as a result.</p><h4>Conclusions</h4><p>Mental models have been researched and debated for decades, yet a lack of clarity still surrounds the topic. Nevertheless, it is popular again in user experience design as designers focus on and provide design rationale tied to a user’s mental model.</p><p>To provide clarity, we emphasize the function of mental models as a framework for structuring procedural knowledge to set expectations and guide behavior. With this perspective, mental models enable us to quickly capture and interpret what we experience in the world to guide our understanding and behavior.</p><p>It’s important to realize that capturing a person’s mental model is not as simple as asking them to describe it or draw it. Having users draw a picture of how a device works, by itself, is a self-reflection technique used to generate answers to a researcher’s question. While this will provide an answer for the researchers, the result may not necessarily reflect the underlying mental structures and procedures actually used when interacting with the device. Many user research techniques, like TAP and post-task interviews, are also not exposing the users mental model either.</p><p>Gaining an understanding of a person’s mental model requires several techniques used to converge on assumptions being made about a device and its behaviors. We suggest starting with tasks that require participants to predict actions based on certain conditions while explaining rationale along the way. While not perfect, this will start to surface nuggets of procedural knowledge that are structuring the participants responses and actions.</p><p>At the end of the day, the researcher and designer should be modest about their understanding of their users’ mental models. At best, they will have a mental model of their users’ mental models — a working hypothesis that is good enough for design but also always subject to revision.</p><p>Hopefully we’ve provided some useful insights on mental models in design. However, we’ve only scratched the surface. There are many other questions related to the concept and how it is used, especially from the perspective of User Experience research and design. We will be exploring these topics, including designing to support a person’s mental model, in a series of upcoming posts that provide other interesting and potentially useful details.</p><h4>In this thread</h4><p><a href="https://jimlentz.medium.com/habits-versus-mental-models-96cba15d100d">Habits versus Mental Models</a></p><h4>References</h4><p>Craik, K. J. W. (1943). <em>The nature of explanation.</em> Cambridge University Press, Cambridge, UK.</p><p>Johnson-Laird, P. N. (1983). <em>Mental models.</em> Cambridge University Press, Cambridge, UK.</p><p>P.N. Johnson-Laird, Mental Models (1989), in Michael L. Posner [Ed.] <em>Foundations of Cognitive Science</em>, MIT Press.</p><p>Donald Norman (1983) Some observations about mental models. In Dedre Gentner and Albert Stephens [Eds.], <em>Mental Models</em>, Erlbaum.</p><p>Donald Norman (1986) <em>The Psychology of Everyday Things</em>. Basic Books.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b08c2bbd10c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/understanding-mental-models-b08c2bbd10c5">Understanding Mental Models</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience Obsolescence]]></title>
            <link>https://medium.com/consilient-design/experience-obsolescence-1106ee05a7ad?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/1106ee05a7ad</guid>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Mon, 31 Jan 2022 00:26:57 GMT</pubDate>
            <atom:updated>2022-01-31T00:28:44.851Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Jim Lentz and Mark Marrara</em></p><figure><img alt="An old television sitting in a field." src="https://cdn-images-1.medium.com/max/1024/1*qPwwdGYo4jqYYQe3eKQUVg.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@anete-lusina?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Anete Lusina</a> from <a href="https://www.pexels.com/photo/retro-tv-set-in-dried-grass-5721898/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Modern technology changes quickly. It doesn’t just advance. It rushes ahead of us. It forces us to constantly adapt to the shape-shifting stuff we make for ourselves.</p><p>Technophiles find this state of affairs to be exciting and overwhelmingly positive. However, others often find it less than desirable and display a range of responses - from mockery to outright rejection of the latest gadget or app trends. For many of us “progress” has limitations.</p><p>More than 50 years ago, the futurist Alvin Toffler coined the term “future shock”, in the eponymous title of his best selling 1970 book. He defined it as a stressful state experienced by individuals and societies when people perceive there has been “too much change in too short a period of time” [1]. He wrote about the cumulative effects of many such changes in a short period of time. We want to examine individual human responses to ongoing technology changes observed “mid-stream” and up close. Understanding our reaction to these changes should help to develop insights for human interaction design.</p><p>Adaptation to change requires both the ability to embrace the new and let go of the old. By better understanding adaptation we may be able to control and manage change in order to enhance technological experiences.</p><h4><strong>“Experience” and “obsolescence”</strong></h4><p>In this article, we often use the terms “experience” and “experience of technology” rather than “user experience” to emphasize that the phenomena described here refers to more than just people interacting with products. To be sure, the things that we use include digital and material tools and devices. It includes acquired behavior patterns (e.g. blogging), group activities (e.g. barn raisings, e-meetings, flash-mobbing) and social structures such as organizations, rules and policies. Technology has downstream influences on our behavior that are more or lesss decoupled from the direct interactions with user interfaces.</p><p>“Obsolescence” is a process in which things<em>, </em>tools, devices, and social constructs are rendered more or less useless and unavailable by changes in technology. Because this article is about the human side of the technology-human experience relation, we focus on the experience of obsolescence. When obsoleted things become less useful and available, <em>human experiences</em> are affected. Rendering a device obsolete also renders our experience of it obsolete and our experience is what really matters.</p><p>Technology obsolescence has knock on effects that go beyond the changes in user experience that are bound up in direct interactions with devices and software. The invention of writing changed and devalued the experience of remembering that was associated with song, poetry, and mnemonic tricks. Digital writing technology has largely obsolesced calligraphy and cursive writing skills and even the ability of young people to read cursive script. When newer media formats replaced large vinyl disks the experiences of enjoying album cover art and inner liner bonus ephemera went away. Technology experience obsolescence has wide ranging effects.</p><h4>Drivers of experience change</h4><p>We often think of technology as the internal mechanisms that make things work —the physical components, materials, gears, batteries, electrical circuits and software. It also includes external features such as the human input and output interfaces, their appearance and the tasks they help us with.</p><p>Engineers change the internal aspects of technology for many reasons. These include improved reliability, durability and production costs. Changes to internal technology sometimes bleed through to impact human experiences regardless of design intentions. Tool handles once made of wood are now usually made of plastic. This primarily reduces manufacturing costs. In addition, changes like this may improve or detract from the experience of use — the tool may be lighter, more or less durable, stronger or weaker.</p><p>Engineers, of course, also intentionally change technology externals to modify human experience. As the pace of innovation has quickened, the power to define these externalities has been delegated to designers in various subspecialitiations — “visual”, “interaction”, “information” or most generally, “experience”. Most design work deals with updating existing products so in a very real sense, experience designers are responsible for managing experience obsolescence.</p><h4>Positive experience obsolescence</h4><p>Belief in technological progress assumes that technological change is for the better. Old technologies produced experiences that were tedious, effortful, boring or error prone. In modern society we no longer fetch water in wooden buckets from a well. We have indoor plumbing. It is difficult to argue that turning on the kitchen faucet is in anyway inferior to trudging outside to fetch a heavy bucket of water. We don’t need to go to the mailbox or telegraph office to send a message to a friend. We just pick up our phones and call or text. There are innumerable obsolete experiences like these that no one misses.</p><h4>Negative aspects of experience obsolescence</h4><p>However, like most things in life, UI changes may also have negative consequences for users. If you doubt this, just google “unnecessary UI change”.</p><p>The most common negative consequences involve the experiences of learning and relearning tasks. Learning to use a new device or app takes time, burdensome mental effort and delays its intended use. Moreover, when people interact with a system repeatedly they learn to become more efficient. When a learned task is modified or made partially obsolete by a design change, prior learning and efficient interactions are lost. This adjustment in user behavior is cognitively expensive and therefore annoying.</p><p>This aggravation is directly proportional to the frequency with which the changing task is performed. Frequent interactions become more automatic, requiring minimal attention and thought. This automaticity, better known as “skill”, is valuable because not only produces better results but it also frees the mind to concentrate on other things. Keyboard typing is an example of a one such skill. People who are highly skilled at typing can do so without looking at the keyboard, listen to music, and even follow conversations without interrupting their work. They acquired the skill through considerable practice and it now requires little conscious involvement.</p><p>Changing the machine interface for an automatic task like typing is disruptive. In the early days of computing, alternatives to the QWERTY keyboard were proposed. These included the efficient Dvorak keyboard and the easy to learn alphabetic keyboard. They all failed because they disrupted to skilled QWERTY typing.</p><p>Even the simple, mundane task of answering the phone can be disrupted. We do it reflexively with no more cognitive involvement than expressing intention to respond. But those of us old enough to remember old telephones with separate receivers experienced initially fumbling with wireless and mobile phones to find their answer button. The lifting of a receiver to the ear had been automatic. It was made obsolete by portable phones in which it was necessary to learn to lift the phone with one hand, find and press a button with a finger of the other hand and then move the phone to the ear. Of course, this too was learned but it took a few times to become automatic.</p><p>Driving a car is another example. Prior to the invention of automatic transmissions, learning to shift a manual transmission was required. This is a requires the coordination of multiple actions involving two feet moving at different rates while moving the shifter. If you learned to do this yourself or better yet, had the experience of teaching another to do it, you know how difficult and attention demanding it is. Yet with practice, it becomes automatic.</p><p>Users sometimes react strongly to these experiential changes. Roxanne Aberchrombie [5] referred to this as “change aversion”. When a “new and improved” technology disrupts the learnings and adaptations users have made to the prior technology, they often resist the change. The persistence of the love some have for manual automobile transmissions is maintained by change aversion as well as emotional attachment to the obsolete shifting experience.</p><h4>Mitigating the negative effects of change</h4><p>Fortunately, we have techniques to deal with the some of the unpleasantness of experience obsolescence and change aversion. These include knowing when change aversion is likely, knowing when an experience should be changed and knowing how to design those changes that are worth making.</p><p><strong><em>Identifying tasks susceptible to change aversion</em></strong><em><br></em>Change can be unpleasant when people need to relearn how to reach their goals with a new technology. But not all tasks benefit from learning and acquired skills. The impact of change is felt less for rarely performed tasks that don’t require investment in learning. The perceived effort required to focus attention when performing these tasks may be forgotten. Furthermore, changes in them are unlikely to be noticed because there was so little learning involved in rare prior uses. And finally, if designed properly, infrequent tasks can be designed to direct the user and thus reduce the cognitive effort required.</p><p>Because one-time and rarely performed tasks are relatively immune to change aversion they afford the designer with considerable freedom to make improvements. These can take the form of reduction in the number of steps to be performed or the reduction in effort required to perform steps.</p><p><strong><em>Identifying and handling useful and necessary changes<br></em></strong>More care is required when redesigning interfaces for repetitive tasks. First, it is important to consider whether and which experiential changes are warranted. This should always be framed in terms of benefits and costs for users. Will there be sufficient user benefit to outweigh necessary relearning costs? Are there areas of the experience that users are perfectly satisfied with?</p><p>Two operations of user interfaces are highly susceptible to change aversion — navigation and identification. Experienced users hate it when they can no longer find a function because someone has decided that it makes more sense to put it in a different area of the user interface or label it differently. Apple did this in IOS 14 when they moved the “Bedtime” feature from the clock app to the health app [3]. Unsurprisingly, many users (including this one) believed the function had been eliminated when it had merely been hidden.</p><p>True, designers don’t always have the luxury of avoiding risky experience changes. Sometimes this is out of their control. These may be forced by the underlying technology, the integration of multiple products into a single coherent platform, or the whims of product owners. In these cases, they should mitigate experience obsolescence impacts in the best possible ways for their users. Designers should thus consider how existing users will respond to change, address how they will perceive and understand the changes and ensure that novel aspects will be readily learned in order to limit unpleasant experiences.</p><p>Of course many changes can be beneficial for user experiences. Some existing experience designs leave room for optimization. These cases provide potential benefits that outweigh the cost of user adaptation. Note however, that they don’t eliminate the need for the designer to address change experience itself. While there are many design improvements that are instantly recognized by users as beneficial there are also many in which users don’t immediately or even ever see the value in the change.</p><p>Some experiences can be improved directly with little relearning required. These include changes in which the designer can reduce user effort in tasks that require multiple and/or cognitively demanding steps by automating them [4]. Still, even in these cases users may be disrupted if they recall obsolete steps but don’t see that the system is now performing them automatically.</p><p>Finally, some redesigns that improve status and feedback information can improve experiences without imposing significant relearning costs.</p><p>Product releases provide the opportunity to make many changes at once. It is important to think about those changes in aggregate as well as individual ones. Not everything should be changed. Things that work well for users should be preserved. Things that don’t work so well should be candidates for change. Cost-benefit tradeoffs should be used to prioritize changes. Lastly, when considering a product in its entirety, there can be a limit to how many changes, even positive ones, should be made in a single release. Sometimes improvements are best when delivered incrementally.</p><p>Cost and benefit data used to prioritize improvements can be gleaned from traditional user research, customer support reports, product forums and discussion groups.</p><p>To sum up, designers should limit change aversion by reducing the amount of egregious change in a product. We all must continually learn and adapt to changing interfaces in our daily lives, and in many cases, the changes provide little value. This is typically because a product development team neglected to consider potential impacts of technology changes from the user’s perspective.</p><p><strong><em>Dealing with the most disruptive product changes<br></em></strong>The most complex experiential changes are those that force a change in the user’s mental model so that it no longer provides a frame of reference for understanding what to do. These kinds of changes are by far the most disruptive and challenging to design. They can be the <em>béte noir</em> of experience obsolescence.</p><p>Not to sound like a broken record[5] but again, ensure that benefits of change are sufficient to outweigh costs. Reforming the users’ mental model is expensive and difficult, therefore the benefits to the user must be large.</p><p>In these highly disruptive cases, changes in Information Architecture (how the product is organized and structured), navigation, terminology, and UI model disrupt a user’s existing mental model of the product. This will inevitably mean heavy reliance on user assistance and documentation — something we are going to disparage in the next section. It will be necessary to be up front with users about the extent of change and to provide encouragement that it will all be worth the transition in the end. It might be useful to compare and contrast metaphors in the old and new versions. When all else fails it might be necessary to provide support for both a “classic” and “new and improved” versions to avert wholesale user abandonment of the application and defection to competitor products. Finally, common functions (e.g. Save, Save As, Copy/Paste, Open, Rename, etc.) should be preserved from the old experience and labelled with same words or icons to provide islands of experience stability and familiarity.</p><p><strong><em>Avoid design arrogance and user assistance mitigation traps<br></em></strong>Designers sometimes make changes for the sake of change itself or to demonstrate their skill as designers. This is fine as long as it doesn’t fail the end-user cost/benefit test. No one wants to kill an opportunity for a good designer to grow her career by producing noteworthy designs. However, the design field needs to above all honor the primacy of the user experience. A truly good designer will improve user experiences while considering the impact of any changes made.</p><p>Sometimes designers assume that any negative consequences of change can be nullified by cleverly integrating user assistance. Rarely if ever is this the case. User assistance should not be viewed as a get-out-of-jail-free card for design hubris. It is yet another thing a user must attend to and therefore is a detour between the user’s intent and end goals. When a person must look up a topic in user assistance, that time could have been better spent productively using the product.</p><p>User assistance varies in size and complexity. Bulky documentation in the form of education, release notes, product welcome or introduction materials are the most burdensome. They are usually added toward the end of development cycles as afterthoughts. No one enjoys reading this stuff and it is often ignored. Even when read, it is often quickly forgotten.</p><p>Lightweight assistance such as contextual help and walk thru UI tours are better but are still costs in the cost/benefit equation. Contextual help comes into play only when the user has been defeated in his attempt to understand the user interface. It does not eliminate the cost of unintuitive design. Walk-through tours are better but they also delay and divert the user’s attention from the task at hand. When given a choice, users will often decline such an experience in favor of attempting a task directly or exploring the user interface under their own control. The best improvements are readily apparent without requiring attentional detours.</p><h4><strong>Conclusions</strong></h4><p>Designing a new release of a product poses the challenges of coming up with a good design and then ensuring that it is implemented as designed. Surmounting these challenges is no small order. So it is understandable that designers sometimes fail to consider the effects of their change on users. But the growing burden experience obsolescence on users demands more attention.</p><p>Change is inevitable but can be managed. It requires proper cost/benefit tradeoff analysis, management of experiential change, and eschewing dependence on user assistance.</p><p>It requires knowing how to address different kinds of task modifications. Changes to tasks that required implicit or explicit learning are more risky and difficult to make. It helps to know what to keep and what can be modified. Changes that reduce mental effort and steps in a task are usually safe and welcomed by users. Those that impact UI navigation and operation identification are dangerous.</p><p>Designers should consider islands of experiential stability as critical to managing change. This should include familiar terminology, organization and iconography so that users can locate and identify task interfaces.</p><p>When changes are large, change mitigation efforts need to be equally large. They will require the tall order of designing learning experiences that engage users as they adapt. This in turn will will require a solid human-centric design process for the bridge to the improved experience.</p><p>Above all, designers should question the need to continually “refresh” experiences with the possible exception of some aspects of visual design. It is possible to fulfill the designer’s hope that they are making things better for users. It simply requires paying attention to what should change, what should be kept and how the transition will be experienced.</p><p>All of this requires that designers have a solid understanding of the strengths and weaknesses of the experiences within their product. Good redesign means shifting toward the strengths. If changes don’t do this, designers should raise the alarm and push back. Hardly anyone wants change for the sake of change.</p><h3>Notes</h3><p>[1] Toffler, Alan. Future Shock 1970</p><p>[2] Roxanne Aberchrombie, Change Aversion And The Conflicted User, Usability Geek, 3/15/2020 <a href="https://medium.com/usabilitygeek/change-aversion-and-the-conflicted-user-17f6b43e0cb4">https://medium.com/usabilitygeek/change-aversion-and-the-conflicted-user-17f6b43e0cb4</a></p><p>[3]RepublicWorld.com. What happened to bedtime in iOS 14? How to set a sleep schedule in iOS 14. 9/21/2020 <a href="https://www.republicworld.com/technology-news/mobile/what-happened-to-bedtime-in-ios-14.html">https://www.republicworld.com/technology-news/mobile/what-happened-to-bedtime-in-ios-14.html</a></p><p>[4] <em>automation:</em> Automation is sometimes assumed to suggest artificial intelligence. However, often a simple calculation or operation performed on behalf of the user will suffice. Presumably you arrived at this footnote by scrolling to the end of the article. This annoyance could have been automated by a simple hyperlink and return-link had Medium provided such a feature.</p><p>[5] <em>broken record:</em> A record is an obsolete form of physical media used to store music or the spoken word that existed prior to compact disks, MP3s, Spotify and Pandora. An early form of records were called “78s” because they rotated(!) at 78 RPM. 78s were made from an obsolete material — brittle shellac based resin. As a consequence, 78s often broke. In turn, 78s were made obsolete by 33s and 45s which were made from a plastic called vinyl (33s and 45s have recently been de-obsoleted by certain demographics for reasons of irony alleged sound quality). Regardless of rotation speed and construction materials, all of these media suffered from a mild form of breakage or glitch would cause the playback to repeat incessentally.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1106ee05a7ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/experience-obsolescence-1106ee05a7ad">Experience Obsolescence</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX focus limits design thinking]]></title>
            <link>https://medium.com/consilient-design/ux-focus-limits-design-thinking-c0f36afd5f61?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/c0f36afd5f61</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[jobs-to-be-done]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 17:24:10 GMT</pubDate>
            <atom:updated>2022-01-12T15:19:45.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A UX design sketch template" src="https://cdn-images-1.medium.com/max/1024/1*UynsJyF-ArkqEfqIR0HFSA.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@picjumbo-com-55570?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">picjumbo.com</a> from <a href="https://www.pexels.com/photo/white-printer-paper-196645/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p><em>Some musings about user intention and user experience. There is more to the human-machine relationship than experience design</em></p><p>Somewhere around 1990, usage emotionality caught the fancy of usability professionals. It seemed like a good idea at the time. After all use of many, especially unnecessarily complex, software products was and still is unpleasant.</p><p>To address this sad state of affairs the community of user interface researchers and designers thought it would be good to focus on the experiential aspects of usage. We hoped that we would not only stop the pain but also that we would exceed expectations and come to “delight” the user with our designs.</p><p>For those of us who have worked on enterprise software, “delight” is a pretty high bar. Not all products need to thrill the user. Many just need to help the user get things done with a minimum of pain and drama.</p><p>Despite my shamelessly provocative title, I believe our focus on experience is not so much wrong as overemphasized. And to clarify, when I suggest this I’m talking mostly about interaction design. Visual design, advertising and game design is all about the experience. If you are doing that kind of design then experience is what you need to focus on.</p><p>The rest of us who advertise themselves as experience designers are concerned with user interactions and the resulting satisfaction … or lack thereof. We often tend to give short shrift to other aspects of technology use.</p><p>The influence diagram below describes the human-product interaction relationship. There is always an environment or context in which usage takes place. People experience aspects of this context. Their perceptions motivate them to act intentionally to modify the experience.</p><p>Products mediate changes in the context to achieve a result. They have interfaces that people interact with. This is the primary concern of experience design. The preceding context, experience and intentions might be seen as influencing but separate from the thing being designed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*QHoQEKld_KpGsH2pr3WiBw.png" /><figcaption>Influence diagram of the human-product interaction relationship</figcaption></figure><p>To be sure, these other aspects are considered. Product managers and planners attend to market needs (i.e. customer experiences and intentions), competition, costs and profits. User researchers study usage context with contextual inquiry. In a multidisciplinary team most of these aspects are covered by one discipline or another. If the team functions well, perspectives of product planning, research and design are mutually embraced and a product concept emerges.</p><p>In the real world however, it often doesn’t work so beautifully. No one person gives appropriate weight to each of the components of the human-product relationship. Each discipline may share their perspective in meetings in which important messages are communicated and received less than perfectly. Different disciplines have distinctly different goals and understandings.</p><p>In any event, product managers should have a sense of what will sell. So they tell the designers, “design something that does this”. And the designers go away and define the interactions and interfaces necessary to do just what the product is supposed to do.</p><p>Often things like the as-is context and experience are covered early in the project. They play a role in deciding which negative or positive interaction experiences the designer will pursue. Lower priority concerns drop out and are forgotten by the time design begins in earnest.</p><p>When I think of the influence diagram above and the design life cycles that I’ve played a role in, I feel that the left side of the diagram has not been addressed sufficiently. User <em>intent</em> should be as important to the designer as user <em>experience</em>. And it follows that to understand intent one needs to understand what people are experiencing prior to using a product.</p><p>In fact, this is what the “Jobs To Be Done” concept is concerned with<strong>. </strong>Jobs To Be Done<em> </em>is about intention. It is about what products are about. It was invented in business management as a way to conceptualize new products. But it didn’t address how products are designed. This suggests an opportunity for a more consilient approach.</p><p>When designers are as focused on <em>what</em> users want to do with a product as they are with <em>how</em> they they interact with it what can result? For one thing, the products might enable users to more completely do what they want to do. In doing so products become more valuable to their consumers.</p><p>When designers can address intentions, they also have more control over design. They aren’t simply adding interaction polish to product concepts handed to them by product managers. They play a greater role in defining <em>what</em> products do not just <em>how</em> they do it.</p><p>This can lead to more creative solutions. Invention occurs when collection of ideas are held in mind at once. Thinking about user intentions and goals in concert with the experience of interaction should lead to better design insights.</p><p>Finally, as they design the interface they might find that wider contexts of usage and as-is experiences might be covered without adding additional complexity. Sometimes it really is possible to kill multiple birds with a single rock. You just need to make sure those birds line up with your throw.</p><p>I confess that this is mostly speculation in response to the kinds of design that I’ve witnessed in my career. This is more about possibilities than pat answers. But I’ve seen too much design time spent in laying out UI panels without due attention to how user intentions drive option choices. I’ve seen too many designs constrained by premature definitions of what a product is and does.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0f36afd5f61" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/ux-focus-limits-design-thinking-c0f36afd5f61">UX focus limits design thinking</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experience design: a twisted history]]></title>
            <link>https://medium.com/consilient-design/experience-design-a-twisted-history-fc58677d1ecb?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc58677d1ecb</guid>
            <category><![CDATA[unintended-consequences]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[social-responsibility]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Wed, 27 Oct 2021 20:14:17 GMT</pubDate>
            <atom:updated>2021-10-27T20:14:17.028Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Jim Lentz and Mark Marrara</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*fHZMLrEk9tqKgLmS4dTJTQ.jpeg" /></figure><p>Experience design has been around for much longer than many designers realize [1]. One could argue that it began in prehistory when a flint knapper first hafted a stone blade into a wooden handle in order to make it more comfortable to hold. Or maybe, it was earlier when someone worked a stone chopper so that the part to be held was rounder and smoother. It would be fun to try and tackle the entire history but that would be a tall order. So we will constrain our story to modern times. Experience design from the 20th century on has been a enterprise motivated by different objectives. Sometimes these favor the best interests of people and sometimes they favor less noble goals.</p><p>It is necessary clarify what we mean by “experience design”. People who intentionally design experiences with technology have gone by many names, “experience designer” and “user experience designer” are just recent ones. If we ignore the others we will have a limited perspective.</p><p>We use “experience design” in a comprehensive sense. This specific term first came to be used primarily to mean the composition of digital applications and media, but in reality, it applies to much, much more. For us, it is the practice of <em>intentionally</em> defining the way in which people interact with some kind of constructed technology. This technology may be physically, digitally, or even socially constructed.</p><p>This definition covers a lot of areas and risks pulling in too much. We have to draw the line somewhere, therefore we won’t be talking about composing music, perfume, food or dance although they are clearly things that affect human experience. We restrict it to experiences arising from interactions with things that might be construed as tools. Business processes, garden tools, toasters, scripted customer service verbal dialogs, aircraft control panels, ranking algorithms, and movie streaming service screens all fall under our definition.</p><h3>The evolution of experience design</h3><p>Modern experience design evolved as in tangle of changing design disciplines and technological advances.</p><p>The concept of experience design as an occupation emerged in four stages. The first was the work early in the twentieth century of Frederick Taylor, Frank Gilbreth and Lillian Gilbreth. They developed the industrial engineering practice of “time and motion study”. Closely observing and timing actions and operations in a task made it possible to increase throughput and reduce errors. Improved productivity meant that more product would be delivered for the same wages paid. This satisfied the interests of industrialists seeking greater profits. Little consideration was given to how the work was perceived by the workers themselves. If the experience of a “scientifically managed” job was mind-numbing repetition and boredom, so be it. The only relevant goal was to increase profits.</p><p>The second stage was the creation of the field of <em>human factors engineering</em> in the United States during World War II. Human factors engineering also sought to improve efficiency and reduce errors. Its scientific base was expanded to applied experimental psychology, systems engineering physical anthropology as well as other areas. There were multiple applications of human factors in these early years but an illustrative one was what was then called “aviation psychology”. In war-time aviation psychology, error reduction meant not getting the pilot killed by inadvertently crashing a plane or being shot down by enemy fire. Productivity meant getting more of the enemy killed. It also meant faster, more effective training.</p><p>Another stage was the creation of the field of ergonomics in Europe. Ergonomics is the engineering science of understanding and improving work for the benefit of the worker. It was initially oriented more toward physical aspects such as tool anthropometry (the measurement branch of physical anthropology) and physical effort in industrial settings. But it soon came to encompass other areas such as cognitive and organizational design. It eventually became clear on both sides of the Atlantic that the ergonomics and human factors fields were attempting to solve similar problems using whatever scientific and engineering tools were applicable. Both ergonomics and human factors professional organizations recognized their mutual interests. The Human Factors Society eventually rebranded itself as as the Human Factors and Ergonomics Society. Similarly ergonomic organizations also formally acknowledged that their domain includes the field of human factors. They are essentially the same thing.</p><p>Finally, Industrial Design provided a parallel focus on manufacturability, appearance and functionality. In addition it began to pay increasing attention to ergonomics and usability. By considering functionality in particular, industrial designers added depth to the notion of ease of use.</p><p>These movements began to coalesce in the 1960s into what would eventually be called usability engineering. They all shared a concern for not only productivity and error reduction but also the notion of “usability”. Usability differs from utility in that it implies “ease”. Usage should be easily learned, it shouldn’t require a large number of operations or repetitions, nor should it require excessive physical or mental effort.</p><p>This notion was a win for both business and users. Businesses could save money on training costs and reap productivity gains through efficiency and error reduction. Furthermore, as consumer products became more usable, they would be more attractive to consumers. At work, users would find their jobs more satisfying because they would perform better and be less frustrated by complex tools. Employees could do more with less effort. At home, using technology would be more satisfying.</p><p>This period marked the beginning of a transition to a society that is deeply enmeshed in information technology. In the 1960s, the primary information technologies that people interacted with consisted of the printed page, telephone, television, and radio. Households had few telephones and televisions and they tended to be fixed in place. Their user interfaces changed very slowly if at all. Very little learning was required to operate them.</p><p>All this began to undergo radical change around 1980. Forward thinking technology companies such as AT&amp;T, Digital Equipment Corporation, Hewlett Packard, IBM, and SUN realized that increasing computerization would bring complexity beyond what the user community was prepared to handle. New technologies were esoteric. Totally new classes of hardware and software products appeared including personal computers, word processing programs, and spreadsheets. Technology companies increasingly hired specialists in systems engineering, human factors and industrial design. When these were in short supply, experimental and cognitive psychologists, sociologists and anthropologists were hired to adapt these new products to less technically trained users.</p><p>A new research and applied domain called “Human-Computer Interaction” (HCI) was the result. HCI specialists spent a decade or or so discovering and documenting the basic principles of the usability of computing devices. These specialists were hired in increasing numbers by product development organizations.</p><p>Corporations recognized the marketing appeal of emphasizing that products were designed with simplicity, ease and comfort in mind. The phrase,”user-friendly” became popular in the 1980s [2]. It was used widely and sometimes indiscriminately to counter concerns about of growing technical complexity. Enterprise software makers began to market and differentiate their products based on ease of use.</p><p>Upper management and marketing teams in these companies even saw ease of use as such a marketable product differentiator that it could be part of their branding. (<em>e.g.</em> “Intuit” and “ Lotus 123”, an early spreadsheet). Famously, Apple Computer used simplicity very effectively in its competitive battles with the IBM PC.</p><p>HCI practitioners in this period often called themselves “usability specialists”. They employed processes called “user-centered design”. One well-known set of principles was branded as “The User’s Bill of Rights.” The slogan “user in control” was touted as a good usability strategy as well as an ethical value. They saw themselves as advocates for the user.</p><p>In the 1990s through the present, five developments have caused more upheaval in the socio-technological landscape. The first was the popularization of the Graphical User Interface (GUI) by Apple, IBM, and Microsoft on desktop personal computers. Desktop environments and applications were designed using usability principles discovered throughout the 1980s and early 1990s. Designs were tightly controlled by applying human interface guidelines and standards. These specified layouts, control features, interactions and response feedback methods. Increasing numbers of people became familiar with this technology at work, if not also at home.</p><p>In addition to ease of use, productivity, and error reduction, experience designers increasingly considered a new factor — emotional responses to technology. It wasn’t enough for users to find a product to be easy to use, they should also feel good about using it, which in turn, could lead them to promote it by evangelizing to friends and associates.</p><p>The second development was the emergence of the web and web-based software applications beginning in the mid 1990s. The web introduced sweeping changes to user experience ecosystems. Emotional design became far more important especially as e-commerce emerged as a major economic driver of digital technology. Now designers were required to consider goals like attention capture, “stickiness” and user engagement. Due to the highly visual nature of the web, visual and graphic design skills became increasingly important.</p><p>The third development, was the mobile revolution. Mobile UIs are limited in both inputs and screen space so the primary experience design challenge was to define short, focused engagements in small, simple applications. Just as competition for attention drove web experience design in new directions, mobile interfaces required design objectives beyond ease of use, productivity and error reduction. These included attention capture, novelty, and aesthetic fashions.</p><p>The fourth development was the ability to easily update user interfaces. Ease of update is almost inherent in the design of web-served content. It can be as simple as editing a file. Other technology enabled desktop computing applications, operating systems and mobile apps to be updated with only the granting of permission, if not automatically.</p><p>Easily and frequently updating user interfaces has had both positive and negative consequences. The positives are obvious. The time consuming misery of complex update and migration tasks has largely been eliminated, at least for consumer software. Design error corrections and improvements come more frequently. Security and stability bugs are rapidly eliminated. Fresh new UIs are often exciting.</p><p>On the other hand, there are some negatives. Users often become extremely facile with UIs that have served them well for years. When these interactions are changed users must relearn their apps (interactive tutorials to mitigate a change is a poor fix when the user doesn’t think the app is broken). Undesired or confusing changes created in the phenomenon of <em>change resistance. </em>Resistance to change is particularly acute with older and disabled consumers. Moreover, some enterprise software updates may incur millions of dollars in migration expenses for the customer. It is no wonder that some organizations will resist upgrades until the vendor removes support for outdated versions.</p><p>The fifth development was the invention of automatic experience personalization. Diverse platforms exemplified by Google, YouTube, Facebook, Twitter, Amazon, and Netflix collect and analyze user profiles and behavior to filter and recommend content. Ostensibly, this is a great usability innovation because it helps users find what they are looking for while sparing them from laborious searches. Alerts and reminders provide situational awareness and personal convenience. Having my phone recognize when I typically leave work to proactively alert me of commute times avoids unanticipated hassles.</p><p>Automatic personalization has again extended the skills needed to craft user experiences. In social media, interaction design is barely relevant because the interfaces are so simple. Instead, data mining and algorithm design skills are exploited to channel information to users. Furthermore to mitigate socially negative effects of this channeling, these platforms have found it necessary (or have been compelled) to add experience design considerations of tradeoffs between free speech, hate speech and dangerous misinformation.</p><p>People love the convenience and/or entertainment value of these platforms. With their popularity comes power. With the possible exception of Netflix, they are essentially innovation-inhibiting monopolies. Furthermore, they all have second-order effects that run counter to the best interests of individuals and society at large. They all automatically personalize content on the user’s behalf. By restricting content to what users most want to see, they steer users away from information and experiences that could broaden their world view. Feedback effects in turn have exacerbated political polarization, group think, and the proliferation of misinformation. In addition, Facebook, Tik-Tok, Twitter, Instagram and other social platforms have exploited social reward systems leading to various forms of social and emotional dysfunction including online bullying, engagement addition and body dysmorphic disorder.</p><p>For the most part, these are <em>unintentional</em> negative consequences produced by the personalization algorithms. However, business interests also come into play [4] and impact the User Experience. Other intentional unethical design practices have come to be called “dark UX”. Dark UX design patterns nudge users into making responses that serve profits by sacrificing user goals. A complete examination of dark UX is beyond the scope of this article; however, a couple of examples will be useful. The U.S. Federal Trade Commission’s CAN-SPAM law requires that commercial emails provide ways for recipients to opt out of future emails but most spammers use the dark UX pattern of defaulting to opt-in while burying the opt-out link in fine print. Another example is Amazon’s defaulting to paid shipping even though a customer has already met the threshold for free shipping.</p><h3>Different roles — different goals</h3><p>Over the past 100 years an array of specialists have been designing how we experience technology. These have included industrial engineers, applied psychologists, human factors engineers, industrial designers, visual designers, data scientists, programmers and product managers to name just a few.</p><p>With different roles come different goals and values. Over time, experience goals have included efficiency, productivity, error prevention, safety, usability, design excellence and of course, business value. Often (but not always) business value and the pro-social design values of putting users first have come into conflict.<strong> </strong>The goal of keeping the “user in control”now competes with many product goals. While designers have worked to refine the fit between people and technology, users have seen their work deskilled and routinized, consumer privacy has been compromised and social cohesion has been disrupted.</p><p><em>Writ large, </em>experience design has changed considerably over the past century. Current designers often see it as primarily a creative prosocial activity. However, user-centrism has been on the decline in recent years. Usability is now just one of several goals of a product team.</p><p>The fact that “Human” or “user” are no longer part of a practitioner’s title is telling. The operative word is now “design”. Usability is still important but is merely one of many design goals. When a project has multiple objectives, trade-offs are inevitable.</p><h3>Summing it all up</h3><p>This is more than just a story about evolution of a discipline. It includes lessons that could help designers avoid the exploitation or trivialization of experience design in the future.</p><ol><li>Experience design has sought to realize a multitude of behavioral goals including personal productivity, safety and error avoidance, ease of learning, social engagement, satisfaction, comfort, effort reduction, and attention management. Similarly, multiple business goals have sought to exploit experience design such as product sales, cross-product sales, effective branding, vendor lock-in, cost savings, advertisement targeting precision and so on. These goals are intertwined and are often inseparable. To consistently design effectively requires understanding how user and business goals should interact.</li><li>Many players are involved in the realization of the user’s total experience. To realize one’s own design goals it pays to be at least conversant in or possibly display mastery in different domains such as systems thinking, data analytics, aesthetics, learning theory, and so forth. Since business and experience goals are intertwined, being knowledgeable of the business is important for influencing product direction.</li><li>Technological advances have always expanded the pool of design languages. With each technological revolution, considerations are added. They are rarely removed. Careers vary in scope but many designers will find they need to continually expand their knowledge of interface technologies.</li><li>We can no longer assume that the experiences we design are inherently good for the user. Experience design often helps users by simplifying their interactions with technology and providing positive emotional responses. But it also can also produce unintended negative consequences that may not be apparent immediately. Finally, experience design can be used to advance business interests at the expense of users. If designers want to ensure that their work is a public good, they need to be aware of the entire set of experiences and outcomes that they are creating.</li></ol><p>Some designers believe that their role and responsibilities end in creating surface level interactions. The total experience consists of so much more. It includes the experience of a product life cycle. It includes first use learning, expert usage and making transitions necessary to use updated products. It has safety and ethical dimensions for both individuals and society.</p><p>Automation and machine learning technologies increasingly shape user experiences, and we’re just beginning to learn some of their effects on society. This sixth major technology development will almost certainly have a greater effect on society than any of the previous advances. It offers both positive and negative consequences. As a minimum, we must do no harm. But we need to do much more. As designers, we need to be proactive. We need to recognize our ever expanding responsibilities for the designs we create.</p><h4>Notes:</h4><p>[1] In a article in a notable magazine, this author claimed to be a pioneer of user experience circa 2000. By our reckoning, he was only off by about 100 years.</p><p>Jesse James Garrett 06–03–2021, I helped pioneer UX design. What I see today disturbs me. <strong>Fast Company</strong> <a href="https://www.fastcompany.com/90642462/i-helped-pioneer-ux-design-what-i-see-today-horrifies-me">https://www.fastcompany.com/90642462/i-helped-pioneer-ux-design-what-i-see-today-horrifies-me</a></p><p>[2] Donald Norman is sometimes erroneously given credit for coining the term “user friendly” in 1982 (e.g. <a href="https://www.nngroup.com/articles/100-years-ux/">https://www.nngroup.com/articles/100-years-ux/</a>) However, it dates to at least 1978: I. Kameny, J. Weiner, M. Crilley, J. Burger, R. Gates, and David Brill. EUFID: The end user friendly interface to data management systems. <strong>VLDB ’78: Proceedings of the fourth international conference on Very Large Data Bases.</strong> Volume, 4 September 1978. pp 380–391 <a href="https://dl.acm.org/doi/abs/10.5555/1286643.1286693">https://dl.acm.org/doi/abs/10.5555/1286643.1286693</a></p><p>[3] In the early days of HCI, the minimum requirement for most positions was a master’s degree in a relevant field. Ph.D.s were preferred.</p><p>[4] This is currently all over the headlines. For example: “People or profit? Facebook papers show deep conflict within” <strong>Seattle Times</strong>. collected October 25, 2021. <a href="https://www.seattletimes.com/business/people-or-profit-facebook-papers-show-deep-conflict-within/">https://www.seattletimes.com/business/people-or-profit-facebook-papers-show-deep-conflict-within/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc58677d1ecb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/experience-design-a-twisted-history-fc58677d1ecb">Experience design: a twisted history</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your research should tell a story]]></title>
            <link>https://medium.com/consilient-design/your-research-should-tell-a-story-1a671cb21084?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/1a671cb21084</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[design-research]]></category>
            <dc:creator><![CDATA[Mark Marrara]]></dc:creator>
            <pubDate>Wed, 08 Sep 2021 22:01:54 GMT</pubDate>
            <atom:updated>2021-09-08T22:01:54.597Z</atom:updated>
            <content:encoded><![CDATA[<p>We frequently field questions from researchers on how to be more impactful and influential with their research. We get it. Research takes significant time to plan, facilitate, synthesize, and report. Then, after all of that, the research team is given 30 minutes to communicate their findings and inspire action to address the opportunities raised. This is occasionally followed by a kind “thank you” with no actions planned as follow up. Many of us have been there.</p><p><em>Is it the topic of research</em>? User research for enterprise problems isn’t that interesting to read about, you are likely thinking. Perhaps. That is not the problem, though.</p><p><em>Data is boring</em>, you say. No doubt, focusing only on data can be boring. Yet, we see this regularly in the way research is presented.</p><p>How does one fix this? Is Design &amp; User Research damned to be boring simply because of the domain and data? Hardly. Researchers need to embrace the art of storytelling to become more influential and break the boredom. Stories, when well written, are naturally engaging, capture your attention, and have the audience attempting to guess what’s next. Perfect for increasing audience engagement, participation, and action as you playback your research.</p><p>A common starting point and approach for documenting and playing back research uses two main sections: Tell the audience what you did and what you found. While this keeps the approach simple, it leads to stale, unconvincing research artifacts that rarely encourage action to be taken by the business. Take a different approach by building a story that communicates a tighter context to business objectives, builds on previously gained knowledge, and drives a deeper understanding of the business impact of both your findings and lack of action. Let’s go deeper.</p><h4>Setting up your story</h4><p>Start by framing your research story around the bigger business and design objectives along with the questions you are seeking to answer. This should provide a clear reason and business justification for the research. Be clear on the questions you need to answer, while illustrating the importance of these questions by connecting them to business context. Let’s say, as an example, that you are planning a study to understand why developers don’t complete all steps in the task of building and publishing a chat bot. While you could frame the research as seeking to understand the general ease of use of bot building, that doesn’t give the audience an understanding of why the research is important to the business.</p><p>Alternatively, you could frame the research with business impact to increase the relevance of your efforts. For example, Developers currently abandon the bot building process before step 4 of 5, which is costing the company approximately $5 million a year in opportunity that is then likely obtained by Acme, our closest competitor. What is causing developers to abandon the task before publishing their bot? Notice that the business context points to one or more critical questions and provides a business impact for the need to arrive at answers. Using some preliminary usage data or heuristic review to frame and describe possible user problems will help map to possible business impacts of user abandonement and pitfalls. This serves as a great introduction to your research and immediately draws in the audience with the business-critical focuses you are going to answer.</p><p>Explaining the motivation for conducting the research in business terms provides the audience with the deeper context and helps them better understand the problem. If the motivation for the study is that we’re doing the research because it is a required part of the process, then stop. Take a step back and reflect on what you are wanting to learn and why. What are the key questions that you are looking to answer and why are those important to the business? This will provide the starting point for building context for your research and tying the motivation to business goals. This will also help you frame what other research has been done in this area.</p><h4>Setting expectations (and creating suspense)</h4><p>After grabbing your audience’s attention with your motivations, business context, and any related research, forecast what you expect to learn based on current knowledge. Returning to the chat bot builder example, a forecast could include something like, “Bot builders are not publishing their bots because they become confused with our process while in step 3 of the task. We believe that this confusion is resulting from confusing text and poorly labeled buttons.” This speaks to the importance of understanding the larger user journeys for the critical jobs to be done that you are assessing. Conducting both a heuristic and competitive review of the application provide good starting points for establishing a starting forecast.</p><p>Providing the forecast of what you expect to find isn’t intended to show that you are clairvoyant. It instead helps your audience more deeply understand the research questions and provides a frame of reference for comprehending your findings. This technique also naturally builds suspense in your story. In more theoretical scientific research, it is critical that you forecast findings based on your theoretical position. These forecasts clearly frame the findings expected from your theoretical position and help your audience understand what you expect to find and why. Remember, your audience may be newer to your research, while you have been focused deeply on it for weeks. Your goal is to build your audience’s understanding of the problem, its importance to the business, and why you expect to find certain results. You want your audience, at this point, to believe in your forecasts and understand why your research is critical to the business. Not setting this stage frequently raises doubts about the need for the research and possibly even the credibility of your findings.</p><h4>Explaining your methodology</h4><p>The research methods used and why you chose them serve as a critical step in your story. Research methods include everything from who participated in your study, how you recruited them (for example, were they recruited from one or more sponsor clients?), what exactly participants were asked to do and why, and what is being measured. Keep in mind that your audience for design research will typically include folks who are not familiar with standard research methods. Why you chose a particular method doesn’t require a lengthy explanation, but you should explain how the method best enables you to answer the key questions to the business and how your participants in the research represent your actual users of the product. When recruiting participants from a single client, you will also want to speak to any biases that may exist and how these are overcome.</p><p>Communicating the overlap in characteristics between your participants and the users of the product in market also increases confidence in the interpretation and application of findings. From an enterprise product design perspective, these characteristics could include jobs regularly done, experience level of job mastery, amount of training, etc.</p><p>When writing scientific research papers, it’s critical that your methods section describe every detail of your methodology, experimental design, stimuli shown to participants, and all equipment involved. This is intended to provide adequate instruction for researchers to follow and replicate your findings before building upon them with additional experimentation. Focusing on design research, it’s advisable to be as clear as possible to increase your audience’s understanding and buy-in on their part to facilitate action. Enabling additional teams to replicate and build upon your study is typically less of a goal for design research.</p><h4><strong>Presenting your findings</strong></h4><p>Here’s where your story can become really impactful when done well. Many researchers will present the data gathered as if it speaks for itself and tells the complete story. It never does. Stating findings from the data without a larger story is similar to just reading the chart for your audience. <em>Option A was faster than option C</em>. So? Tell a story of the participants as you present your findings, including how they started, where they struggled, excelled, and why. This will increase the understanding the audience has of your findings.</p><p><em>How many stories am I telling here? </em>Good question. To this point, we’ve stressed the need to tell one story of your research. For example, describing why you are conducting the research, what others have done in this area, what you expect to find, the business impact of the research, etc. A second yet equally important story surfaces when communicating your findings. Telling a participant-focused story from your data facilitates a much deeper understanding of your findings by giving your audience a framework for remembering the data and comparing it to their own experiences.</p><p>Now that your audience clearly understands the behaviors shown by participants, frame your findings with the larger business context to increase your impact. You can communicate this context either as you tell the participant-focused story of your data or directly afterwards in a <em>Taking Action </em>section. Doing both won’t hurt either. The intent is to communicate what behaviors from your participant-focused story are important to the business and why. Another way of describing this is to note what went wrong and why on the part of the participants, and why this matters in business terms.</p><p>Returning to an ease of use example, stating that no participants made it past step 4 when publishing a chat bot or that people navigated path A faster than path B certainly represents findings from the data. Including causes for the behaviors and linking these to business outcomes is critical step. For example, a relevant story could include participants excelling at building a bot in less than 10 minutes to then get stuck by not understanding how to publish the bot. Assuming that this happens to 80% of the user base, this will result in 250,000 bots being built but not published, which in turn, will lead to $1.5 million of revenue being lost (just an example, folks!). While I’m certainly making up these data for an example, researchers should link the successes and struggles in the participant story to business outcomes when possible. While linking behaviors to business outcomes requires that researchers gain a deeper understanding of the business behind the product, doing so will increase the impact and relevance of the story and demand action on the part of your stakeholders. Who wouldn’t want to ensure those thousands of bots are published?</p><h4>Wrapping up and forcing action</h4><p>Researchers will occasionally shy away from connecting findings to business outcomes, yet this increases the relevance and impact of their research. Concluding your larger research story with a summary of critical findings, the business impacts of those findings, and specific improvements needed set the stage for forcing action. The business outcomes you provide enable you to specifically speak to what the business should expect if no action is taken, and in most cases, this will be a scary set of outcomes that folks want to avoid. When presenting the research, plan to spend the majority of presentation time here as you want the actions needed (and the why) to be understood and agreed to, and ideally a plan should be created during or as an immediate next step from your research playback.</p><h4>Keeping your conclusions within your study</h4><p>While we point to the need to understand the business behind the product so that you can provide a real and meaningful business context, care should be taken not to extrapolate your research findings to problems you haven’t researched. For instance, knowing what is causing the bot builders from successfully publishing a bot (and the business cost) does not also apply to various scenarios in which a person is publishing content. It might, but you need to specifically research this rather than inappropriately applying the findings from one study to other scenarios that may have some overlaps. Changing many variables such as task, content, people, etc. between studies renders any extrapolated conclusions as meaningless (and quite possibly incorrect).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a671cb21084" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/your-research-should-tell-a-story-1a671cb21084">Your research should tell a story</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Journey Maps to Hell and Back]]></title>
            <link>https://medium.com/consilient-design/journey-maps-to-hell-and-back-9840a74b40ad?source=rss----62c5e8c2a510---4</link>
            <guid isPermaLink="false">https://medium.com/p/9840a74b40ad</guid>
            <category><![CDATA[journey-maps]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[cd-articles]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Thu, 08 Jul 2021 20:50:28 GMT</pubDate>
            <atom:updated>2021-07-08T20:50:28.369Z</atom:updated>
            <content:encoded><![CDATA[<p>a critical survey</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qt6H9NM_4BYygPNR" /><figcaption>Cross Section of Hell. <strong>[1]</strong></figcaption></figure><p>People who design products and services are fond of creating charts that they call “maps”. One kind of map is variously called a journey map, experience map, customer experience map, and customer journey map. You want to cover all bases you could call them customer-experience journey maps, or customer user-experience journey maps. Strangely, “journey maps” almost never describe the movement of people from one place to another.</p><p>Sometimes one hears the term “story map”. Story maps are used by writers to plan the major episodes in a story. From a naming standpoint, story maps are spot on. The map of Dante’s Inferno is a map that comes from a story about a journey.</p><p>Some people inappropriately use “journey map” to refer to things more accurately called “roadmaps”, “process diagrams”, “user interface screen flows” and so forth. To be understood, you need to draw a line somewhere. So to put a stake in the ground, “journey map” will herein be used for diagrams that describe an experience, usually entailing technology or services that pass through multiple steps, stages and/or phases to arrive at a goal. In Dante Alighieri’s Divine Comedy, Hell, Purgatory, and Heaven are stages in his travels. He even has stages within stages such as the nine circles of Hell. In the story, his ultimate goal is to hang out with his best girl, Beatrice, in heaven. Sweet.</p><p>Note that visualizations of Mr. Alighieri’s travels violate the rule that journey maps never describe physical travel let alone metaphysical travel.</p><p>To understand how people make and use journey maps, I surveyed various examples and their attributes. I didn’t collect an exhaustive sample using a clever methodology. I didn’t dignify my survey with statistics. I instead relied on collections of examples and templates offered by others using Google and Pinterest. If you are looking for scientific rigor, then you don’t belong in this article. Stop reading now.</p><p>I noted recurring patterns and motifs. I critiqued practices that I found problematic . To be fair, I admit that I have committed most if not all of the sins that I accuse others of. I am guilty of hypocrisy which puts me smackdab in the eighth circle of Hell. This is a pretty harsh outcome, I think. So just in case, I hereby abjure and renounce these practices.</p><p>This is an exercise in meta-analysis. It analyzes types of diagrams that designers use to analyze experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aBGJxkEBLTpHY_tY" /><figcaption>A proscriptive journey map [2]</figcaption></figure><h3>Journey Map Functions</h3><p>People, or more precisely, <em>designers</em> make journey maps for different reasons. Sometimes they make maps to describe and analyze an experience. The experience described may be the way a journey is today. These are called <em>as-is journey maps</em>. Joyce and Kaplan [3] describe three approaches to journey map construction: stakeholder hypothesis first , quick and dirty based on existing knowledge and research first. In a perfect world, as-is maps would always be based on research. It is usually better if you don’t just make things up. However, the stakeholder hypothesis approach is can be useful for political reasons — with the caveat that it is properly followed by research to validate or disprove the stakeholders ideas.</p><p>Designers also create journey maps to describe how great the trip will be after they make some design improvements. These are called <em>to-be journey maps</em>. Given the degree to which a design as-implemented often fails to actually reflect the design as-designed, more realistic terms might be <em>should-be journey maps</em> or <em>wishful thinking journey maps</em>. Either way, they help product design and development teams share the same notions of what their customers’ experience is or should be.</p><p>Finally, some people create <em>prescriptive</em> and <em>proscriptive journey maps</em>. These don’t describe what the journey is or should be. Instead they describe what people should or should not do on their journey. The Road to Success illustration depicted above is a prescriptive journey map because it describes both.</p><p>Dante’s story is about a journey through Hell, in poetic rather than map form. His goal was to communicate his feelings about the relative importance of different kinds of misbehavior. He also sought to troll some famous historical figures and contemporaries in his13th Century Italy.</p><p>Journey maps may be very general (e.g. “The B2B customer journey”). They may describe the collective experiences of multiple people on journeys with the same purpose. They may also be very specific and describe the experiences of a single person on a particular journey.</p><h3>Journey Map Styles</h3><p>Journey maps come in different styles and formats. Boy, do they.</p><p>A popular style is a table where columns denote stages or phases, and rows denote almost anything. A common version of this approach uses a row of the table to show the ups and downs of the experience. The peaks describe positive experiences and the valleys are potholes in the path. Designers care about these potholes, more commonly called pain points, because they identify what they should fix. They are also known as <em>opportunities</em>. In other words, a customer’s pain is the lifeblood of an experience designer. Ponder that for a moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ePjj_ErEbsq-WA66" /><figcaption>A prototypical journey map of the car buying experience [4]</figcaption></figure><p>Edward Tufty [5] coined the term “chart junk” to refer to graphical features, usually decorative, in information diagrams that don’t convey useful information. Chart junk abounds in journey maps.</p><p>A common example of chart junk in journey maps is the use of continuous curves to chart changes in the degree of dissatisfaction/satisfaction, unpleasantness/pleasantness, or misery/ecstasy experienced on the trip. OK, that last one refers to a different kind of trip.</p><p>The point that I’m making here is about using continuous, roller-coaster curves to represent data that was almost certainly not granular and copious enough to create a smooth plot. I get that this is just a symbolic way to say that a journey has its ups and downs; however, I’m suggesting it would be best to avoid this shortcut and base mood charts on actual user responses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*VsZxZHeUR3fx14zx.jpg" /><figcaption>Journey map with roller-coaster mood graph and emojis [6]</figcaption></figure><p>Graphs in journey maps can also be used to display other qualities. In the map below, up represents “digitalness” and down represents “physicality”. That’s potentially useful. However, digital versus physical is a binary distinction rather than continuous data. So again, the curvy, roller coaster effect is misleading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*q_T-IxYKYFA14F6Z" /><figcaption>Journey map with digital and physical touchpoints [7]</figcaption></figure><p>Another common style is more cute than useful. It resembles a board game with squares or arrows representing moves that the user makes in a journey. We might call this a <em>snake diagram</em>. Or if you want to be fancier, call it a <em>boustrophedonic squamatiform itercartograph. </em>But if you go around using words like that people are just going to laugh at you behind your back. You will deserve ridicule but there isn’t a level of Hell for this kind of verbal sin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/0*33YW39HfOCNZDXx7" /><figcaption>A snake diagram for the car buying journey [8]</figcaption></figure><p>The trouble with snake diagrams is that they don’t display any more information than a simple list while taking up far more space. Furthermore, they are arguably less readable than a list. The graphic pattern of snake diagrams is merely decorative.</p><p>A journey map usually describes a single pathway from beginning to end. However, it can include branching pathways. When a snake diagram has these, it might be called a<em> chutes and ladders diagram</em>. These at least illustrate alternative pathways although this could be done in a simpler, easier to read manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*tmR3Gv4rZEtMhYSe" /><figcaption>A chutes and ladders journey map [9]</figcaption></figure><p>Stripped of chart junk, a journey map consists of a use case, a beginning, an end, stages that move someone from the beginning to the end and activities within stages. If the goal of map designers is to convey the essence of the journey this is all they need.</p><h3><strong>Bells and Whistles</strong></h3><p>Although the core features of journey maps are stages and activities within stages, many details are often included. Such as:</p><ul><li><strong>A persona or description of the type of person who undertakes the journey.</strong> This is useful if the journey is applicable to a specific type of human being.</li><li><strong>Persona/journey goals.</strong> Journeys are undertaken for one or more reasons. Sometimes the motives are obvious and don’t need to be explicitly stated. Sometimes they aren’t and should be called out.</li><li><strong>Starting conditions and scenarios. </strong>It may be useful to list the preconditions that must be fulfilled before starting the journey.</li><li><strong>Stages.</strong> Stages or phases are usually useful. They help to chunk a large number of steps into manageable groupings. Moreover, they often encapsulate parts of the journey that end in achieving subgoals.</li><li><strong>Stage goals.</strong> Sometimes a stage will have a goal that delivers more than the simple completion of part of a journey. For example, accessing a website to perform some task often includes a registration stage that must be completed before moving on to the task. If the site will be accessed multiple times in the future (why else should it require registration?) completion of the registration stage has future payoffs — the user no longer needs to register and secure access to the assets managed on the site are assured. As a bonus, the user will sometimes be rewarded with a new source of spam.</li><li><strong>Stage duration. </strong>Stages last a certain amount of time. This may be useful diagnostic information. If a stage lasts too long, it may indicate excessively delayed gratification. A long lasting stage in a journey may also afford a large window of opportunity for screwing things up.</li><li><strong>Mood.</strong> One of the primary reasons for creating a journey map is the elucidation of journey events or activities that have emotional impacts on the journey-person. Designers should pay attention to these. Understanding rough spots in context can lead to powerful insights. Occasionally journeys also offer little rewards and pleasant activities along the way. These are the things you don’t want to screw up in a redesigned journey. Many people use emojis to represent mood. Others (i.e. me) find them hokey. Another reason for avoiding emojis and their evil twins <a href="https://en.wikipedia.org/wiki/Chernoff_face">Chernoff faces</a> is that although they are intuitive the viewer must visually fixate on each face to read its mood. This makes it impossible to read the overall mood trajectory of the journey at a glance. Color (with due regard for accessibility), placement and brightness are superior for revealing mood issues at a glance.</li><li><strong>Touch-points.</strong> It may be useful to list the individuals, services, tools, devices, channels and user interfaces encountered along a journey. The user doesn’t actually have to touch these things. That’s just what they are called. Indicating touchpoints may provide diagnostic value. The number of ways a journey can go awry is directly related to the number of touchpoints.</li><li><strong>Choice points and branches. </strong>These are useful but are often neglected. This is probably due to the design practice of concentrating only on the so-called “happy path”. The assumption behind this approach is that designing for all possible pathways is difficult or infeasible. This is a dangerous cop-out because it is a scientific fact that occasionally things do go wrong.</li><li><strong>Moments of Truth.</strong> This is a marketing term for highly significant branch points that can positively or negatively affect the trajectory of an experience. In marketing this may mean clinching or losing a sale. In experience design it means falling off the happy path. Insofar as less than perfectly happy diverging paths are often omitted this could lead to the user being diverted into a dark and mysterious wood where fierce beasts lurk behind every tree.</li><li><strong>Quotes. </strong>Some people like to put quotes in their journey maps to drive home messages about phases or steps in the journey. Sometimes they are actual quotes from real people. Sometimes they are made up in order to give the map a narrative feel. This is another case of being loose with the truth in order to make a point. You should decide how to feel about this.</li></ul><p>Other bells, whistles, kazoos, geegaws, and gimcracks are sometimes found in journey maps as well. Kaplan [10] surveyed UX practitioners on their use of journey maps and found (in decreasing order) that user actions, personas, scenarios, emotions, thoughts, channels and devices were included by at least 50% of users.</p><h3><strong>Uses and abuses of journey maps</strong></h3><p>Journey maps have many uses. First of all, a journey map may be used as a data-summarization and analytic tool. When researching how people experience the use of tools, systems, and services a map can be used to indicate useful information along a temporal dimension. As mentioned earlier, a cluster of pain-points or an overly lengthy stage can indicate problems. Identifying end and stage goals can illuminate motivations. By doing so, they may provide insights for improving the experience and making the service or product more desirable for customers.</p><p>When a journey is not well understood, it might be useful for further analysis to throw in as many bells as whistles as the research data affords. Most of the data may be useless but you might not know until you see it laid out in front of you. But this kind of data vomit should only be used for exploratory analysis.</p><p>Journey maps may also be powerful expository devices. When pitching the results of research on a particular experience, a well-designed journey map can convey findings very effectively. Kaplan [10] found in her survey that some of the strongest benefits obtained by UX professionals involved forming a common vision and growing a customer-centric approach.</p><p>These benefits accrue when a map tells a concise and clear story. A common error made by journey map authors is to confuse analytic uses by experience professionals with reaching consensus. Elaborate, data-rich journey maps constructed for analysis are often be the best one to present to your cross-disciplinary product team, unless you want to confuse or bore them. It will likely only dilute the message you should be trying to convey. The moral of this story is to include only relevant data in the map.</p><p>Too many design researchers make the mistake of dumping a ton of data in clever, elaborate, multi-dimensional visualizations onto their audience. Then they are puzzled and frustrated when the product planners and developers don’t agree with their conclusions. Why should they? A complex journey map can become a Rorschach test. If you believe designers and researchers should lead the design direction (and why wouldn’t you?) then you need to sell your conclusions to your audience. A researcher’s job is not just to collect and present data. It includes interpreting the data and telling a story that helps us understand and believe your conclusions.</p><p>Some inexperienced journey cartographers may be led into the complexity trap by picking up a snazzy template from the web and then attempting to fill in all the various types of data it includes. These things should be used for ideas not as forms to be filled out.</p><p>It is also important to consider the possibility of hidden motives for constructing a beautiful data rich map. Your primary goal may not be to understand or convey project requirements. It may be, and often is, to convince the audience of one’s research thoroughness or graphic design prowess. If you have an implicit goal of enhancing your status in the organization by showing off rather than improving an experience, then don’t be surprised if the project team doesn’t follow your conclusions.</p><h3><strong>The journey just completed</strong></h3><p>Journey maps are a powerful visualization tool for understanding and communicating the experiences of people engaging with technology and services in order to satisfy goals. Journey map designers often exhibit a great deal of creativity by incorporating multiple data dimensions in their visualization. This can be helpful if the goal of the designer is to explore data collected by research; however, it can be counterproductive when the designer seeks to convince a larger product team of desired design directions and problems to be solved. Just as in any other design effort, creating a journey map should be an intentional act focused on the goals of the design rather than slavishly following a template or scripted procedure.</p><h3><strong>Notes</strong></h3><p>[1] <a href="https://digital.library.cornell.edu/catalog/ss:3293749">Caetani, Michelangelo (1855) Cross-section of Hell. Cornell University Library, Persuasive Cartography: The PJ Mode Collection.</a></p><p>[2] <a href="https://digital.library.cornell.edu/https://digital.library.cornell.edu/catalog/ss:3293749">Unknown (1913) The Road to Success. Cornell University Library, Persuasive Cartography: The PJ Mode Collection.</a></p><p>[3] Joyce, Alita and Kaplan , Kate (April 7, 2019) <a href="https://www.nngroup.com/articles/journey-mapping-faq/?lm=analyze-customer-journey-map&amp;pt=article">Journey Mapping: 9 Frequently Asked Questions</a> Nielsen-Norman Group.</p><p>[4] by the author.</p><p>[5] Tufte, Edward R. (1983). <a href="https://archive.org/details/visualdisplayofq0000tuft"><em>The Visual Display of Quantitative Information</em></a>. Cheshire, CT: <a href="https://en.wikipedia.org/wiki/Graphics_Press">Graphics Press</a></p><p>[6] Bodine, Kerry — cited by <a href="https://www.2040digital.com/the-impact-of-digital/mapping-the-multi-channel-customer-and-member-journey/">https://www.2040digital.com/the-impact-of-digital/mapping-the-multi-channel-customer-and-member-journey/</a></p><p>[7] unknown. <em>Journey map with digital and physical touchpoints. </em>There are several instances and variations of this map on the web. I was unable to find the original source.</p><p>[8] by the author.</p><p>[9] Primary-Intel.com 15-for-15. 15 powerful customer journey maps. <a href="https://www.primary-intel.com/15-for-15/15-powerful-customer-journey-maps/">https://www.primary-intel.com/15-for-15/15-powerful-customer-journey-maps/</a>. Unable to find the original source.</p><p>[10] Kate Kaplan (10/16/2016) <a href="https://www.nngroup.com/articles/journey-mapping-ux-practitioners/?lm=analyze-customer-journey-map&amp;pt=article">Journey Mapping in Real Life — a survey of UX Practitioners, </a>Nielsen-Norman Group.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9840a74b40ad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/journey-maps-to-hell-and-back-9840a74b40ad">Journey Maps to Hell and Back</a> was originally published in <a href="https://medium.com/consilient-design">Consilient Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>