<?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 Nash Sofan on Medium]]></title>
        <description><![CDATA[Stories by Nash Sofan on Medium]]></description>
        <link>https://medium.com/@sofannash?source=rss-72c7befec800------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*A0mAtRTzh-6xinnQBiEWcQ@2x.jpeg</url>
            <title>Stories by Nash Sofan on Medium</title>
            <link>https://medium.com/@sofannash?source=rss-72c7befec800------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:33:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sofannash/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[Challenge 2 | Wire-framing PayPal]]></title>
            <link>https://medium.com/@sofannash/challenge-2-wire-framing-paypal-74303aa901b1?source=rss-72c7befec800------2</link>
            <guid isPermaLink="false">https://medium.com/p/74303aa901b1</guid>
            <category><![CDATA[task-analysis]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[prototype]]></category>
            <dc:creator><![CDATA[Nash Sofan]]></dc:creator>
            <pubDate>Tue, 22 Feb 2022 05:29:22 GMT</pubDate>
            <atom:updated>2022-02-25T21:26:17.902Z</atom:updated>
            <content:encoded><![CDATA[<h4>Creating a wireframe version of the User Flow of a chosen app.</h4><p>The scope of this challenge is to design and <strong>create a wireframe prototype </strong>version of a <em>specific</em> user flow of an app of our choice. Let’s dive into a detailed analysis and walk through the Wireframe.</p><h4>The Chosen One</h4><p>After contemplating, I chose to ‘reverse engineer’ the app that aims to decentralize financial services: <strong>PayPal</strong>. Besides its great mission, services provided, and ease of use; I chose PayPal <em>mainly</em> because it’s the one app that never fails to <em>stimulate</em> and <em>flare</em> my <strong><em>emotions </em></strong>💥.</p><p>From feeling discomfort, fear, and sadness when <strong>sending</strong> money; to shyness, surprise and joy when <strong>receiving and requesting </strong>money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ne9B5s9qlDjXxM_i.png" /></figure><h4>About the User Flow</h4><p>As much as I wanted to construct a wireframe of the whole app, the challenge is to only focus on one User Flow. Therefore, I have chosen the flow that triggers the most emotions: <strong>Sending money to a friend abroad.</strong></p><p><strong>| Hierarchical Task Analysis <br></strong>As shown in the Figure below, I have broken down the main task into 6 subtasks to clearly understand the user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LwTuW_mUkKTw66WLEZpFmw.png" /><figcaption>Hierarchical Task Analysis for ‘Sending Money’ on PayPal</figcaption></figure><p>Since the app and the user flow was chosen based on emotions, it would only be fair to show you the emotions triggered throughout each subtask:<br>1 - <strong><em>Discomfort</em></strong> of sending money. 😤<br>2 - <strong><em>Stress</em></strong> when typing recipient details. 🧐 <br>3 - <strong><em>Fear</em></strong> of mistake. 😰 <br>4 - <strong><em>Sadness</em></strong> to see money vanish. 😔 <br>5 - <strong><em>Anxiously</em></strong> waiting for money to get sent. 😬 <br>6 - <strong><em>Relief</em></strong> when money is delivered. 😮‍💨<br><em> — (please share </em><strong><em>your</em></strong><em> emotions in the comments section below) —</em></p><h4>Low-fi, Mid-fi and Hi-fi of PayPal User Flow</h4><p>After doing multiple drafts of Hand sketches, I ended up with an accurate hand sketch that made the process of creating a mid-fi prototype much easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QHY2eNbc0btwV2xDIfRw7g.png" /><figcaption>Hand Sketches</figcaption></figure><p>After completing the hand sketches, I used Figma to create my wireframes. Frame by frame, I ended up with neat wireframes for each section. To focus on the selected user flow, I only made the necessary buttons interactive. Before we jump into the prototype, I attached photos of the wireframes that I created as well as the real app screenshots.</p><p>Below you can see both the mid-fi and hi-fi prototypes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j96nv07NygkReBNyWFglZg.png" /><figcaption>Mid-fi Prototype</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cyRayzxBH-VMvGUdh0IQvg.png" /><figcaption>Hi-fi Screenshots of PayPal</figcaption></figure><h4><strong>Live Prototype</strong></h4><p>As promised, I have embedded the <em>interactive</em> prototype version of the wireframe for the specific User Flow: <strong>Sending money to a friend abroad.</strong></p><p>Check out the prototype <a href="https://www.figma.com/embed?embed_host=share&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FArNrlZB3Yk5mOe36qypHnR%2FPayPal-Wireframe%3Fnode-id%3D2%253A155%26scaling%3Dscale-down%26page-id%3D0%253A1%26starting-point-node-id%3D2%253A155&quot;%20allowfullscreen">here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FArNrlZB3Yk5mOe36qypHnR%3Fnode-id%3D0%3A1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FArNrlZB3Yk5mOe36qypHnR%3Fnode-id%3D0%3A1&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2Ffc752c68-e018-4b6c-8ca4-66370688a261%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/9a5dd19f0c8b1261aac197614932a039/href">https://medium.com/media/9a5dd19f0c8b1261aac197614932a039/href</a></iframe><p>Please share your insights and feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74303aa901b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 1]]></title>
            <link>https://medium.com/@sofannash/challenge-1-1a61db063d6c?source=rss-72c7befec800------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a61db063d6c</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[solution-design]]></category>
            <category><![CDATA[ux-writing]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Nash Sofan]]></dc:creator>
            <pubDate>Wed, 16 Feb 2022 04:01:12 GMT</pubDate>
            <atom:updated>2022-02-19T07:15:48.208Z</atom:updated>
            <content:encoded><![CDATA[<h3>Challenge 1 | User-Centric Solution for Citymapper</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*53NGLVGtl-bY3_a3.png" /></figure><p>I will be using my newly developed UX research skills to analyze user pain points and design a user-centric solution for <a href="https://citymapper.com/london?lang=en">Citymapper</a>. Furthermore, clearly present the whole process and methodologies used.</p><h4><strong>1 | Company Profile 🏢</strong></h4><p>Citymapper is a public transit app that aims to provide <strong>fast, cheap, and real-time</strong> transport options between two points. It integrates data across all modes of transport, from walking to public and private transit and everything in-between. They call themselves as the <em>‘Ultimate Transport App’</em> and aim to make city travel as <em>stress-free as possible.</em></p><blockquote>The question is, have they managed to make it <strong>stress-free</strong>?<em> If not, how should they!</em></blockquote><h4><strong>2 | Empathize 🔬</strong></h4><p>In order to answer the question above, I had to investigate and understand the users at a deep and personal level. Hence, I conducted <strong>9 </strong>online surveys using <a href="http://surveymonkey.co.uk/">SurveyMonkey</a> and performed <strong>5</strong> face-to-face interviews.</p><p><strong>2.1 | Methodology and Findings</strong></p><p>Interviewees were all millennials aged between 23–38, as they are the most traveled age group according to <em>Condor Ferries</em> (<a href="https://www.condorferries.co.uk/travel-statistics-by-age-group">Travel statistics by age group 2020–2021</a>). I sent out my online open-ended surveys to 15 users, but only 9 completed the survey. As for the interview, I believe 5 thorough interviews was enough for the scope and complexity of this challenge.</p><p>Besides user characteristic questions, I tried to guide interviews around the following topics:<br>- Problems they’ve encountered with Citymapper<br>- What are things they love about the app<br>- What would they change about the experience</p><p>After a couple of days of primary research, the data gathered was <strong>conclusive.</strong></p><p>Although users expressed their love to the user-friendly UI, 72% of the users interviewed shared one main frustration: the different amount of tickets the user has to purchase to get from point A to point B.</p><p>A few <strong>pain points </strong>that came to light:<br>- Purchasing lots of tickets just for one journey.<br>- Not knowing which tickets are needed for the journey.<br>- Language barriers when buying tickets.<br>- Buying expensive alternatives just to avoid complications.</p><blockquote><em>Relatable comments made by interviewees:</em><br>“I once got frustrated mid-way through my journey and ended up taking a taxi, costing me £24 instead of £4.5&quot; — <strong><em>Alison</em></strong><em> from England</em></blockquote><blockquote>“Last time I was in Istanbul, I queued for 15 minutes just to finally realize that the kiosk didn’t have English, I wanted to scream!” — <strong><em>Bae</em></strong><em> from Korea.</em></blockquote><blockquote>“Barcelona has plenty of different tickets for public transportation and it is confusing, I wish Citymapper made it clear which one I should buy for my Journey” — <strong><em>Michael</em></strong><em> from California.</em></blockquote><h4>3 | Define 📖</h4><p>Now that I have learned as much about the users as possible, conducting interviews and observation techniques, I now have a great understanding of who the users are, their needs, and pain-points.</p><p>With all the data in hand, I then articulated and crafted an actionable problem statement that will help me find the most accurate user-centered solution.</p><p><strong>3.1| Problem Statement <br></strong>Alison is a masters student that just moved to Rome who needs a seamless transit app experience without having to purchase different multiple tickets because the language barrier frustrates her and the transit system is confusing.</p><h4>4 | Ideate 💡</h4><p>With the meaningful problem statement above, we now have a kick-start to the next stage of the UX process: the ideation stage. I have come up with a few solutions that will help solve the problem defined above. All solutions start and end with the user in mind.</p><p>Analyzing the findings and problem definition, the solution must be a feature added to the page <strong>after </strong>route<strong> </strong>selection<strong> </strong>and <strong>before</strong> starting the journey. My idea is to make Citymapper a <strong>One-stop-shop </strong>transit<strong> </strong>App where users will end up buying and purchasing their tickets for the journey using Citymapper.</p><p>One-stop-shop benefits:<br>1. Solves user pain-points. <br>2. Generates a <strong>revenue</strong> <strong>stream</strong> for the company.<br>3. Create a full user experience (or customer journey) from start to finish that will create emotions because users are paying and it triggers <strong>emotions</strong>. Resulting in an increase of <strong>retention</strong> rates and building loyal customers.</p><blockquote><strong>Solution:</strong> One-stop-shop, where users will search, decide, choose, and <strong>pay</strong> all within one app and in one place.</blockquote><h4>5 | Prototype 📲</h4><p>Some would want to <strong><em>buy tickets using the app</em></strong>, others would prefer to have the <strong><em>‘step-by-step’</em></strong> instructions and then buy them in real-life in a kiosk or customer agent on ground. In the end it’s a matter of convenience.</p><p>Let me walk you through the prototype I have crafted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*DQ3ZLMw80ryCY7yi8Ec2IQ.png" /><figcaption>Prototype Sketch Draft 2 Final</figcaption></figure><p><strong>Pages One and Two </strong>are<strong> </strong>a clone of the existing Homepage of Citymapper. It was good practice to sketch low-fi prototypes. On these pages the user will find their destination they want to go and select “GO”. Then select which route they would like to go on. Including time-sensitive info and details of each route.</p><p>Once preferable route and mode of transportation is selected, the user will then be directed to the newly added feature that I have designed: <strong>Page Three</strong>. On this page, you will see the selected route and you will be prompted to select one of two options.</p><ul><li>Option 1: <strong>Buy Now:</strong> This button will allow users to automatically buy the tickets needed for this specific journey on the spot. With a single-click, a QR Code will be generated for the user to use throughout their journey as their ticket.</li><li>Option 2: <strong>‘Step-by-step’ guide</strong>: This button is for those faint-hearted. Those who are more traditional and would like to buy the tickets themselves, but want Citymapper to instruct them and assist to which tickets and how, where to buy them from.</li></ul><p>By selecting either option, the bottom half of the screen will change accordingly. Pages three and four show what happens if you select <strong><em>‘Buy Now’</em></strong> or<strong><em> ‘Step-by-step’, </em></strong>respectively.</p><h4>6 | Lessons Learned 📝</h4><p>A| Although conducting <strong>interviews</strong> is time consuming, it remains a vital part of the whole process of UX. Without interviews, one does not understand users at a personal level.</p><p>B| The process is a never-ending cycle of <strong>Iteration</strong>. A UX designer will keep on going around in cycles adding or removing things from their designs. I still question whether there is a time to stop Iterating, maybe there isn’t 🤔.</p><p>C| Problem Statement — SUPER important to narrow down. Problem statements should be clear and concise and should represent all the pain points from all users interviewed. Without a clear <strong>actionable problem</strong> <strong>statement</strong>, your ideas and solutions will be all over the place. Its always good to have it written down clearly then ideating afterwards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a61db063d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>