<?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 Sarah Leach on Medium]]></title>
        <description><![CDATA[Stories by Sarah Leach on Medium]]></description>
        <link>https://medium.com/@suresarah?source=rss-61ef3104c003------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PRJ_oKLTza7_3SwddQQ0yA.jpeg</url>
            <title>Stories by Sarah Leach on Medium</title>
            <link>https://medium.com/@suresarah?source=rss-61ef3104c003------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:06:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@suresarah/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[User Journeys]]></title>
            <link>https://medium.com/@suresarah/creating-user-journeys-4f68173d34ff?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f68173d34ff</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-journey-mapping]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 02:35:14 GMT</pubDate>
            <atom:updated>2023-01-16T02:35:45.270Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating a user journey is a crucial step in the product design process. It helps teams to understand the experience of the user, from their initial engagement with the product to the final outcome. By understanding the user journey, teams can identify pain points, opportunities for improvement, and areas where the user may need more support or guidance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cV276ZiGGkqY8zV8pPnZMg.jpeg" /></figure><p>A user journey is a visual representation of the steps a user takes in order to complete a specific task or achieve a specific goal using the product. It includes all the touchpoints that the user has with the product, such as visiting a website, using a mobile app, or interacting with customer support.</p><p>Creating a user journey also helps teams to understand the emotional state of the user at different stages of the process. It allows teams to identify the moments of friction, confusion, and frustration, and design solutions to mitigate those emotions. A user journey also helps teams to identify the moments of delight, satisfaction, and success, and amplify those emotions.</p><p>One of the most important aspects of creating a user journey is to ensure that it is based on real user data. This means conducting user research and testing to gather data on how users interact with the product. This can include surveys, interviews, and usability testing. By basing the user journey on real user data, teams can ensure that the journey accurately represents the experience of the user and that the solutions proposed will address the identified pain points.</p><p>The user journey helps to align the product team with the users’ needs. This can be done by creating user journey maps and sharing them with the entire team. This allows the team to understand the user’s perspective, and to think about the product from their point of view.</p><p>A user journey can be used to inform the wireframing process by identifying the key screens and interactions that the user will need to complete their task. This can help to ensure that the wireframes are designed with the user in mind and that they provide a clear and intuitive path for the user to follow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8mM_KYvjP_CZv8Ekepl1w.png" /></figure><p>Once the wireframes have been created, prototyping can be used to bring them to life and test their functionality. A user journey can be used to inform the prototyping process by identifying the key interactions and animations that need to be included. This can help to ensure that the prototype accurately represents the user’s experience and that it provides a clear and intuitive path for the user to follow.</p><p>Creating user journeys can also help to identify potential usability issues and areas where the user may need more support or guidance. By testing the wireframes and prototypes with users, teams can gather feedback and make adjustments to the design as needed. This allows teams to iterate on the design and create a more user-friendly product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f68173d34ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Personas]]></title>
            <link>https://medium.com/@suresarah/user-personas-d69e21f6c6a1?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/d69e21f6c6a1</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[personas]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 02:25:00 GMT</pubDate>
            <atom:updated>2023-01-16T02:25:00.085Z</atom:updated>
            <content:encoded><![CDATA[<p>User personas are fictional characters that represent a specific segment of the target audience and help teams to understand the needs, goals, and behaviors of their users. Building out user personas can help to ensure that the product is designed with the end user in mind, resulting in a more successful and user-friendly final product.</p><p>The process of building out user personas begins with research. Teams should gather information about their target audience through surveys, interviews, or user testing. This information should include demographic data, such as age, gender, and occupation, as well as information about their goals, pain points, and behaviors.</p><p>Once the research has been conducted, the team should analyze the data and identify common patterns and themes. These patterns and themes can be used to create a set of user personas that represent the different segments of the target audience. Each persona should have a name, a description, and a set of characteristics that are representative of that segment of the audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2HkzS7GBaWtYDN66QAFsEg.jpeg" /></figure><p>It’s important to note that user personas are not meant to be a representation of every single member of the target audience. Instead, they are meant to be a representation of the majority of the target audience, and should be used to guide the product design process.</p><p>When creating the user personas, it’s also important to include empathy in the process. Empathy mapping is an effective technique that can help to understand the user’s pain points, goals, and motivations. Personas should be created with empathy in mind, understanding their feelings, thoughts, and needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUSe-nLNLURqhdWzqVfDhA.jpeg" /></figure><p>Once the user personas have been created, they should be shared with the entire team and used to guide the product design process. Every decision made during the design process should be made with the user personas in mind, ensuring that the product is tailored to the needs of the target audience.</p><p>User personas are a crucial element of the product design process. By researching the target audience, analyzing the data, and creating fictional characters that represent the different segments of the target audience, teams can ensure that the product is designed with the end user in mind. Personas should be used throughout the design process and should be crafted with empathy in mind, to ensure that the product meets the needs, goals and pain points of the user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d69e21f6c6a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Identify Research Areas to Craft a Right-sized Research Plan]]></title>
            <link>https://medium.com/@suresarah/identify-research-areas-to-craft-a-right-sized-research-plan-5bb2770be029?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bb2770be029</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research-plan]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 02:17:01 GMT</pubDate>
            <atom:updated>2023-01-16T02:17:01.032Z</atom:updated>
            <content:encoded><![CDATA[<p>Product design is a complex and multi-faceted process that involves a wide range of different techniques and tools. One of the most important aspects of product design is research, particularly when the problem space is unknown. In order to make informed decisions and create a successful product, it is essential to identify and prioritize key research areas that will provide the knowledge and empathy needed to understand the problem space and the users’ needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uo7JA1UQ2nQs7WOcV8oFbA.jpeg" /></figure><p>One effective approach to researching an unknown problem space is to use “assumption mapping.” This process involves identifying and mapping out the groups’ assumptions around the problem space. By getting all assumptions on the table, the team can gain a better understanding of what is known and what is not known about the problem space.</p><p>Once the assumptions have been identified and mapped, they can then be grouped and sorted on a risk/confidence matrix. The matrix is a tool that helps to identify the key assumptions that are in the high-risk/low-confidence quadrant. These assumptions are the ones that the team should focus on researching first, as they are the most uncertain and have the highest potential impact on the product.</p><p>Tools such as Miro and Figjam can be used to facilitate the option assumption mapping and risk/confidence matrix process. Miro is an online collaboration tool that allows teams to brainstorm, organize, and share ideas visually. Figjam is a digital whiteboard that allows teams to collaborate in real-time and create diagrams, flowcharts, and other visual aids. Both tools are useful for organizing and visualizing information, which can help to make the research process more efficient and effective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*k34pQNMEAxotKq7p06Z5VA.png" /></figure><p>Questions and low confidence assumptions will have emerged and will inform crafting. The goal of the research plan is to gain knowledge and perspectives, understand empathy and pain points, and build confidence in decision making. A well-crafted research plan will help to ensure that the team has the information they need to create a successful product.</p><p>One of the first steps in crafting a research plan is to build out a set of questions that get to the root of what needs to be learned. These questions should be specific, relevant, and focused on understanding the problem space and the users’ needs. For example, instead of asking a general question such as “What do users think of our product?”, a more specific question would be “What specific pain points do users experience when trying to accomplish task X with our product?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/1*vKGi5-E3nQQQkEwB8YdPpA.png" /></figure><p>Once the questions have been defined, it’s important to define success criteria and research methodologies. Success criteria will help to determine if the research goals have been met and provide a way to measure the effectiveness of the research. Research methodologies will determine the methods used to gather data, such as surveys, interviews, or user testing.</p><p>Identifying an appropriate audience and planning to recruit participants is also an important step in crafting a research plan. The audience should be representative of the target users, and the recruitment plan should be designed to reach the right participants. This might include recruiting through social media, online communities, or by reaching out to specific organizations or groups.</p><p>It’s important to remember that a research plan doesn’t need to be overly comprehensive or expensive. A “right-sized” research plan is one that is tailored to the specific needs of the product and the team’s goals. By focusing on the most important questions, recruiting the right participants, and using appropriate research methodologies, teams can gain the knowledge and perspectives they need to make informed decisions without spending excessive time and resources.</p><p>By building out a set of questions that get to the root of what needs to be learned, defining success criteria and research methodologies, and identifying an appropriate audience and plan to recruit participants, teams can gain the knowledge and perspectives they need to create a successful product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bb2770be029" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Comic Sans: History and Accessibility]]></title>
            <link>https://medium.com/@suresarah/comic-sans-history-and-accessibility-c022c338bd75?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/c022c338bd75</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[fonts]]></category>
            <category><![CDATA[comic-sans]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 01:39:38 GMT</pubDate>
            <atom:updated>2023-01-16T01:39:38.842Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Zjpls4t73NY_qgfnb79ebA.jpeg" /><figcaption>Microsoft Bob</figcaption></figure><p>It all started back in the early 1990s, when a designer named Vincent Connare was working at Microsoft. He was tasked with creating a font for a new program called Microsoft Bob. Released in 1995, Microsoft Bob was a program was designed to provide a more user-friendly interface for the Windows operating system, and it was intended to make computers more accessible to first-time users and those who were less technologically proficient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Nw6HYKAhhwBDvmuLZxohQ.png" /><figcaption>Bobbies — Clippy the Paperclip (not pictured) was a part of this group</figcaption></figure><p>One of the main features of Bob was the “Bobbies,” which were animated characters that helped guide users through the program and provided assistance with various tasks. These characters were designed to be friendly and approachable, and they were intended to make the computer feel less intimidating to new users.</p><p>As Connare was working on the font, he came across a comic book that featured a character talking in a speech bubble. The font used in the speech bubble caught his eye and he thought it would be perfect for the new program. He used the comic book font as inspiration and created a new font called Comic Sans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y68VVyMHs5_-wZgrjk7-Sg.png" /></figure><p>Despite its innovative features and user-friendly design, Microsoft Bob was not well-received by the public. Critics complained that the program was too simplistic and that it did not offer enough advanced features for more experienced users. Additionally, the program was criticized for its high system requirements and for its slow performance on older computers.</p><p>When Microsoft Bob was released in 1995, it included the new font. And while the program itself wasn’t a huge success, the font quickly took off and became one of the most widely used fonts in the world.</p><p>But not everyone was a fan. In fact, many designers and typographers have criticized Comic Sans for its informal and playful style, arguing that it’s not suitable for serious or professional documents. This has led to the creation of many memes, jokes and even campaigns against the font.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/168/1*IvU07g-Vgh5k2u3Jm3NKvQ.jpeg" /></figure><p>Despite the backlash, Comic Sans has continued to be used in all sorts of settings, from children’s books and educational materials to advertisements and even official documents. It’s even been used in hospitals, schools and government buildings. The font’s unique style is highly recognizable and can help with cognitive access, especially for people with dyslexia.</p><p>When it comes to accessibility, there are a few key things to consider, such as the font’s size, spacing, and color. These elements can make a big difference in how easy it is for people with visual impairments to read text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_0G61i22cwLvFPyB6klkbw.png" /><figcaption>Many fonts use repeated shapes to create different letters (like ‘p’ rotated to make ‘q’) but Comic Sans uses few repeated shapes creating distinct letters</figcaption></figure><p>One of the things that makes Comic Sans a good choice for accessibility is its large, open lettering. The letters are easy to distinguish from one another, which can make it easier for people with visual impairments to read. The font’s unique style is highly recognizable and it can help with cognitive access, especially for people with dyslexia.</p><p>Another thing to consider is the font’s spacing. Comic Sans has a generous amount of space between letters and words, which can also make it easier for people with visual impairments to read.</p><p>It’s important to consider the color of the text. For people with visual impairments, high contrast between the text and the background can make a big difference in readability. Comic Sans is often used in bold and bright colors, which can help to make the text more visible.</p><p>Comic Sans can be a good choice for accessibility, it’s not a one-size-fits-all solution. There are other accessibility-friendly fonts out there, such as Arial and Verdana. Ultimately, the best font choice will depend on the specific needs of the user and the context in which the text is being presented.</p><p>Comic Sans has a lot of potential as an accessibility-friendly font. Its large, open lettering and generous spacing can make it easier for people with visual impairments to read. It’s bold and bright colors can help to make the text more visible. However, it’s important to keep in mind that accessibility is a complex issue, and different users will have different needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c022c338bd75" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a Mentorship Program]]></title>
            <link>https://medium.com/@suresarah/designing-a-mentorship-program-a09689a3fdd2?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/a09689a3fdd2</guid>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[empowerment]]></category>
            <category><![CDATA[mentor]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Sun, 15 Jan 2023 19:41:41 GMT</pubDate>
            <atom:updated>2023-01-15T19:41:41.793Z</atom:updated>
            <content:encoded><![CDATA[<p>A mentorship program can have a significant positive impact on the future, yet it is often underestimated.</p><p>When people talk about traveling to the past, they worry about radically changing the present by doing something small, but hardly anyone in the present really thinks they can radically change the future by doing something small.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19r0Zia1wOcknEhRyMSwyQ.png" /></figure><p>A well-designed mentorship program can empower individuals and create a ripple effect of positive change in an organization or community. It can provide opportunities for mentees to learn new skills, gain valuable experience, and make valuable connections. In addition, it can also support the growth and development of mentors, who in turn can pass on their knowledge and experience to others. The benefits of mentorship programs can be far-reaching, from improving employee retention and engagement to fostering innovation and creativity. Investing in a mentorship program can be a small step that has a big impact on the future.</p><h4>What does a mentorship program look like?</h4><ol><li><strong>Define goals: </strong>What do you want to achieve with your mentorship program? Are you looking to support the development of specific skills or promote diversity and inclusion? Clearly defining your goals will help you to create a program that meets the needs of your organization and its employees.</li><li><strong>Identify potential mentors and mentees: P</strong>itch the idea to managers, asking them if they have any mentor/mentee candidates who would be interested in participating. Consider the skills, experience, and goals of your employees and match them with appropriate mentors and mentees. You can also consider external mentors from other organizations or industries to bring in fresh perspectives.</li><li><strong>Establish clear guidelines and expectations: </strong>Create a set of guidelines and expectations for both mentors and mentees to follow. This can include things like meeting frequency, communication expectations, and goals for the mentorship.</li><li><strong>Provide training and support:</strong> Provide training for mentors on effective mentoring practices and support for mentees to help them make the most of the mentorship experience.</li><li><strong>Evaluate and adjust: </strong>Regularly evaluate the program and make adjustments as needed. This can include gathering feedback from mentors, mentees, and the organization to ensure that the program is meeting its goals and having a positive impact.</li></ol><h4>Working agreements</h4><p>When participants agree to participate in a mentorship program, they are not only committing to their own growth and development, but also to the growth and development of their mentor/mentee. It means representing yourself authentically, committing to showing up and respecting and valuing each other’s time and contributions. It means pledging to ensure a positive experience.</p><p>Participants in a mentorship program are expected to actively engage in the relationship and take responsibility for their own growth and development. This means being open to feedback, setting goals and working towards achieving them, and actively seeking out opportunities to learn and grow. It also means being respectful of each other’s time and experience and valuing their contributions.</p><p>Participants also agree to be positive role models, leading by example in the workplace and fostering a culture of collaboration, learning, and mutual support. They are expected to be dedicated to the program and actively work to make the most of the experience.</p><h4>Designing the relationship</h4><p>One important step in this process is to take the time to discuss the structure of the relationship, to ensure that both parties have a shared understanding of the process. This includes discussing things like contact and response times, meetings, confidentiality, focus, feedback, goals, and accountability.</p><p>It’s important to set the agenda for the mentoring relationship, with both parties being clear about the purpose and focus of the mentoring. The mentor and mentee should articulate what they hope to get out of the experience. Reflecting and evaluating the relationship every few meetings is also important, to ensure that it is working for both parties. This can be done by asking questions such as “How is this going for you? What’s been helpful? What hasn’t? What could I do differently to make this a more rewarding experience?”.</p><p>When the mentorship is coming to an end, it’s important to have a closeout process where both parties reflect and appreciate what they gained from the experience. Mentees and mentors should clearly articulate their appreciation for the other, and be specific about what they learned and gained from the experience. This will help to ensure a positive end to the mentorship, and will allow both parties to walk away with valuable insights and experiences.</p><h4>Run a pilot</h4><p>A pilot mentorship program can be a great way to test the effectiveness of a mentorship program before rolling it out to a wider audience. The first step is to pitch the idea to managers, asking them if they have any mentor/mentee candidates who would be interested in participating. This could be done through an email, chat, or in-person meeting.</p><p>Once you have a pool of potential mentors and mentees, it’s important to send out a survey to gather information on pairings. This survey should include questions about what the mentee and mentor are hoping to gain from the experience, their availability, and any other relevant information. Then manually pairing mentees and mentors based on the survey responses.</p><p>Once the pairs have been made, it’s important to have a kickoff meeting to go over the expectations and best practices for the program. This should include information on how often the pairs will meet, how they will communicate, and what the expectations are for feedback and progress.</p><p>Periodic check-ins should be scheduled throughout the program, either through chat or surveys, to ask how things are going, if the pairs are still meeting, and if they are finding value in the experience. This can help to identify any issues early on and make adjustments as needed.</p><p>The pilot mentorship program should have an end date, approximately 60 days, where feedback is gathered on the pilot program. This could be done through a retro meeting or survey. After the pilot program, it’s important to take the learnings, iterate on the process, and if all was successful, roll out the mentorship program to a wider audience.</p><p><strong>Mentoring is a great opportunity to deliver a rewarding and potentially life-changing experience for both the mentor and the mentee.</strong></p><p><strong>It takes time and commitment, but it is well worth the effort. 🙌</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a09689a3fdd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prototyping and User Testing]]></title>
            <link>https://medium.com/@suresarah/prototyping-and-usertesting-bc9dba298a52?source=rss-61ef3104c003------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc9dba298a52</guid>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Sarah Leach]]></dc:creator>
            <pubDate>Sun, 15 Jan 2023 19:01:56 GMT</pubDate>
            <atom:updated>2023-01-15T19:03:47.608Z</atom:updated>
            <content:encoded><![CDATA[<p>A crucial step in the design process: prototyping and user testing. Whether you’re creating a new app, website, or product, these practices can make all the difference in the success of your project. Building and testing prototypes helps us learn about user interactions so that we can create more informed user-centered designs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*BwmkQ9fpaU6BOprZy_ncbg.png" /><figcaption>reduce 80–90% of Blue Spaghettin by building components</figcaption></figure><p>A prototype is an interactive environment that simulates how something will function and the experience it creates and can be created with wireframes, mockups or other visual elements. It’s a preliminary model of your design that allows you to test out different ideas and concepts. It’s like a rough draft or hypothesis of your final product, and it gives you the opportunity to make changes and improvements before finalizing the design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apEROKBFrVsu6F33scJOAw.png" /></figure><p>One of the biggest benefits of prototyping is that it helps you to identify and solve problems early on in the design process. By creating a prototype, you can test out different features, layouts, and user flows to see what works and what doesn’t. This can save you time and money in the long run, as it’s much cheaper and easier to make changes to a prototype than to a finished product.</p><h4>Types of Prototypes</h4><p>There are many ranging anywhere between horizontal prototypes and vertical prototypes. A horizontal prototype is a panoramic view for whole systems or subsystems. A vertical prototype shows one function at a time of the final product and is most often used during usability testing because users can give focused feedback about what they see on the screen.</p><p>The choice of prototype will vary greatly depending on goals of testing, completeness of the design, and tools available. Task-based user tests of sketched (low-fidelity) and HTML (high-fidelity) are equally good at uncovering usability issues.</p><h4>Low-fidelity</h4><p>Quickly and inexpensively tests the functionality of a product without getting bogged down in the details of its final appearance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*F1jXOFbiEi9ypxkvdh67qQ.png" /></figure><p>These prototypes are often created using pen and paper and can be easily modified and iterated on, encouraging creativity and experimentation. They typically only include headlines and call-to-action links, but this minimalistic approach allows for more targeted feedback from users. One of the major benefits of low-fidelity prototypes is that they can be created without a lot of technical skill, and they can be tested using a person as a “computer” to manipulate different pages and provide real-time responses to user actions. Low fidelity examples.</p><h4>High-fidelity</h4><p>Tests a product’s usability and user experience as they closely resemble live experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*xBadLUrfZHNN6Fx7JbYpnQ.gif" /></figure><p>These prototypes often have a realistic visual hierarchy, priority of screen elements, screen size, graphics, spacing, and layout, which can help users behave in a more realistic way. Because of their level of realism, high-fidelity prototypes can be used to test the workflow, specific UI components (e.g. mega menus, accordions) and engagement of the product. However, creating high-fidelity prototypes can be time-consuming as it requires getting all the click targets right and making the system respond only when the user interacts with a clickable target. This level of attention to detail is necessary to ensure accurate results and user feedback.</p><h4>Low-fidelity vs High-fidelity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*N8SFYI5OdCwKSVQIm-IKSQ.png" /><figcaption>From NNGroup</figcaption></figure><p>Low-fidelity prototypes are a great option for testing designs because they take less time to prepare and can make design changes more easily during the test. They can be created using directed routes, suspension of disbelief, missed states, and pre-selected options which can be useful in gathering specific information. Additionally, low-fidelity prototypes puts less pressure on users, as they may better understand that you are testing the design and not them, and may feel less obliged to be successful. This can result in more honest and accurate feedback. Low-fidelity prototypes are also beneficial for stakeholders as they recognize that the work isn’t finished yet, and when people see a rough prototype, they don’t expect it to ship tomorrow.</p><p>High-fidelity prototypes include detail and functionality that you would recognize in the finished product, but creating a clickable prototype takes time. High-fidelity prototypes also require that the test facilitator can observe the person interacting with the design, not have a conversation or provide a lot of context with the participant. However, “computer” errors can have a negative impact as users form a mental model of how the system and the research method work. When a design looks very polished, it’s easy for an executive to fall into the trap of saying, “this looks good, let’s make it go live now.”</p><h4>Building the Prototype</h4><p>Regardless of the level of fidelity required, most prototypes will go through a series of stages to ensure a successful design process.</p><p><strong>Empathize: </strong>the goal is to find out what users want and develop an empathetic understanding of the issue. This stage is crucial as it allows the team to gain a deeper understanding of the user’s needs and pain points.</p><p><strong>Define: </strong>the team identifies the needs of users and identifies the most important problems. One or two key features of their product are singled out to focus on in the prototype. This stage helps to prioritize and focus on the most important aspects of the design.</p><p><strong>Ideate:</strong> the goal is to challenge assumptions and develop ideas. This stage is essential as it allows the team to come up with creative solutions to the problem at hand. A tech representative can be involved to make sure they are informed either in this step or the previous.</p><p><strong>Prototype:</strong> the team starts executing the ideas and plans. The level of detail and functionality will vary depending on the level of fidelity required.</p><p><strong>Test: </strong>the prototype is evaluated and further iterations, changes, and refinements are made. This stage is crucial as it allows the team to build, measure, and learn from the prototype.</p><p><strong>Present:</strong> the prototype is presented to different audiences, such as developers, stakeholders, etc.</p><p>These stages are crucial for a successful design process and it is important to go through them in order to achieve a final product that meets user needs.</p><h4>Prototype only what you need</h4><p>When testing a prototype, it is important to map out tasks and have a clear goal for every testing session. Having an actionable plan in place will help you be efficient and solve as many issues as possible. Usability is key when testing a prototype, so it’s essential to pick the right users and find the right group to test your prototype. Quality over quantity is important, so make sure to do multiple iterations, and be ready to adjust as the testing process isn’t always linear.</p><p>One important step in the testing process is to turn off hotspot hinting. You don’t want to bias contributors by showing them where to click. Sharing the correct sharing link is also important, and make sure to tell contributors they are working on a prototype and that not everything might be functional. Give clear instructions when you want contributors to click on something and when you simply want them to respond where they expect to click.</p><p>Another important consideration is to test the experience, by completing a dry run and pilot to make sure you’re getting the feedback you need to answer your research objectives. This will help you evaluate the prototype before the official testing session and make any necessary adjustments to your testing plan. Having a clear plan, the right users, multiple iterations, and testing the experience are key when testing a prototype to ensure that you get the feedback you need to improve your product.</p><p><strong>Your design will be tested, whether you plan for it or not. Test prototypes, whether clickable or static, whether high- or low-fidelity. Whatever prototype you may use, testing it will help you learn about users’ interactions and reactions, so you can improve the design.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc9dba298a52" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>