<?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 Rutuja Jog on Medium]]></title>
        <description><![CDATA[Stories by Rutuja Jog on Medium]]></description>
        <link>https://medium.com/@rjog?source=rss-a0621c8e3259------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YTTEN6Xy7xD5nxDKGMjQXA@2x.jpeg</url>
            <title>Stories by Rutuja Jog on Medium</title>
            <link>https://medium.com/@rjog?source=rss-a0621c8e3259------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:45:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rjog/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[Case study: The user experience of COVID-19 vaccination in Toronto]]></title>
            <link>https://medium.com/design-bootcamp/the-user-experience-of-covid-19-vaccination-in-toronto-433d6a43ff26?source=rss-a0621c8e3259------2</link>
            <guid isPermaLink="false">https://medium.com/p/433d6a43ff26</guid>
            <category><![CDATA[ontario]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[e-governance]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[healthcare-experience]]></category>
            <dc:creator><![CDATA[Rutuja Jog]]></dc:creator>
            <pubDate>Wed, 02 Jun 2021 23:15:31 GMT</pubDate>
            <atom:updated>2021-06-04T05:07:17.450Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p>I recently immigrated to Canada from the US. As a new immigrant, one of the things that intrigued me about Canada was the universal healthcare system managed by the government. Last month, I got vaccinated against COVID-19 in the province of Ontario and the efficiency of that experience was impressive. This is the story of that experience.</p><h4>Background</h4><p>In Canada, the healthcare system comes within the realm of the provincial government. As a resident of a particular province, an individual is able to receive a government-issued health card and is able to thereby receive (mostly) free healthcare. The same applied to the COVID-19 vaccination.</p><h4>Target users</h4><p>Canadian residents over the age of 18</p><h3>Problem Statement</h3><p>How did the government design the experience of COVID-19 vaccination for millions of citizens without causing chaos or confusion?</p><h3>Solution Approach</h3><h4>Prioritization</h4><p>With a limited vaccine supply and a high number of COVID cases, the Ontario government prioritized the vaccination based on “hot spots” — meaning the zip codes that had a high case count. If an individual over the age of 18 belonged to one of the hot spots, then they were eligible to book an appointment online. This controlled the amount of stress imposed on the system.</p><figure><img alt="Map of the hot spot zip codes in the Greater Toronto Area" src="https://cdn-images-1.medium.com/max/1024/1*m3iBwgdBJo59oRqE-mBVlA.png" /><figcaption><a href="https://www.google.ca/maps/d/viewer?mid=1AWpLP99wbhkGdey7MO3AguLAJJSwnaK8&amp;ll=43.77877439709809%2C-78.81805700243856&amp;z=9">https://www.google.ca/maps/d/viewer?mid=1AWpLP99wbhkGdey7MO3AguLAJJSwnaK8&amp;ll=43.77877439709809%2C-78.81805700243856&amp;z=9</a></figcaption></figure><h4>Segmentation</h4><p>The collective number of 18+ individuals in these hot-spot regions would have easily been over a million. Can you imagine an online system to handle the stress of thousands of users clicking a booking button that sent thousands of queries to the server at once? <br>This is how they handled that problem — When a user clicked on the “Book Appointment” button, instead of redirecting them straight onto the booking site, they were brought on an intermediate page and were put in a virtual queue with a progress bar, and the following information displayed on the screen: <br>1. The user’s number in the queue<br>2. The exact number of people ahead of them<br>3. Estimated wait time in minutes or hours<br>4. Approximate time of arrival on the booking site</p><h4>Reliability</h4><p>As the number of people in the virtual queue reduced, the system updated the information displayed in real-time, and the progress bar advanced accordingly. What made this experience great was not the visual design of the page, but the transparency and accuracy of information displayed. E.g. When the system estimated the wait time to be 5 minutes, it actually took 5 minutes or less to be redirected to the booking site. The efficiency of this experience made that site reliable to the users.</p><figure><img alt="The virtual queue interface" src="https://cdn-images-1.medium.com/max/1024/1*2WnFeZGee8YpwGr64CiyMQ.jpeg" /><figcaption><a href="https://www.bttoronto.ca/2021/05/18/ontario-expands-covid-19-vaccine-eligibility-to-18-starting-tuesday/">https://www.bttoronto.ca/2021/05/18/ontario-expands-covid-19-vaccine-eligibility-to-18-starting-tuesday/</a></figcaption></figure><h4>Ease and efficiency of use</h4><p>As the wait time in the virtual queue got over, the users were then navigated to the actual vaccine booking site. The vaccine booking was very intuitive and easy to use. There was a helper link next to every field of information that allowed users to see an example of the type of information that was supposed to be entered in the text fields. <br>The amount of information to be filled in was not lengthy. After filling out the necessary information, users were taken straight to pick a venue and a date for their first and second dose of the vaccine. And that was that.</p><h4>Post booking experience</h4><p>After the vaccine booking was reserved online, the users got an email confirmation from the ministry of health which had a QR code to be used at the time of vaccination, appointment details, and instructions to be followed.</p><h3>The Vaccination Experience</h3><p>The challenge with designing an experience for any event is that it doesn’t just end with an online transaction. There’s a much greater responsibility to execute on the expectation that was set during the online experience; especially when it impacts millions of people. The scale on which this particular experience was executed was truly creditable.</p><p>Going to the venue and getting the vaccine was also an equally seamless experience. There were a good amount of volunteers and healthcare workers, with a helpful attitude and a smiley face, to guide users into the building and to the vaccination booths. There were signages and ramps for accessibility purposes. After a user was vaccinated, the nurse logged in the details of the vaccination and sent an e-receipt with an exact timestamp. <br>Throughout this entire experience, sustainability was also given thought and every part of the documentation was maintained online.</p><figure><img alt="Mass vaccination center in the Greater Toronto Area" src="https://cdn-images-1.medium.com/max/1024/1*F6eTgn8743Z5pftZgkjHeg.jpeg" /><figcaption><a href="https://www.utoronto.ca/news/more-20000-receive-covid-19-vaccine-dose-u-t-mississauga-hosted-clinic">https://www.utoronto.ca/news/more-20000-receive-covid-19-vaccine-dose-u-t-mississauga-hosted-clinic</a></figcaption></figure><h4>Closing Remarks</h4><p>Empathy for the citizens leads to efficient governance. And focusing on designing a user-centered experience always plays a crucial part in taking that governance from ordinary to extraordinary.</p><h4>References</h4><ol><li>MIRIAM KATAWAZI. (April 8, 2021). Full list of Ontario neighborhoods where the COVID-19 vaccine will be available to those 18+.<br><a href="https://toronto.ctvnews.ca/full-list-of-ontario-neighbourhoods-where-the-covid-19-vaccine-will-be-available-to-those-18-1.5379755">https://toronto.ctvnews.ca/full-list-of-ontario-neighbourhoods-where-the-covid-19-vaccine-will-be-available-to-those-18-1.5379755</a></li><li>REGION OF PEEL. Book your appointment.<br><a href="https://www.peelregion.ca/coronavirus/vaccine/book-appointment/#18">https://www.peelregion.ca/coronavirus/vaccine/book-appointment/#18</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=433d6a43ff26" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-user-experience-of-covid-19-vaccination-in-toronto-433d6a43ff26">Case study: The user experience of COVID-19 vaccination in Toronto</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[Design QA: a powerful but neglected step in Agile Development]]></title>
            <link>https://medium.com/design-bootcamp/design-qa-a-powerful-but-neglected-step-in-agile-development-8dce0466c04c?source=rss-a0621c8e3259------2</link>
            <guid isPermaLink="false">https://medium.com/p/8dce0466c04c</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Rutuja Jog]]></dc:creator>
            <pubDate>Sun, 10 Jan 2021 12:37:27 GMT</pubDate>
            <atom:updated>2021-01-10T12:37:27.370Z</atom:updated>
            <content:encoded><![CDATA[<p>“We’ve successfully made the first release of our product and our users are going to love it!” announced the product owner of one of the agile teams I was working with. Since I heard everyone speak so highly of the released work, I decided to see what the developed product looked like. I couldn’t believe my eyes at what I saw. It was misaligned, chaotic, and definitely not user friendly. The interesting thing is that this wasn’t the first time in my work experience where a developed product looked so different from the design.</p><p>In the software world, “Agile” has become the magic term and a preferred solution to product development due to its iterative nature. As a designer, the reason why I like Agile methodology is that it can seamlessly blend the ‘Design Thinking’ framework into product development.</p><figure><img alt="Outcome of design thinking feeding into the agile and getting passed back to design thinking based upon feedback" src="https://cdn-images-1.medium.com/max/850/1*U9EDvVY3NJ2-mNZL2XAvEQ.png" /><figcaption><a href="https://www.researchgate.net/figure/Applied-design-thinking-and-agile-development-methodology_fig4_328861078">https://www.researchgate.net/figure/Applied-design-thinking-and-agile-development-methodology_fig4_328861078</a></figcaption></figure><p>When we think about the integration of design thinking with agile, oftentimes it gets portrayed as if there’s no real overlap between the two, and hence, designers on the agile team are considered as more of supporting resources. Except, there is one major overlap that gets overlooked - the Quality Assurance or QA. Most agile teams will have a dedicated QA resource that is responsible for reviewing the overall quality of the product. However, what gets missed in that review is the quality of coded UI. This is where the designers come in as a part of the mainstream agile process to conduct a design QA.</p><h3><strong>What is design QA?</strong></h3><p>Design QA is a review of the developed UI against design to assess the visual quality of a product by making sure that the design and developed UI match.</p><h3>Why should designers care about QA?</h3><ol><li><strong>To capture usability issues before the release — </strong>The quality of a product shouldn’t just be measured in terms of its technical soundness, because a technically sound product may still have usability issues. If those issues get caught before the release, their repair can be planned efficiently.</li><li><strong>To catch accessibility issues</strong> — Often times designers use high-quality machines such as the Macbook for designing. Macs are known for having an excellent screen resolution. In reality, our users may not use that quality of the screen. Hence, it is important to conduct design QA on a targeted device so that we can catch accessibility issues such as low contrast.</li><li><strong>To maintain a consistent visual language </strong>— Every successful product has a visual language associated with it. This consists of basic design elements like colors, fonts, iconography, etc. When a product is shipped to its users, the users subconsciously start associating these visual elements with the product. Hence, it is important to catch inconsistencies in visual language through design QA.</li></ol><h3>What should designers review for QA?</h3><ul><li>Placement of visual elements such as images, text, buttons, icons on a page and general alignment of those elements to each other</li><li>Fonts — Size, weight, and color of fonts used on a page as well as the line-height of the body copy to ensure readability</li><li>Colors — Making sure that the colors in the coded version use the same hex value as the design in order to ensure accessibility</li><li>Interactions — This includes micro-interaction animations as well as CTA interactions such as hover, active, error, disabled states</li><li>Contrast — Making sure that there is enough contrast between foreground and background and making sure that the contrast passes accessibility standards</li><li>Overall consistency between the design and the coded version</li></ul><figure><img alt="A design and it’s developed version compared side to side. This can be a useful way to directly spot the inconsistencies." src="https://cdn-images-1.medium.com/max/1024/1*u6EJ3Ip2ymRrZuJJl69ABg.png" /></figure><h3>General best practices for conducting design QA</h3><p>Unfortunately, there isn’t a universally used method for design QA. But the following has proven helpful to me in the past —</p><ul><li>Documenting your feedback from the QA review in a way that can be easily handed off to the developers. e.g. using tools such as JIRA, Confluence, Asana</li><li>The feedback from the QA review should use development terms instead of design terms. e.g. using terms such as ‘margins’ and ‘padding’ to indicate spacing.</li><li>Creating a side-by-side comparison of the designed and developed version in Sketch, InDesign, or Word and jotting down the inconsistencies.</li><li>If a product team uses tools such as JIRA, a subtask for ‘Design QA’ can be created for UI epics to ensure that it goes through the designer’s review prior to release.</li></ul><h4>References</h4><ol><li>BRENDAN MAHONY. (Jan 22, 2019). Make design QA official<br><a href="https://uxdesign.cc/make-design-qa-official-5aea540ae907">https://uxdesign.cc/make-design-qa-official-5aea540ae907</a></li><li>ANGELA DELISE. (May 4, 2019). The QA Process in UX Design<br><a href="https://blog.prototypr.io/the-qa-process-in-ux-design-7cd3ffa771ad">https://blog.prototypr.io/the-qa-process-in-ux-design-7cd3ffa771ad</a></li><li>JAMIE O’LEARY. (Dec 5, 2018). Systemizing Visual Design QA<br><a href="https://rangle.io/blog/systemizing-visual-design-qa/">https://rangle.io/blog/systemizing-visual-design-qa/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8dce0466c04c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/design-qa-a-powerful-but-neglected-step-in-agile-development-8dce0466c04c">Design QA: a powerful but neglected step in Agile Development</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[Project Cybersyn: An early attempt at IoT governance and how we can apply its learnings.]]></title>
            <link>https://medium.com/@rjog/project-cybersyn-an-early-attempt-at-iot-governance-and-how-we-can-apply-its-learnings-5164be850413?source=rss-a0621c8e3259------2</link>
            <guid isPermaLink="false">https://medium.com/p/5164be850413</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[cybernetics]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Rutuja Jog]]></dc:creator>
            <pubDate>Sun, 26 Jan 2020 17:23:39 GMT</pubDate>
            <atom:updated>2020-01-26T17:23:39.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/764/1*tGejx9ysxzTqBTF0Ovu9sA.jpeg" /><figcaption><a href="https://99percentinvisible.org/episode/project-cybersyn/">https://99percentinvisible.org/episode/project-cybersyn/</a></figcaption></figure><p>Doesn’t this image look like it came straight out of some 70’s sci-fi movie? This mysterious room, the chairs, the remote controls, all was a part of a real experiment in Chile called the “project Cybersyn”. Between 1971–1973, based on the vision of president Salvador Allende, a cybernetician named Stafford Beer worked on a revolutionary concept that resembled the modern-day Internet of Things.</p><p>Before moving forward, let me take a moment to explain what cybernetics is. The term “Cybernetics” comes from a Greek word meaning “the art of steering”. The steering signifies the use of feedback to reach a goal. Merriam Webster Dictionary defines Cybernetics as <strong><em>“the science of communication and control theory that is concerned especially with the comparative study of automatic control systems”</em> </strong>This definition, though apt, presents Cybernetics as a purely technical domain. Stafford Beer, however, defines it as <strong><em>“The art of effective organization”</em></strong>. Following the thread of that philosophy, Beer focused on applying cybernetics to systems management.</p><p>In mid-1971 Allende government approached Beer for advice on applying his cybernetic theories to the management of the Chilean economy. From there, the project Cybersyn was born. The word “Cybersyn” came from a combination of the words “Cybernetics” and “Synergy”.</p><h3>The Cybersyn System</h3><ul><li>The problem:<br>By the end of 1971, the Allende government had taken control of more than one hundred and fifty enterprises but had no experience on how to manage them efficiently. To design a solution to this problem, Stafford Beer created a cybernetic model of Chile’s economy that captured a wholistic view of components of the economy and the connection of those components to each other. The solution to the problem was aimed at a system that would gather daily production data and predict future trends in economic behavior.</li><li>The system setup:<br>Coming back to the picture of the room - this room was an important part of the project and was meant to be used by high ranking officers. It was hexagonal in shape and contained telex machines, along with big screens on the wall. The room had seven chairs with controls attached to them along with liquor glass holders and ashtrays. The room was hexagonal so that all the stakeholders could see each other and communicate directly to make decisions. Seven stakeholders were expected to use the room because, in case of voting between two situations, the 7th person would cast a final vote.</li><li>The functioning of the system:<br>Katie Mingle, a producer at 99% Invisible describes the functioning of the Cybersyn system as per the following — “a telex is like a typewriter connected to a phone line. So if one factory had a telex, they could type out a message, and send it to another telex. The messages might contain data about shortages in raw material or how many workers were showing up to their shifts. This data would be entered into the computer and analyzed, and subsequently, decisions could be made about how to address problems.”</li></ul><h3>What is so special about “Project Cybersyn”?</h3><p>The concept of this project was very similar to the modern-day Internet of Things. This effort was carried out in an era where neither the internet nor portable computers were functional.</p><p>Cybersyn designed a solution for effective communication and collaboration intended to drive efficient decision making — something that a lot of the organizations still struggle with. Project Cybersyn conceptualized the use of machine learning, where the system would analyze the patterns of production data and predict the future behaviors of the economy. That’s a genius thing to conceptualize in a non-internet era.</p><h3>Applying the Cybersyn framework in the modern context</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xqrYkany0yxbIdESVxJhFw.png" /><figcaption>The functioning of the cybersyn system</figcaption></figure><p>Let’s assume that the Cybersyn project was redeveloped in 2020, which made it an IoT driven AI system. How would that system work to solve a complex problem?</p><blockquote><strong>Speculated Problem</strong>: “9 key countries are on the verge of recession, driving fears the U.S. could follow” — The Washington Post</blockquote><p>Here’s how the Cybersyn system would help in preventing this problem:</p><h4><strong>Part 1: Data collection and pattern analysis</strong></h4><p><strong>1. </strong>The system would collect data of the global economy, politics and economics of countries heading towards recession</p><p><strong>2. </strong>Map out the patterns of the economic behavior of the countries heading towards recession</p><p><strong>3. </strong>Compare the US economy to those countries and analyze the place of the U.S. economy within the global economy</p><p><strong>4. </strong>Based on the variables in the analyzed patterns, predict different scenarios that could impact the U.S. economy.</p><h4><strong>Part 2: Decision making</strong></h4><p><strong>5.</strong> Invite 7 key decision-makers of the U.S. economic affairs in the <a href="https://99percentinvisible.org/episode/project-cybersyn/">Cybersyn room</a></p><p><strong>6.</strong> Present the predicted patterns to them</p><p><strong>7. </strong>The decision-makers will discuss each prediction and brainstorm to vote on the best-case scenario</p><p><strong>8. </strong>The decision-makers would then feed their decision into the cybersyn system</p><p><strong>9.</strong> The system would back-trace the origins of the scenario and suggest courses of action be taken to reach the desired state (the best case scenario)</p><p><strong>10.</strong> The 7 decision-makers would again gather in the Cybersyn room and come up with a strategy to implement the plan to reach the desired state.</p><h3>Conclusion</h3><p>Project Cybersyn was a pioneer in conceptualizing the Internet of Things and Artificial Intelligence. It used the cybernetic framework for problem-solving. In today’s world, we can find solutions to complex socio-economic issues by applying the cybersyn framework.</p><ol><li>KATIE MINGLE. (Oct 04, 2016). Project Cybersyn.<br><a href="https://99percentinvisible.org/episode/project-cybersyn/">https://99percentinvisible.org/episode/project-cybersyn/</a></li><li>EDEN MEDINA. (Apr 27, 2015). The Cybersyn Revolution.<br><a href="https://www.jacobinmag.com/2015/04/allende-chile-beer-medina-cybersyn/">https://www.jacobinmag.com/2015/04/allende-chile-beer-medina-cybersyn/</a></li><li>PAUL PANGARO. “Getting Started” Guide to Cybernetics.<a href="https://www.pangaro.com/definition-cybernetics.html"><br>https://www.pangaro.com/definition-cybernetics.html</a></li><li>World Organization of Systems and Cybernetics<br><a href="http://wosc.co/outstanding-contributors/stafford-beer/">http://wosc.co/outstanding-contributors/stafford-beer/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5164be850413" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A documentation guide for UX Designers]]></title>
            <link>https://uxdesign.cc/a-documentation-guide-for-ux-designers-8a555bb1495a?source=rss-a0621c8e3259------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a555bb1495a</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Rutuja Jog]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 01:08:31 GMT</pubDate>
            <atom:updated>2019-12-17T01:08:31.141Z</atom:updated>
            <content:encoded><![CDATA[<p>Let me start with a question — Which one(s) of the following examples do you think, qualify as documentation?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4fBkmysvbNpGeTE3T1ASZw.png" /></figure><p>All of the above.</p><h3>So what exactly is documentation?</h3><p>According to “Bruce McIntosh”: a designer and an educator featured in the “Smithsonian”<strong> </strong>magazine, “documentation is a form of storytelling”. I strongly agree with that statement. The way documentation relates to storytelling is that they have a beginning and an ending and a cohesive order of events or steps that connect the beginning to the ending. Generally, documentation is meant to be shared with people, just like a story.</p><h4><strong>Attributes of a documentation</strong></h4><p>Successful documentation generally has the following attributes:</p><ol><li><strong>A goal</strong>: documentation should always have a set goal to be achieved. E.g. a goal could be to educate, to spread awareness, to inspire, etc.</li><li><strong>An audience</strong>: the audience is the target users that the documentation is meant for.</li><li><strong>The right medium</strong>: as per the phrase “The medium is the message” coined by Marshall McLuhan, it is important to use the right medium to reach the right audience. E.g. If documentation is meant for a tech-savvy audience, the appropriate medium could be a website or an app.</li><li><strong>An appropriate language</strong>: the language or the tone of the documentation should resonate with the target audience.</li><li><strong>Clarity of content</strong>: since documentation is supposed to be shareable, it is important to document the content in such a way that it gets interpreted as intended.</li><li><strong>Search-ability of content</strong>: documentation should be organized in a way that anyone, who may or may not be familiar with the context, can browse the content by some order.</li><li><strong>A story</strong>: lastly, the content of documentation should tell a story that reveals its process from inception to completion.</li></ol><h3>Why is documentation important for UX designers?</h3><ol><li><strong>It can help build empathy</strong><br>A story of user research or a usability test that contains evidence of user needs and pain points can be an important resource in helping the product stakeholders to empathize with the users.</li><li><strong>It is a tool for effective collaboration </strong><br>One of the key tasks of a UX designer is to collaborate with various product stakeholders. Documentation of a design process is a great way to present the story of the design rationale and to encourage the product stakeholders to add their own perspectives to the story.</li><li><strong>It is also a tool for retrospection</strong> <br>Documentation can be a great source of retrospection of our own work process. We can go back to the beginning and follow the story to understand what we did well and where we need to improve.</li><li><strong>It creates a foundation for innovation</strong><br>No matter who documents the content, anyone can follow the story and add value to it based upon their own research, knowledge, and expertise.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tZMJYG4tm7H2BAzPx4TE0w.jpeg" /><figcaption><a href="https://www.pexels.com/photo/working-in-a-group-6224/">https://www.pexels.com/photo/working-in-a-group-6224/</a></figcaption></figure><h3>What should a UX designer document?</h3><p>Simple answer: EVERYTHING! Everything that is relevant to the design process — starting from the research plan, field research notes, ideation sessions to mood-boards, sketches, prototypes, usability testing sessions. This includes any and every format of document — images, videos, word documents, excel sheets, hand-written notes, post-its, paper prototypes, sketch/photoshop files. I’ll take a step further and say that we can even document any conversations that we had about the context or the content.</p><p>What’s important here is to preserve every little piece of information that we come across or every version of the design that we create. Because, when it is time to compile the documentation, that little presumably insignificant piece of information can add significant value to the story.</p><p>No matter what type of work environment we are in, it is vital to document in a clear and cohesive way, that tells a story of the users and the process aimed at changing their current situation into a preferred one.</p><p>This story was inspired by my learnings from a workshop conducted by Bruce McIntosh: a designer, educator, artist, and a consultant.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a555bb1495a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-documentation-guide-for-ux-designers-8a555bb1495a">A documentation guide for UX Designers</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[Apathy to empathy: Engaging product stakeholders with User Experience]]></title>
            <link>https://uxdesign.cc/apathy-to-empathy-engaging-product-stakeholders-with-user-experience-8af0dc3ce9d2?source=rss-a0621c8e3259------2</link>
            <guid isPermaLink="false">https://medium.com/p/8af0dc3ce9d2</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Rutuja Jog]]></dc:creator>
            <pubDate>Thu, 03 Oct 2019 23:05:13 GMT</pubDate>
            <atom:updated>2019-10-03T23:05:13.726Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Apathy to empathy: engaging product stakeholders with User Experience</strong></h3><p>“What’s the big deal if the buttons don’t have a tap interaction?” asked a developer. “For an employee facing application, why should it matter how the app looks?” Asked a product manager. “We should introduce a new business process and educate the users. There’s no need to ask the users what they want”, claimed business. These are some very real statements that were made around me throughout my career as a User Experience designer.</p><p>We, the UX designers are supposed to be the ones that collaborate with all of the product stakeholders and design an experience that brings an efficiency and effectiveness into the user’s tasks. We are expected to have at least some understanding of programming, product development, business goals etc., and I think that the understanding is necessary for us to build good quality products. While we strive to work around building this understanding, most of our counterparts know very little about User Experience, and why it matters.</p><p>Why does this happen?</p><h3><strong>Lack of awareness</strong></h3><p>One reason why the product stakeholders don’t understand what User Experience Design really is, could be because it is a relatively young field. Even though ergonomics and usability were applied in various products throughout history, Don Norman points out that it wasn’t until the Apple era, that the term “User Experience Design” was used. The intention of the term and its usage was around the human centric aspect of interactions, but somehow over the years it got interpreted to be more about “creating beautiful screens”. As a result, UX is still considered as more of a luxury than a necessity in the product development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*3M984G0gzjS8L0qoEF23Hw.jpeg" /></figure><h3><strong>UX is more than just about devices and screens</strong></h3><p>Not every user experience needs to have a digital interface. I was watching a show on television the other day, where two interior designers take old properties and convert them into out-of-the-box Airbnb rentals. I think that the reason why those rentals turn out to be out-of-the-box is not just because they look pretty, but because they are centered around a great experience. That experience is built by bringing a taste of the local culture into the property. e.g. the designers leave coupons for iconic restaurants or tourist attractions, maps and information on fun things to do around that rental. They try to make sure that at no point should the guest feel lost. Is this all not a part of a great user experience?</p><h3>What is UX anyway?</h3><p>Sometimes User Experience Design is perceived to be closer to Graphic Design, and sometimes to research and analysis, is it neither? Is it both? In order to increase awareness about User Experience, it’s important to communicate with our stakeholders what it really is. This is how I always define User Experience - “An experience that a user gets while interacting with a product or a service, and the impressions of that interaction left in their mind afterwards.” UX as a discipline has evolved from, and hence overlaps with, many others. e.g. Information Architecture comes from library science, A/B testing comes from behavioral statistical analysis, user personas come from marketing and psychology.</p><p>Even though that’s the case, what ultimately matters is, the product or service that we are trying to develop,<br>a. solves a problem<br>b. is usable<br>c. can change the user’s current situation into a preferred one</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mcefrer_jhrZ7jzxQiE1FA.png" /></figure><blockquote>The question is, how can we, the designers make a difference?</blockquote><h3><strong>Communicate the “Whys” to the stakeholders</strong></h3><p>We can use simple interactions with various product stakeholders to communicate the rationale behind our design decisions. For the UI part, I conducted an experiment where, rather than just telling the developers how the design is expected to function, I told them why it should function the way I designed it. This generally led to a greater precision in implementation.</p><h3><strong>Let the users speak for themselves</strong></h3><p>The best resource to speak for a good user experience is the user itself. I found that collecting audio/videos of user feedback on the product experience and presenting it to the product stakeholders is one of the effective ways of conveying the value of UX to them.</p><h3><strong>Help the stakeholders empathize</strong></h3><p>One of the great things about working as a UX designer is that we get an opportunity to empathize with our users by learning about their tasks, goals, needs, desires and pain points. If we could encourage our product stakeholders to empathize through simple things such as observing a usability test or a user research session, then it is possible that they could understand the value of UX and endorse the importance of UX on an organizational level.</p><blockquote>Conclusion - In order to create awareness and understanding about the domain of User Experience, us designers will have to be the advocates and take simple steps to create empathy and build understanding.</blockquote><p><em>Special thanks to Dr. Paul Pangaro and Gissoo Doroudian for their contribution to this article.</em></p><h4>References</h4><ol><li>EMILY STEVENS. (July 12, 2019). The Fascinating History of UX Design: A Definitive Timeline.<br><a href="https://careerfoundry.com/en/blog/ux-design/the-fascinating-history-of-ux-design-a-definitive-timeline/">https://careerfoundry.com/en/blog/ux-design/the-fascinating-history-of-ux-design-a-definitive-timeline/</a></li><li>HOWARD SILVERMAN. (June 15, 2013). Herbert Simon: Design for understanding.<br><a href="https://www.solvingforpattern.org/2013/06/15/herbert-simon-design-for-understanding/">https://www.solvingforpattern.org/2013/06/15/herbert-simon-design-for-understanding/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8af0dc3ce9d2" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/apathy-to-empathy-engaging-product-stakeholders-with-user-experience-8af0dc3ce9d2">Apathy to empathy: Engaging product stakeholders with User Experience</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>