<?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 Azin Rostami on Medium]]></title>
        <description><![CDATA[Stories by Azin Rostami on Medium]]></description>
        <link>https://medium.com/@azin.rostami74?source=rss-be7b46a6c697------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*CW4PZAQe2BLrRiAkGVcubw.jpeg</url>
            <title>Stories by Azin Rostami on Medium</title>
            <link>https://medium.com/@azin.rostami74?source=rss-be7b46a6c697------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:02:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azin.rostami74/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[Scaling Organic Growth Through Content Architecture]]></title>
            <link>https://medium.com/@azin.rostami74/scaling-organic-growth-through-content-architecture-958ee2cbdcb8?source=rss-be7b46a6c697------2</link>
            <guid isPermaLink="false">https://medium.com/p/958ee2cbdcb8</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[website-design]]></category>
            <dc:creator><![CDATA[Azin Rostami]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 17:14:03 GMT</pubDate>
            <atom:updated>2026-06-19T13:58:33.083Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Balancing SEO Recovery with a Better User Experience in Nobitex Price &amp; Coin Pages</blockquote><pre>Role: Product Designer &amp; UX Researcher<br>Company: Nobitex — Iran&#39;s largest cryptocurrency exchange<br>Collaboration: Product, Marketing, SEO, Engineering<br>Scope: Price List, Buy List, BTC Page, USDT Coin Page</pre><p>Nobitex’s <a href="https://nobitex.ir/price/"><strong>Price List</strong></a><strong> and </strong><a href="https://nobitex.ir/price/btc/"><strong>Coin Detail pages</strong></a> are among the most visited pages on the platform. They serve as the primary entry point for millions of users — traders looking for real-time prices, newcomers comparing coins, and users ready to make their first purchase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZ5xryotq6HiBCi7dLYT4A.png" /></figure><h3><strong>The Challenge</strong></h3><p>The <strong>Price List</strong> and <strong>Coin Detail pages</strong> were losing ground in Google search rankings. The SEO team’s audit pointed to five compounding issues: pages not differentiated by search intent, shallow content architecture, weak internal linking, misalignment with Google’s latest quality signals, and near-zero interactive engagement. The core question wasn’t “what’s broken” — it was “how do we fix the structure without disrupting the experience for 11M users.”</p><h3>What We Analyzed</h3><p>Before defining any design direction, we ran a structured behavioral analysis across the Price List and Coin Detail pages — covering <strong>user journeys, engagement patterns, page retention, drop-off points, and navigation paths.</strong></p><blockquote>Some business metrics and internal data have been modified or omitted in accordance with NDA obligations while maintaining relative proportions.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y03VB9LVA4m7_JoMYbjFUw.png" /></figure><p><strong>1. Path Exploration — Price List : </strong>29.6% of users returned to the homepage after viewing the Price List, while only 3% reached Sign-up and 14.3% went to Login — a clear sign the page wasn’t guiding high-intent users forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KG5RXsg8VsxTTPKNNmULpQ.png" /></figure><p><strong>2. Path Exploration — BTC Page</strong> : The pattern repeated on the BTC page 19.3% of users bounced back to the homepage, while only 15.2% navigated to Login or Sign-up combined — still lower than the homepage return rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ra3tO_0KRNr0UOFW_23Pdg.png" /></figure><p><strong>3. Device Distribution</strong> Over 75% of sessions across both pages came from mobile — making mobile-first a design constraint, not a preference, and directly shaping layout and navigation decisions throughout the redesign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEMyIuQwwhyyhVoN-M_nZg.png" /></figure><p><strong>4. Session Recordings &amp; Heatmaps</strong> Engagement concentrated heavily above the fold. Most users never scrolled past the price chart — not because they found what they needed, but because there was nothing below worth staying for.</p><h3>Redesign Goals</h3><p>With the behavioral data mapped and the core problems identified, we split goals into two tiers to keep the roadmap focused and the team aligned.</p><h4><strong>Must Have</strong></h4><ul><li>Separate Price and Buy pages by user intent — serving distinct content for users researching prices vs. users ready to purchase</li><li>Reduce bounce rate and increase conversion rate toward Login, Sign-up, and the Exchange</li><li>Improve internal linking structure across coin and market pages</li><li>Update existing content to align with Google’s latest ranking requirements</li></ul><h4>Nice to Have</h4><ul><li>Increase user engagement through interactive sections and tools</li><li>Expand content architecture to support broader SEO coverage</li><li>Improve accessibility across data-heavy components</li></ul><h3>Competitor Analysis</h3><p>We audited <strong>40 landing pages</strong> — 20 international crypto platforms and 20 local Iranian competitors, analyzing each through three lenses:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-wy7UeEZP2TWXUHbLhlMaw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gyye8M-c2uTUcXC4NZSxKw.png" /><figcaption>International crypto platforms and local Iranian competitors</figcaption></figure><p><strong>1.Structure Analysis: </strong>We mapped layouts, section count, and variety across all 40 pages — with particular focus on creative and high-utility sections. Comparing local and international patterns helped us understand what Nobitex’s users were already familiar with and where we had room to differentiate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HQOBbt8CT1Re3oTyVXxDYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f8leGJHpKontJyw9ng_2BA.png" /></figure><p><strong>2. Volume &amp; Hierarchy</strong> We examined how sections were ordered and sized relative to each other — understanding which content was treated as primary, which was supportive, and how visual weight guided user attention down the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qIeinJbwl7psCQcdelKQig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFEEXBE22yL9tzAjk8rjfw.png" /></figure><p><strong>3. Content Analysis per Section</strong> For the most frequently recurring sections across all 40 pages, we analyzed their internal content structure — understanding not just <em>what</em> they contained, but <em>why</em> they appeared so consistently and what user need they were serving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zs8R3DfXA721GNz_GeU01w.png" /></figure><blockquote><em>We mapped recurring competitor patterns to our own challenges, identifying which sections solved similar problems. High recurrence suggested strong user familiarity and established expectations.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRhSbsHOMT_LsLWK4OjQNQ.png" /></figure><h3>Design Decision:</h3><p>Before any section was designed, we made a foundational decision: separate every page by the two core user intents we’d identified — <strong>Price and Buy.</strong><br>This wasn’t a layout choice; it was a response to how G<strong>oogle evaluates intent-matched</strong> content. Users searching for a coin’s price and those looking to buy it have fundamentally different goals, and serving them identical pages diluted relevance for both.</p><p>With this split defined, we moved into <strong>Content Mapping</strong> with a clear lens: every section would be evaluated against one of these two intents.</p><h3>Content Mapping</h3><h4>Step 1 — Section Inventory</h4><p>Drawing from behavioral findings, competitor analysis, and team requirements across SEO, Marketing, and Growth, we compiled a full list of candidate sections for each page type — every element that could potentially serve a user need or business goal, mapped against the Price vs. Buy intent split.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5kNGBgO_sNnT7oYj95H9w.png" /></figure><h4>Step 2 — Prioritization &amp; Architecture</h4><p>We then applied information architecture principles to prioritize sections by goal alignment, user need . This produced a defined content structure for each of the four pages — <strong>Price List, Buy List, Price Coin Page, Buy Coin</strong> Page — with every section placed deliberately to serve its page’s specific .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWYPIZAEV1N7Rnl2YD9C2Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9mNuqXF3xZMG6OF0FWBFg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PtTEAlvWZ3A-Uoych8xukA.png" /></figure><h3>Design Decisions: Translating Goals into Sections</h3><blockquote>Page design centered on four core objectives, each driving a set of sections:</blockquote><h4>1. Comprehensive Coin Information — Covering SEO Content Requirements</h4><p>To meet <strong>Google’s content depth requirements</strong> across both price and buy intents, we introduced:</p><ul><li><strong>Coin Price Analysis</strong> — market data beyond the raw number</li><li><strong>Price History</strong> — historical context for informed decisions</li><li><strong>About Coin</strong> — descriptive content targeting informational search intent</li><li><strong>FAQ Section</strong> — structured to match real user search queries</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNo3ztcuawO3rCSdmrUOAg.png" /></figure><h4>2. Interactive Sections — Driving Engagement &amp; Click-Through</h4><ul><li><strong>Price Forecast Poll</strong> — a bullish/bearish voting mechanism letting users register their own price prediction with a single click</li><li><strong>Fear &amp; Greed Index</strong> — a market sentiment indicator with selectable timeframes</li><li><strong>ROI Calculator</strong> — letting users project returns on a hypothetical investment, turning passive viewing into active exploration</li><li><strong>Comments Section</strong> — allowing users to post and reply to comments, increasing time-on-page and contributing user-generated content.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAQTDyxKZ7dKj3G9iOIE7A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-RaOqvN7cGXvbRWyhBHJw.png" /></figure><h4>3. Chart &amp; Trading Card Redesign| The Most Critical Interaction Point</h4><p>Since the <strong>chart and trading card</strong> represent the highest-value interaction on the page, we focused on two key improvements:</p><ul><li><strong>Improving the chart experience.</strong> We added precise timeframe selection and a Toman/Tether toggle — since some users compare prices in Tether to match global markets, while others think in Toman.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UANSmi0py4bXXXe9V5zZbA.png" /></figure><ul><li><strong>Opening a path to the market.</strong> Previously, the buy card only routed users to the exchange’s quick-buy flow, with no option to reach the full market. We added this missing path.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6QAlhSUGQijSdSnjjFx-g.png" /></figure><h4>4. Internal Linking &amp; Educational Sections:</h4><p>To strengthen internal linking and guide undecided users, we added:</p><ul><li><strong>Similar Coins list</strong> — improving internal link structure</li><li><strong>User Guide section</strong> — supporting newer users</li><li><strong>Closing Sign-up/Login banner</strong> — a final, low-pressure conversion point</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7EtLcEaWgDYg-sump0j7g.png" /></figure><h4>5. Persistent Navigation — Reducing Friction During Scroll:</h4><p>To keep key actions accessible regardless of scroll position — directly addressing the high bounce rates identified during discovery — we added:</p><ul><li><strong>Sticky top bar</strong> — giving users constant access to different page sections without scrolling back up</li><li><strong>Persistent buy button</strong> — embedded in the sticky bar, keeping the purchase action accessible at any scroll depth</li><li><strong>Sticky bar on the coin list</strong> — keeping search and filter controls accessible while browsing long lists</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gr4W4FS6R47pn05xgIBcIQ.png" /></figure><h3>Final Designs</h3><p>Bringing every decision together, the four pages came to life with <strong>richer interactivity, stronger content, clearer guidance</strong>, and<strong> improved internal linking</strong> — each shaped by its own user intent, yet sharing a consistent visual language and interaction model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOjiNo5l-pM76r3Pjz4lGw.png" /></figure><h4><a href="https://nobitex.ir/price/"><strong>Price List</strong> Page</a></h4><p>Designed for users exploring the market, prioritizing real-time price data and market context across all available coins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kKQNHkMOeo3b0ChUkQ42A.png" /></figure><h4><a href="https://nobitex.ir/price/btc/">Price Coin Page</a></h4><p>A coin detail page built for price-focused users, surfacing depth of market data, chart analysis, and sentiment tools like the Fear &amp; Greed Index.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QmVj4rNnaDjahPfeHmfRPg.png" /></figure><h4><a href="https://nobitex.ir/buy/">Buy List Page</a></h4><p>The purchase-intent counterpart to the Price List, presenting available coins through the lens of buying — optimized for users ready to transact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hrzqJa2B-irHKeTPgShq-A.png" /></figure><h4><a href="https://nobitex.ir/buy/btc/">Buy Coin Page</a></h4><p>A coin detail page centered on the buying experience, featuring tools like the ROI Calculator and a direct path to the exchange.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uMhkIjTp3R2agss5cdwamw.png" /></figure><h3>Measuring Against What We Set Out to Fix</h3><p>We designed directly against the gaps the data revealed. Here’s how each decision mapped to a measurable goal:</p><p><strong>Separating pages by search intent</strong> gave Google two distinct, intent-matched pages instead of one diluted layout — directly addressing the misalignment with its ranking algorithm and improving visibility for both price and buy-related queries.</p><p><strong>Optimizing section structure and mobile navigation</strong> tackled the 29.6% homepage return rate and the 75% mobile session share that had no mobile-first experience. Users now have a clear path forward regardless of where they are on the page.</p><p><strong>Strengthening internal linking</strong> across coin and market pages improved Google’s ability to evaluate the site’s topical authority — contributing to better ranking across related search queries.</p><blockquote>Full post-launch metrics were not available at the time of writing. The baseline data above represents the gaps this redesign was built to close.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=958ee2cbdcb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving Security Without Increasing Complexity]]></title>
            <link>https://medium.com/@azin.rostami74/improving-security-without-increasing-complexity-4fb763f1598e?source=rss-be7b46a6c697------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb763f1598e</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Azin Rostami]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 12:54:46 GMT</pubDate>
            <atom:updated>2026-06-04T15:18:15.612Z</atom:updated>
            <content:encoded><![CDATA[<p>Redesigning the 2FA activation and recovery experience to reduce user confusion and support dependency.</p><pre>Role: Product Designer &amp; UX Researcher <br>Platforms: Web, PWA, Mobile App <br>Scope: 2FA Activation &amp; Recovery Flow</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Co5wHJrT4Q1wIPK3KF5VpQ.png" /></figure><p><a href="https://nobitex.ir/"><strong>Nobitex</strong></a> is Iran’s largest cryptocurrency exchange, allowing users to buy, sell, and trade digital assets securely. To increase account security, users were required to enable two-factor authentication (2FA) for sensitive actions such as cryptocurrency withdrawals.</p><p><strong>This project </strong>focused on redesigning the <strong>2FA</strong> activation and recovery experience to reduce friction, improve user understanding, and create a more accessible security onboarding journey.</p><blockquote>Some sensitive details and business metrics have been intentionally omitted due to NDA restrictions.</blockquote><h3>The Challenge:</h3><p>In 2023, support requests related to the 2FA feature increased significantly, accounting for nearly 15% of all support chats and calls. As one of the most recurring support issues, we began investigating the activation and recovery experience to better understand the challenges users faced during the 2FA process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1heRIc9vSv8b0K9T8I78_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dy6Ag2KF2YbqJJOBRb4cYw.png" /></figure><h3>Research Approach</h3><h4>1. User Chat Analysis</h4><p>We reviewed over 200 live chat conversations and grouped recurring user issues into five main categories to identify the most frequent pain points in the 2FA activation and recovery flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eCqAf67sHYawLmPNHCbyDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FMIahvG2te4ecBFLgFjwMg.png" /></figure><h4>2. Support Team Interviews</h4><p>To better understand user challenges during the 2FA activation and recovery process, we conducted sessions with support specialists to validate our assumptions about users’ key pain points and challenges across chats, calls, and support tickets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nuXtfDznxKCUI9B8zF-P2w.png" /></figure><h4>3. Behavioral Data Analysis</h4><p>We analyzed user behavior and drop-offs using GA4 Funnel Exploration, GA4 Path Exploration, and Microsoft Clarity session recordings to identify friction points across the 2FA journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xjGz3cgBVVOrNxIDoGeNtA.png" /><figcaption>Due to NDA obligations, numerical data cannot be disclosed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJHKRXb2l4hZ4s-OilsMEQ.png" /></figure><h4>4. competitor analysis crypto industry</h4><p>We analyzed 2FA activation and recovery flows across leading crypto platforms such as Binance, OKX, to identify current UX patterns, security best practices, and emerging onboarding approaches in authentication flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8tqM3grbX4DslhzomyDoSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olQWh3Pn01GEpQgZDogaJw.png" /></figure><h3>Key Findings &amp; Problem Definition</h3><blockquote>In collaboration with the Data and Support teams, we analyzed user chats and support calls across four recurring issue categories to understand their frequency and impact on support operations.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGLsn7N-dqhs8yJ90WXs_A.png" /><figcaption><em>Due to NDA restrictions, figures have been modified while maintaining relative proportions</em></figcaption></figure><h4><strong>Finding 1:</strong></h4><p>Most support requests were related to helping users download, install, and set up the <strong>Google Authenticator App.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ll_FxhOOI7cMo0-p7zoWwQ.png" /></figure><h4><strong>Problem :</strong></h4><ul><li>Users received no guidance when setting up the authenticator app, making activation difficult for many first-time users.</li><li>There was no clear path to download the correct authenticator app, causing some users to install incorrect alternatives and contact support for confirmation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pOGdV-SnP_jA03jkjxjRPw.png" /></figure><ul><li>No guidance was provided for setting up the authenticator app, leaving users unsure how to connect their account and complete the activation process without support assistance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vJ7av-q9m13N3drpIsEKPQ.png" /></figure><h4>Finding 2:</h4><p>Invalid OTP Error During Setup 2-Factor Authentication</p><h4><strong>Problem :</strong></h4><ul><li>Invalid OTP errors accounted for the largest share of 2FA-related support requests after Google Authenticator Setup.</li><li>OTP codes were sent before users completed the authenticator setup process, creating confusion and frequent activation failures.</li><li>Long OTP expiration times (20 m) increased user frustration and did not align with common expectations for security verification codes.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*209nNI5wDb_reZBbAeDvLA.png" /></figure><h4>Finding 3 :</h4><p>Users Frequently Lost Access Due to Missing Backup Codes</p><h4>Problem :</h4><ul><li>A significant portion of 2FA deactivation requests resulted from users not retaining their backup codes for future account recovery.</li><li>he setup flow did not emphasize the importance of saving backup codes or clearly communicate the consequences of losing access to the authenticator device.</li><li>Most affected users had lost their phones and were unable to restore access to their authenticator application. they contacted support and were guided through the two-factor authentication removal process.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7coAtZE3ontFXGi59qXcBQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YIL5Fy7TPJ7oBMH6wnevXQ.png" /></figure><h3>Design Decisions for Activation:</h3><h4>1. Increasing Awareness of Account Security</h4><p>Due to low 2FA adoption rates, we introduced security indicators within the user profile and added a persistent banner on the homepage for users without 2FA enabled. These prompts increased awareness of account protection and encouraged users to activate 2FA</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C0tUu5-oG5krYzNOfHysXA.png" /></figure><h4>2. Redesigning the 2FA Activation Journey</h4><p>The activation flow was restructured into clear, sequential steps. Users first complete the authenticator app setup before starting the 2FA activation process, reducing confusion and cognitive load.(Previously, the entire setup process was presented in a single step)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVwhAoA-mtSczxWX4ZwvvQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3DE-6bTW1T-3pvpHs6byQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qksFDiL0aJx3teAw_tm-ig.png" /></figure><h4>3. Providing Quick Access to Authenticator Apps</h4><p>To reduce setup friction, we provided direct download access to Google Authenticator across all major mobile app stores, helping users quickly install the correct app and continue the activation process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-68LYZuLX7ruK8Oz0hsgg.png" /></figure><h4>4. Introducing Step-by-Step Setup Guidance</h4><p>Clear and concise setup instructions were integrated into the flow to help users complete authenticator configuration without relying on support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XzG7dxfpJE-wH2iKiXIR2A.png" /></figure><p>Clear written instructions combined with visual motion guidance were provided across two steps: Google Authenticator setup and 2FA activation .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*lg6PHYP5fpqlrJadq595kQ.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*rrbeT1Yx2-wSqeP-09MXZA.gif" /></figure><h4>5.Improving the 2FA Activation Experience</h4><p>We placed the QR code alongside the verification input, allowing users to scan the code and enter the generated 2FA code within the same step. This reduced context switching and created a smoother activation experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu7158VTtioWGiHnYJHPMQ.png" /></figure><h4>6. Improving the Backup Code Experience</h4><p>After completing 2fa activation, We introduced reminder modals to highlight the importance of backup codes and encourage users to store them securely for future account recovery.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b9BNrVTvjOxvQwmSM-qY5g.png" /></figure><h3><strong>Reflection</strong></h3><blockquote>Improving the 2FA experience was not only about increasing security, but also about reducing confusion and helping users complete critical security tasks with confidence. By combining research insights with product design decisions, we created a more guided and accessible security onboarding experience.</blockquote><h3>Impact</h3><ul><li>Reduced support requests related to 2FA across chats and calls.</li><li>Decreased user drop-off throughout the 2FA activation flow.</li><li>Increased 2FA adoption among registered users.</li><li>Created a more accessible and secure activation experience for account protection.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb763f1598e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improving User Registration & Identity Verification Flow at Nobitex]]></title>
            <link>https://medium.com/@azin.rostami74/improving-user-registration-identity-verification-flow-at-nobitex-951f5533c5e7?source=rss-be7b46a6c697------2</link>
            <guid isPermaLink="false">https://medium.com/p/951f5533c5e7</guid>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Azin Rostami]]></dc:creator>
            <pubDate>Sat, 23 May 2026 15:02:19 GMT</pubDate>
            <atom:updated>2026-06-30T13:06:40.806Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Redesigning the onboarding, Registration and Level 1 identity verification experience to reduce friction and improve user activation.</em></p><pre>Role: UX Researcher &amp; Product Designer<br>Scope: registration flow, and identity verification redesign</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZ7gcTbkfGnT_UWjnPBp2g.png" /></figure><p><a href="https://nobitex.ir/"><strong>Nobitex</strong></a> is the largest cryptocurrency exchange in Iran, providing users with a secure platform for buying, selling, and trading digital assets. Nobitex uses a multi-level verification system, Users must complete identity verification to access core features such as deposits and trading. As part of this redesign project, I worked on improving the onboarding, verification, and user guidance experience for new users.</p><blockquote>To comply with NDA agreements, sensitive business data and confidential information have been omitted or intentionally abstracted in this case study.</blockquote><h3>The Challenge:</h3><p>Through data analysis, we identified a significant drop-off in the new user journey across the registration and identity verification flow. This friction was not limited to a single step, but persisted throughout the entire onboarding process, from initial sign-up to completion of verification, ultimately impacting the overall user activation rate.</p><ul><li><em>The conversion rate from registered users to Level 1 verified users showed a significant drop throughout the onboarding journey.</em></li><li><em>The existing manual verification process increased operational workload for support and verification teams due to frequent user errors and rejected submissions.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EW4qWCB2HvUalOSR8_h6lQ.png" /></figure><h3>Project Goals</h3><p>The primary goal of this project was to improve the conversion rate from registered users (Level 0) to verified users (Level 1) by optimizing the onboarding and identity verification experience.</p><h4>Key goals included:</h4><ul><li>Improving the conversion rate from registration to successful verification</li><li>Reducing user errors during data entry and increasing verification approval rates</li><li>Removing unnecessary friction from the verification flow to create a faster experience</li><li>Reducing operational workload and improving the verification review process for support teams</li></ul><h3>Research Methods:</h3><p>To better understand the drop-off in the new user journey and the low conversion rate from registration to verified users, I conducted a data-driven analysis of user behavior across the onboarding funnel.</p><ul><li>Using WebEngage, we analyzed the user funnel</li><li>Measure conversion rates at each step</li><li>Identify key drop-off points</li><li>Track user behavior patterns over time</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j82kMgjIP0RYdFTUfcKkcg.png" /><figcaption>30 days , 2024</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I2Tg5tBYvHTr4nGdi7Yn7A.png" /></figure><p>2. Using <strong>Funnel Exploration and Path Exploration</strong> in Google Analytics<strong>(GA4)</strong>, we examined the journey from registration to the end of Level 1 verification to:</p><ul><li>Track which paths users follow after registration</li><li>Identify pages with the highest deviation from the main flow</li><li>Pinpoint stages where users stop or drop off</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zv5sj_OxseWIAP07-n3Ahw.png" /><figcaption>Dec 1, 2024 — Jul 31, 2024 | Funnel Exploration KYC Flow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffoSe2_Rc0d8J_aoHW2M8g.png" /><figcaption>Dec 1, 2024 — Jul 31, 2024 | Path Exploration KYC Flow</figcaption></figure><p>3. Session recording analysis using <strong>Microsoft Clarity</strong> to observe real user behavior, interaction issues, and friction points during Level 1 verification.</p><p>4. Alongside behavioral analysis, rejected Level 1 and Level 2 verification requests were reviewed to identify common failure patterns and user mistakes.</p><ul><li>Identify the most common rejection reasons</li><li>Understand user input error patterns</li><li>Review high-friction verification cases</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_QOwdG96ljA4L_solZVW-A@2x.png" /></figure><blockquote>These insights provided a clearer understanding of the real user experience and helped define more effective design solutions.</blockquote><h3>Key Research Findings:</h3><ol><li>The transition between registration and identity verification was not clearly guided, causing users to navigate to unrelated pages instead of continuing the verification process.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gfBroqUpkU1z8vTTfYEovw.png" /><figcaption>Users should not be redirected to the user levels page immediately after sign-up</figcaption></figure><p>2.Long verification forms and excessive manual input created friction during onboarding, leading to user drop-off and increased support workload caused by invalid or incomplete submissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CsIzRPVgyxibE9c01iDVqg.png" /></figure><p>3. The onboarding flow lacked a clear direction for guiding users to the next verification step, causing confusion and navigation to unrelated sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pK78oIol2K-4IUVt38N7nA.png" /></figure><p>4. Requesting identity document uploads early in the verification process created significant friction for users. In many cases, users did not have immediate access to their documents, faced upload limitations, or encountered submission issues, leading to drop-off during onboarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wcIcMNNgbi1TMvN7u5P_QA.png" /></figure><blockquote>The onboarding and verification flow created friction for new users due to unclear navigation, excessive manual input, and early document upload requirements, leading to lower completion rates and increased operational .</blockquote><h4><strong>Key focus areas:</strong></h4><ul><li>Minimize manual input to reduce user errors and failed verifications</li><li>UX Improvements for Level 1 Verification</li><li>Reducing Friction During Verification</li><li>Creating a Faster Onboarding Experience</li></ul><h3>Design Decisions For Improving Verification Level 1</h3><h4>Improving Customer Journey</h4><p>Improving the user journey after sign-up by guiding users to a simplified <strong>(L1)</strong>verification process, followed by directing them to the “Add Card” flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GE637sr-eduJttP0zdyWEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZYGC6A5ahGaiBQ3p0nnsBA.png" /></figure><h4>API-Based Verification Redesign</h4><p>By integrating a new identity verification API with the national registry service, we simplified Level 1 verification and reduced the need for manual data entry during registration. This allowed users to verify their identity with only a national ID and birth date, creating a faster and lower-friction onboarding experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7EWFPfdTvQzftnagI8Umw.png" /></figure><h4>Moving national ID image upload to Level 2 verification</h4><p>By changing the API model, users are no longer required to upload any identity documents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FfQXi7WZG8OELzz4SfVPTA.png" /></figure><h4>Increasing Transparency of the Verified State</h4><p>Clearly displaying the verification status to the user to ensure full awareness of their KYC state, which wasn’t visible in the previous flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5SxWRybe184ptD3Xcoijw.png" /></figure><h3>Design Decisions For Improving User Registration</h3><h4>Reducing users’ cognitive load on the sign-up page</h4><p>To reduce cognitive load during onboarding, we simplified the registration form and removed unnecessary elements such as CAPTCHA, creating a faster and more focused sign-up experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sFLiFCwTV6bCr8I-376nSQ.png" /></figure><h4>Modal-Based Login &amp; Registration Experience</h4><ul><li>We redesigned login and registration as modal-based flows, allowing users to Login or Registration without leaving their current page.</li><li>This prevented users from losing their ongoing journey and created a smoother experience across the website.</li><li>After signing in or registering, users remained in the same context and could continue their previous actions seamlessly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zaXOt41LXMt4GfN90IxkcQ.png" /></figure><h3><strong>Design Decisions </strong>For Login</h3><h4>Simplifying the Login Experience</h4><ul><li>We moved the two-factor authentication field to a separate step to reduce cognitive load during login.</li><li>In the previous experience, users saw the 2FA field even when they had not enabled it, causing confusion and input errors.</li><li>Separating this step created a clearer and more focused login experience for users without active two-factor authentication.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UzD7sqHIrZg0o5r4KghpQg.png" /></figure><h3>Simplifying CAPTCHA Placement</h3><ul><li>We moved CAPTCHA interactions into a separate modal to create cleaner and more focused login and registration forms.</li><li>Separating CAPTCHA from the main form reduced visual clutter and created a smoother authentication experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xTRqZpS02xfDPLDxt9hSg.png" /></figure><h3>UI Design Decisions</h3><ul><li>Reduced reliance on primary colors to improve focus on form clarity .</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QikXrw4qt97tX7wuMCOCUA.png" /></figure><p>2. Simplified verification input fields for a cleaner and easier form experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWhgk9RkicanihCr-spQ1w.png" /></figure><p>3. Increased whitespace and visual simplicity to improve user focus during onboarding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_pKJYZYjHK9eH3P9sSRVbw.png" /></figure><blockquote>Final Thoughts: <br>Designing onboarding experiences is not only about reducing steps — it’s about reducing uncertainty. Small friction points during registration and verification can significantly impact activation, trust, and long-term user engagement.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=951f5533c5e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>