<?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 Sara Ghasemi on Medium]]></title>
        <description><![CDATA[Stories by Sara Ghasemi on Medium]]></description>
        <link>https://medium.com/@sara.gh1997sp?source=rss-5b121c383c5b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6S_mW16i0RExH8XYrEHt6g.jpeg</url>
            <title>Stories by Sara Ghasemi on Medium</title>
            <link>https://medium.com/@sara.gh1997sp?source=rss-5b121c383c5b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:39:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sara.gh1997sp/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[Creating a Smooth Login & Sign-Up Experience]]></title>
            <link>https://medium.com/@sara.gh1997sp/creating-a-smooth-login-sign-up-experience-09c54c796276?source=rss-5b121c383c5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/09c54c796276</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[clarity]]></category>
            <category><![CDATA[login]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Sara Ghasemi]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 13:01:04 GMT</pubDate>
            <atom:updated>2025-12-13T13:01:04.323Z</atom:updated>
            <content:encoded><![CDATA[<p>How many online stores have you signed up for so far?</p><p>Have you noticed that you can spend hours browsing products and completely lose track of time — but the moment you’re asked to sign up and enter your information, the process suddenly feels long, difficult, and exhausting?</p><p>Have you ever left a website at exactly that point?</p><p>Designing a simple and frictionless login and sign-up flow is critical for e-commerce websites.</p><h3>Redesigning the Login &amp; Sign-Up Flow</h3><p>When redesigning a login and registration form, attention to detail is everything. Tools like <strong>Microsoft Clarity</strong> or <strong>Hotjar</strong> can help identify friction points and reveal where users struggle.</p><p>Before diving into the redesign, it’s worth mentioning that the login and sign-up dialog in <strong>Digishehr</strong> already had several strong points:</p><ul><li>Consideration of the on-screen keyboard space</li><li>Use of a numeric keypad</li><li>Support for both Persian and English digits</li><li>Separating the phone number visually for easier scanning</li><li>Accepting terms and conditions as an informational statement instead of a checkbox</li><li>Using a 4-digit verification code to shorten the sign-up process</li></ul><p>For a deeper look at why these details matter, you can read the article <em>“A Case Study of PuffFilm’s Login Page Design.”</em></p><p>But the key question remains: <strong>how can we make this experience even better?</strong></p><p>To answer that, we first needed to identify the existing problems.</p><h3>Story 1: Confusion Between Login and Sign-Up</h3><p>In Digishehr, a single dialog was used for both login and registration. While combining these flows has benefits — such as consistency and reduced UI complexity — it can also be confusing, especially for new users.</p><p>Users might wonder:</p><ul><li><em>“Have I already signed up before? Why am I seeing this?”</em></li><li><em>“Which phone number should I enter?”</em></li><li><em>“Am I registering again even though I already have an account?”</em></li></ul><p>All of this confusion can be resolved with a clear and explicit title like <strong>“Login or Sign Up.”</strong><br> Once the user enters their phone number and the system detects whether the number is already registered, the dialog title updates to either <strong>“Login Verification Code”</strong> or <strong>“Sign-Up Verification Code.”</strong></p><p>This makes the user’s current state completely clear and aligns with the <a href="https://www.nngroup.com/articles/ten-usability-heuristics/"><strong>first Nielsen Norman heuristic</strong></a><strong>: Visibility of system status</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqQ8g5sqhGnU6bXfBCBLPg.png" /><figcaption>Introducing the Dialog with a Clear Title</figcaption></figure><h3>Story 2: Difficulty Closing the Dialog</h3><p>When users want to close a dialog, they instinctively look for a close (✕) icon. If it’s not obvious, they may not understand how to exit.</p><p>At the same time, when users are entering a verification code, accidental taps on the blurred background can close the dialog unexpectedly — which is frustrating and may cause drop-off during registration.</p><p>To solve this, the dialog was redesigned so that:</p><ul><li>Clicking on the background no longer closes it</li><li>The dialog can only be closed using the close (✕) icon</li></ul><p>This change supports <strong>Nielsen Norman’s third heuristic: User control and freedom</strong>, ensuring users don’t lose progress unintentionally.</p><h3>Story 3: Problems Receiving the Verification Code</h3><p>Sometimes SMS verification codes are delayed due to mobile operator issues. After waiting two minutes and tapping “Resend,” users may still be unable to log in.</p><p>According to <strong>Nielsen Norman’s seventh heuristic (Flexibility and efficiency of use)</strong>, offering alternative methods is essential in these cases. One helpful solution is adding <strong>“Receive code via phone call.”</strong></p><p>However, if options like:</p><ul><li>“Login”</li><li>“Resend SMS”</li><li>“Receive code via call”</li></ul><p>aren’t prioritized correctly, the experience can quickly become confusing.</p><p>In this flow, entering the correct OTP automatically logs the user in — no “Login” button is actually required.</p><p>So I tested two design variations:</p><ul><li><strong>Version A:</strong></li><li>Removed the “Login” button</li><li>Made “Resend SMS” the primary action</li><li><strong>Version B:</strong></li><li>Kept the “Login” button</li><li>Displayed “Receive code via SMS” and “Receive code via call” with equal priority</li></ul><p>Usability tests conducted in <strong>Maze</strong> showed better click behavior and higher conversion rates in <strong>Version A</strong>.</p><p>In real user tests, participants were asked:<br> <em>“If you don’t receive the SMS after requesting the code, what would you do?”</em></p><ul><li>In Version A, most users chose the <strong>phone call</strong> option immediately.</li><li>In Version B, users repeatedly clicked the SMS option again and then searched for alternatives.</li></ul><p>Another clear issue was users clicking on the text <strong>“Resend”</strong>, which wasn’t clickable at all — a strong signal of confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4n9WzmD-ZyAeU_pFhYHBnQ.png" /><figcaption>Providing the Option to Receive the Code via Call</figcaption></figure><p>Overall, on the <strong>first retry</strong>, assuming the SMS wasn’t delivered or the sender number was blocked, we resend <strong>the same code from a different number</strong> to avoid confusion if both messages arrive.<br> On subsequent attempts, a <strong>new code</strong> is generated.</p><p>By offering phone calls as an alternative, we introduce a genuinely different fallback method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTjJAkyVWsI5Geeaxs-lug.png" /><figcaption>Retry Logic for Receiving the Verification Code</figcaption></figure><h3>Hypothesis &amp; Measurement</h3><p>In <strong>Phase 1</strong>, we implemented:</p><ul><li>Clear dialog titles</li><li>Improved dialog closing behavior</li></ul><p>In <strong>Phase 2</strong>, we added verification via phone call.</p><p>To evaluate Phase 1, we focused on the <strong>health of the login and sign-up funnel</strong>.<br> The hypothesis was that:</p><ul><li>Misclicks would decrease</li><li>In an optimal state, clicks on:</li><li>Phone number input</li><li>“Get verification code” button</li><li>OTP input<br> would be roughly equal — indicating a healthy conversion flow.</li></ul><p>In the chart below, click data from two one-week periods is compared. The results show that clicks on the “Get code” button and the phone number input became much closer.</p><p>Previously, higher clicks on the button compared to the input suggested issues such as:</p><ul><li>Clicking without entering a number</li><li>Clicking with an invalid number format without noticing the error</li><li>Returning from the OTP screen assuming the code would be resent</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AF5TKinTaLNBhSZsLaTIpA.png" /><figcaption>Changes in User Click Behavior</figcaption></figure><p>Clicks on the <strong>OTP input field</strong> — the main goal of this dialog — increased, indicating fewer errors and less confusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXASNm6EhsTutai4RocjkA.png" /><figcaption>Reduction in Misclicks</figcaption></figure><h3>Final Thoughts</h3><p>Designing a simple and seamless login and sign-up experience has a direct impact on the success of online stores. When friction points are identified and user experience is optimized through real testing, user satisfaction increases — and so does conversion rate.</p><p>The key takeaway is simple:<br> <strong>details matter</strong>, and continuous improvement based on real user behavior is essential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09c54c796276" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resume Redesign with the Motto “Think Again”]]></title>
            <link>https://medium.com/@sara.gh1997sp/resume-redesign-with-the-motto-think-again-b05af2290820?source=rss-5b121c383c5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b05af2290820</guid>
            <category><![CDATA[resume]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[heatmap]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Sara Ghasemi]]></dc:creator>
            <pubDate>Sun, 30 Nov 2025 12:53:42 GMT</pubDate>
            <atom:updated>2025-11-30T12:53:42.277Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>-</strong> “It’s better if you add your portfolio link <em>inside</em> the resume.”<br><strong>+</strong> “I did! I even added a black button at the top — that <em>is</em> the link!”</p><p>This was an actual conversation between me and a friend…</p><p>We’ve all heard that design is subjective — but there’s one solid rule:<br> <strong>If a design needs to be explained, it’s not a good design.</strong></p><p>So I decided to send a screenshot of my resume to a few people and ask what they noticed and what stuck with them in the first five seconds.<br> And specifically, I asked them: <strong>“Did you see my portfolio link?”</strong><br> The answer was: <strong>No.</strong><br> So clearly, something was wrong… maybe even more than one thing.</p><h3>Version 1 of the Resume</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ybkuLYKsCM0zcgh8gPNGjw.png" /></figure><p>My assumptions were that the issue was in one (or all) of these areas:</p><ol><li>Attention to user eye-tracking patterns</li><li>Color palette</li><li>Empty/white space design</li></ol><p>.</p><p>.</p><p>.</p><h3>1. Eye-tracking patterns</h3><p>You’ve probably read about this — if not, definitely look it up.<br> Since my resume is in English, reading patterns go left to right.<br> Meaning: placing the portfolio link on the right side made it almost invisible.<br> So I changed its position.</p><h3>2. Color palette</h3><p>My resume mainly used gray plus a single red line to highlight work experience.<br> But gray is a dead, neutral color; it doesn’t draw attention unless the whole page uses <em>only</em> gray so layout alone can guide visual focus.<br> That wasn’t happening here, so I changed the colors.</p><h3>3. White-space design</h3><p>Think of it like Japanese painters :)<br> You need to give the viewer’s eyes room to rest and move around.<br> When everything is packed tightly into rigid grids and columns, a resume starts to look like a newspaper.<br> If something needs emphasis, give it some breathing room.<br> For example, after repositioning the portfolio link, more space naturally appeared next to it and my work experience section.</p><p>In the end, I tried placing the portfolio link in several different colors.<br> Then I used the trial version of an AI testing tool called <strong>Clueify</strong> to predict where users’ focus would land.</p><h3>Heatmap test</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yDZNUl85iBjcAe5I94PSNQ.png" /></figure><p>The results helped me decide to go with <strong>orange</strong>.</p><p>If you were me, what color would you use?<br> Or do you have a completely different solution in mind?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*orbBvh3MyoHCI8No9jZAeQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b05af2290820" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Warning Colors Aren’t Always Orange]]></title>
            <link>https://medium.com/@sara.gh1997sp/warning-colors-arent-always-orange-273ea061ca8a?source=rss-5b121c383c5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/273ea061ca8a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[warning]]></category>
            <dc:creator><![CDATA[Sara Ghasemi]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 14:16:43 GMT</pubDate>
            <atom:updated>2025-11-29T14:16:43.674Z</atom:updated>
            <content:encoded><![CDATA[<p>When Brand Language Collides with UX Color Semantics.</p><p>A few weeks ago, I got into a surprisingly heated debate with the graphic designer on our team.</p><p>From a UX perspective, I insisted that warning and alert messages should use the classic attention-grabbing colors — orange and yellow.</p><p>But he pushed back:<br> <strong>“We can’t use orange or yellow. Our brand color <em>is</em> yellow. If we use it for warnings, users will think it’s a CTA. It mixes our conversion color with a danger signal.”</strong></p><p>My first instinct?<br>He was overreacting.</p><p>But the deeper we analyzed the issue, the clearer it became:<br> <strong>He was at least half right.</strong></p><p>As product designers, we crave structure and consistency. Red means error. Green means success. Orange means warning. These color semantics help create interfaces that feel predictable and understandable.</p><p>But in real products, things aren’t that simple.</p><p>When universal UX rules collide with brand colors, product context, or users’ mental models, one truth becomes obvious:</p><p><strong>A rule is only a rule as long as it’s useful.<br> And warning colors aren’t always orange.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*xzEhEau-iYbHIqQNS5KGig.png" /></figure><h3>The Cognitive Clash: Color Semantics Overload</h3><p>Our discussion was a textbook example of a phenomenon I call <strong>Color Semantics Overload</strong>.</p><p>From the UX point of view, I argued:<br> <strong>“Warnings must be orange or yellow to grab attention.”</strong></p><p>The graphic designer argued:<br> <strong>“Our brand’s core color is yellow. Using it for warnings confuses the user — they’ll interpret a warning as a positive action.”</strong></p><p>Both arguments were valid:</p><ul><li><strong>The UX perspective:</strong><br> Alerts should be visually and semantically distinct.</li><li><strong>The brand perspective:</strong><br> The conversion color (CTA) should never overlap with danger or caution cues.</li></ul><p>When one color (like yellow) tries to carry two conflicting meanings — <br> <strong>1) positive action<br> 2) caution</strong><br> — both meanings weaken. The interface becomes cognitively noisy.</p><p>The user is left wondering:<br> <strong>“Is this something I should click… or something I should be careful about?”</strong></p><p>And ambiguity is the enemy of good UX.</p><h3>The Smart Fix: Separate Meaning Through Context and Intensity</h3><p>You don’t fix this clash by forcing brand colors or fighting color psychology.<br> You fix it by adjusting <strong>context, contrast, and hierarchy</strong>.</p><p>A great example is Binance — whose entire brand identity revolves around yellow.</p><p>Instead of painting warnings yellow, they:</p><h3>1. Reserve brand color for CTAs and value</h3><p>Yellow is sacred. It’s used for action, money, energy — not danger.</p><h3>2. Downgrade warnings to a neutral background</h3><p>Mild alerts use gray or other neutral tones instead of full-color blocks.</p><h3>3. Add meaning through an accent icon</h3><p>A small yellow icon on a neutral background communicates “attention” without hijacking the semantic role of the brand color.</p><p>This approach keeps the interface clean, reduces cognitive load, and preserves brand meaning.</p><h3>Why More Color ≠ More Attention</h3><p>In a UI saturated with warm brand tones (yellow/orange CTAs), adding another orange alert doesn’t increase visibility.</p><p>It creates <strong>visual noise</strong>.</p><p>Sometimes the most attention-grabbing thing in a colorful UI… is a patch of gray.</p><p>Neutral backgrounds work beautifully for medium-level warnings because they:</p><ul><li>clearly differentiate alerts from energetic CTAs</li><li>avoid mixing brand identity with danger signals</li><li>preserve red for truly critical errors (security, payments, password issues)</li></ul><p>This is hierarchy, not guesswork.</p><h3>Maturity in Design Means Breaking Rules — Intentionally</h3><p>Product design isn’t a rigid science.<br> It’s a balancing act between logic, psychology, and brand identity.</p><p><strong>Warning colors aren’t always orange.</strong><br> In a brand ecosystem dominated by warm tones, gray can deliver a warning more clearly — and more loudly — than orange ever could.</p><p>Knowing the rules is essential.<br> But blindly applying them without context leads to interfaces that are technically correct and practically ineffective.</p><p>Break the rules — but do it consciously, with an understanding of your product, your brand, and how your users actually think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=273ea061ca8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>