<?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 Paul McInerney on Medium]]></title>
        <description><![CDATA[Stories by Paul McInerney on Medium]]></description>
        <link>https://medium.com/@paulmci?source=rss-e1a8cd77495e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ayx_tLKxSPM27vD1b0FHdg.jpeg</url>
            <title>Stories by Paul McInerney on Medium</title>
            <link>https://medium.com/@paulmci?source=rss-e1a8cd77495e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:28:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulmci/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[UX in the 1990s: Amusing stories from unsung pioneers]]></title>
            <link>https://uxdesign.cc/ux-in-the-1990s-amusing-stories-from-unsung-pioneers-aab8604355db?source=rss-e1a8cd77495e------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab8604355db</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Paul McInerney]]></dc:creator>
            <pubDate>Thu, 26 May 2022 10:31:03 GMT</pubDate>
            <atom:updated>2022-06-02T12:20:13.345Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Including UX as an integral part of a project is a mainstream practice today, but that was not always so.</em></h4><figure><img alt="A scene depicting pioneers in the American west. A horse-drawn wagon on a dirt trail." src="https://cdn-images-1.medium.com/max/1024/0*ciW6ILICIU27ZeEF" /><figcaption>Photo by <a href="https://unsplash.com/@scarlettweiss?utm_source=medium&amp;utm_medium=referral">Josie Weiss</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>By the end of the 1990s, the conceptual foundations of UX were well established. Thought leaders at UX HQ like Don Norman had defined many of the aims, concepts, and methods of this field. But in business project teams, awareness of UX was … er … <em>uneven, </em>and the task of evangelizing UX fell to many uncredited pioneers. Part of their legacy is amusing stories, some which are compiled here.</p><p>Whether you were one of these pioneers, or whether you joined the field more recently, these stories provide the opportunity to reflect on where we’ve come from, and where our field might be headed.</p><h3>I guess I’ll call this a win</h3><p>Delivering a great user experience (or even an adequate one) was not a widely accepted goal of project teams in the 1990s. Projects focused instead on delivering more functionality with the latest technology, and this was seen as equivalent to delivering a great UX. So, UX pioneers often gained lots of experience being assertive and wily advocates for aims and methods of UX. In that culture, it was important to cherish each small win to maintain morale.</p><blockquote>I was working for a company where programming priorities usually trumped UX considerations — a typical culture for the time. But on one occasion I was able to use this to my advantage.</blockquote><blockquote>One day an executive asked me to join his key project to leverage my programming skills. This was an offer I did not wish to accept. So, knowing he would refuse, I said disingenuously, “Fine, but only if I get a healthy budget for UX design, and carte blanche for how to use it.”</blockquote><blockquote>After a moment of consideration he said, “Deal”. So… I guess I’d call this a win?</blockquote><blockquote>As the first usability specialist on a project, I usually encountered a fair amount of pushback. But people eventually came around, at least to some degree.</blockquote><blockquote>However, one technical lead was exceptionally obstructive. He would not make any allowance for any UX activity in his project plan and would reject any usability input.</blockquote><blockquote>After the final project meeting, he came up to me and said something out of character: With the benefit of hindsight, he now saw the value of what I was advocating for, apologized, and vowed to be more receptive to usability and UX in his next project.</blockquote><p><strong>Questions for reflection</strong></p><p>While there’s more acceptance of UX today, UX leads still need to champion UX as a project goal and priority.</p><ul><li>What is the right balance between improving the UX and adding more functionality in a project’s priorities and resource allocation?</li><li>How can UX success be articulated in project goals and metrics?</li><li>Making UX a priority often hinges on the support of a key decision maker like an executive project sponsor or technical lead. How can these people be won over?</li></ul><h3>Agile UX — 90s style</h3><p>In the 1990s, when an organization got onboard with the idea of UX, a common next step was hiring some UX staff and setting them loose to “do UX.” These UX pioneers were faced with working out the logistical details of adapting to, or changing, project practices to create a space for “doing UX”. While most pioneers faced a tough trail, some had the good fortune to co-create practices that would still be considered exemplary today.</p><blockquote>I once worked on a project team that was exemplary in how it integrated UX and Agile practices — but this was in 1993! (about 10 years before most people had even heard the term “Agile.”)</blockquote><blockquote>The full team of six people met every Monday to plan the goals for the week, then we met each morning to coordinate our work for that day. I was the UX designer but many others contributed to the design, and I contributed to other other activities like writing QA test cases. Since then, I’ve worked on many Agile teams — some as good, but none better.</blockquote><blockquote>In the early 1990s, I worked in a usability lab that scheduled a full day of usability sessions for a single project. When it was a project team’s “day at the usability lab”, we required the attendance of every project role — product manager, developer, writer, business sponsor — you name it. (There was no “UX designer” role in our company back then).</blockquote><blockquote>During the lunch break, the team would revise their prototype based on what they learned in the morning sessions, and test their revised design in the afternoon. It doesn’t get much more Agile than that.”</blockquote><p><strong>Questions for reflection</strong></p><p>Today, there’s much published guidance available on fitting UX into a project’s work practices. But UX leads still need to iron out the details to address the unique circumstances of each project team.</p><ul><li>What is the right balance between changing team practices to accommodate UX practices vs. adapting UX practices to fit the existing team practices?</li><li>Some project teams have low-quality Agile practices which poses a limiting factor on UX success. To what extent should UX leads expend effort on improving overall project practices vs. focusing on better adoption of UX?</li></ul><h3>“Move fast and break things” reconsidered</h3><p>In the 1990s, when UXers were not busy evangelizing to executives or integrating with project teams, they got out of the office to speak with users. UX textbooks had led UXers to believe that users would greet them with open arms. But this was not always the case, as these stories show:</p><blockquote>I was given access to some back office staff to interview for a project to enhance an internal system they used. There’s one user interview I still remember decades later. A fire plug of a woman sits down for the interview and says, <em>“My boss told me to come to this meeting, but he didn’t say what it was about.”</em></blockquote><blockquote>Earnestly, I explained that we wanted her input on some enhancements to the software she used. Then she said, <em>“My input is that I don’t want you to change anything. Every time you people change our system, we can no longer do our work the way we’re used to. So, that’s my input: don’t change the system.”</em></blockquote><blockquote>Then she stood up and left the room.</blockquote><blockquote>I was working on a project for the Air Force of a certain European country to modernize a staff management reporting system. When I sought access to the intended users, I was repeatedly stymied. Eventually, someone took me aside to explain the reason.</blockquote><blockquote>The existing process was mind bogglingly inefficient for a good reason: it provided jobs for lots of people doing their mandatory National Service. These people had lucked into this office role that avoided the typical experience of marching in the mud and being yelled at by NCOs. Their primary goal was to get to complete their two-year commitment without jeopardizing their position.</blockquote><p><strong>Questions for reflection</strong></p><p>While the details of these stories might be dated, their lesson is not: People don’t appreciate having their ways of working “disrupted” by technologists.</p><ul><li>When generating and evaluating “big ideas” for improving the current state, do UXers adequately consider possible negative reactions to change?</li><li>When conducting user research, do UXers give adequate attention to understanding how the new UX will require the user to adapt, and how they feel about that?</li></ul><h3>Conclusion</h3><p>In the 1990s, the conceptual foundations of the UX discipline were well established, but innovation and stamina were still required to achieve their adoption in the field. This work fell to countless uncredited pioneers in many companies, some of whose stories have been shared here.</p><p>This pioneering work involved several constituencies:</p><ul><li>Project sponsors and leaders: To align on the aims and priority of UX.</li><li>Project team members: To determine how to integrate UX activities into day-to-day project work.</li><li>Users: To remind ourselves that we’re designing for real people who might have mixed feelings about having their current experience “improved.”</li></ul><p>How are things compared to the 1990s? Certainly, today’s typical project team is more enlightened. However, as the saying goes, the future does not arrive everywhere at the same time. In the early 1990s, one could find teams with UX practices that were just as enlightened as the best teams of today. Conversely, today there remain teams that seem still stuck in the 1990s. So there’s still more pioneering work to be done.</p><p><strong>Share your stories! </strong>There’s lots more great stories from the 1990s. Share yours in the comments.</p><h3><strong>Resources</strong></h3><p>To learn more about the origins and history of the UX field, here are some suggested resources:</p><p><a href="https://www.nngroup.com/articles/100-years-ux/">A 100-Year View of User Experience (Jakob Nielsen)</a></p><p><a href="https://www.nngroup.com/videos/don-norman-term-ux/">Don Norman on the term “UX” (Don Norman)</a></p><p><a href="https://uxplanet.org/the-evolution-of-ux-process-methodology-47f52557178b">The Evolution of UX Process Methodology (Ian Armstrong)</a></p><p><a href="https://measuringu.com/usability-history/">A Brief History of Usability (Jeff Sauro)</a></p><p><a href="https://medium.com/user-experience-design-1/classic-ux-book-from-the-1980s-ed4151a166ab">Classic UX Books from the 1980s (Paul McInerney)</a></p><p><a href="https://uxpamagazine.org/want-to-understand-the-future-of-hci/">From Tool to Partner: The Evolution of Human-Computer Interaction (Jonathan Grudin)</a></p><h3><strong>Thanks!</strong></h3><p>Several people contributed their stories for this article. Thanks to Matthew Laurence, Franca Ferrara, Carl Zetie, John Schrag, and others who wish to remain out of the limelight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab8604355db" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/ux-in-the-1990s-amusing-stories-from-unsung-pioneers-aab8604355db">UX in the 1990s: Amusing stories from unsung pioneers</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Classic UX books from the 1980s]]></title>
            <link>https://uxdesign.cc/classic-ux-book-from-the-1980s-ed4151a166ab?source=rss-e1a8cd77495e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed4151a166ab</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[t]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Paul McInerney]]></dc:creator>
            <pubDate>Mon, 03 May 2021 11:20:07 GMT</pubDate>
            <atom:updated>2022-06-04T12:41:59.151Z</atom:updated>
            <content:encoded><![CDATA[<h4>Michael Jackson, Prince, Sade, and New Order — these artists released some of the classic albums in the 1980s. But what were the classic UX books of the ‘80s?</h4><figure><img alt="A grayscale sketch of the Thriller album cover modified to show Michael Jackson reading a book with the title UX." src="https://cdn-images-1.medium.com/max/791/1*-KWbCYblemY-_we-LTI1sg.png" /><figcaption>Image credit: Arden Mason-Ourique</figcaption></figure><p><strong>Welcome to yet another “best UX books’’ list, but with a twist. </strong>This compilation revisits the best books from one decade, the 1980s. If you were there, you can take a stroll down memory lane — or get apoplectic if your fav book was overlooked. If you joined the UX field later, you can get a taste of the latest-greatest ideas from that era, and see which ones are still around.</p><p>Of course, the term <em>UX </em>had not yet been coined, and the field was more commonly known as <em>human-computer interaction (HCI)</em> and <em>user-centered design (UCD), </em>which are terms featured in many of the classic books we’ll cover.</p><h3>Timeless classics</h3><p>Classics in this category are still being read today (with only minor updates). So, these titles are likely familiar to the latest generation of UX designers.</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/318/1*5nzxmSUZQMXqM6HDIwMSnQ.jpeg" /></figure><p><strong>The Visual Display of Quantitative Information</strong> (Edward Tufte,1983) covers what is known today as “data viz”. While the author was not specifically addressing software UX, this book had a deep impact on people working in the field at the time. This book fused functional communication principles with the pursuit of aesthetic goals. As one reviewer put it, this book is both a masterpiece <strong><em>about </em></strong>design and is itself a masterpiece <strong><em>of </em></strong>design.</p><p>[For more info: <a href="https://www.edwardtufte.com/tufte/books_vdqi">Book/Author site</a> | <a href="https://jeffhale.medium.com/five-takeaways-from-the-visual-display-of-quantitative-information-dd36dae35299">Recent review article (Jeff Hale, 2018)</a>]</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/255/1*IkI0PIvrSZi6CDSKX5_7fA.jpeg" /></figure><p>What can cognitive psychology tell us about designing a door knob or light switch that is easy to use? Quite a bit, actually. <strong>The Psychology of Everyday Things </strong>(Donald Norman, 1988) was a bestseller that introduced usability and user-centered design to the general public. You might recognize the author’s name; he appears elsewhere in this list, and remains a thought leader today. If the title seems a bit off, it’s because the book was later re-published with its more familiar title, <strong>The Design of Everyday Things</strong>. This book is still reaching new audiences — even my teenage son has heard of this book, albeit from watching a YouTube video.</p><p>[For more info: <a href="https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things">Wikipedia</a> | <a href="https://www.nngroup.com/books/design-everyday-things-revised/">Author discussing the revised edition</a>]</p><h3>Seminal classics</h3><p>Classics in this category were first-of-a-kinds that evolved through several editions up to the present day. And they provided a template for later authors.</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/274/1*nPfzwN1Wd3Cf4aLByLMVuw.jpeg" /></figure><p>A milestone in any new field is the appearance of the first widely used textbook. <strong>Designing the User Interface: Strategies for Effective Human-Computer Interaction </strong>(Ben Shneiderman, 1987) is still going strong — the 6th edition was released in 2016. In the original edition, many chapters addressed the technology of the time, including menu selection, system messages, and printed manuals. Other topics have persisted to the current edition, including direct manipulation and devices.</p><p>[For more info: <a href="http://www.cs.umd.edu/hcil/DTUI6/">Latest edition book site</a> ]</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/335/1*9_cGkshqphew_HrcDJXGbA.jpeg" /></figure><p>As the first OS style guide, <strong>Human Interface Guidelines: The Apple Desktop Interface </strong>(Apple Computer, 1987) provided the template for the many style guides that followed, which evolved into today’s design systems. Apple has been updating this book for over 30 years, and traces of the original edition are still apparent. As befits a style guide, the writing is clear and accessible to the general developer audience, and the book is attractively produced.</p><p>[For more info: <a href="https://blog.prototypr.io/rediscovering-apples-human-interface-guidelines-1987-59731376b39e">Recent review article (Bryant Hodson, 2016)</a> | <a href="https://developer.apple.com/design/human-interface-guidelines/">Latest edition</a> ]</p><h3>More of what was big in the ‘80s</h3><p>Classics in this category had a major impact in their day and illustrate three different ways the field’s pioneers sought to document the rapidly evolving state of the art.</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/269/1*7_EcW3uMychPJWJLGeuRmA.jpeg" /></figure><p>If you were a UX expert in academia or industry in the 1980s, you joined working groups, travelled to symposia, and generally had a good time comparing notes with your peers. Afterwards, you would publish a book to let everyone else know what you talked about. These efforts often tried to cover the entire field, unlike today’s more specialized efforts. One notable result is <strong>User Centered System Design: New Perspectives on Human-Computer Interaction</strong> (Edited by D. Norman and S. Draper, 1986). This proceedings includes 22 chapters, some with amusing titles like <em>There’s More to Interaction Than Meets the Eye: Some Issues in Manual Input </em>and <em>Answers First, Then Questions</em>. The editors point out that this book is not a how-to guide, but rather speculative and introspective essays intended to formulate new ways of thinking about the field.</p><p>[For more info: <a href="https://www.semanticscholar.org/paper/User-Centered-System-Design%3A-New-Perspectives-on-Norman-Draper/2beae13d1039414ef166f2a14f32e17eca0f581c">Semantic Scholar entry</a> ]</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/949/1*qOeqVu6Ck3eIbGVyFovGew.png" /></figure><p>The 1980s witnessed some heroic efforts to capture everything worth knowing about the field. Apparently, that was a lot. <strong>Readings in Human-Computer Interaction: A Multidisciplinary Approach </strong>(Edited by R. Baecker and W. Buxton, 1987)<strong> </strong>weighs in at 714 pages, and for readers wanting even more, it includes a guide to further reading. <strong>Handbook of Human-Computer Interaction </strong>(Edited by M. Helander, 1988) is also no lightweight,<strong> </strong>with 52 chapters and over 1100 pages. These books show how deep and broad the field was at that early stage. Both publications have since been updated and are even longer.</p><p>[For more info on Readings in Human-Computer Interaction: <a href="https://www.semanticscholar.org/paper/Readings-in-human-computer-interaction-%3A-a-approach-Baecker-Buxton/6bd10cf5498eed6cdd075368ee48eedd7faa4b2b">Semantic Scholar</a> | <a href="https://www.sciencedirect.com/book/9780080515748/readings-in-human-computer-interaction#book-info">Publisher entry to later edition</a> ]</p><p>[For more info on of Human-Computer Interaction: <a href="http://hcibib.org/search:bookmark=E.Helander.88">HCI Bib </a>| <a href="https://books.google.ca/books?hl=en&amp;lr=&amp;id=6vnSAwAAQBAJ">Google Books</a> | <a href="https://www.semanticscholar.org/paper/Handbook-of-Human-Computer-Interaction-Helander-Landauer/8da0a40bd5386c885ea5df7384cf3e28c1b328cc">Semantic Scholar entry for the second edition (1997)</a> ]</p><figure><img alt="A photo of the book which is discussed next." src="https://cdn-images-1.medium.com/max/827/1*pyg2mWmWpex1cc9fXTByuw.png" /></figure><p>The third, and final, type of book we’ll look at painstakingly codifies prescriptive guidance on myriad design details. Guidelines were such a common approach to writing about design that there was even a conference paper entitled <em>Guidelines for Designing Design Guidelines.</em> These books were a response to the fact that many UIs were being designed by developers — people with sometimes neither the training nor inclination to deliver a great user experience. So, guidance had to be spelled out in excruciating detail.</p><p><strong>Handbook of Screen Format Design </strong>(W.O. Galitz, 1985)<strong> </strong>approached the topic by covering different types of screens in turn, including data entry, inquiry, and menu screens. This author went on to write several more books in the subsequent decade including the amusingly named <em>It’s Time to Clean Your Windows: Designing GUIs That Work. </em>Another stand-out from the 1980s, <strong>Human-Computer Interface Design Guidelines </strong>(M. Brown, 1988), covered similar ground along with some bonus content: guidance on implementation and a checklist for auditing designs for compliance with the guidelines.</p><p>[For more info on Handbook of Screen Format Design: <a href="https://books.google.ca/books/about/Handbook_of_Screen_Format_Design.html?id=X5t9AAAAIAAJ">Google Books</a> ]</p><p>[For more info on Human-Computer Interface Design Guidelines: <a href="http://hcibib.org/search:bookmark=B.Brown.88">Google Books</a> ]</p><p>In the 1980s, people were busy writing and reading books on UX. However, today, books compete for attention in a crowded media marketplace. In fact, I have it on good authority (my teenage son), that nobody under 30 reads books anymore. Be that as it may, if you ever feel like reading a good UX book, consider one of these classics from the 1980s. Or if you want to dig deeper, see the appendix for even more classics from the 1980s.</p><h3>Appendix: More classic UX books from the 1980s</h3><ul><li><strong>1980</strong> | Software Psychology: Human Factors in Computer and Information Systems | Shneiderman</li><li><strong>1983 </strong>| Online Help: Design and Evaluation | Duffy, Thomas, Palmer, Mehlenbacher</li><li><strong>1983</strong> | The Psychology of Human-Computer Interaction | Card, Moran, Newell</li><li><strong>1983</strong> | The Psychology of Computer Use | Green, Payne, van der Veer (Eds)</li><li><strong>1983 </strong>| Human Error in Computer Systems | Bailey</li><li><strong>1984</strong> | Human Factors in Computer Systems | Thomas, Schneider (Eds)</li><li><strong>1985 </strong>| Computer Usability Testing and Evaluation | Spencer</li><li><strong>1985 </strong>| Advances in Human-Computer Interaction | Hartson (Ed)</li><li><strong>1986 </strong>| Understanding Computers and Cognition | Winograd, Flores</li><li><strong>1987 </strong>| Interfacing Thought: Cognitive Aspects of Human-Computer Interaction | Carroll (Ed)</li><li><strong>1987 </strong>| Plans and Situated Actions: The Problem of Human-Computer Communication | Suchman</li><li><strong>1988 </strong>| Designing User Interfaces for Software | Dumas</li><li><strong>1989 </strong>| Computer-Supported Cooperative Work: A Book of Readings | Greif (Ed)</li><li><strong>1989 </strong>| Task Analysis for Human-Computer Interaction | Diaper</li></ul><h3>Thanks</h3><p>For their encouragement and help in this quixotic venture, thanks to: Chauncey Wilson, Laura Teich, Ian McInerney, Ilona Posner, and all the volunteers who compiled <a href="http://hcibib.org/">HCI Bibliography: Human-Computer Interaction Resources</a>, which is better known <em>HCI Bib.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*9qk511XluQnd_o8F" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.wcd.school/">World-Class Designer School</a>: a college-level, tuition-free design school focused on preparing young and talented African designers for the local and international digital product market. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed4151a166ab" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/classic-ux-book-from-the-1980s-ed4151a166ab">Classic UX books from the 1980s</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX research findings: distinguishing base hits from home runs]]></title>
            <link>https://medium.com/design-ibm/ux-research-dd8ea8336f08?source=rss-e1a8cd77495e------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd8ea8336f08</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Paul McInerney]]></dc:creator>
            <pubDate>Mon, 16 Apr 2018 14:17:12 GMT</pubDate>
            <atom:updated>2018-04-16T20:17:27.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8LDD7AD89Gmo3waclS6e7w.jpeg" /></figure><p>You’ve collected mounds of data for your UX study. And you’ve stared at the data long and hard to make sense of it. Finally, you’ve drafted a set of findings and verified that each one meets the basic quality criteria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mgj2T6cpgL_Ilba7yuTo2g.gif" /></figure><p>Many researchers would feel ready to share their findings with the project team. This article proposes two additional quality checks that can help you deliver better findings in your next UX study. These additional quality criteria are:</p><ul><li><strong>Value: </strong>The finding delivers a medium or high value.</li><li><strong>Course correction: </strong>The course correction prompted by this finding is clear and advisable.</li></ul><p>By thinking about these criteria intentionally, you can often fine-tune your findings to make them more valuable, clear, or persuasive.</p><p>Let’s start by discussing the value of a finding. It’s useful to be able to articulate the value of each finding because stakeholders often say things like, “We can’t address all these findings right away — which is the most important one?”</p><p>By analogy to baseball, we should be able to recognize whether a finding gets us to first base (low value) or is a home run (high value). A <em>low value </em>finding<em> </em>is still worthwhile — just like a steady stream of base hits often wins the game.</p><p>So, how can we assess the value of a research finding? To explore this question, let’s do an exercise using some real-life research findings. Review the examples below and rate the value of each one as <em>high value</em>, <em>medium </em>value, or <em>low</em> <em>value</em> using whatever criteria you deem appropriate.</p><h3>Case study examples</h3><h4>Example 1: Advisor</h4><p><strong>Background:</strong> The project mandate was to deliver a tool that provides advice on one topic. UX research aimed to understand fine-grained user needs such as, <em>How much detail do users want in the advice provided by the tool?</em></p><p><strong>Finding from UX research: </strong>We discovered that users also need advice on a related topic.</p><p><strong>Outcome:</strong> The project team was surprised by this finding. They expanded the project scope to include advice on this second topic. The resulting increase in project cost was negligible (+10%) because the algorithm that generated the advice required only minor enhancements.</p><h4>Example 2: Troubleshooting aid</h4><p><strong>Background:</strong> The project mandate was to deliver a tool to help technicians troubleshoot problems. UX research sought to identify the information that technicians would find useful so the tool could provide it.</p><p><strong>Finding: </strong>We were not able to produce one list that worked for everyone. Instead, we found there were two types of technicians, each using a different troubleshooting method that required its own set of information.</p><p><strong>Outcome:</strong> The team expanded the solution design to cater to two troubleshooting methods. This expanded scope required the project budget to increase by 50%.</p><h4>Example 3: Dashboards A</h4><p><strong>Background:</strong> The project mandate was to enhance the content in existing dashboards in response to anecdotal customer requests for enhancements. UX research was conducted to identify suitable changes.</p><p><strong>Finding: </strong>We discovered the problem was not with the dashboard <em>content</em> but the overall dashboard <em>organization</em>. To address the real user need, an entirely different set of dashboards was needed — dashboards organized around each task rather than around each part of the system.</p><p><strong>Outcome:</strong> The team pivoted from tweaking the existing dashboards to defining a new set of dashboards. There was a 200% increase in project cost — because creating a new set of dashboards is a bigger undertaking than tweaking existing ones.</p><h4>Example 4: Dashboards B</h4><p><strong>Background:</strong> The project mandate was to deliver a new dashboard. UX research aimed to validate the content the team planned to include.</p><p><strong>Finding: </strong>One suggestion was to group the issues on the dashboard by category. When we elicited the underlying need, we found out that users often work with issues in one particular category at any given time.</p><p><strong>Outcome:</strong> The team recognized the suggestion was good and adopted it. There was no impact on the project cost because the budget already accounted for the need to iterate on the original design.</p><p>The examples are summarized below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*StLdsGd5paPnj2pGf2MDQA.png" /><figcaption>Summary of examples</figcaption></figure><p>Of course, these thumbnail descriptions gloss over many real-life details. Before a project team accepts a finding, they need to see evidence and understand why users feel the way they do. For instance, in Example 1, the team would want to know why users want advice on the other topic. As well, some team members can be … er … <em>not easily convinced</em> when a finding indicates they’ve been on the wrong path. So, getting from research finding to product team outcome can be a more arduous and convoluted path than these descriptions suggest.</p><h3>Quality check #1: Value of the finding</h3><p>What criteria determine whether a research finding is <em>high</em>, <em>medium</em>, or <em>low value</em>? Here are some answers I’ve heard in the past:</p><blockquote>“The value of a finding is proportional to the size of the <strong>benefit for users</strong>; a <em>great</em> research finding has a <em>great</em> deal of benefit for users.”</blockquote><blockquote>“The value of a finding is proportional to the size of the <strong>response by the project team</strong>; a <em>great</em> research finding is one that <em>greatly</em> changes the thinking and direction of a project team towards a better outcome.”</blockquote><p>While these answers each identify one important factor, the approach proposed here considers multiple factors. The approach is based on the Importance vs. Feasibility matrix used in priority-setting exercises. The criteria for <em>high</em>, <em>medium</em>, and <em>low</em> value research findings are shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Iabk_KGZTlELfuMnk084sQ.png" /><figcaption>Value of a finding based on UX impact and project feasibility</figcaption></figure><p>This approach rates the value of a research finding by considering both the impact on users (that is, the improvement to the UX) and the cost to the project team (such as pushing out the delivery date or redeploying staff from another initiative).</p><p>The assessment is done using a <em>before-and-after</em> comparison. For instance, consider one of the case study examples:</p><p>Example 3: Dashboards A</p><ul><li>BEFORE the finding: The project team planned to tweak existing dashboards.</li><li>AFTER the finding: The project team pivoted to replace the existing dashboards with different ones.</li></ul><p>Considering the size of the impact on the UX, this example rates a <em>High</em> score, according to my own rule of thumb:</p><ul><li>High impact: At least 50% of the original user experience is changed by the finding</li><li>Medium impact: 10% to 50%</li><li>Low impact: less than 10%</li></ul><p>On the feasibility dimension, this example gets a <em>Low</em> feasibility rating because it entailed an incremental project cost of 200%. So, the <em>high</em> impact rating and the <em>low</em> feasibility rating would result in an overall value rating of <em>medium </em>or possibly <em>low</em>.</p><p>My ratings for all the examples are shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*8xDRcsW6c6bEenkSc9FXVw.png" /><figcaption>Ratings of examples (impact X feasibility = value)</figcaption></figure><p>Examples 1 to 3 vary only in their feasibility, which accounts for the different value ratings. Example 1 illustrates the type of research finding that is most appealing to a project team — it produces a large improvement in the user experience with a small incremental cost. This is a home run!</p><p>Example 4 illustrates the common humble research finding — it’s not going to change the world but at least there is little or no cost entailed. This makes it a <em>medium</em> value finding in my book.</p><p>In summary, this section examined research findings on a quantitative dimension by asking how much value a research finding provides.</p><h3>Quality check #2: Type of course correction</h3><p>It’s a commonplace that a finding must be <em>actionable</em>; in other words, it should prompt some type of <em>course correction</em> to the project. As findings can steer a project in different directions, it’s worth scrutinizing our findings and asking the following questions:</p><blockquote><em>Is the course correction prompted by this finding clear? Is it advisable?</em> <em>Could the finding be re-framed to prompt a different and better outcome?</em></blockquote><p>Answering these questions can help clarify the implications of what you’re proposing and thus better communicate and advocate your findings.</p><p>To help perform this quality check, this section will present a taxonomy of course corrections. But first, you might want to re-read the case study examples; the <em>Outcome</em> section of each example illustrates different type of course correction. See if you can identify each one.</p><p>The first point to note is that a finding can point of a shortcoming in either the (1) problem statement or (2) the design solution. For instance, consider one of the examples:</p><p>Example 1: Advisor</p><ul><li>BEFORE the finding: The project scope was to provide advice on one topic.</li><li>AFTER the finding: The project scope was extended to provide advice on one more topic.</li></ul><p>This example illustrates a course correction to the problem statement: the finding resulted in the project addressing a larger problem scope.</p><p>All the remaining examples involve changing the project solution. For instance:</p><p>Example 3: Dashboards A</p><ul><li>BEFORE the finding: The solution was to tweak existing dashboards</li><li>AFTER the finding: The solution was changed to replace the existing dashboards with a new set</li></ul><p>The second point to note is that a finding can <em>change</em>, <em>extend</em>, or <em>refine some </em>aspect of the project direction:</p><ul><li><strong>Change:</strong> “You’re going in the wrong direction, so change direction, i.e., <em>pivot</em>.”</li><li><strong>Extend:</strong> “You’re going in the right direction, but you’ve overlooked a major opportunity, So, extend your project scope to address it.”</li><li><strong>Refine:</strong> “You’re mostly on the right track, but you need a minor refinement.”</li></ul><p>Considering both points (or dimensions) together, we can summarize the case study examples as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*NRNGrhP5FCZcrsQtLsTt6Q.png" /><figcaption>Type of course correction illustrated by each example</figcaption></figure><p>Using this taxonomy, we can clearly describe the course correction in each example as follows:</p><ul><li>Example 1 (Advisors): <em>Extended the problem statement</em> to also provide advice on an additional topic.</li><li>Example 2 (Troubleshooting aid): <em>Extended the solution</em> to support the full user population, which consists of two types of users.</li><li>Example 3 (Dashboards): <em>Changed the solution</em> from tweaking existing dashboards to replacing them with a new set.</li><li>Example 4 (Dashboards): <em>Refined the solution</em> to add a breakdown of issues by category.</li></ul><p>Here are additional examples to fill in the missing cells in the table, based on modifying Example 1:</p><ul><li><strong>Example 1A finding from UX research: </strong>We discovered that users did not want advice on topic A; instead they want advice on topic B.</li><li><strong>Example 1B finding from UX research: </strong>We validated that users wanted advice on topic A, but only on three key subtopics.</li></ul><p>In summary, this section built the commonplace that a finding must be <em>actionable </em>by providing a quality check to help us be clear about what <em>type of action </em>we’re proposing.</p><h3>Conclusion</h3><p>We’ve seen two quality checks that can improve the quality and impact of research findings. The first assesses the value provided by a finding, from low to high value. The second quality check helps us ensure that the type of course correction prompted by each finding framed clearly and steers the project in the right direction.</p><p><em>Paul McInerney works in a UX research and design role at IBM in Toronto. The above article is personal and does not necessarily represent IBM’s positions, strategies or opinions. Thanks to Jake Volz for his valuable contributions!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd8ea8336f08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-ibm/ux-research-dd8ea8336f08">UX research findings: distinguishing base hits from home runs</a> was originally published in <a href="https://medium.com/design-ibm">IBM 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 & Agile: dream team or odd couple?]]></title>
            <link>https://uxdesign.cc/https-medium-com-paulmci-ux-agile-dream-team-or-odd-couple-1e06f9a01a26?source=rss-e1a8cd77495e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e06f9a01a26</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[lean-ux]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Paul McInerney]]></dc:creator>
            <pubDate>Mon, 15 May 2017 14:19:43 GMT</pubDate>
            <atom:updated>2022-06-13T09:26:57.331Z</atom:updated>
            <content:encoded><![CDATA[<h4>UX and Agile staff can form a Dream Team if they harmonize their practices. Otherwise, they’ll form an Odd Couple team.</h4><figure><img alt="An abstract image for visual interest that shows blurred circles of light" src="https://cdn-images-1.medium.com/max/1024/1*fmW-Pz_fdS-em2FOQ0qbJg.jpeg" /></figure><p>Are UX specialists satisfied with their experiences in Agile projects? While participating in a recent panel discussion, I asked the audience this question and only about half were satisfied, judging from the show of hands. These mixed reviews are consistent with what I’ve heard from UXers in various organizations over the past 10+ years and from what I’ve read in books like <em>Lean UX</em>.</p><p>While UX staff sometimes adopt an “us vs. them” perspective, we should start from the position that both UX and Agile have the same goal — to deliver great software that delights users. Problems can arise because each community has its own ideas about how to get there, which results in friction points. To succeed as a team, these communities need to establish common ground and make some accommodations: UX staff need to ensure their practices are Agile-friendly and Agile staff need to make some of their practices a little more UX-friendly. When UX and Agile harmonize their practices to remove friction points, we can call the result a Dream Team. And when they don’t, we can call the result an Odd Couple team.</p><p>Let’s see what a dysfunctional team, or Odd Couple, looks like. On Odd Couple teams, non-UX staff engage in practices such as:</p><ul><li>keeping UX outside the core team (that is, “us” or “the team” is understood to include only developers),</li><li>doing a poor job applying Agile best practices (for example, writing user stories that don’t effectively articulate the user value), and</li><li>failing to allocate project resources (people, money, time) to UX activities like user research and design evaluation.</li></ul><p>For their part, UX staff on Odd Couple teams engage in practices such as:</p><ul><li>working part time on multiple projects, rather than being dedicated to a single project,</li><li>taking a long time to produce elaborate design artifacts to hand-off to developers, and</li><li>treating developers as “them” and not taking an interest in their work beyond UX.</li></ul><p>This article identifies the topics where UX needs to find common ground with their Agile teammates to form a Dream Team. We’ll examine collaboration challenges for each of these aspects of UX in turn:</p><ul><li><strong>Understanding</strong> users, that is, conducting user research</li><li><strong>Large-scale UX design</strong>, that is, overall project design direction</li><li><strong>Small-scale UX design</strong>, that is, design in an individual sprint story</li><li><strong>Evaluating</strong> designs</li></ul><p>UX leaders can use these topics as a checklist to assess the health of their team and identify areas for improvement.</p><h3>Understanding users</h3><p>A tenant of UX is to develop a solid understanding of target users as a foundation for design. The quotes below illustrate the difference between a Dream Team and an Odd Couple project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkZhafCfqGMV7yBWlZfMMA.png" /></figure><p>The key topics where UX needs to find common ground with Agile are:</p><ul><li>How much UX research is enough, in the context of limited project resources?</li><li>How should that UX research be aligned with the project schedule?</li></ul><p>Generally, UX staff feel that more research is needed than project leaders do, so both parties need to find common ground on how much is enough.</p><p>Given agreement to conduct research, the next point of discussion is how to schedule it vis-a-vis the agile sprint schedule. Models I’ve seen projects use include:</p><ul><li>Up front — before project kick-off (Sprint 0)</li><li>Concurrently with sprints, but outside the sprint schedule</li><li>Integrated into the sprint schedule</li></ul><p>The models above are listed in increasing order of logistical difficulty.</p><h3>Large-scale UX design</h3><p>It’s useful to divide “design” into large-scale vs. small-scale aspects. Here “large scale” design refers to:</p><ul><li>Project direction, UI architecture, and visionary design concepts</li><li>Sprint planning and content definition</li></ul><p>For this aspect of UX, the difference between success and failure looks like this:</p><figure><img alt="Two quotes comparing a dream team to an odd couple. The dream team quote says I work on designs two or three iterations ahead of the agile team to allow for more high-level design work. The odd couple quote says it’s hard to juggle supporting the current sprint while designing for upcoming sprints. My entire UX team can get consumed with supplying wireframes for the current sprint." src="https://cdn-images-1.medium.com/max/1024/1*YNS2Yi-96adUypnUnuX-4Q.png" /></figure><p>Success from a UX perspective means having a “seat at the table” as one type of project leader and having adequate opportunity to develop and present a vision of the UX to guide the project.</p><p>Common topics of negotiation include:</p><ul><li>What portion of sprint story content (i.e., project resources) will be devoted to delivering UX quality vs. feature quantity?</li><li>How much is the project team willing to revisit (refine, iterate on) designs from earlier sprints?</li><li>What portion of the UX team resource will be allocated to large scale design vs. keeping the Agile story teams supplied with detailed UX designs?</li><li>How willing is the team to start planning 2–3 sprints ahead so UX can get a head-start?</li></ul><h3>Small-scale UX design</h3><p>Here “small-scale” design refers supporting individual sprint stories. One thing that UX staff say they like about Agile is its fluid back-and-forth between design and coding, rather than enforcing a formal hand-off from a design stage to a coding stage. However, not all teams have achieved this ideal state:</p><figure><img alt="Two quotes comparing a dream team to an odd couple. The dream team quote says we can adjust the design on the fly as the developer works on it. The odd couple quote says developers sometimes want to develop only the basic functionality then stop before the experience is refined." src="https://cdn-images-1.medium.com/max/1024/1*Guo4adwFSGXF5mbY7bkzRw.png" /></figure><p>Aspects that have to be optimized include:</p><ul><li>ensuring the user stories clearly articulate the problem being solved in terms relevant to UX,</li><li>getting developers engaged and collaborating in the UX design work prior to coding, and</li><li>getting developers to be receptive to UX input and feedback during coding.</li></ul><h3>Evaluating designs</h3><p>Another tenant of UX is the importance of evaluating designs with users. As with the other aspects of UX, success varies:</p><figure><img alt="Two quotes comparing a dream team to an odd couple. The dream team quote says we conduct quick usability tests and discuss design options with a small number of users.
 
 The odd couple quote says the closest approximation of design evaluation is holding agile sprint reviews for stakeholders." src="https://cdn-images-1.medium.com/max/1024/1*G6OEnXTIYdCeswphefJbrA.png" /></figure><p>Aspects that have to be ironed out between UX and the Agile project leads are:</p><ul><li>In the context of limited project resources, how much design evaluation is enough?</li><li>What are the expectations for fixing issues?</li></ul><p>The first challenge is simply getting the opportunity to conduct evaluations. Opportunities can be limited due to staff resources, schedule, or access to users. The second challenge is getting issues fixed. The larger the fix, the harder it is to get it addressed.</p><h3>Conclusion</h3><p>We’ve identified several friction points between the UX and Agile parties in a project team. The more that UX and Agile staff find common ground and make accommodations on these points, the better for everyone — including the users of your software.</p><h3>Further reading</h3><p>For more quotes and case studies, see my recent article <a href="https://interactions.acm.org/archive/view/march-april-2017/ux-in-agile-projects"><em>UX in Agile projects: Taking stock after 12 years</em></a><em>.</em></p><p>For a practical book on this same general topic, see <a href="https://www.amazon.com/Lean-UX-Designing-Great-Products/dp/1491953608"><em>Lean UX</em></a>.</p><p>For a deep dive on UX research, see the article <a href="http://www.uxmatters.com/mt/archives/2016/11/agile-development-is-no-excuse-for-shoddy-ux-research.php"><em>Agile Development Is No Excuse for Shoddy UX Research</em></a><em>.</em></p><p>For a recent scholarly treatment, see the edited book <a href="http://www.springer.com/gp/book/9783319321639"><em>Integrating User-Centred Design in Agile Development</em></a><em>.</em></p><p>To improve your empathy with software developers, I recommend the book <a href="https://www.amazon.com/Team-Geek-Software-Developers-Working/dp/1449302440/"><em>Team Geek: A Software Developer’s Guide to Working Well with Others</em></a><em>.</em></p><p>Finally, if you’re looking to read something completely different, and you’re a history buff, you might like the novel <a href="https://www.amazon.com/Siege-Ismail-Kadare/dp/0802144756"><em>The Siege</em> by Ismail Kadare</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e06f9a01a26" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/https-medium-com-paulmci-ux-agile-dream-team-or-odd-couple-1e06f9a01a26">UX &amp; Agile: dream team or odd couple?</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>