<?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 Oana Mihail on Medium]]></title>
        <description><![CDATA[Stories by Oana Mihail on Medium]]></description>
        <link>https://medium.com/@oanamihail00?source=rss-893e2102ad58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sVqiquFrEZxrELTqx9v9lg.jpeg</url>
            <title>Stories by Oana Mihail on Medium</title>
            <link>https://medium.com/@oanamihail00?source=rss-893e2102ad58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:29:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oanamihail00/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[What is a discovery workshop and how to facilitate it]]></title>
            <link>https://oanamihail00.medium.com/what-is-a-discovery-workshop-and-how-to-facilitate-it-8f6478338fb8?source=rss-893e2102ad58------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f6478338fb8</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[discovery-workshop]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Oana Mihail]]></dc:creator>
            <pubDate>Tue, 10 Aug 2021 11:10:00 GMT</pubDate>
            <atom:updated>2025-06-20T05:58:31.852Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a discovery workshop?</h3><p>Whether you are building a product and you are a startup founder, a big company owner or you’re approaching a project as an agency, you might hear “We gotta do a discovery workshop” from the product designer.</p><p>Discovery workshops are in my opinion the stepping stones that lead to a better understanding of the product, and they focus on collaboration between teams to help collect information required to begin a project. When you find yourself passionate about a specific idea, it’s easy to get lost in the details — discovery workshops shift the focus to looking at the project in its entirety and ensure all questions about business objectives, user experience, creative and technicalities are covered.</p><p>With this article, I hope to shed some light on this topic and explain the process I go through with our clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CirE748VesRQ5Nc-7Z5ZHw.png" /></figure><h3>Why is a discovery workshop important for your project?</h3><ol><li>No matter how great the idea is, a product can lose its value if not enough thought is given to it in the initial phase of development. You must answer in advance all the necessary questions that may arise from both parties during the app development lifecycle. Doing that in the beginning phase of a discovery workshop provides clarity and saves a lot of time to both parties.</li><li>Through a workshop, complex projects can be easily simplified resulting in a structured roadmap and clear requirements that align with your goals.</li><li>It helps the product team to arrive at a common ground even though they may have varying opinions. It also ensures that the project is completed in the given deadline or in some cases even earlier, as the core functionalities are always prioritized.</li><li>Helps identify potential challenges that may arise later and unravel discrepancies, by highlighting project areas that lack clarity.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8SQpRPQ_qB3JmGpx7D65A.png" /></figure><h3>Why do you need a discovery workshop before working on your product?</h3><p>In general, a discovery workshop usually lasts from 2 to 4 days depending on the scope of the project. Doing so, by the end of it you should have a structured roadmap to accomplish set milestones and goals.</p><p>It typically occurs at the beginning of a project or at the beginning of significant key substages of a project when there is a need to:</p><ul><li>Understand existing research and gather existing knowledge</li><li>Understand stakeholder expectations</li><li>Build a common understanding of the overall project direction, key milestones, and vision for the entire team</li><li>Minimize the risk of building the wrong thing</li><li>Understand who the customers are and how the product will improve their lives</li><li>Define what sets the product apart in the market</li><li>Define what success looks like</li></ul><p>But there are also situations in which conditions within the team make additional workshops necessary.</p><p>For example unaligned stakeholders. They can pull the team’s focus in different directions and away from the original purpose or problem being solved. During workshops, all stakeholders need to be active, vocal, and open-minded in order to make good forward progress. If a participant can’t or won’t make a decision about something, that can derail the entire process. Make sure key stakeholders are ready and willing to contribute.<br>It doesn’t really matter if the project is big or small, a discovery workshop is the most logical first step.</p><p>Small business owners tend to cut out discovery time and skip the workshop, but I observed that even with standard or minimum functionality, with a discovery workshop, you can unravel new frontiers and efficiently build a product.</p><p>For large and complex products, a discovery workshop is a necessity. It helps in defining and assessing the scope of work for every phase and streamlining the entire project at once. Through a discovery workshop, we dive deep, turn challenges into opportunities, and explore new avenues to tackle a problem. It is an essential aspect of an <a href="https://rebeldot.com/agile-methodology-for-startups-and-enterprise-companies/">agile development process</a>.</p><p>Sometimes when a client considers a project to be complex and outlines a big scope of work, a discovery workshop helps us identify which functionalities represent the core of the product for the initial phase. This reduces the scope and cuts costs for the client. In other cases, we unravel too many complexities as opposed to what was predicted which gradually increases the scope of the project.</p><h3>What can be the output of a discovery workshop?</h3><p>Focus on objectives and not only on deliverables.</p><p>A discovery workshop plays an important role in transforming an idea into a usable product. All the planning, scoping, and streamlining are done in the very beginning to witness tangible results.</p><p>Some of the desired and expected outputs from a discovery workshop are:</p><ul><li>Aligned product vision and purpose inside the whole team</li><li>Setting clear, realistic goals for the product</li><li>Define the target audience, user personas, flows, and scenarios,</li><li>Sketch the User Journey mapping</li><li>Aligned vision over the project roadmap and priorities</li></ul><h3>Who can participate?</h3><p>What I think it’s the best thing to do is to include representatives from every specialty like Founders, UX/ product designers, developers, and QA teams; In this way, everyone has a chance to weigh in from different perspectives and everyone feels more engaged with the business and product as a result.</p><h3>Planning the Discovery Workshop.</h3><p>1. Define a goal and output for the workshop.</p><p>Be clear about what you want to achieve, and what the tangible artifacts produced during the session will be.</p><p>2. Decide on workshop participants.</p><p>The power of design workshops comes from a varied perspective, so like I said, make sure you invite a wide range of roles.</p><p>3. Gather needed materials</p><p>The environment can be informal and creative if you are holding the workshop in the office (face-to-face) and plan on using tools such as markers and blank paper for sketching, post-its, and water and/or snacks for longer sessions. When we work remotely with our clients we rely on Miro.</p><p>4. Plan your agenda</p><p>If you are the facilitator of the workshop make sure to have an agenda in place. Plan for a structured sequence of rapid timed sketching cycles, presentation, critique, and choose a prioritization method such as dot voting.</p><h3>Here is an example of how my agenda looks like:</h3><p>It not only aligns the project team, stakeholders and clients but also provides the opportunity to mutually explore the scope of an idea and steer the project in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MNSU2MaWfyQYjavg9ECMSg.png" /></figure><ol><li>Introductions (Workshop intro, attendee intro) — 15 min</li><li>Design process overview (Walkthrough the design process steps, milestone and desirable outcome for each) — 15 min</li><li>Stakeholder interview (About the Client, Business Goals &amp; Objectives)- 45 min</li><li>Assumption mapping (Mapping how desirable, viable and feasible is the product)- 45 min</li><li>Coffee break- 15 min</li><li>Who are our users — 45 min</li><li>What are your user&#39;s goals (Get everyone to know the users better) — 30 min</li><li>Personas — 45 min</li><li>Lunch — 60 min</li><li>Brain dump exercise (Great way to generate a lot of ideas)- 60 min</li><li>Voting — 15 min</li><li>Discuss the results — 15 min</li><li>Coffee break — 15 min</li><li>User journey mapping (Will help generate feature ideas)- 90 min</li><li>Coffee break- 15 min</li><li>Present journey — 30 min</li><li>Final review — 60 min</li><li>Coffee break- 15 min</li><li>Feature prioritization — 90 min</li><li>Coffee break — 15 min</li><li>Define MVP — 90 min</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rd1nFk-PR-IpcazMe6G8IA.png" /></figure><p>Even if a discovery workshop may seem like an added expense on the project’s budget, it is completely worth it. Having a discovery workshop at the beginning of the product will minimize the risk of building the wrong thing, will help everyone involved to understand who the users are and how the product will improve their lives and it will lead to defining clear, realistic goals for the product. Once you got through this stage, you can then move on to <a href="https://rebeldot.com/how-to-build-a-minimum-viable-product/">building an MVP</a> and test the assumptions and insights gathered in this initial stage of the process.</p><p>With this article, I hope to shed some light on this topic and explain the process I go through with our clients.</p><p>If you’re wondering how to build better, smarter products and avoid team confusion, this is where I’d tell you to start. Let’s connect: <a href="https://valll.studio/">https://valll.studio/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f6478338fb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: Helping gymnasium pupil stay connected]]></title>
            <link>https://oanamihail00.medium.com/ux-case-study-helping-gymnasium-pupil-stay-connected-6861f1a3c0d1?source=rss-893e2102ad58------2</link>
            <guid isPermaLink="false">https://medium.com/p/6861f1a3c0d1</guid>
            <category><![CDATA[get-connected]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[pupil]]></category>
            <category><![CDATA[online-schooling]]></category>
            <dc:creator><![CDATA[Oana Mihail]]></dc:creator>
            <pubDate>Mon, 09 Nov 2020 08:19:28 GMT</pubDate>
            <atom:updated>2020-11-09T10:51:52.578Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nKhdDjrwgDcGUOI3kbB7jw.png" /></figure><h4>Why I accepted this challenge?</h4><p>In short, this is a very hot topic right now that I didn’t know anything about, so it was an interesting exercise for me. I wanted to gain more knowledge and try to find a solution for this one while experimenting with some UI screens as well. The challenge was timeboxed, so I had one week to complete as much as I could.</p><h3>My Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KfxSb6qoQ7P8trd3-F5txw.png" /></figure><h3>1. Discovery</h3><p>I started the research to gain a broader understanding of the problem at hand and to have a solid starting point for my product. I found lots of research papers and articles about online schooling, during the pandemic situation.</p><p>My audience is formed by pupils in the gymnasium, so I knew that I wanted to create something really fun, a way for them to interact with each other in a different manner than the classical chat tools.</p><p>They are between <strong>10 –13 years old.</strong> This means they are both <strong>pre-adolescents and adolescents. </strong>From the psychologic point of view, they can be both <strong>introverts and extroverts</strong>, so their idea of fun interactions will differ.</p><p>I wasn’t aware of the struggle that parents have to keep their kids entertained, so I started reading articles.</p><blockquote>“This situation may make parents feel differently about social media than we did in the past, when we cast a jaundiced eye on it,” says clinical psychologist- Lisa Damour</blockquote><p>Since I don’t have access right now to gymnasium pupils to have <strong>user interviews</strong>, I found an alternative way. I started looking at vlogs on Youtube and find out from the kids, how they are experiencing this situation.</p><blockquote>“I don’t like being away from school because there is really nothing to do, but with my friends there is FaceTime and stuff.”</blockquote><h4>My key findings:</h4><ul><li>The majority of kids spend more than 6 hours/day online;</li><li>Some parents don’t have help/sitters and work from the office and they don’t know how to keep the adolescents entertained;</li><li>Negative side effects of online schooling include: <strong>irritability, irascibility, feeling isolated, feeling inferior, low self-esteem;</strong></li><li>Most used platforms of communication between pupils are Whatsapp, Facebook, and Facetime;</li><li>There are far more websites supporting professors and teaching them how to hold online classes, then websites supporting pupils;</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDoPy5YMAysHUbJASDf0ig.png" /></figure><h3>2. Define the problem</h3><p>I usually use this step to fully understand the goal of my product and to articulate the main problem(s), and provide a clear objective to work towards.</p><p>I used the <strong>empathy map</strong> method to capture and synthesize my findings. The map has four major areas in which to focus my attention and this exercise provided me an overview of a persona’s experience that I created later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODMxTPsvhhdvSnVpNtT3AQ.png" /></figure><p>At the end of this exercise, I knew that I wanted to create a different “get to know each other” experience for the pupils. They already have a lot of chat platforms, so I needed to think about an alternative solution that will engage them to interact. So, What brings people together? Common interests of course! Creating a “club or group” of people sharing the same interests like reading, sports, and gaming, was the idea that I gravitated around.</p><h3>3. Persona</h3><p>I wanted to understand the users, their motivations, their requirements, and build a user-centered product. That’s where personas help to keep in check the concerns of a user at the forefront of every design decision.</p><p>I created two different personas, based on the findings I have:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HwyzWdEKFLXylIzOO2XjbQ.png" /><figcaption>Icons source: <a href="https://www.flaticon.com/">https://www.flaticon.com/</a></figcaption></figure><h3>4. Ideate</h3><p>The <a href="https://www.nngroup.com/articles/ux-ideation/">Nielsen Norman Group</a> defines ideation as “the process of generating a broad set of ideas on a given topic, with no attempt to judge or evaluate them.”</p><p>In the ideation phase, I came up with as many ideas as I could. Some of those transformed into solutions for my design challenge. At that stage, the focus was on quantity of ideas rather than quality.</p><p>There are a lot of methods of ideation, I chose two of them: First, I used the How-Might-We exercise as a way to frame my ideation, and to help launch a brainstorming session. The idea here is to create questions that inspire meaningful and relevant ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KyqqBPcn0naxPh7kLim_Tw.png" /></figure><p>After this, I continued the ideation process by playing around with the Brain Dump exercise. This forces you to think outside the box and it empowers innovation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NY4RN05oWXkBzPCPyUgfJg.png" /></figure><p>I continued my process by defining the features, so I would have a clear vision before starting to sketch the wireframes. Here is a list of the main features I thought about:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GLjYs7jNMS3JzJS5yp1vjw.png" /></figure><p>I wanted to deliver the most effective result, so I focused on building a <strong>user flow, </strong>and I placed the user needs in the heart of the design process. While providing clarity, user flows also provide a suitable structure and hierarchy. Some of my features are TBD at this point, but in the given time this is the main flow I came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCFxhDkILuaemKsRgcnj-g.png" /></figure><h3>5. Prototype</h3><p>Next, I created low fidelity screens. I sketched my ideas with a pen on paper first, and then I moved on to digital wireframes.</p><p><strong>This step brings me clarity: </strong>Creating<strong> </strong>a<strong> </strong>wireframe helps in the execution of concepts and ideas into a solid layout. This step helped me brainstorm and explore alternative possibilities. I focused on adjustments for the essential information and navigation elements on the page without getting distracted by visual appeal and aesthetics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Ep-qhrG5hHQda-4slJyuw.png" /></figure><h3><strong>6. Test</strong></h3><p>Since this was a time-boxed challenge and we have the pandemic context going on, I did not have enough time or proper audience to test my designs, so even if this is a very important step, this is something that will remain a work in progress.</p><h3>7. High fidelity screens — The UI</h3><p>I wanted to explore some styles so I came up with a light and a dark theme for the UI. I knew I wanted to create something that will be <strong>clear, consistent, simple, and user-oriented</strong>, so I started playing around.</p><p>The dark themes are super popular with adolescents and also they minimize eye strain, so for a pupil that spends most of the time online looking on a device, this will be a good thing.</p><p>What I learned while exploring is: <strong>avoiding pure black and white text</strong>. This contrast can be painful to look at. Instead, I played around with dark and light greys.</p><p><strong>My second finding was that </strong>colors are actually perceived differently depending on their background. Finding some colors that work well on both white and dark theme was a challenge. I needed to test the contrasts for both backgrounds a few times before deciding on a color palette that worked.</p><p>This is a sneak peek of the UI:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4L66KuUWXvrposfQ8ME6w.png" /></figure><p><strong>Next steps</strong>:</p><ul><li>I have to schedule a few usability sessions to determine what issues people are encountering while interacting with the prototype, to gather unbiased feedback, and get insights that will help me create a better overall user experience for my audience. There is still plenty to iterate on and improve the usability of this concept.</li><li>Now I’m working on creating the “Coach” feature.</li><li>I’ll update this post with my findings after the sessions.</li></ul><p>If you want to get involved in the usability sessions, or if you have any ideas on how to improve this concept, or if you just want to say hi, <a href="https://www.linkedin.com/in/oana-mihail-8696208a/">let’s chat</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6861f1a3c0d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Change Blindness” in UX]]></title>
            <link>https://oanamihail00.medium.com/change-blindness-in-ux-8c2aa4058e7c?source=rss-893e2102ad58------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c2aa4058e7c</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Oana Mihail]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 15:36:09 GMT</pubDate>
            <atom:updated>2020-11-09T11:07:10.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*tkbTRo2BpVo_LiC_QNfMoA.png" /><figcaption>Image Source: Freepick</figcaption></figure><p>There is a strong discrepancy between the amount of information being transmitted and the amount of information our brains have the capacity to process.</p><p>I have always been fascinated by the way the human brain works and I also think that being familiar with cognitive science is a key skill of any designer. In the digital world, there is a huge number of websites, apps, articles, and advertisements trying to get <strong>our attention</strong>.</p><p>People are programmed to focus their <strong>attention</strong> on anything that is <strong>different or new</strong>.</p><p>As you are reading this article, there are numerous sensations, sights, and sounds going around you. The traffic sounds, other people talking around you, the warmth of the room or maybe the memory of a conversation you had earlier today.</p><p>So, depending on your ability to <strong>focus</strong>, the brain can induce a specific blindness that makes you miss the changes happening in your visual field.</p><p>In one experiment, participants were shown an image that was changed during a brief blank interval in the visual scene. The researchers found that when there is a brief break in the visual scene, people find it more difficult to detect changes. This is called<strong> Change Blindness.</strong></p><p><strong>Change Blindness </strong>is a common phenomenon in the digital world, where visual elements can appear and disappear or change their label almost instantaneously. For <strong>example</strong>, observers often fail to notice major differences introduced into an image while it flickers off and on again, like a page that refreshes. In many cases, the changes in the visual seem so big, that they seem impossible to miss. Yet when attention is directed elsewhere, people are capable of missing both minor and major changes that take place right in front of them.</p><p>Change Blindness is rooted in the human brain’s instinctual ability to filter out unnecessary information and stimuli. Basically, any time a new visual element is introduced to an existing display, it is at risk of being ignored.</p><p>Here is a popular example about how <strong>Change Blindness </strong>works, on the Vans.com mobile website. If a visitor selects a size that is not available, the label of the “<em>Add to Cart”</em> button changes to say “<em>Out of Stock”. </em>This slight, but important, change in the label doesn’t stand out, when the rest of the display stays the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/0*dnJuej_42EOaWV5C" /><figcaption>Source: the Holy Google.</figcaption></figure><p>This is happening because:</p><ul><li>One: the user’s attention is focused here on the Size and Quantity fields;</li><li>Two: The <em>“Out of Stock” </em>label was overlooked because it looked too much like the <em>“Add to Cart”</em> label, and was too far from the user’s attention was focused;</li></ul><p>Although the design is perceived by our senses (vision, touch, hearing), it is immediately processed by our brain. As designers, we have the power to guide the human mind during and even beyond the interaction with the product by using some key steps in our design process:</p><ol><li><strong>Make your page easy to scan</strong></li></ol><p>Remove clutter and make the page as easy as possible for your user to achieve their desired outcome, rather than trying to find actions or buttons. An important part of the design is making it highly usable for the targeted users and allowing for extra functionality to be discovered as it is needed. This will help you fight the <strong>change blindness</strong> and will help you increase the conversion rate.</p><p><strong>2. Minimize visual interruptions</strong></p><p><strong>Avoid page refreshes whenever possible. </strong>This will cause an <strong>Interruption</strong> in the user’s visual perception and lead to an unnecessary shift in their attention.</p><p><strong>3. Provide smooth, continuous feedback</strong></p><p>Keep the users informed about what is going on within reasonable time, without leaving them wondering and waiting. You can do this through: loading bars, spinners, active state of a button, scroll flag, feedback sounds etc. Also, make sure the feedback is delivered in a natural place, where the user expects it, so it can be followed and understood.</p><p><strong>4</strong>. <strong>Use appropriate visual emphasis</strong> for significant new elements (such as contrast, size, and padding) to ensure they are noticeable. Use data from <strong>multiple sources</strong> to get a more accurate picture; combining the insights you gain from your experience and knowledge, your quantitative web analytics, and qualitative sources (like surveys, heat maps, sessions replays, or usability tests).</p><p><strong>5. Rely more on Recognition rather than Recall</strong></p><p>Minimize the user’s memory load by making actions, elements, and options visible. Therefore, the users won’t need to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily regained.</p><p><strong>6</strong>. <strong>Focus on</strong> <strong>Aesthetic and minimalist design</strong></p><p>The less elements on the screen, the more potent the remaining ones are. Focus on using only relevant information and avoid every extra details or element that could be irrelevant and that will cause an unnecessary shift in user’s attention.</p><p><strong>7</strong>. <strong>Build products with Consistency and Standards</strong></p><p>Make sure that the users won’t have to wonder whether different words, labels, colours, or actions mean the same thing.</p><p><strong>8. Prevent errors</strong></p><p>Try to either eliminate error-prone conditions or check for them and provide users with a confirmation option before they commit to the action. Even better than good error messages is a product that prevents a problem occurring in the first place. This will help you keep the users focused.</p><p><strong>9. Use good contrast</strong></p><p>Use tools to measure the contrast you are using. Low color contrast creates legibility problems. The basics of color contrast are easy to understand: a higher contrast between text color and the background color is better for legibility.</p><p><strong>10. Mind the Typography and build a visual hierarchy</strong></p><p>Typography has a huge effect on the Mood and attention of users and also, by using the right typography, we can improve the user engagement.</p><p>This is more than selecting fonts. It is the study of how humans read, perceive, how they recognise words and how the brain processes the information.</p><p><strong>So why should anybody care about Change Blindness?</strong></p><p>Change blindness is a one of the psychological phenomenon that affects user perception in this digital Universe. As designers, we have the power to control the human mind during and even beyond the interaction with the product and bring more value to the digital world by using our knowledge on the cognitive science and start improving the digital world.</p><p>Change blindness plays an important role in the way users understand and look at websites. It’s important to notice that people often fail to detect changes to a visual scene and why users don’t see what you think they actually should see. By being aware of this cognitive phenomenon and understanding how can avoid it can aid you creating your strategy in your design process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c2aa4058e7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>