<?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 John Scott Bowie on Medium]]></title>
        <description><![CDATA[Stories by John Scott Bowie on Medium]]></description>
        <link>https://medium.com/@johnscottbowie?source=rss-b2e3a81ab2da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LN-mWeOthEUxZ50uci_UmQ.jpeg</url>
            <title>Stories by John Scott Bowie on Medium</title>
            <link>https://medium.com/@johnscottbowie?source=rss-b2e3a81ab2da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:43:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johnscottbowie/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[Simple questions with complex answers]]></title>
            <link>https://medium.com/design-bootcamp/simple-questions-with-complex-answers-eddd3f0e4a77?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/eddd3f0e4a77</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Fri, 25 Mar 2022 00:41:33 GMT</pubDate>
            <atom:updated>2022-03-25T00:41:33.433Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two roadsigns, one labeled Questions, one labeled Answers, point in different directions" src="https://cdn-images-1.medium.com/max/1000/1*i9lQAFX-Hy_g0O3Te5Ntug.jpeg" /></figure><p>Several years ago, I began my UX design workshops with a clip from the movie <em>City Slickers.</em> In the scene, Billy Crystal tries to explain to Daniel Stern how to operate his VCR. It was hilarious back in the 1990s when everyone could relate to Stern’s frustration and confusion, but not so much today when everyone has forgotten (or never experienced) what it was like to use a VCR.</p><p>If you’re feeling nostalgic and want to see the clip, you can find it here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FqQGgaI-BcI4%3Fstart%3D2%26feature%3Doembed%26start%3D2&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DqQGgaI-BcI4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FqQGgaI-BcI4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e813026a59a685cd0a6c8466f5eda7b8/href">https://medium.com/media/e813026a59a685cd0a6c8466f5eda7b8/href</a></iframe><p>The scene ends with Stern asking, “How do you do the clock?”</p><p>This is a simple question. But too often, even after decades of attention to paid to user experience mindsets and methodologies, simple questions have complex answers.</p><p>This is particularly relevant this month (March) when most states in the U.S. switch to Daylight Saving Time, requiring people to set their clocks forward one hour.</p><p>After hundreds of years of clock evolution, the procedure for setting the time on a digital clock has only recently been simplified or automated. It was only 25 years ago when you needed to change the time on the clock radio in your Chrysler minivan, you were confronted with a confounding user interface:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8UjcpuLQiyD7Xe3-g2Aj4A.png" /></figure><p>Quick! At a glance, how do you set the time? You might think SET will get you there, but that’s not the first step. Here’s what Chrysler required you to do:</p><p>1. Insert the key in the ignition and turn it to the “Accessories” setting.</p><p>2. Turn on the radio.</p><p>3. Press the SET button.</p><p>4. Press the SEL button once.</p><p>5. Press the TUNE button up or down to change the hour.</p><p>6. Press the SEL button once again.</p><p>7. Press the TUNE button up or down to change the minute.</p><p>8. Wait for the display to return to the radio settings.</p><p>(Actually, there’s a step 0: Find the Owner’s Manual and look up “Clock” in the Index.)</p><p>Makes perfect sense, right? An easy procedure to remember when the last time you changed the time was six months ago! Yet for the Chrysler product team, “tuning” your clock was a perfectly reasonable solution.</p><p>As UX professionals, product managers, and development engineers, we must train ourselves to recognize when our products deliver complex answers to simple user questions. We must then invest the extra effort to design a better solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eddd3f0e4a77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/simple-questions-with-complex-answers-eddd3f0e4a77">Simple questions with complex answers</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Activating Your UX Practice Across the Organization]]></title>
            <link>https://medium.com/design-bootcamp/activating-your-ux-practice-across-the-organization-e958b4433ccb?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/e958b4433ccb</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 04:11:32 GMT</pubDate>
            <atom:updated>2022-02-25T04:11:32.862Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*TSqDuMX6hu3qDrhxqAFCUw.jpeg" /></figure><p>In Part 1 of my new book, Navigating the Politics of UX, I discuss strategies for recruiting new allies to the UX cause. Why? Because UX practitioners tend to spend most of their time with their partners in development with only limited contact with other functional areas.</p><p>But what about your colleagues in Product Management, QA, Sales, Professional Services, Technical Communication, Support, Marketing, and the C-suite? If you are not engaging every functional team in UX activities, you’re missing a huge opportunity to activate your UX practice across the entire organization and drive UX maturity and culture change.</p><p>PRODUCT MANAGERS can schedule and attend on-site observational research sessions and raise the priority of UX initiatives in the product roadmap.</p><p>QA PROFESSIONALS can help you prioritize UX defects as critical and serious issues that must be resolved before the product ships.</p><p>SALES PROFESSIONALS can include you on sales calls, providing yet another channel for user research, and help you gauge customer reactions to early design prototypes.</p><p>PROFESSIONAL SERVICES CONSULTANTS AND TRAINERS can connect you with first-time users for research purposes and provide evidence-based support for your viewpoints in design sprints.</p><p>TECHNICAL COMMUNICATORS can collaborate with you as UX writers and content designers on language-intensive elements of the user experience.</p><p>SUPPORT PROFESSIONALS can help you establish a closed user feedback loop in which common UX issues are identified and resolved, and collaborate with you to embed support assets directly into the product UI.</p><p>MARKETING PROFESSIONALS can enhance the UX team’s eminence by promoting your innovations inside and outside the company, and set up research opportunities at conference expos.</p><p>The EXECUTIVE LEADERSHIP TEAM can recognize the contribution of UX initiatives to financial OKRs and establish business practices that evolve the company toward a a UX-driven culture.</p><p>Start reaching out to people in your company with whom you’ve never worked before. Invite them to participate in user research, ideation, UX analysis, data collection, and design iteration. Understand their drivers and demonstrate how UX can help them succeed.</p><p>Do this, and you will make great strides toward infusing UX considerations into every business decision your company make.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e958b4433ccb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/activating-your-ux-practice-across-the-organization-e958b4433ccb">Activating Your UX Practice Across the Organization</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Design Reviews Done Right]]></title>
            <link>https://medium.com/design-bootcamp/ux-design-reviews-done-right-8a07e6fcf70e?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a07e6fcf70e</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 06:33:19 GMT</pubDate>
            <atom:updated>2022-02-15T06:33:19.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iepsJpdYxZp0cdgmRcnFOw.jpeg" /></figure><h3>Telling the Story of Your Design Journey is Key</h3><p>When you walk out of a design review, are you frustrated or inspired?</p><p>If your design reviews are forums where product partners search for ways to criticize your work, you’re probably frustrated. If your design reviews are jam sessions where you encourage others to join your journey toward the best possible user experience, you’re probably inspired.</p><p>Design reviews — meetings where UX designers share their recent work with stakeholders and partners — can be affirming or demoralizing. When facilitated correctly, UX design reviews are important catalysts for new insights and ideas. They educate and engage the organization on your thought process, and make others feel they are co-owners of the design.</p><p>Design reviews are necessary. Stakeholders need to be kept apprised of design decisions as the product evolves. You want to receive feedback early and often to avoid throwing out weeks of work after objections surface at the end of an iteration cycle.</p><p>But remember, you’re asking non-designers to offer design advice. You have spent hours, days, or weeks thinking through the design problem. They have spent only minutes. Participants with little understanding of UX often comment on only the most superficial aspects of the design. If you don’t guide the discussion carefully, design reviews can be a huge waste of time as you navigate the politics of responding to every suggestion.</p><h3>You Asked for It</h3><p>When you ask others for feedback, you will definitely get it. Reviewers often feel obligated to find <em>something </em>wrong with the original design no matter how minor, otherwise they think they’re not doing their job. Many times their suggestions will simply make the design different, but not better.</p><p>So how do you reduce the churn and increase the value of design reviews? Here are a few suggestions:</p><h3>Schedule Design Reviews Weekly or Biweekly, But Don’t Be Afraid to Cancel Them</h3><p>It can be difficult to find a time when all your stakeholders can meet for a design review, so meetings need to be blocked off on calendars well in advance. Depending on your sprint schedule, biweekly meetings are usually sufficient — early enough to allow time for additional iterations but late enough to give you sufficient time to think through the design problem.</p><p>If you’re still struggling with the design when the meeting time arrives, you have two choices:</p><ol><li>Cancel or reschedule the meeting. If you’re not prepared to defend your early concept, this may be the most productive choice, saving everyone time. Usually no one complains when a meeting is canceled or moved.</li><li>Meet as planned if you need to solicit others’ ideas on the design problem you’re struggling with. Explain that you need their help with the problem definition and are not looking for detailed feedback on your very preliminary concept.</li></ol><h3>Explain Your Design Journey</h3><p>Use the time you’ve spent thinking through the design problem to your advantage. Don’t just present your final mockup or prototype — explain how you got from iteration #1 to your current iteration. Participants need context if they are to provide useful ideas rather than superficial critiques.</p><ul><li>Articulate the design problem as a story using the name of one of your personas (<em>not</em> the term “user”) as the main character. Structure the story like this: An event has occurred in the life of your main character (let’s call her Julie) that triggers her to use your product. Julie wants to achieve a very specific result. The journey to the result is how she will assess success or failure with your product.</li><li>Show a few of the iterations you have worked through. For each, demonstrate the actions Julie must take and the information she must know to navigate through the design to reach the result.</li><li>Explain how each subsequent iteration requires fewer action and information requirements than the previous one.</li><li>Show your proposed design. Emphasize that it complies with your design system and branding standards (to emphasize your commitment to consistency and development efficiency).</li><li>Rather than asking, “What do you think of this design?,” ask: “Do you have any ideas for making Julie’s experience simpler or more rewarding?” This subtle difference in your opening question helps your stakeholders focus on the broader experience rather than on the visual and structural details of your prototype.</li><li>If audience suggestions require further UX analysis, say that you’ll get back with everyone after you’ve had time to mockup their ideas. If the suggestions are minor (e.g., labeling changes, UI object repositioning) and the group has reached consensus, impress everyone by redesigning on the fly.</li><li>Thank everyone for their contributions to creating the optimal user experience.</li></ul><p>Ideally, your UX analysis is sufficient to prove your final design is superior to all alternatives. But, at the close of the meeting, if you can’t get signoff on the final design direction…</p><h3>…Let Your Users Decide</h3><p>If you haven’t done so already, form a user advisory council that you can convene when you need a quick feedback session. Use social media channels to get participants to sign up.</p><p>Run an experiment. Mock up the alternative design concept in addition to your own. Use a teleconferencing app like Zoom to present both concepts to a small group of users in a usability/preference test. Record the sessions and share the results of your quick-and-dirty research with your stakeholders. Be objective: let the best design win.</p><figure><img alt="Navigating the Politics of UX Book Cover" src="https://cdn-images-1.medium.com/max/362/1*8IMeu7eNwfUc1WgXBQ93Eg.png" /></figure><p>More design review strategies and stories will be shared in my upcoming book, <em>Navigating the Politics of UX, Volume 2: Operations</em>, coming later this year.</p><p><em>Navigating the Politics of UX, Volume 1: People</em> is available now on Amazon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a07e6fcf70e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ux-design-reviews-done-right-8a07e6fcf70e">UX Design Reviews Done Right</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Solution to Everything (from Navigating the Politics of UX)]]></title>
            <link>https://medium.com/design-bootcamp/the-solution-to-everything-from-navigating-the-politics-of-ux-80d354ffa7f9?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/80d354ffa7f9</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Sun, 09 Jan 2022 21:14:48 GMT</pubDate>
            <atom:updated>2022-01-11T04:38:39.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2jC--syVs86bOFcArdmpSw.jpeg" /></figure><h3>The Solution to Everything</h3><p>So often, companies measure things but they don’t manage them.</p><p>Product management measures customer satisfaction and Net Promoter Scores (NPS). Support measures call resolution rates, product returns and warranty costs. Sales and Marketing measure market share, sales closure rates, and retention rates.</p><p>All of these metrics are driven by the user experience. But none are diagnostic; none reveal where the experience is broken and needs to be improved.</p><p>NPS, for example, asks: how likely are you to recommend our product to a friend or colleague? It determines which customers are Promoters (score 9–10), which are Passives (score 7–8), and which are Detractors (score 0–6) Promoters will tell three people about their experience; detractors will tell nine people.</p><p>Net Promoter Scores are useful for <em>measuring</em> improvements or declines in customer perception over time, but field research is needed to take the targeted action needed to <em>manage</em> the score. NPS without field research leaves changes to the user experience in subsequent releases to guesswork and chance.</p><p>To understand and manage the drivers of these metrics, you must observe users in their native environment as they attempt to attain the results your product promised them.</p><p>Without user research, you have no foundation for advancing your UX initiatives. Without user research, you’re just a zealot standing on a soapbox; your sermons will fall on deaf ears. It’s not that others in your company don’t find your arguments compelling; perhaps they will. But no action or change in behaviors will occur until you have compelling user research that directly correlates to your corporate-level Objectives and Key Results (OKRs).</p><p><em>Navigating the Politics of UX </em>will be submitted to Amazon on Sunday, January 16th. After Amazon’s quality check, it should be available later that week. This is a snippet from Part 2: Fostering a UX-Driven Corporate Culture.</p><p>Also read on LinkedIn, in addition to other newsletter topics: <a href="https://www.linkedin.com/posts/john-bowie-9286671_ux-culture-userexperience-ugcPost-6885972671671144448-xsoZ">https://www.linkedin.com/posts/john-bowie-9286671_ux-culture-userexperience-ugcPost-6885972671671144448-xsoZ</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80d354ffa7f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-solution-to-everything-from-navigating-the-politics-of-ux-80d354ffa7f9">The Solution to Everything (from Navigating the Politics of UX)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Motivating and demotivating creative teams with performance reviews]]></title>
            <link>https://medium.com/design-bootcamp/motivating-and-demotivating-creative-teams-with-performance-reviews-9e089146eed?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e089146eed</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[creative]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Sat, 12 Jun 2021 14:09:35 GMT</pubDate>
            <atom:updated>2021-06-15T02:20:20.117Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrznTHHtDcTvtWtgHo82ow.jpeg" /></figure><p>I’ve led (and been led by) creative teams for over 25 years. This means there have been over 25 times in my career when I seriously considered quitting my job. If you’ve led a creative team for several years, you probably know what I’m talking about.</p><p>The potentially job-terminating event begins with a meeting of all managers in the division. In preparation for the meeting, each manager has rank-ordered and assigned a number to each of their employees based on their “performance” over the past year — ranging from a “5” for outstanding performance to a “1” for unsatisfactory performance (i.e., for employees who will be placed on a performance improvement plan, laid off, or fired).</p><p>A bloody battle ensues in which the contributions of marketers are compared to call center agents, technical writers are ranked against software engineers, and UX designers are evaluated against product managers. To ensure conflict, each performance category has a “target” percentage assigned to it: typically 15% for 5s and 4s, 15% for 2s and 1s, and 70% for the middling 3s.</p><p>Managers come armed with evidence of stellar results that their superstars have achieved, and hide in their back pockets a list of their employees who may need to be sacrificed to a lower level to meet the category quotas. Top performers from the previous year tend to stay at the top, but sometimes, after metaphorically comparing Marie Curie, Albert Einstein, Isaac Newton, and Harriet Tubman as candidates for the 5s category, Einstein is demoted to a 4 in order to meet the percentages. Moving up requires extraordinary achievement, although the precise definition of that level of achievement is a mystery. A lot of times it’s about which employees are “visible” to the most managers.</p><p>Over the course of the following week, employees are summoned to appear before the all-knowing judge (i.e., the creative team’s manager) to find out which number the entirety of their past year’s work has been reduced to. Usually the employee has completed a self-evaluation beforehand describing their results across a dozen or so performance criteria, and the manager searches for ways to restate what the employee has said in different words. Sometimes the manager is <em>required</em> to include “opportunities for growth” in the feedback (i.e., negative comments) to balance out the praise for accomplishments.</p><p>Maybe you’ve had this experience; I hope that you haven’t. I can tell you that, in many of my management jobs across multiple companies, this is the way things worked. Not always, but more often than not. To me, it’s hard to imagine a better way to demotivate employees at the start of a new fiscal year.</p><p>But it doesn’t have to be this way. You could, for example, give every member of your team a 5 rating (I did). Or, if your boss won’t let you get away with that, you can explain to your teammates during your meeting that policy requires you to assign them a number but that the numbers are meaningless and don’t reflect your assessment of their results.</p><p>Instead of calling your employees into a conference room to deliver the performance review, you could take them out to lunch. And instead of rehashing their past performance (including the requisite negative “development opportunity” comments), you could talk about the future: the challenges and opportunities your department will face in the coming year. Talk about their career goals and have a conversation about how their goals can contribute to the team’s success. Ask what opportunities you can give them to support their interests. Express your confidence in their ability to make the upcoming year their best year ever. And always end the meeting by thanking them for all that they’ve done and all that they are about to do.</p><p>After all, you, as their manager, only have your job because of them.</p><p>This approach may violate HR policies, but you can do this with the best interests of the company in mind: inspiring your team will produce much better performance results in the coming year than rating and judging their past performance. Isn’t that in the best interests of the company?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e089146eed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/motivating-and-demotivating-creative-teams-with-performance-reviews-9e089146eed">Motivating and demotivating creative teams with performance reviews</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product design’s missing link]]></title>
            <link>https://medium.com/design-bootcamp/product-designs-missing-link-6b2dd0832050?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b2dd0832050</guid>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Thu, 13 May 2021 01:03:17 GMT</pubDate>
            <atom:updated>2021-05-14T04:05:27.421Z</atom:updated>
            <content:encoded><![CDATA[<h4>When you design a product, you also design its user</h4><figure><img alt="Image of a jigsaw puzzle with one piece missing and a man standing in the space of the missing piece" src="https://cdn-images-1.medium.com/max/1000/1*x7ZAlM0GImR8Qi0Ty_0crQ.jpeg" /></figure><h3>What are we designing?</h3><p>The answer seems obvious. We design products and services, right? After decomposing outcomes into epics and then into features and further into stories, we design and develop a small fragment of a meaningful user requirement, pulled out of our sprint backlog. The end result: a minimally viable product (or maybe better).</p><p>But is that really what we’re designing and coding? A set of product functionality that enables a person to achieve a collection of desireable results? No, we’re not just designing product functionality, or in the case of a service, a set of steps in a process. If we do only that, we’re leaving out a huge part of the design, a part that will determine the success or failure of our product or service.</p><p>Here’s a clue: creating Journey Maps can reveal part of the missing design element. Jeff Patton’s User Story Mapping approach can get us even closer.</p><p>What the conventional practice of design ignores is the design of the human component. And, aware of it or not, when we design a product or service, we are simultaneously (and probably unconsciously) designing its user.</p><p>Think of it this way: a software development process often begins with a software architecture schematic.</p><figure><img alt="Image of a software architecture showing standard technology components" src="https://cdn-images-1.medium.com/max/1024/1*Z-mttzA-D6Fm5_wVYdXgTA.png" /></figure><p>Responsibility for all of the product’s functionality and information requirements are distributed among the objects in this architecture. But there’s one object that’s missing. What is it?</p><p>That’s right — the human component is missing. Yet, despite this oversight, the design always delegates essential functional responsibilities to this invisible object in the architecture whether we are aware of it or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q22sKGProLpDylUON1g1vw.png" /></figure><p>Without a well-designed human component, a product or service can achieve nothing, no matter how many great features it has. Unless the user takes action — clicks or taps the right buttons, enters the right information on a form, chooses the right menu option, etc. — the product does nothing. It just sits there, totally useless.</p><p>So back to our question: What are we designing? We are not designing a product or service. We are designing a Results System of which the technology components are a part, but not all the parts. A Results System is a collection of components — including the human component — that, when functional requirements are distributed properly, is capable of achieving the system’s acceptance criteria. Each component is assigned functional responsibility for performing some of the actions and processing some of the information required to achieve a result.</p><p>In our sprints, we design and code the functional requirements assigned to the product components. But have we unconsciously assigned functional requirements to the human component for which no pre-installed functionality exists? In other words, does our product design require its user to execute actions that he/she does not know how to perform and supply information he/she does not already know and cannot easily find?</p><p>If it does, our only option is to try to “install” — at the moment of need — the missing functional code into the human component via documentation, training, in-product support, or a help desk agent. Regardless of the mode of installation, the odds that the human processor can successfully compile and execute that code are reduced considerably. The system grinds to a halt; no result is achieved (and if a Results System can’t achieve its intended result, that is a fatal error). When this happens, as the Results System’s designers, we have failed just as surely as if we had shipped code with critical bugs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b2dd0832050" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/product-designs-missing-link-6b2dd0832050">Product design’s missing link</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The shareholder is always right?]]></title>
            <link>https://medium.com/design-bootcamp/the-shareholder-is-always-right-bd2d7bcb6500?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd2d7bcb6500</guid>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Tue, 04 May 2021 17:57:21 GMT</pubDate>
            <atom:updated>2021-05-07T04:57:57.020Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your company cannot succeed unless your customers do</h4><figure><img alt="Shareholder proudly showing off the money he has made in the stock market" src="https://cdn-images-1.medium.com/max/1024/1*qh7mwcpWvkQJ9gysWEhl6A.jpeg" /></figure><p>“The customer is always right” was the very first business maxim. It’s so old no one can remember who said it, but for decades companies from local gas stations to multinational conglomerates have placed it at the center of their mission statements.</p><p>Sadly, “the customer is always right” has given way to “the <em>shareholder</em> is always right.” The modern mission statement centers on meeting or beating shareholders’ expectations — at the expense, if necessary, of employees, of customers, and of company values. Every decision is evaluated for its impact on the bottom line; customers are not even a consideration — they are simply sources of revenue. Today when an employee wants to solve a customer problem, she has to show a return-on-investment.</p><p>How do these new business priorities affect product development? Like everything else, product success is measured in terms of financial objectives — profit margin and market share — the factors that drive the stock price.</p><p>While profit margin and market share are often used to <em>measure</em> the success of a product, they do not <em>determine </em>success. Companies cannot design profit or engineer market share; they can only design and engineer products. So what are the ingredients that must be mixed into a product design to ensure its success?</p><p>Conventional wisdom says reliability, features, and price determine product success. Reliability reduces support costs, which increases profit. A rich feature set entices customers to buy, which grows market share. And a competitive price means customers receive good value for their money, which improves brand loyalty.</p><p>Reliable. Rich in features. Low in price. Combine these ingredients and surely your product will succeed.</p><p>Or will it? Is it possible to design a product that is highly reliable, rich in features, and low in price — but still fails? You know it is. So, what is the missing ingredient that completes the recipe for success?</p><p>To answer this question, think of a successful product, a Sony TV for example. Sony televisions enjoy all the trappings of success: excellent market share, high profit margins, and loyal customers. Now imagine that Sony releases a new line of UHD TVs. These new TVs include all the functionality of previous models, exceed Sony’s reliability standards, sell for less than their predecessors, and offer better picture quality.</p><p>Now imagine that just before release, some mischievous product developer secretly reassigns every TV function to a different button on the remote. So now when the customer presses the volume up button, the TV turns off. Pressing the channel down button adjusts the color setting. Pressing 14 changes the channel to 28. And so on.</p><p>Would this new line of Sony TVs succeed? Let’s apply our success formula:</p><p>Reliability? Check.</p><p>Rich feature set? Check.</p><p>Low price? Check.</p><p>This new line of TVs has all the attributes of earlier models; they’ve just moved things around a bit. Why then is this TV line destined to fail?</p><p>The answer is obvious. The new TVs just don’t work. Or more precisely, customers don’t work with them. Customers will quickly realize their new TV is useless, and off they will go to the store for a refund. Reliability, a rich feature set, and low cost are clearly not sufficient to ensure a product’s success.</p><p>So, returning to our question: what is the missing ingredient that completes the recipe for a successful product? The answer: results.</p><p>Success is not defined in terms of what your <em>product</em> can do, but in terms of what your <em>customers</em> can do with your product. Reliability, functionality, and price are important, but they are all meaningless if your customer can’t achieve results.</p><p>Your product, by itself, can’t accomplish anything. It just sits there. It’s useless. It may have great potential, but unless your customers can figure out which buttons to push and when to push them, the product might as well stay in the box.</p><p>I want you to create a poster containing the following words. I want you to post it in your office/cubicle and read it every day. I want you to send a copy to your CEO. The poster reads:</p><p><strong>Our company cannot succeed unless our customers do</strong></p><p>Take a minute to think about what this means:</p><ol><li><strong>Technical Excellence is Not Enough.</strong> It doesn’t matter how many features your product has or how technically superior it is. If your customers cannot <em>use</em> these technically superior features without a lot of hassle, the product will fail and so will you.</li><li><strong>An Elegant Design is Not Enough.</strong> Any product can seduce a customer with an appealing and distinctive design. But the allure of beauty fades quickly when the product’s ugly and demanding behavior begins to show.</li><li><strong>Creative Marketing is Not Enough.</strong> Slick marketing and false promises can sell even lousy products for a while, but eventually reality catches up with the hype. Your company’s reputation will be irreparably damaged.</li></ol><p>So, what <em>is</em> enough? It’s very simple: deliver on your promises. Every product promises results; deliver those results, and make sure they come easily. Make this your #1 objective. Take a leap of faith: focus on ensuring that your customers achieve <em>their</em> Job 1 objectives and have faith that <em>your</em> business objectives will follow. Business results flow from customer results; the reverse is rarely true.</p><p>Taking care of business means taking care of customers. If your product requires its customers to know things they don’t want to know and do things they don’t want to do, you are in a very precarious position. Your support costs and product returns will be high; your customer loyalty will be low. You’ve also wasted your R&amp;D investment developing features that no one uses. But don’t despair. Observe your customers using your product. You’ll learn how to pinpoint where your product fails, why it fails, and how to make it work.</p><p>And your customers — and even your shareholders — will love you for it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd2d7bcb6500" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-shareholder-is-always-right-bd2d7bcb6500">The shareholder is always right?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Smart People Paradox]]></title>
            <link>https://johnscottbowie.medium.com/the-smart-people-paradox-ac462fe77e84?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac462fe77e84</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[sme]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Fri, 19 Feb 2021 22:42:32 GMT</pubDate>
            <atom:updated>2021-02-19T22:42:32.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQtnxHXmMXfr36LIS43w8w.jpeg" /></figure><p><strong>Also available on my blog at </strong><a href="https://www.coloradodesignlabs.com/blog-1"><strong>ColoradoDesignLabs.com</strong></a></p><p>Companies need smart people — subject matter and technical experts — to design and build things. Smart people are required to solve the hundreds of technical challenges required to bring a product to market. Smart people who are experts in their fields are consulted to design a company’s internal IT applications and business processes.</p><p>There’s only one problem with smart people: they tend to design things for people like themselves — for other smart people. But people are not all smart about the same things, nor do they want to be, nor should they be. An expert accountant might design a company’s time and expense reporting system in a way that makes perfect sense to another expert accountant, but most of the people using the system are not expert accountants and find the myriad accounting codes unnecessarily complex. An expert technologist might design a cell phone that has all the latest features and functionality, but the Nobel-Prize-winning chemist who buys the phone has no desire to be an expert in cell phone technology — she just wants to make a phone call. A seasoned human resources manager might design an employee performance management process that makes perfect sense to other human resources experts, but to the managers who have to use the system it is unnecessarily tedious, time-consuming, and complex.</p><p>This is the Smart People Paradox: companies need smart people to be successful, yet these smart people often insist on adding complexity to products and operations that can render the company less successful. Because the complexity is routine and second nature to them, these Smart People don’t even see it, or if they do, they insist that everyone <em>needs</em> to understand it.</p><p>I once worked with a team of engineers on a new oscilloscope project. The underlying complexity of the technology was surfacing in the proposed user interface design. When I tried to call attention to this, the engineers insisted that users needed to understand the underlying technical architecture of the product and become familiar with terminology that they assumed was commonplace in the industry. “Sure it’s kind of complex,” they would argue, “but our customers are smart people. They’re scientists and engineers. They love this kind of stuff, and after all, it’s not rocket science.”</p><p>This was a compelling argument in our engineering-dominated culture until we got the opportunity to visit Los Alamos National Laboratory, one of our major customers. Here our users — rocket scientists all — told us that they had less time to learn how to use their scientific instruments than in the past, and that they needed to be significantly easier to use.</p><p>Apparently even rocket scientists don’t want to be experts in oscilloscope technology.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac462fe77e84" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turn ’em Loose! #8]]></title>
            <link>https://johnscottbowie.medium.com/turn-em-loose-8-1a7d42d25323?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a7d42d25323</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Sat, 21 Nov 2020 22:30:32 GMT</pubDate>
            <atom:updated>2020-11-21T22:30:32.932Z</atom:updated>
            <content:encoded><![CDATA[<h3>Performance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrznTHHtDcTvtWtgHo82ow.jpeg" /></figure><p>I’ve led (and been led by) creative teams for over 25 years. This means there have been over 25 times in my career when I seriously considered quitting my job. If you’ve led a creative team for several years, you probably know what I’m talking about.</p><p>The potentially job-terminating event begins with a meeting of all managers in the division. In preparation for the meeting, each manager has rank-ordered and assigned a number to each of their employees based on their “performance” over the past year — ranging from a “5” for outstanding performance to a “1” for unsatisfactory performance (i.e., for employees who will be placed on a performance improvement plan, laid off, or fired).</p><p>A bloody battle ensues in which the contributions of marketers are compared to call center agents, technical writers are ranked against software engineers, and UX designers are evaluated against product managers. To ensure conflict, each performance category has a “target” percentage assigned to it: typically 15% for 5s and 4s, 15% for 2s and 1s, and 70% for the middling 3s.</p><p>Managers come armed with evidence of stellar results that their superstars have achieved, and hide in their back pockets a list of their employees who may need to be sacrificed to a lower level to meet the category quotas. Top performers from the previous year tend to stay at the top, but sometimes, after metaphorically comparing Marie Curie, Albert Einstein, Isaac Newton, and Harriet Tubman as candidates for the 5s category, Einstein is demoted to a 4 in order to meet the percentages. Moving up requires extraordinary achievement, although the precise definition of that level of achievement is a mystery. A lot of times it’s about which employees are “visible” to the most managers.</p><p>Over the course of the following week, employees are summoned to appear before the all-knowing judge (i.e., the creative team’s manager) to find out which number the entirety of their past year’s work has been reduced to. Usually the employee has completed a self-evaluation beforehand describing their results across a dozen or so performance criteria, and the manager searches for ways to restate what the employee has said in different words. Sometimes the manager is <em>required</em> to include “opportunities for growth” in the feedback (i.e., negative comments) to balance out the praise for accomplishments.</p><p>Maybe you’ve had this experience; I hope that you haven’t. I can tell you that, in many of my management jobs across multiple companies, this is the way things worked. Not always, but more often than not. To me, it’s hard to imagine a better way to demotivate employees at the start of a new fiscal year.</p><p>But it doesn’t have to be this way. You could, for example, give every member of your team a 5 rating (I did). Or, if your boss won’t let you get away with that, you can explain to your teammates during your meeting that policy requires you to assign them a number but that the numbers are meaningless and don’t reflect your assessment of their results.</p><p>Instead of calling your employees into a conference room to deliver the performance review, you could take them out to lunch. And instead of rehashing their past performance (including the requisite negative “development opportunity” comments), you could talk about the future: the challenges and opportunities your department will face in the coming year. Talk about their career goals and have a conversation about how their goals can contribute to the team’s success. Ask what opportunities you can give them to support their interests. Express your confidence in their ability to make the upcoming year their best year ever. And always end the meeting by thanking them for all that they’ve done and all that they are about to do.</p><p>After all, you, as their manager, only have your job because of them.</p><p>This approach may violate HR policies, but you can do this with the best interests of the company in mind: inspiring your team will produce much better performance results in the coming year than rating and judging their past performance. Isn’t that in the best interests of the company?</p><p>Of all the things you can do as a manager of a creative team, motivating employees through performance celebrations, appreciation, and future envisioning is one of the most important tools you have for turning ’em loose!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a7d42d25323" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Turn ’em Loose #7]]></title>
            <link>https://johnscottbowie.medium.com/turn-em-loose-7-58ce9a630876?source=rss-b2e3a81ab2da------2</link>
            <guid isPermaLink="false">https://medium.com/p/58ce9a630876</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[John Scott Bowie]]></dc:creator>
            <pubDate>Sat, 21 Nov 2020 22:26:33 GMT</pubDate>
            <atom:updated>2020-11-21T22:31:14.841Z</atom:updated>
            <content:encoded><![CDATA[<h3>Turn ’em Loose! #7</h3><h3>Failure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vd6xNth8jwyPisBVNW5Gjg.jpeg" /></figure><p>I once had the honor of leading (and being led by) a team that consistently produced outstanding designs that delighted both our customers and the leadership of our organization — except one time. The one failure involved designing a completely new experience for a cohort of customers who were known to be very diverse and who had an extremely low tolerance for technology. The design solution would have to be both visually engaging and extraordinarily simple.</p><p>After several iterations, the “final” attempt was shared with the organization in a design review. Afterwards, the CTO pulled me aside and as gently as possible told me that he and the rest of the leadership team were disappointed with our design.</p><p>It’s never fun to hear that your stakeholders believe that your team has failed. We were discouraged, but only for an hour or so.</p><p>I called an impromptu meeting with the team and shared the feedback with them. Yes, I know, it’s a cliché in business to recast every setback as an opportunity, but this one really was. I told the team (and believed it myself) that this failure was an opportunity to be heroes. No one — and especially not our competitors — had succeeded in designing a solution that satisfied the big unmet needs of this particular audience. Our team, I told them, was uniquely qualified to be the first. If we could get past this temporary failure and demonstrate to our stakeholders that we had the talent and the persistence to solve this problem, our esteem within the organization would skyrocket.</p><p>We had only a few days — not weeks — before we promised to deliver a new approach to the leadership team. While the mission before us was urgent, the challenge was also liberating. We abandoned all constraints and let our creative juices run wild. Of course, we didn’t produce just one alternative design, but five unique solutions, each with a different theme. To be clear, though, as director of the team, I issued the challenge and backed off, giving the designers the time and space they needed to work. So, when I say “we,” I really mean “they” — the designers deserve all the credit.</p><p>The new designs were a huge success and confidence in our team was restored. In just a matter of days, we had turned what could have been a debilitating failure into a resounding success.</p><p>The mantra in many lean development organizations is to embrace a strategy of failing fast so that the team can understand what works and what doesn’t work and converge on success more quickly. Innovation is produced through a process of rapid experimentation. Yet process-heavy companies still exist that require every project to follow a prescribed sequence of steps in order to reach a “certified” result. These processes (really just well-documented fads) include time-sink activities that delay discovery of workable solutions and kill inspiration and invention. Imagine, for example, if Thomas Edison had been forced to follow Six Sigma in his quest to invent the light bulb. We’d be sitting in the dark today.</p><p>Professor Rosabeth Moss Kanter once said that “in the middle, everything looks like a failure.” Success, too, looks like failure in the middle. We all face failure; we just have to have the persistence and confidence to push past it, to see it as an opportunity for ever greater success. As the leader of a creative team, you do this by reframing the failure as a challenge that your team is uniquely qualified to solve.</p><p>Then turn ’em loose!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58ce9a630876" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>