<?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[Stories by Jim Lentz on Medium]]></title>
        <description><![CDATA[Stories by Jim Lentz on Medium]]></description>
        <link>https://medium.com/@jimlentz?source=rss-ddc83df39c9f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Y-A-AwtHFJr65jkKb8y_4w.jpeg</url>
            <title>Stories by Jim Lentz on Medium</title>
            <link>https://medium.com/@jimlentz?source=rss-ddc83df39c9f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:18:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jimlentz/feed" 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-ddc83df39c9f------2</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 19:56:47 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[Overloading and Mental Models]]></title>
            <link>https://medium.com/consilient-design/overloading-and-mental-models-12d84a748edf?source=rss-ddc83df39c9f------2</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>Sun, 05 Jun 2022 22:10:52 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-ddc83df39c9f------2</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:35:02 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[Experience Obsolescence]]></title>
            <link>https://medium.com/consilient-design/experience-obsolescence-1106ee05a7ad?source=rss-ddc83df39c9f------2</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-ddc83df39c9f------2</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-ddc83df39c9f------2</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[Journey Maps to Hell and Back]]></title>
            <link>https://medium.com/consilient-design/journey-maps-to-hell-and-back-9840a74b40ad?source=rss-ddc83df39c9f------2</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>
        <item>
            <title><![CDATA[Toward Unifying UXD and JTBD]]></title>
            <link>https://medium.com/consilient-design/toward-unifying-uxd-and-jtbd-cd38d4c0c2b0?source=rss-ddc83df39c9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd38d4c0c2b0</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-motivation]]></category>
            <category><![CDATA[jtbd]]></category>
            <category><![CDATA[design-methods]]></category>
            <category><![CDATA[cd-articles]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Thu, 08 Jul 2021 19:43:26 GMT</pubDate>
            <atom:updated>2021-07-08T19:43:26.252Z</atom:updated>
            <content:encoded><![CDATA[<p>authors: Mark Marrara and James Lentz</p><p>Over the past 80 years or so, the rate of technological change increased so rapidly that it became necessary to create entirely new disciplines and approaches to ensure that the design of new devices and systems aligns with human motivations, abilities, and limitations. These practices go by many names: Human Factors Engineering (HFE), ergonomics, engineering psychology, Human Computer interaction (HCI), usability engineering, User Centered Design (UCD), User Experience Design (UXD), Activity Centered Design (ACD), design thinking and Jobs To Be Done (JTBD) to mention only a few. Although they may differ in details, they are all based on research and design activities as a means to improve our interactions and experiences with technology. Furthermore, design practices have increasingly recognized innovation as a goal in and of itself that builds brand identities around creative solutions to old problems.</p><p>These practices developed over time and drew from multiple scientific and engineering fields, including psychology, cognitive science, anthropology, software engineering, industrial design, marketing and product management. This complex heritage is both a blessing and a curse. Different perspectives have been valuable; however, they also gave rise to a panoply of methodologies, tools, terminologies, and objectives. These are sometimes used together to good effect but relying on a grab-bag of techniques can give stakeholders the perception that design and design research are not serious disciplines.</p><p>Furthermore, this complex melange obscures simpler ways to understand and design the human — technology relationship. At its core, this relationship is a function of human <em>actors</em> in situations or <em>contexts</em> who perform <em>activities </em>using <em>technology </em>to achieve <em>outcomes</em>. We believe it is possible to describe a common underlying structure for understanding and modeling actors, their activities, and the desired outcomes as input to design. This structure weaves together the JTBD frameworks with journey mapping and user narratives to identify key activities, understand current and desired outcomes given ideation in technology or approach, and build empathy through storytelling.</p><p>In a previous paper (<a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.fzy6frvzmlfc">Lentz and Marrara, 2021</a>) we focused on simplifying personas, i.e. actor models, by demonstrating how their outcome-driven activities are more important to the design process than personal details and dispositions. In doing so, we provided a narrative-oriented persona model that meshes with JTBD frameworks.</p><p>In this paper, we will extend our unification efforts by developing a simple model for understanding the activities that users perform in order to realize their goals and desired outcomes. We will do this in a way that is consistent with JTBD frameworks and can be integrated with two popular design thinking tools, journey mapping and user narratives. We’ll first cover the basics of each method before discussing our unification strategy (see figure 1).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/0*0ARHrIpV3Z_BBAZt" /><figcaption>Figure 1.Integration of JTBD and Design Thinking methods</figcaption></figure><h3>Jobs to Be Done, activities and tasks</h3><p>Jobs to Be Done approaches originated in the business management discipline as a way to facilitate new product innovation (<a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.fl35s969lho9">Christensen et al. 2016</a>, <a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.6derlrylf80x">Ulwick 2016</a>). Its primary contribution was the realization of the importance of knowing the motivations for buying a product or service to the generation of innovative new concepts.</p><p>Ulwich’s Outcome Driven Innovation (ODI) framework (<a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.6derlrylf80x">2016</a>) is one of the most systematic and elaborate JTBD methodologies communicated to date. ODI describes a job as consisting of a situation, an outcome and an activity that produces the outcome. Ulwich created an elaborate framework that includes a taxonomy of job types (core functional jobs, emotional jobs, etc.), methods for identifying needs (i.e. outcomes), quantitatively prioritizing them, and a complete development life cycle model. However, much of the framework is irrelevant to our current objective of unifying JTBD and design methodologies.</p><p><a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.2amcfzn40zb1">Alan Klemet (2014) </a>advocated using “job stories” to describe the desired human-technology relationship. These are slightly modified user stories as found in agile development processes:</p><p>When <strong>situation</strong> I want to <strong>activity</strong> so that <strong>outcome</strong>.</p><p>In a job story, the situation (context or condition) and desired outcome (goal) define a person’s motivation for purchasing (or “hiring”) a product or service. The activity portion of the story defines what is needed to transform or “progress” from the current situation to the desired outcome.</p><p>The designer’s task is to design a mechanism and/or procedure to easily effect change from the current situation to the desired outcome.</p><p>As an example, a car buying scenario could be represented as the following job story:</p><p>When my car is old I want to go car shopping so that I can have a new car</p><p>It could also be elaborated as a scenario as shown in figure 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TU52Ig-E-65eppZpz9QygQ.png" /><figcaption>Figure 2. Car buying job</figcaption></figure><p>The importance of JTBD job stories to design can be understood by considering how different motivations influence what the user does. In this context, motivation is defined as the difference between the initial situation and the desired outcome. Different pairings of situation and outcome define different motives.</p><p>In addition, each pair of situations and outcomes (i.e.each motive) potentially defines a different set of activities performed by the actor. The activities, challenges, and expectations will differ depending on the actor’s motivation. Returning to the previous car purchasing scenario, the actor who desires to add an additional car to her car collection behaves differently (and completes some different activities) compared to the actor who is rapidly looking to replace his recently wrecked vehicle. At a macro level, both actors share the same objective of buying a car. However, when taking the actor’s motivations into account, the activities and success criteria vary widely (See figure 3)<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eXEIWQWbwo-DLcFP_aroqg.png" /><figcaption>Figure 3. Car buying jobs can vary depending on motivation</figcaption></figure><h3>Journey Mapping</h3><p>A set of popular techniques for understanding the activities, impediments and stages that a person experiences while striving to reach a goal are variously called “journey mapping”, “experience mapping”, and other combinations and permutations of user, customer, journey, experience, story and mapping. Some people make distinctions between these terms (e.g. <a href="https://www.nngroup.com/articles/ux-mapping-cheat-sheet/">Gibbons, 2017</a>); however, these distinctions are not relevant to this article. For our purposes, we will use “journey map” to mean an (analysis and presentation method) infographic table in which columns denote phases or stages and rows denote activities and emotional responses as well as other embellishments added to suit particular information needs for analysis. Journey maps illustrate end-to-end experiences and often include a representative persona, touchpoints, pain points and goals. Figure 4 provides an example journey map using our car buying scenario.</p><p>Journey maps are used by multidisciplinary product teams to achieve consensus about the current experience, to identify areas for improvement, and to prioritize design and development work to build a better resulting experience (typically referred to as the “to-be experience”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6yBgW2DwOsLFduVW" /><figcaption>Figure 4. Car buying journey map example</figcaption></figure><p>Journey maps are useful for at least the following reasons. First, they are highly efficient formats for presenting a large amount of design-relevant information. Second, they organize a user’s activities into meaningful stages or phases for further alignment and ideation. Finally, the types of information included can be tailored as necessary to describe different types of experiences. In our figure 4, we included activities, mood, and touchpoints, but there are almost endless possibilities of data to include, such as user interfaces, tools, effort, risk, and so forth.</p><h3>User Narratives</h3><p>Another highly popular approach for explaining a person’s experience with a product is to simply tell a story about the human-technology relationship (e.g. <a href="https://docs.google.com/document/d/10VTOh80XKLmW5zlb-ONml_J8Aib1-QiMRq0DOPCdKBA/edit#bookmark=id.kp298z3xslfu">Spool, 2018</a>). As with experience maps, stories can describe end-to-end experiences that include information about key activities and outcomes. They may be represented semi-visually in a storyboard or as a textual narrative.</p><p>Human beings are particularly attuned to stories. They explain why people do what they do. They facilitate empathy and understanding for the needs of others. As an added benefit, they are a highly memorable format for communicating a user’s situation, desired outcome, and activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YnjkQK5IMFZa_kczKUN1_w.png" /><figcaption>Figure 5. Car buying story example.</figcaption></figure><p>For these reasons, narratives are an ideal vehicle for explaining how users (actors) interact with devices and services. Story details that communicate the setting for the actor, what they are trying to achieve and why, along with all activities completed provide deeper context for collaborators to understand the actors, their objectives, and activities. See Figure 5 as an example. Through a brief story narrative, we set the context of Carl, why he’s buying a new vehicle, and many of the activities he does to complete this task. This brief narrative illustrates Carl’s mindset and challenges in an efficient and memorable way.</p><h3>Unifying Jobs, Narratives, and Journeys</h3><p>JTBD, journey maps, and user narratives were developed in isolation in different design practices. Often, which method used on a project is a matter of taste, habit or design ideology. They are typically seen as unrelated tools in a designer’s toolkit. However, it is worth considering how they relate to each other, their similarities and differences. Table 1 shows how each technique includes similar elements labelled by different terms. Notice the overlap between methods in describing and analyzing context, actors, and activities. While different terms are used between methods, they all emphasize the actor and steps taken to accomplish a goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rizoNRD6zpVOgri9VAu1wg.png" /><figcaption>Table 1. Correspondence of methods.</figcaption></figure><p>Insofar as each approach has advantages and disadvantages, harmonizing them could be beneficial to design processes in the following ways:</p><ul><li>By highlighting similarities between approaches, concepts and terminology could be reused. This would simplify learning and using these approaches as an ensemble.</li><li>By using the strengths of each approach to reduce the deficiencies of others.</li><li>By suggesting when, where and how each approach can be used for maximal effect in the design process.</li></ul><p>Although a common thread runs through all, the approaches vary in how effectively they use each element to drive design. All approaches include a beginning, a human component, action, emotional features and an end. They differ in how elaborately these aspects of the experience are described. For example, JTBD works well in concisely identifying motivations while narratives and journey maps primarily describe the activity and many steps included. In the latter two approaches, motives are either implicit or omitted altogether.</p><p>As a brief side note, we’re using JTBD methods specifically because of the discovery and identification of motivation. We are not subscribing to or suggesting that folks need to use the entire ODI framework and process. Many methods of generative user research will provide the necessary input into the design process as long as they are gathering and communicating motivation.</p><p>To unify the JTBD, journey mapping, and user narrative methods, we recommend starting with the deeper understanding of context and motivations provided by the JTBD method, and then use the context and motives when creating journey maps and narratives. Since the JTBD framework identifies reasons why a person or organization might acquire a product, it presents an ideal starting point for defining and aligning on project focus and scope. Searching for unmet needs and identifying the situations that drive usage provide the basis for ideation, invention, and on occasion, market disruption through new product innovation. These unmet needs depend on the motivations of the actor, which the JTBD framework provides.</p><p>Understanding job motivations, common narratives and journeys with current, “as-is” solutions is essential for grounding a design project in reality. Surveys, interviews and ethnographic techniques can be used to build this understanding. Once analyzed, journey maps and narratives can be used to explain the weaknesses of the current solutions. The scope of design should include not only user interfaces but also tasks and activities. As the design solidifies, “to-be” narratives and journeys may be used to demonstrate the magnitude of improvement.</p><p>Investigating jobs to be done is the best place to start research. Understanding which motivations (situation and desired outcomes) to pursue in a product sets the direction for the design effort. Researching and analyzing activities in existing solutions will indicate further opportunities to be had by addressing pain points, effort and time to obtain outcomes. Unmet needs can be understood in terms of unaddressed situations, cumbersome activities, and unsatisfactory outcomes. Subsequent ideation around solutions to unmet needs provides fertile ground for innovation.</p><p>Journey maps and narratives can be used for exploring and discussing new ideas. These techniques help the design team and stakeholders visualize the story, understand the actions completed by the actor, and gauge the impact of new experiences. In addition, including the essence of the starting situation in a journey map can help contextualize the reasons for undertaking the specific journey as well as decisions made along the way.</p><p>Journey maps can also be improved by using the JTBD situation-activity-outcome syntax of a JTBD job story. In Figure 6, the complete Job/Journey is Situation: Car broke down; Outcome: drive off with new car; Activity: the stages from Investigate through Purchase. Furthermore each stage in the journey map can be cast as a sub-job. For example, the investigation stage begins with an initial situation (unsure of finances) and outcome (financial decision), and has activity steps (identify liquid assets, examine monthly budget) interposed between. A design that acknowledges stages in an actor’s situation (often carried over from the outcome of the previous step), activity, and outcome format, helps the user mark forward progress in the journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/0*v3rajC-MobfhxRJy" /><figcaption>Figure 6. Journey map using the situation-activity-outcome pattern</figcaption></figure><p>Journey maps often follow a single route (“a happy path” or “golden thread”) through an experience. The reason usually given for this optimistic tact is that it is too difficult or distracting to stakeholders to consider alternative paths. However, designs that fail to anticipate different experiences and motivations in the long run likely produce poor satisfaction.</p><p>We included negative outcomes (in blue) in the journey map depicted in figure 6 to demonstrate the feasibility of considering path variability. The use of a situation-activity-outcome format in each stage of a journey also affords a good opportunity for identifying different outcomes that may need to be planned for each stage.</p><p>The alternative outcomes constitute branch points to be considered in design explorations. This ensures a more thorough basis for design planning and thinking and helps to guarantee that no experiences fall through the cracks within a project. Furthermore, tracking all outcomes also enables project stakeholders to understand and prioritize where to focus efforts to ensure a meaningful product release and measure return on investment for design focus on a project.</p><p>While we recommend starting with JTBD analysis to surface the actor’s motivations and context for the problem, progressing next into journey mapping and narrative building represents a reasonably simple process. Journey mapping and user narrative building are best considered iterative (or frequently done iteratively and in parallel). Journey maps enable further analysis, ideation, and alignment on the steps taken or needed by the actor, whereas narratives provide an effective way to communicate and sell the concept by fostering empathy by stakeholders. Plotting the activities on a journey map and combining this with the actor’s motivations serve as an outline for creating a narrative that communicates the opportunities and desired outcome while building empathy for the actor. Through the processes of composing and discussing a narrative, new ideas and details will emerge and these can be fed back into the journey map.</p><p>The evolving design will inevitably alter the narrative as constraints and new ideas emerge through ideation. Using journey maps as the foundation for building a narrative ensures the story accounts for the actor’s motivations and communicates the actor’s primary activities and challenges along the way. Discussions around the narrative can raise questions about the journey and steps included, which encourages these activities to be done iteratively and in parallel. Adjusting the journey to reflect narrative discussions will occasionally be needed to ensure project artifacts remain in sync. An evolved journey map may be valuable for a product’s user documentation, and similarly, a revised narrative may become effective marketing collateral or advertising material.</p><h3>Summary</h3><p>As designers leverage design thinking activities, such as journey mapping and user narrative creation, to ideate and improve the human-technology relationship, it’s critical that they account for user motivation as part of their process. It’s important to understand the why behind many or all of the steps along a journey. Knowing the actor’s motivation can also enable a better to-be journey to be created because the motivation gives designers a lens for looking at the current journey of steps to understand how much of the existing actions truly support the actor’s goal at hand.</p><p>We’ve described a simple approach for unifying JTBD, journey mapping, and user narratives. Start with JTBD analysis to understand the motivations of users. This deeper understanding of the actor’s desired outcomes and motivations frame which journeys to map along with the steps and possible outcomes along the way. We also recommend journey analysis, to-be ideation, and narrative creation to be done iteratively and in parallel following alignment on the actor’s motivations for all steps in their journey. The journey map serves as the foundation to writing the user narrative, and the narrative builds a memorable and empathic view of the actor’s problem and possible opportunities. Iteratively building journey maps along with user narratives provides many opportunities to ideate, communicate, and revise solutions as they mature.</p><p>The JTBD framework combined with journey mapping and user narratives enable designers to focus more deeply on the human in the human-technology relationship. We find that starting by understanding the desired outcome and the motivations driving that outcome easily frame which journeys to map and which sub-tasks to prioritize in ideation and product planning.</p><h3>References</h3><p>Christensen, C. M., Hall, T., Dillon, K., &amp; Duncan, D. S. 2016, September 1. Know Your Customers’ “Jobs to Be Done.” Harvard Business Review, September 2016. <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">https://hbr.org/2016/09/know-your-customers-jobs-to-be-done</a></p><p>Gibbons, S. November 5, 2017. UX Mapping Methods Compared: A Cheat Sheet, Nielsen Norman Group, <a href="https://www.nngroup.com/articles/ux-mapping-cheat-sheet/">https://www.nngroup.com/articles/ux-mapping-cheat-sheet/</a></p><p>Klement, A. 2014 Replacing The User Story With The Job Story, JTBD.info, Medium, <a href="https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27">https://jtbd.info/replacing-the-user-story-with-the-job-story-af7cdee10c27</a></p><p>Lentz, J. and Marrara M. May, 2021 Personas Reconsidered. <strong>Consilient Design</strong>, Medium.<strong> </strong><a href="https://medium.com/consilient-design/personas-reconsidered-5242ec36b671">https://medium.com/consilient-design/personas-reconsidered-5242ec36b671</a></p><p>Spool, J. (2018) When It Comes To Personas, The Real Value Is In The Scenarios. UX Articles by UIE, <a href="https://articles.uie.com/when-it-comes-to-personas-the-real-value-is-in-the-scenarios/">https://articles.uie.com/when-it-comes-to-personas-the-real-value-is-in-the-scenarios/</a></p><p>Ulwick, A. (2016). Jobs-to-be-Done. Idea Bite Press. <a href="http://jobs-to-be-done-book.com/">http://jobs-to-be-done-book.com/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd38d4c0c2b0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/toward-unifying-uxd-and-jtbd-cd38d4c0c2b0">Toward Unifying UXD and JTBD</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[Why Consilience?]]></title>
            <link>https://medium.com/consilient-design/why-consilience-4ce5bb5c427c?source=rss-ddc83df39c9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ce5bb5c427c</guid>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Sat, 19 Jun 2021 15:37:20 GMT</pubDate>
            <atom:updated>2021-06-19T15:37:20.640Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Consilience and Design?</h3><p>The inspiration for the title of this publication comes from the title of a book by E.O. Wilson. It may seem odd that a blog about user experience design was inspired by a book by a famous ant scientist. Wilson, a Harvard entomologist and two time Pulitzer Prize winner is sometimes referred to as the “father of sociobiology”.</p><p>In addition to his bug work, Wilson has an abiding interest in humanism and its relationship to science. His book “Consilience — <em>the unity of knowledge” </em>took on the challenge of finding unity between the humanities and the sciences.</p><p>Our publication has more modest goals. First, we want to explore the notion that at the core of different design approaches, ideologies and theories of experience design lies a deeper structure of human behavior that needs to be understood and accounted for in the design process. Successful experience (or product?) design requires that designers develop a sense of situational awareness of the person, their motivations, and context of use. Building this deeper understanding of users requires assembling knowledge and connecting ideas and concepts from a variety of disciplines, including psychology, business, marketing, engineering, etc. We draw inspiration from the need to connect various concepts to create big ideas and inform the design process.</p><p>Second, much writing about design has an antagonistic stance. It is easy to understand why this is so. Obviously, if one develops a new approach to design and writes about it, it will draw more attention than yet another recitation of well-worn ideas. If you want to draw attention, you need to differentiate yourself from others. If you <em>really</em> want to get someone’s attention, say something controversial. Of course, there is nothing wrong with advancing new ideas. This is how progress is made. However, when the intellectual products of the motivation to stand out are viewed across the field as a whole, the signal of good, practical design can be lost in the noise. Counterintuitively, we seek to stand out by highlighting commonality.</p><p>Third, we seek a broader consilience beyond the craft of User Interface design. While focusing on the mechanics of interactions and visual presentation is important for great product design, not including and pulling from the larger universe of useful ideas that exist outside of the UI design field misses key opportunities to innovate. There are valuable ideas in not just design-adjacent areas such as engineering but also in sciences far removed from interface design such as biology and of course, psychology and the social sciences. Drawing upon these notions can serve to fuel creativity and ensure that design focuses deeply on human beings, including performance limits, behaviors, motivations, and goals.</p><p>Finally, we want to promote <em>understanding </em>in contrast to <em>technique </em>alone<em>.</em> We assert that design innovation increases when designers combine and synthesize concepts from a variety of fields. This makes designing, as a cross-disciplinary collaborative problem solving activity, extremely powerful to converge ideas from a variety of sources. Knowing why a method works, having the ability to critically analyze alternatives and recognize what is useful and what is not makes one a better designer. The same goes for developing the ability to find inspiration in the broader world of knowledge. In short, we want to both illuminate the essence of design as a practice while integrating design into the larger contexts of business, science, and engineering.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ce5bb5c427c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/why-consilience-4ce5bb5c427c">Why Consilience?</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[Personas - Reconsidered]]></title>
            <link>https://medium.com/consilient-design/personas-reconsidered-5242ec36b671?source=rss-ddc83df39c9f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5242ec36b671</guid>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[cd-articles]]></category>
            <dc:creator><![CDATA[Jim Lentz]]></dc:creator>
            <pubDate>Thu, 13 May 2021 22:43:44 GMT</pubDate>
            <atom:updated>2022-05-03T17:40:57.559Z</atom:updated>
            <content:encoded><![CDATA[<p><em>authors: James Lentz and Mark Marrara</em></p><p>Personas have been a part of the experience designer’s and researcher’s toolkits since Alan Cooper introduced the term more than 20 years ago (Cooper, 1999). They are now pervasively used in design, marketing and product management (Owens, 2017; de Haaff, 2017). and help to design a variety of experiences with products, tools, and services.</p><p>Given their popularity, we might expect consensus in their definition and use but this isn’t the case. Many authors have advocated different approaches for persona construction. More importantly, some now question their value (e.g. Price, 2018; Thelwell, 2017; Massanari, 2010; Christensen, 2016). Yet they continue to be a standard part of design practices.</p><p>There are as many critiques of personas as there are approaches, yet they tend to focus on isolated issues such whether or not personas should be created in an ad hoc manner or contain fictional details. We provide a deeper examination of the attributes used to define personas, assess whether they are helpful in the design process, and then construct a leaner approach to personas that, as a foundation, communicates contextual information related to goal, job, and skill. By doing so, we unify personas with Jobs to be Done (JTBD) frameworks and story-based scenario approaches. We recommend eliminating all other persona attributes, such as demographics and personal details. Communicating this information in the narrative form of a scenario or story further helps collaborators frame the problem and build cognitive empathy for designers.</p><h3>The many faces of personas</h3><p>To identify and evaluate the elements used to create personas we will first briefly define what we mean by a “persona”. For us, a persona is a fictitious representation of a person, composed of a name and zero or more attributes that has a relationship to a product, tool, service or system. By this definition, actors in UML diagrams would not be personas because they lack names. A role would not be a persona because roles are functions performed in a system. However a role could be an attribute of a persona. There are many varieties of personas and some have found it useful to classify them in taxonomies (Peterson 2016 and Nielsen, 2014). We discuss the most common types; however, because many practitioners create mashups of common types, our analysis will focus on attributes.</p><p>As noted above, Alan Cooper is usually credited for the basic idea of personas. His persona was to be a fictional person, based on one or more real people using a tool. He argued that designers should target specific imaginary users rather than seeking to accommodate everyone. By doing so, the design might capture, say 80%, of the target audience without introducing the complexity resulting from addressing the needs of the other 20% (Cooper, 1999).</p><p>Kim Goodwin, a director in Cooper’s consulting practice, elaborated and refined Cooper’s concept of personas (Goodwin, 2018). In their scheme, personas are defined using observations and/or interviews. They include the following empirically identified attributes:</p><ul><li>Skills</li><li>Attitudes (possibly)</li><li>Environments</li><li>The course of daily activities</li><li>Goals</li></ul><p>In addition, they advocated adding a few fictional personal attributes in order to make the persona seem more realistic and thereby generate empathy with designers. Lene Nielsen’s (2014) personas are similar to Cooper’s and Goodwin’s but much more strongly emphasizes adding fictitious personal detail in order to achieve a strong sense of realism. In one example, she described a persona with more than 30 attributes, including not just the name, an image, education and place of employment but also how old the persona was when she married, her husband’s name, how frequently her adult children come to visit and why they visit (her cooking). In this very extensive persona bio, Nielsen also includes the persona’s attitudes about new technology (skeptical), a need for email receipt confirmation, confidence in her technical skills (low). She also describes her persona’s daily experiences and lists tasks involved in her job</p><p>Nielsen states that these details improve empathy for designers and reduce tendencies to stereotype users. She further claimed that behavioral attributes provided in personas fail to consider the whole person.</p><p>Another approach, pastiche personas, uses well-known fictional characters (e.g. Bart Simpson) to explore design issues (Blythe and Wright, 2006). Pastiche personas are discussed in the context of pastiche scenarios which are well known stories or settings (e.g. George Orwell’s 1984). The purported value of pastiche personas and scenarios is asserted to be their tendency to provoke lively design discussions. Whether or not they are intended to, the attributes of well-known characters implicitly influence the designer’s perspective of the persona. For example, Bart Simpson’s penchant for risk taking and causing trouble are attributes that are not separable from Bart Simpson as a persona.</p><p>Not all persona approaches stress the use of fictional attributes. For example, behavioral personas communicate what people do rather than who they are (Bartel, 2016). Defined by the activities that users engage in or the tasks they perform, behavioral personas can identify and describe behavior in terms of the function of a person in an organization or context (Bartel, 2016). Peterson (2016) sees behavioral personas as means of grouping people based on common goals, motivations and behavior patterns. Others define them in terms of dispositional attributes such as likelihood to ask for help in challenging situations (Mesibov, 2019). Ben-Menachem (2016) elaborates the dispositional approach and derives personas from patterns of values of bipolar attributes on semantic differential scales.</p><p>Many persona approaches include demographic data as the foundation for a persona description. These approaches rely on clusters of demographic attributes collected in interviews or surveys, and the demographic attributes tend to be persistent features of individuals such as age, gender, income, education, and so forth. This approach is similar to demographic market segmentation (e.g. Yanelovitch, 1964).<br> <br>Demographic persona attributes are assumed to correlate with usage or purchasing behavior. This approach also yields highly data-driven personas that, due to the nature of demographic data, are relatively unbiased by prior assumptions. Demographic attributes help describe the potential audience for a product, but demographic attributes alone do not provide adequate details for understanding the user’s challenges or develop designer empathy.</p><h3>Persona Attributes</h3><p>As persona approaches evolved, the types of attributes used to create them has grown. Once they consisted of a few research-based details with some fictional details to liven them up. Now, it is common to see personas include demographic data, behavioral data, and even some attitudinal descriptions to suggest how a person would react in scenarios. Are there benefits to adding various types of attributes to personas? For instance, do more persona attributes produce better discussion, less churn, and stronger designs? We suggest that they do not. More often, unnecessary attributes cause churn and distract from understanding the scenarios and context needed for design. We will review the types of attributes frequently added into personas and follow this with a discussion of problems commonly encountered with these persona attributes.</p><h4>Fictional Personal Attributes</h4><p>Most persona models include some attributes that are invented rather than identified empirically. These have at least three functions:</p><ul><li><strong>Identification</strong>: The name and an image of an avatar label it so that it is easily differentiated from other personas. This is essential when designs involve multiple personas.</li><li><strong>Memorability</strong>: The name and image also help make it easier to remember and recognize a persona. Other details facilitate storytelling. These narrative attributes (Lentz, 2019) can include personal details, activities and scenarios. Narrative formats themselves greatly enhance understanding and remembering (Bartlett, 1920; Bower and Clark, 1969).</li><li><strong>Empathy</strong>: perhaps the most often cited reason for including personal details is the generation of empathy. This is a complex topic that we will discuss in detail.</li></ul><p>The argument in favor of including fictional personal details in personas asserts that these details “bring the persona to life” (Goodwin, 2018). Essentially the claim is that the more real that personas appear, the better job the designer will do for them. While we agree that details that support story lines help us to identify, remember and understand user activities; however, we question the claim that fictional personal details generate empathy that is useful for design. We will address and discuss empathy more deeply below in the<em> Common Problems with Persona Attributes</em> section, below.</p><h4>Aspirational Attributes</h4><p>Aspirational persona attributes are qualities that describe an anticipated future user. These attributes are designed to address a limitation of data-driven personas. Data-driven personas are based on research with existing user experiences. These experiences were the result of a design created in the past that possibly was created in response to even earlier design experiences. Designers implicitly forecast how the legacy product user will experience the new product. They don’t always take into account how the users may have adapted to and are invested in the current experience. They may not accurately predict how the user will react to the new experience.</p><p>This should be a concern when the experience changes radically. For example, consider how useful research on the use of corded landline phones would have been in predicting the use of modern mobile smart phones. It seems unlikely that research on these tethered phones would have predicted that highly mobile phones would cause tens of thousands of deaths as a consequence of distracted driving.</p><p>Furthermore, when researching existing users, those users typically will discuss needs in terms of pain-points within the current experience. This cuts two ways. Although it helps to identify what needs to change, it also frames design problems in terms of legacy experiences. This can make it difficult to re-conceptualize designs and jobs, leaving alternative design paths unexplored. Some of these design paths may be far superior to the current design. Rather than focusing on the users that a product currently has, it is possible to define personas based on predicted users, jobs and even markets. A case in point is the “citizen developer” (e.g, Hinchcliffe, 2016) or “end-user developer” (e.g. Liberman, 2006).</p><p>The citizen developer persona came about because skilled programmers are expensive; traditional development cycles are slow; and products developed by nonusers often fail to satisfy all requirements. In theory, businesses would be more agile if users could create their own tools rather than levying requirements on trained software developers. These so-called citizen developers would be able to recognize the inefficiencies in their own work, and then create or modify their tools as needed. This is an old idea and many no- or low-code platforms have been brought to market to meet this need. In this case, the need was identified before the user type existed.</p><p>Aspirational persona attributes can be based on observations of existing usage but ultimately, they are forecasts. They might also be based on observations of people who aren’t currently using the type of products being designed. Aspirational persona attributes can be valuable because if successfully used, they can help to anticipate usage of radically different technologies. However, developing experiences for aspirational personas is far riskier than improving the experiences of existing users, as the expected market may not exist now or ever. The target user persona may be misidentified or forecast incorrectly. Google-glass is a commonly cited example of a product for a user who doesn’t exist (e.g. Morgan, 2019) or a product created for the wrong user (Levy, 2017). There are legions of examples of such mis-targeted products (Microsoft Bob, Apple Newton, the Edsel, etc.).</p><h4>Demographic Attributes</h4><p>Demographics are easy to collect in a survey or interview and the responses are easily coded and summarized. Researchers collect demographic attributes because they implicitly expect them to correlate with product experiences, usage or purchase.</p><p>Demographic attributes have been criticized by advocates of the Jobs to Be Done (JTBD) product design and marketing philosophy. Their objection boils down to two simple observations (e.g. Christensen et al. 2016):</p><ul><li>Correlations do not determine causation — my age, income, the brand of car I drive, and my marital status do not cause me to subscribe to one streaming service versus another.</li><li>Motivations determine causation — I purchase a product so that I can achieve a particular outcome. I will buy an electric drill with a built-in level so that it can help me drill a hole parallel to the ground.</li></ul><p>In addition, demographic attributes don’t appear to inform design in any but the most trivial of cases. We will concede that the design of the My Little Pony: Music Princess video game has likely been informed by awareness of prepubescent girls and the design of the modern Mini Cooper and second-generation VW Beetle were informed by awareness of nostalgic Baby Boomers. However, the design influences don’t go any further than particular aesthetic directions to attract a target market. They tend to be useless for the majority of product design scenarios.</p><h4>Role attributes</h4><p>In business enterprises, what a person does is mostly defined by their position, responsibilities or function. These are referred to as <em>roles.</em></p><p>Unfortunately, the term “role” has different connotations in product design and development. One refers to a behavioral mode. I can assume the role (mode) of writer when using a word processor but that does not mean I perform the role (organizational function) of technical writer. Unless qualified, we will use the term in the second sense, an organizational role.</p><p>In addition, roles can be fluid. People change roles during their career or within the life cycle of a single project. They aren’t fixed attributes. The work done by the role is more stable than the identity of the user and therefore should be more valuable for design activities</p><p>Organizational roles may have many different attributes such as job title, mission, knowledge, skills, collaborators, environmental aspects, activities, work intensity and stress, focused versus interrupt driven, degree of specialization, and other aspects of work inside of an organization (Adkissen, 2019; Canziba, 2018; Nielsen, 2014). An organizational role encompasses a set of responsibilities into a single functional identity. These responsibilities are activities that one or more persons perform. Therefore, an organizational role can be thought of as defining a group of behaviors.</p><p>Many organizational roles are well known and are highly consistent from one enterprise to another. Including the role in a persona effectively encapsulates a great deal of information about behavior, yet the role alone does not provide adequate detail of the actual work to be done and challenges experienced along the way. It is necessary to enumerate the responsibilities, activities and tasks performed by a persona with a specific organizational role as they relate to an experience being designed to provide adequate detail needed to support design activities.</p><h4>Goal attributes</h4><p>Many persona descriptions include one or more goals that the persona is assumed to have. “Goal” is also an overloaded term. A goal can be a personal goal (leave work on time, be promoted, buy a new car, etc.), a goal defined by the organization (complete the financial report on time), or the end-state of a particular activity, task or subtask (fill the car’s gas tank).<br> <br>Persona authors often list personal goals in their persona definition. These are likely specified in the service of empathetic design. However in enterprises, the harsh reality is that personal goals are at best secondary to organizational goals. Enterprises hire people with specific skills for roles or positions, assign them responsibilities and projects in order to support organizational goals. Enterprise goals and worker goals can be in opposition (the environmentalist working in the petrochemical industry) or consonant (the volunteer working in a soup kitchen). They often have nothing to do with each other. <br> <br> The products that the enterprise software designer designs exist to help employees achieve organizational goals. Moreover, employee users may sometimes influence purchases but ultimately their likes are subordinate to the goals of the organization. Often the decisions about which products are purchased are made by people who will never use them without even consulting the prospective users. Therefore, it is typically unreliable to list and treat personal goals as a driving factor of behavior and usage for a persona in an enterprise environment.</p><h4>Dispositional Attributes</h4><p>Dispositional Attributes of personas include traits such as attitudes that might influence the user’s relationship with the product. Examples include:</p><ul><li>Confidence (or lack thereof) in using new technology</li><li>Orientation toward detail</li><li>Conscientiousness</li><li>Privacy concerns</li><li>Security concerns</li><li>Motivation to learn</li></ul><p>Dispositional attributes are often vague, context-dependent and transitory. A user of a product will have very different attitudes when they are using it for the first time compared to when they become skilled at it. Highly-skilled users may even demonstrate positive attitudes toward a product that took them months to learn — a phenomenon that we should call the <em>Difficult Product Stockholm Syndrome</em>. A person may be confident about using some types of technology but intimidated by others. Additionally, many dispositional attributes, such as privacy concerns, security concerns, and motivation to learn, will often depend on the context of use. Other dispositional attributes are difficult to define and measure (e.g. detail-oriented and conscientiousness), and the inherent ambiguity within these dimensions leads to needless churn. In a few cases, attitudinal issues may be important — security or privacy concerns might call for specific design features; however, many soft attributes often create just noise without design implications.</p><h4>Universal Attributes</h4><p>Ostensibly, attributes are supposed to differentiate personas. However, some commonly listed attributes are more or less universal and consequently fail to differentiate. For example:</p><ul><li>Has more work than time</li><li>Dislikes reading documentation</li><li>Has invested time in learning how to accomplish tasks</li><li>Doesn’t like replacing a familiar experience with an unfamiliar experience</li><li>Dislikes repetitive tasks</li><li>Values privacy and security</li><li>Enjoys the feeling of closure upon completion</li><li>Enjoys explicit confirmation</li><li>Hates making mistakes</li><li>Hates losing data</li></ul><p>Ubiquity doesn’t mean that universal attributes have no place in design. They can be useful to remind designers about general user qualities. However, they probably belong in a different kind of supporting design artifact similar to a “user’s bill of rights” (e.g. O’Reilly, 2009).</p><h4>Work-related attributes</h4><p>Some attributes found in persona descriptions are not properties of people. They instead have to do with the work that people do. Work-related attributes are closely associated with organizational roles and goals. Roles determine the work and the work defines the goals.</p><p><strong>Motivational attributes of work:</strong> As noted above, the Jobs to Be Done (JTBD) approach arose as a reaction against the use of demographic personas and attributes in order to foster innovation in product concepts (Christensen, 2016; Ulwich 2016). Unlike persona advocates, the originators of JTBD hailed from business schools, product management and marketing. They were primarily concerned with what causes a person to buy a product or in their terminology, “the job the product was hired to do”. The JTBD approach is based on the realization that features of the person are frequently less important than the problems (or jobs) they are trying to solve.</p><p>This insight poses some critical questions for design. Can one really successfully and efficiently design a product without understanding what people will do with it and why? Or without deeply understanding the motivating problem and challenges to be solved by the product? Understanding strengths and weaknesses of current products with respect to the work being done is critical for finding opportunities to innovate.</p><p>Work-related attributes include the outcomes sought (i.e. goals), the context or situation in which the job takes place, and some notion of a bridging function between the situation and the outcome. Ulwich (2016) referred to the bridge between situations and outcomes as steps which are really no different from “activities”. Activity-centered design (Norman, 2008) aligns well with the notion of job steps.</p><p>The focus on outcomes and contexts is valuable because it de-emphasizes characteristics of the person and by doing so becomes less discriminatory and more inclusive. It’s important to stress that everyone doesn’t need to have the ability or desire to perform the same jobs.</p><p><strong>Constraining attributes of work: </strong>Some persona descriptions mention aspects of work that constrain or influence the persona’s behavior in some way or another. These may be inherent aspects of certain jobs or design challenges. Examples include:</p><ul><li>Locus of control — Does the person control the ordering and pace of the work that they perform or does the work drive the person?</li><li>Workload</li><li>Susceptibility to interruption</li><li>Skill requirements</li><li>Organizational Environment</li></ul><p>Some constraining attributes of work can be helpful in setting context and aligning stakeholders on the work being done. For example, understanding how the work is started and handed off to collaborators or how newer employees learn the work to be done can help designers to further understand the problem space.</p><h3>Common Problems with Persona Attributes</h3><h4>The empathy problem</h4><p>As noted previously, a claimed benefit of providing rich and detailed personas is the creation of empathy on the designer’s part. As designers create more empathy towards the potential user, they will construct better and more meaningful solutions to further improve their users’ lives. This assumed benefit warrants further discussion.</p><p>One problem with empathy is that the term is used, misused and confused without a careful consideration of what it means. First, empathy is often confused with <em>sympathy. </em>Empathy has to do with co-experiencing the mental state of another person. Sympathy has to do with an emotion felt when thinking about the circumstance, usually unpleasant, of another person. It is possible to feel sympathy for a person who nevertheless is perfectly content with their current situation.</p><p>Sympathy aside, psychologists and philosophers make distinctions between different kinds of empathy. Furthermore, they don’t often agree about how many kinds there are. Nevertheless, they often distinguish between affective and cognitive empathy. <em>Affective empathy </em>is the sharing of an <em>emotional</em> state — “I feel your pain”. <em>Cognitive empathy </em>is the experience of imagining another person’s state of mind (Stueber 2019). For example:</p><p><strong>Sympathy:</strong> I feel sorry for John because he has to use the product.</p><p><strong>Affective empathy</strong>: I <em>feel</em> John’s delight (or pain) when I see him using the product.</p><p><strong>Cognitive empathy:</strong> I imagine myself as John using the product.</p><p>Depending on how the designer or researcher interprets “empathy” very different outcomes might result. At a minimum, researchers, designers and stakeholders should understand what kind of empathy they seek to develop in their personas and the outcome they expect to achieve.</p><p>Those who believe that empathy leads to good design assert that when a designer reads personal details about a persona, she finds it easier to think empathically. Although these details about the persona may make it seem “real”, the extent to which a cartoon character with accompanying bullet points is capable of generating either affective or cognitive empathy in the same sense that a living breathing person can is questionable. Furthermore, even if they do, how is the empathy altered by whether those details are consonant or dissonant with those of the designer herself? The effect of similarity between empathizer and “empathizee” is an active topic of research in social psychology. Rather than wading into this tall grass here, it is sufficient to say that similarities and differences do have an effect on empathy created. Adding multiple details to personas only serves to muddy the waters.</p><p>Even if a persona allows a designer to assume the perspective of a user, this only begs the question of whether or not being empathetic produces better designs. For instance, Eyal, Steffel and Epley (2018) conducted a series of experiments to answer a similar question. They found that giving instructions to take the perspective of another person failed to improve predictions of emotions, opinions and preferences and were even a little worse than control participants who weren’t given these instructions. Moreover, this was true even when the target perspective was that of a significant other.</p><p>What <em>did</em> help was to ask participants to <em>get</em> the perspective of the other person before making predictions. This should be obvious. However, they also found no difference between perspective getters and takers in their confidence in their predictions. In other words, perspective-takers overestimated their ability to make predictions.</p><p>More empirical work is needed, but we know enough to question the assumed efficacy of emotional empathetic design. There is no evidence that it works and some evidence that it doesn’t. Adding rich detail to personas provides an opportunity to enliven the persona description but risks unknown influences from designer biases. On the other-hand, cognitive empathy, or understanding the experience of the user interacting with a product, may help the designer create a better experience. Understanding a user’s current experience in most cases will not require personal persona details.</p><h4>The average user problem</h4><p>Most approaches to persona creation assume that, at some point, research on potential users is conducted in order to base personas on real data. Persona attributes typically summarize the data by listing those that show up most frequently. This makes intuitive sense, but there are problems with this approach.</p><p>There is often an implicit assumption that it is best to design for an ‘average’ or ‘most common’ user. In reality, this person may not be representative because attributes may not covary with each other (Price, 2018). This approach also stereotypes users by ignoring their variability. When designers focus on stereotypical personas, they optimize designs for a few users while ignoring the natural variability. In effect, they create designs that discriminate. To avoid this, Price (2018) has argued for dispensing with individual personas and design for “persona spectrums” to accommodate variation.</p><p>That researchers would present models of “average” users is remarkable and not in a good way. It runs counter to inclusive approaches like accessible design and many principles accepted long ago in anthropometrics, ergonomics and human factors (Lentz, 2019). It is also a self-defeating market strategy. Why design for a smaller audience when you can have a larger one?</p><h4><strong>The attribute noise problem</strong></h4><p>Identifying and including many attributes in a persona is often assumed to enhance the predictive power of the persona. If we just collected data from a large number of potential users on a huge number of personal variables, we could predict with perfect accuracy how many people would choose one design over another. You might think of this as the big data theory of product design, where good design results from gathering more data. However, this more-is-better assumption has problems. As previously discussed, the assumption that persona attributes create useful cognitive empathy is questionable, and this remains true regardless of the number of attributes specified. Adding more attributes can create noise. In addition, selecting attributes for inclusion in a persona profile creates opportunities for injecting bias into the design.</p><p>Finally, although behavioral attributes may be more relevant for interactions with technology, their implications for design may be obscure. Dispositional attributes can be vague or more closely associated with personality traits than a user’s interaction needs. Universal attributes by definition don’t differ between personas and therefore are redundant and useless for persona differentiation.</p><p>To summarize, many attributes that often appear in persona descriptions don’t perform a useful function. Unfortunately, many persona authors assume that a large number of attributes in their personas demonstrates thoroughness. However, if those attributes don’t help the designer to design, then they are only distracting the design team. It forces designers to separate the design wheat from the persona chaff. It does not help the designer form the cognitive empathy required to understand what it is like to use the design.</p><h3><strong>A lean approach to personas</strong></h3><p>Many have recognized these problems and some have called for abandoning personas altogether. However, as much as we would like to kill them off, some of the details embedded in persona models can inform design. We just need to make personas more useful and usable. <br> <br>To do this we believe that personas must be simplified and reframed. Rather than being elaborate, richly researched proxies for actual human beings, personas should be viewed as concise artifacts that serve to define reliable associations between individuals, situations, goals, and activities. When these are framed in narrative scenarios, personas provide the cognitive empathy needed by designers to solve user problems.</p><p>A good persona model follows the rule that less is more. When a persona has minimal but targeted detail, it will facilitate communication between designers and stakeholders. The set of personas related to a design will be easy to remember and keep straight. With fewer features and nuances there should be fewer personas to manage, hopefully reducing the need for inflexible and bureaucratic persona libraries for large projects and enterprises.</p><p>Most importantly, these minimalistic personas will be <em>more inclusive </em>because they serve as stand-ins for a greater variety of people.<em> </em>They can be used to encourage designers to create experiences that are open to more users. They lend themselves to ad-hoc discussions and design explorations (e.g. “How can we design the course catalog to satisfy both lackadaisical and diligent students without adding additional complexity?”). They also support aspirational personas for products designed to rely less on skills and knowledge.</p><p>Our persona model is represented graphically in Figure 1, below. For us, a persona is an organizing mechanism referenced by an identity. It consists of a <strong>person </strong>and his or her <strong>jobs. </strong>For design,<strong> </strong>the jobs of interest are those facilitated by a <strong>product</strong> (tools or services). When situated in a business enterprise, it is often useful to also understand the <strong>organization</strong> that determines jobs and products. We will describe these objects in greater detail.</p><p><strong>Person: </strong>The person consists of an <em>identity</em> (name and optional image). Its most essential attributes are <em>responsibilities</em>, <em>abilities</em>, and <em>goals</em>. Responsibilities inform what jobs the person performs and abilities define prerequisite skills or knowledge for performing the jobs. Goals are objectives derived from responsibilities.</p><p>This model acknowledges that people have personal attributes, however, they are not related to the jobs performed and therefore need not be described. Universal attributes that are common to all potential product users include, for instance, perceptual abilities, reaction times, intolerance for slow system response times, feelings of closure upon task completion and so forth. These attributes are sometimes critically important; however, because they do not distinguish between personas they may be treated as supporting information to a set of personas.</p><p><strong>Job: </strong>A job reflects the work done in the conduct of the person’s responsibilities. We believe that understanding and communicating jobs is more critical than understanding many other additional details about personas. We use the term “job” here in the same way that JTBD advocates do. A job encapsulates the goals (outcomes) that arise in various contexts (situations) and the activities performed to realize those goals (Ulwick, 2016).</p><p>Coincidentally, job situations, activities and outcomes map directly onto the structure of a user story or narrative. A story consists of a situation, action, and resolution. In job terms, the situation is the setting, the activities are the action, and the outcome is the resolution. Stories are a natural, efficient, memorable, and empathetic communication method in design, and as a result, we see these as an important part of a lean persona.</p><p>The narratives of as-is and to-be experiences are so important that the story can be used to define the persona rather than the other way around. The story should guide the selection of the important attributes to include in communicating the persona.</p><p>Jared Spool (2018) demonstrated how well-written scenarios (i.e. stories) can convey the context for the work, the type of work, and the challenges that arise — an efficient way to communicate essential design problems while building cognitive empathy in designers. All of this can be achieved with little more than the name of the persona.</p><p>In Spool’s stories, details are provided in an introductory paragraph or two. For example, in an air travel check-in scenario, he introduces his persona as traveling with an infant and a mobility-challenged elder relative. This defines part of the situational context in a way that stakeholders can easily imagine and empathize with the various demands placed on the traveler as he checks in. Note that the important aspects of empathy here are cognitive rather than emotional. The fact that the traveler’s attention is divided has serious design implications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/913/1*tQKjEl5JKsRF_CIDx5xE3w.png" /><figcaption><strong>Figure 1. Conceptual model of personas and design context</strong></figcaption></figure><p><strong>Product: </strong>The product is the thing being designed — a tool or service. It exists to help the persona accomplish her jobs. In an enterprise context, the product helps the persona satisfy organizational and individual jobs. In scenarios outside of work, the product still enables the person to satisfy their jobs, with the subtle difference of the jobs not being defined by the organization and instead the individual person.</p><p><strong>Organization: </strong>The organizational layer is specific to products designed for business enterprises and can be dispensed with when designing consumer products. It defines the social context that the work is performed within. Enterprises have objectives. For business enterprises these include profits, return on investments, market share and so forth. Non-profit enterprises also have objectives, usually dealing with some form of social good.</p><p>Organizational objectives are achieved by organizational jobs. Organizational jobs have requirements that define completion or success criteria, and these jobs are performed by organizational roles (CEO, marketing director and so forth). Describing the requirements for the organization jobs as part of the persona narrative is useful to ensure designers fully understand the nature of the work and success criteria of the organization.</p><h3>Conclusion</h3><p>Since their inception, personas have developed in different directions. One commonality in their maturation is the inclusion of many different types of attributes to describe and enliven the persona. Whether personal, demographic, or aspirational, for instance, the attributes added to personas were thought to provide additional necessary detail to better understand the person being designed for and build empathy for this person. We suggest that these details do not create the cognitive empathy desired on the part of designers nor do they create a deeper understanding of the user and their abilities, goals, and jobs. Some attributes, like fictional attributes, occasionally work against building a deeper understanding of users and their abilities.</p><p>We offer a leaner approach to personas that moves away from the traditional persona model that calls out various demographic data and personal characteristics to describe potential users. We instead encourage building a narrative-based scenario that describes the person in reference to their responsibilities, abilities, and goals.<br> <br> Personas can be documented by first providing an introductory narrative description of the person, then the person’s jobs that they are performing, the product (tool or service) that assists in performing the jobs, and when operating in a business enterprise, some aspects of the organization that influence the job. When designing outside of a business context, including environmental details that influence the job can also be beneficial for setting context in the narrative.</p><p>Presenting the jobs in narrative form increases effectiveness of presentation and cognitive empathy. Notably including details of when (the situation) the persona works (the activity) so that a result (the outcome) occurs starts to unify this persona approach with the JTBD framework.</p><p>This approach builds a persona that provides a much more useful description of a person, their work to be done, and the context in which the work is done. Using a narrative to construct the persona also naturally builds cognitive empathy for designers through the use of storytelling to set context and provide details. When a persona is involved in more than one scenario in a design effort, the same introductory paragraph of the persona can be reused where applicable, although the details in the narrative that describe the job and related outcomes would differ. This eliminates the need for personas as separate design artifacts that list personal attributes and demographics, by instead describing the person as part of a set of user stories that set context, communicate the problems, and build cognitive empathy.</p><h3>References</h3><p>Adkisson, H. (2019, October 5). Creating Role-Based Personas for the Enterprise. <em>Medium</em>. <a href="https://medium.com/@hpadkisson/creating-role-based-personas-for-the-enterprise-6471e7060d82">https://medium.com/@hpadkisson/creating-role-based-personas-for-the-enterprise-6471e7060d82</a></p><p>Bartel, D. (2016, August 9). Do you know your Users? Introducing Behavioral Personas. <em>Medium</em>. <a href="https://medium.com/@taaminsights/do-you-now-your-users-introducing-behavioral-personas-8668f56b97d8">https://medium.com/@taaminsights/do-you-now-your-users-introducing-behavioral-personas-8668f56b97d8</a></p><p>Bartlett, F.C. (1920) Some Experiments on the Reproduction of Folk-Stories, <em>Folk-Lore</em>, 31: 30–47. <a href="http://www.bartlett.psychol.cam.ac.uk/SomeExperimentsOn.htm">http://www.bartlett.psychol.cam.ac.uk/SomeExperimentsOn.htm</a></p><p>Blythe, M., &amp; Wright, P. C. (2006). Pastiche scenarios: Fiction as a resource for user-centered design. <em>Interacting with Computers</em>, <em>18</em>(5), 1139–1164. <a href="https://doi.org/10.1016/j.intcom.2006.02.001">https://doi.org/10.1016/j.intcom.2006.02.001</a></p><p>Browne, J., Manning, H., Dorsey, M., Drego, V. L., Beckers, A., &amp; Catino, S. (2009). <em>Assumption Personas Help Overcome Hurdles To Using Research-Based Design Personas</em>. Forrester. <a href="https://www.forrester.com/report/Assumption+Personas+Help+Overcome+Hurdles+To+Using+ResearchBased+Design+Personas/-/E-RES53874">https://www.forrester.com/report/Assumption+Personas+Help+Overcome+Hurdles+To+Using+ResearchBased+Design+Personas/-/E-RES53874</a></p><p>Bower, G.H. &amp; Clark, M.C. (1969). Narrative stories as mediators for serial learning. Psychonomic Science, 14(4), 181–182.</p><p>Canziba, E. (2018). <em>Hands-On UX Design for Developers: Design, prototype, and implement compelling user experiences from scratch</em>. Packt.</p><p>Christensen, C. M., Hall, T., Dillon, K., &amp; Duncan, D. S. (2016, September 1). Know Your Customers’ “Jobs to Be Done.” <em>Harvard Business Review</em>, <em>September 2016</em>. <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">https://hbr.org/2016/09/know-your-customers-jobs-to-be-done</a></p><p>Cooper, A. (1999). <em>The Inmates Are Running the Asylum</em> (1st ed.). Macmillan Publishing Co., Inc.</p><p>de Haaff, B. (2017, December 6). How Product Managers Quickly Define Customer Personas. <em>HuffPost</em>. <a href="https://www.huffpost.com/entry/how-product-managers-quic_b_10530850">https://www.huffpost.com/entry/how-product-managers-quic_b_10530850</a></p><p>Eyal, T., Steffel, M., &amp; Epley, N. (2018, October 9). Research: Perspective-Taking Doesn’t Help You Understand What Others Want. <em>Harvard Business Review</em>. <a href="https://hbr.org/2018/10/research-perspective-taking-doesnt-help-you-understand-what-others-want">https://hbr.org/2018/10/research-perspective-taking-doesnt-help-you-understand-what-others-want</a></p><p>Goodwin, K. (2018, September 27). Getting from Research to Personas: Harnessing the Power of Data. <em>UX Articles by UIE</em>. <a href="https://articles.uie.com/research_to_personas/">https://articles.uie.com/research_to_personas/</a></p><p>Hinchcliffe, D. (2016, April 18). The advent of the citizen developer. <em>ZDNet</em>. <a href="https://www.zdnet.com/article/the-advent-of-the-citizen-developer/">https://www.zdnet.com/article/the-advent-of-the-citizen-developer/</a></p><p>Nielse, L. (2014). <em>Personas</em> (2nd ed.). Interaction Design Foundation. <a href="https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/personas">https://www.interaction-design.org/literature/book/the-encyclopedia-of-human-computer-interaction-2nd-ed/personas</a></p><p>Lentz, J. (2019, April 25). <em>Should you design for People, Personas, Activities or Jobs?</em> <a href="https://medium.com/@jimlentz/should-you-design-for-people-persons-activities-or-jobs-652d5e396e6d">https://medium.com/@jimlentz/should-you-design-for-people-persons-activities-or-jobs-652d5e396e6d</a></p><p>Levy, S. (2017, July 18). Google Glass 2.0 Is a Startling Second Act. <em>Wired</em>. <a href="https://www.wired.com/story/google-glass-2-is-here/">https://www.wired.com/story/google-glass-2-is-here/</a></p><p>Liberman, H., Paternò, F., Klann, M., &amp; Wulf, V. (2006). End User Development: An Emerging Paradigm. In <em>End User Development</em> (Vol. 9, pp. 1–8). Springer.</p><p>Massanari, A. L. (2010). Designing for imaginary friends: Information architecture, personas and the politics of user-centered design. <em>New Media &amp; Society</em>, <em>12</em>(3), 401–416. <a href="https://doi.org/10.1177/1461444809346722">https://doi.org/10.1177/1461444809346722</a></p><p>Morgan, B. (2019, September 9). 10 Recent Product Design Failures And What We Can Learn From Them. <em>Forbes</em>. <a href="https://www.forbes.com/sites/blakemorgan/2019/09/09/10-recent-product-design-failures-and-what-we-can-learn-from-them/">https://www.forbes.com/sites/blakemorgan/2019/09/09/10-recent-product-design-failures-and-what-we-can-learn-from-them/</a></p><p>Norman, D. (2008, November 17). Ad-Hoc Personas &amp; Empathetic Focus. <em>Jnd.Org</em>. <a href="https://jnd.org/ad-hoc_personas_empathetic_focus/">https://jnd.org/ad-hoc_personas_empathetic_focus/</a></p><p>Norman, D. (2005, July-August). User centered design considered harmful. <em>Interactions. <br> </em><a href="https://dl.acm.org/doi/10.1145/1070960.1070976">https://dl.acm.org/doi/10.1145/1070960.1070976</a></p><p>O’Reilly, D. (2009, December 29). Time to update the software user’s bill of rights. <em>CNET</em>. <a href="https://www.cnet.com/news/time-to-update-the-software-users-bill-of-rights/">https://www.cnet.com/news/time-to-update-the-software-users-bill-of-rights/</a></p><p>Owens, S. (2017, March 30). Design Personas vs Marketing Personas: They. Are. Different! <em>Medium</em>. <a href="https://medium.theuxblog.com/design-personas-vs-marketing-personas-they-are-different-2724992acc78">https://medium.theuxblog.com/design-personas-vs-marketing-personas-they-are-different-2724992acc78</a></p><p>Peterson, M. (2016, October 10). The Problem with Personas. <em>Medium</em>. <a href="https://blog.prototypr.io/the-problem-with-personas-82eb57802114">https://blog.prototypr.io/the-problem-with-personas-82eb57802114</a></p><p>Price, M. (2020, April 9). Kill Your Personas. <em>Medium</em>. <a href="https://medium.com/microsoft-design/kill-your-personas-1c332d4908cc">https://medium.com/microsoft-design/kill-your-personas-1c332d4908cc</a></p><p>Spool, J. (2018, September 11). When It Comes To Personas, The Real Value Is In The<br> Scenarios. <em>UX Articles by UIE</em>. <a href="https://articles.uie.com/when-it-comes-to-personas-the-real-value-is-in-the-scenarios/">https://articles.uie.com/when-it-comes-to-personas-the-real-value-is-in-the-scenarios/</a></p><p>Stueber, K. (2008). Empathy. In <em>Standford Encyclopedia of Philosophy</em> (Fall 2019). <a href="https://plato.stanford.edu/archives/fall2019/entries/empathy/">https://plato.stanford.edu/archives/fall2019/entries/empathy/</a></p><p>Thellwell, C. (2017, April 12). <em>Are personas ruining your product?</em> <a href="https://www.invisionapp.com/inside-design/personas/">https://www.invisionapp.com/inside-design/personas/</a></p><p>Ulwick, A. (2016). <em>Jobs-to-be-Done</em>. Idea Bite Press. <a href="http://jobs-to-be-done-book.com/">http://jobs-to-be-done-book.com/</a></p><p>Yankelovich, D. (1964, March 1). New Criteria for Market Segmentation. <em>Harvard Business Review</em>, <em>March 1964</em>. <a href="https://hbr.org/1964/03/new-criteria-for-market-segmentation">https://hbr.org/1964/03/new-criteria-for-market-segmentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5242ec36b671" width="1" height="1" alt=""><hr><p><a href="https://medium.com/consilient-design/personas-reconsidered-5242ec36b671">Personas - Reconsidered</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>