<?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 Célia Lobet on Medium]]></title>
        <description><![CDATA[Stories by Célia Lobet on Medium]]></description>
        <link>https://medium.com/@lobet.c?source=rss-cd7aa99fed98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gFPZbzAKoYVjDbgJWirzFg.jpeg</url>
            <title>Stories by Célia Lobet on Medium</title>
            <link>https://medium.com/@lobet.c?source=rss-cd7aa99fed98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:22:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lobet.c/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[Case Study: Redesigning the registration process of a freelance platform, Cherry Pick]]></title>
            <link>https://medium.com/@lobet.c/case-study-redesigning-the-registration-process-of-a-freelance-platform-cherry-pick-aa71bc81a15d?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa71bc81a15d</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 09:59:42 GMT</pubDate>
            <atom:updated>2022-02-25T10:10:31.836Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Final Project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2P8BRcchGhjm1QMnRNjlg.png" /></figure><p><strong>Role</strong>: UX/UI designer</p><p><strong>Duration</strong>: 2 weeks (01/31/2022 to 02/10/2021)</p><p><strong>Team</strong>: <a href="https://medium.com/@zuninogreta">Greta</a> and I</p><p><strong>Platform</strong>: Desktop</p><p><strong>Tools</strong>: Figma, Figjam</p><h3>Overview</h3><p>Our challenge for this project was to <strong>redesign </strong><a href="https://app.cherry-pick.io/home"><strong>Cherry Pick</strong></a><strong>’s registration process to make it more fluid and fun</strong>.</p><h3>Client and Business</h3><p>For our last project of the Ironhack UX/UI Design Bootcamp, we had the chance to work with <a href="https://app.cherry-pick.io/home"><strong>Cherry Pick</strong></a>, a <strong>French platform helping freelancers in IT find jobs and matching them with companies</strong>. It acts as an intermediary between freelancers and companies, providing them full support.</p><p>After creating a <strong>roadmap </strong>for this project, our team started off by preparing <strong>questions for the first meeting with the client</strong> to <strong>better understand their business and their expectations for the new design</strong>.</p><p>We learned that <strong>in order to make the best matches</strong>, Cherry Pick needs to <strong>get relevant information from the freelancer during the registration process</strong> and this is where my team comes in to help.</p><p>Below is a screenshot of Cherry Pick’s current website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARrkWl-IHpyi__9XFl6R6g.png" /><figcaption>Cherry Pick’s current registration page</figcaption></figure><h3>Competitive Analysis</h3><p>After the first meeting, we did a <strong>competitive analysis</strong> to see the <strong>differences between Cherry Pick and its competitors</strong> and <strong>what could be missing within the registration process</strong>.</p><p>The main findings of our competitive analysis were the followings:</p><ul><li><strong>Experience</strong>: Some platforms highly value the length of experience. They don’t allow people who are newly freelancers to register.</li><li><strong>Pre-screening</strong>: Some platforms pre-screen the freelancers before registering them and adding them to their database.</li><li><strong>Number of roles</strong>: Some platforms allow freelancers to enter more than one role.</li><li><strong>Intermediaries</strong>: Some platforms act as an intermediary between freelancers and companies while others don’t.</li><li><strong>Self-assessment</strong>: Many platforms ask freelancers to self-assess their skills with a star-rating system.</li></ul><h3>Interviews and Survey</h3><h4>Stakeholder Interview</h4><p>Next, we wanted to know <strong>what key information Cherry Pick’s recruiters need</strong> about freelancers in order to find them the best matches and we also wanted to know their outlook on the whole process. We prepared questions for our <strong>interview with Youssef, a Tech Recruiter at Cherry Pick</strong>, and conducted the interview.</p><p>Here are some insights from our interview with Youssef:</p><ul><li>“The key information I need is the freelancer’s average daily rate, his availability, his expertise, and the type of job he is looking for.”</li><li>“I want to know freelancers’ preferences, what technologies they want to work on in priority.”</li><li>“These days many freelancers want to work remotely: it is an important criterion for them.”</li></ul><h4>Survey and User Interviews</h4><p>To have a <strong>better understanding of our target users’ behaviours and needs</strong>, we continued our research with a <strong>survey and user interviews</strong>.</p><p>In our survey, we asked Cherry Pick’s users about their criteria when choosing a platform, the features they enjoy the most, what information they are willing to give to a platform, and what they want to highlight in their profile.</p><p>From the survey results, we understood that the main criteria for freelancers to choose a job was the <strong>average daily rate (TJM in French)</strong>, followed by the <strong>possibility to work remotely</strong>, and finally the <strong>required skills</strong> for this particular job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vjMIASwhvu8f6bhfRoYSnw.png" /><figcaption>The Average Daily Rate (TJM) is the most important criterion</figcaption></figure><p>After the survey, we interviewed 5 freelancers in IT. We interviewed both Cherry Pick’s users and people who aren’t registered at Cherry Pick to get different insights.</p><p>Here are some important quotes from our interviews:</p><ul><li>“<strong>I don’t want to spend more than 5 to 10 minutes</strong> registering on a platform.”</li><li>“<strong>I don’t have only one job</strong> and <strong>I want to be able to show them all</strong> in my profile.”</li><li>“<strong>I don’t like to self-assess my technical skills</strong>. I tend to underestimate my capabilities.”</li></ul><h3>Persona</h3><p>Based on the results of our survey and interviews, we created a <strong>Persona</strong> to <strong>define more precisely our target user</strong> and <strong>understand his pain points</strong>.</p><p>Meet Mehdi, our Persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCmFyThxu9QCtLlWZlgpZA.png" /><figcaption>Mehdi, our Persona</figcaption></figure><h3>Our Problem Statement</h3><blockquote><strong>Freelancers in IT who register on Cherry Pick</strong> need a way to <strong>highlight their job goals to match with good opportunities</strong> because <strong>otherwise they would stop using the platform</strong>.</blockquote><h3>Our Hypothesis</h3><blockquote>We believe that <strong>allowing freelancers to show their strengths during the registration process will make them feel valued and better help them find the job they are looking for</strong>. We will know we are <strong>right</strong> when the <strong>number of registration will go up</strong> and when we will have <strong>positive feedbacks from the users</strong>.</blockquote><h3>Ideation</h3><p>During the ideation process, we came up with many ideas to <strong>improve the registration process </strong>by<strong> brainstorming</strong>. We wanted to make it <strong>clearer, more efficient, and straight to the point</strong>.</p><p>Here are some of the main changes we decided to implement:</p><ul><li>Make the registration form fill the whole page</li><li>Move testimonials to the bottom of the page</li><li>Change the wording to make it more consistent and friendly</li><li>Let the user enter up to 3 different jobs</li><li>Review skill section</li><li>Add new relevant categories to the form</li></ul><h3>Low-fidelity Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fnPuZ0MXGDRh5K5tyTmCSw.png" /><figcaption>Low-fidelity Wireframes</figcaption></figure><p>After creating the <strong>low-fidelity wireframes</strong>, we did some <strong>concept testing</strong> to see if we were heading in the right direction with our solution. We <strong>iterated our prototype</strong> <strong>based on the feedback</strong> we had. For example, we had to change some wording, allow the user to add more than 5 technical skills, and allow the user to add an Average Daily Rate for each of his roles.</p><h3>Mid-fidelity Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dcclrn5LmI5j1Z2Ano0DQQ.png" /><figcaption>Mid-fidelity Prototype</figcaption></figure><p>We did a <strong>mid-fidelity prototype</strong> and conducted a <strong>usability test</strong>.</p><h3>High-fidelity Prototype</h3><p>We then <strong>iterated again </strong>after receiving feedback from the usability test<strong> </strong>on the <strong>high-fidelity prototype</strong>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQAHmnmRfvxU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQAHmnmRfvxU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQAHmnmRfvxU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a25b00af79c07950d901b17dca3080d0/href">https://medium.com/media/a25b00af79c07950d901b17dca3080d0/href</a></iframe><h3>Next Steps</h3><p>The next steps for this project would be to:</p><ul><li><strong>Iterate Usability Test</strong>:<strong> </strong>Real testing of the hi-fi prototype with freelancers</li></ul><h3>Conclusion</h3><p>This project was a great experience and the team at <strong>Cherry Pick</strong> was amazing! We really enjoyed working with them. Throughout this project, we could better <strong>see the impact of our work as UX/UI Designers</strong> and how <strong>each decision we make is important</strong>.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa71bc81a15d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Designing a Wellness App “Piatto”]]></title>
            <link>https://medium.com/@lobet.c/case-study-designing-a-wellness-app-piatto-2cdfa2d695bc?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cdfa2d695bc</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Sun, 23 Jan 2022 20:53:29 GMT</pubDate>
            <atom:updated>2022-01-26T13:53:45.099Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Project n°4: Wellness</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d6gf7FO6W5Cndary4gZ13A.png" /></figure><p><strong>Role</strong>: UX/UI designer</p><p><strong>Duration</strong>: 11 days (01/10/2022 to 01/20/2022)</p><p><strong>Team</strong>: <a href="https://medium.com/@zuninogreta">Greta</a> and I</p><p><strong>Platform</strong>: iOS</p><p><strong>Tools</strong>: Figma, Figjam</p><h3>Overview</h3><p>The challenge was to create an app for the <strong>National Wellness Institute</strong> that <strong>helps people adopt and maintain healthy eating habits</strong>.</p><h3>Competitive Analysis</h3><p>We started the project by doing a <strong>competitive analysis</strong> to have an <strong>overview of the current diet app market</strong> and see what <strong>features the other apps have</strong>.</p><p>We noticed that most apps have the 3 following features:</p><ul><li><strong>Tracking</strong>: other apps focus on tracking every meal in detail</li><li><strong>Calorie Counting</strong>: they are overly focused on calorie counting</li><li><strong>Coaching</strong>: coaching by a professional is a Premium feature</li></ul><p>After that, we used the <strong>CSD matrix</strong> tool (Certainties, Suppositions, and Doubts) to explore the context even more. Here are some assumptions we had:</p><ul><li>People don’t want to spend too much time entering data into a diet app</li><li>People feel stressed about counting calories</li><li>There are all kinds of dietary advice out there and it makes many people confused</li></ul><h3>Interviews &amp; Survey</h3><p>To check our assumptions, <strong>we first interviewed a certified dietitian</strong> named Anita. She told us the following things:</p><ul><li>“Most of my patients are young adults. They come to me to <strong>learn how to eat in a healthy way</strong>, more than to lose weight.”</li><li>“I created my Instagram account to <strong>reach more people</strong>, outside the clinic.”</li><li>“My main goal is to <strong>break the stereotype eating healthy = eating sadly</strong>.”</li></ul><p>Then we prepared the <strong>survey and interviews</strong> questions to <strong>better understand our target users’ needs and behaviors</strong>. Once we collected all the data, we did an <strong>Affinity Diagram</strong> to <strong>find patterns</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ejFUipcyDSkALUuB" /><figcaption>Survey results</figcaption></figure><p>From the answers to the survey, we discovered that <strong>most people believe that they already have a quite healthy diet</strong>. We asked them from 1 to 6, how healthy would they rate their diet and 47% answered 4 and 47% answered 5.</p><p>Also, <strong>78% of people</strong> who answered the survey said that <strong>dietitians are the only source of information they trust</strong>.</p><p>Next, we interviewed 5 people to get more detailed answers about people’s eating habits and their use of diet apps. Here are some interesting quotes from our interviews:</p><ul><li>“I have never consulted a dietitian, but <strong>if I had the opportunity I would</strong>.”</li><li>“<strong>Counting calories stressed me out</strong> and had a <strong>negative impact on my mental health</strong>.”</li></ul><h3>Persona</h3><p>Based on our user research, we created a <strong>Persona</strong> to <strong>define our user’s motivations, needs, goals, and pain points</strong>. Meet Claire, our Persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r82Hf8hDUQNTrdSUGDfPiQ.png" /><figcaption>Our Persona Claire</figcaption></figure><p>After creating the Persona, we did her <strong>Journey Map</strong> to see the <strong>process that she goes through </strong>and get more insights.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_wfnnK4Q4fx_9aZoETgWw.png" /></figure><p>The Journey Map showed us that her <strong>main pain points</strong> are:</p><ul><li>The <strong>lack of time and money </strong>to consult with a dietitian</li><li><strong>Accurate information</strong> about diet is <strong>hard to find</strong></li></ul><h3>Our Problem Statement</h3><blockquote>“<strong>People who have good eating habits</strong> need to <strong>educate themselves about nutrition</strong> because they want to <strong>have an even more balanced diet</strong>.”</blockquote><h3>Our Hypothesis</h3><blockquote>“We believe that <strong>giving guidance to people who want to have a healthier diet</strong> will allow them to <strong>strengthen their good eating habits and acquire new ones</strong>.<br>We will know we are <strong>right</strong> when people <strong>use the app over the long term and the rating of the app will increase</strong>.”</blockquote><h3>Ideation</h3><p>Starting from the Problem Statement, we started to think about the kind of app we wanted to create, its concept, and the implementation. Here are the things we wanted to include into our app:</p><ul><li><strong>Recommendations based on diet preferences:</strong> choice of diet (omnivore, vegetarian, vegan, etc.)</li><li><strong>No restrictive tracking system: </strong>no precise data entry, just tap to add</li><li><strong>Educate the user: </strong>tips, healthy eating plate illustration</li><li><strong>Help the user build good habits (become autonomous): </strong>food servings tracker</li><li><strong>Let the user check his progress: </strong>Progress tracker (stats)</li><li><strong>A bridge between user and dietitian: </strong>share stats with a dietitian</li></ul><h3>Brand Positioning</h3><p>We also thought about where we wanted to position ourselves within the market. We wanted our app to be easy-going and self-paced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSu34UdeBLop0Piy0Q5LAQ.png" /></figure><h3>Value Proposition Canvas</h3><p>Then we used the Value Proposition Canvas tool to help us <strong>ensure that a product is positioned around what the user values and needs</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rtLEIQu77wFfo353NbKpsA.png" /><figcaption>Value Proposition Canvas</figcaption></figure><h3>Low-fidelity Wireframes and Concept Testing</h3><p>After creating our <strong>User Flow</strong>, we did our <strong>Low-fi wireframes</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CnH_lZnXQz2J9cWx-WuiNg.png" /><figcaption>Low-fi Onboarding</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*BGmBeW5mqoRzvYhak8p9hw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Wg05Jcemg3qNsWlhtVrqsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*egBjWn2RKmvZYlxcLZl7uA.png" /><figcaption>Low-fi Homepage on the left, Stats in the middle, and Tips on the right</figcaption></figure><p>It was time for our <strong>Concept Testing</strong> and we <strong>iterated our prototype based on the feedback we had</strong>. Some feedbacks we had were to add a “Flexitarian” category, make the homepage more understandable, review the stats page, etc.</p><h3>Mid-fidelity Prototype</h3><p>Then we did the <a href="https://www.figma.com/proto/fuXhOW53Im6KI91gNXgFnV/Project-4_Wellness?page-id=56%3A56&amp;node-id=56%3A469&amp;viewport=241%2C48%2C0.13&amp;scaling=scale-down&amp;starting-point-node-id=56%3A469"><strong>Mid-fi prototype</strong></a> and a <strong>Usability Test </strong>to help us iterate our prototype.</p><h3>High-Fidelity Prototype</h3><h4>Moodboard</h4><p>For our app, we wanted something playful and colorful but not too overwhelming either. We decided to go with pastel colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVf1Os4heeUAdHagWf1BoA.png" /><figcaption>Piatto Moodboard</figcaption></figure><p>You can see our prototype in action below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FnS3TOy-CFvw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DnS3TOy-CFvw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FnS3TOy-CFvw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/29323b097ffd53cd4ff92e1770dc00ee/href">https://medium.com/media/29323b097ffd53cd4ff92e1770dc00ee/href</a></iframe><p><a href="https://www.figma.com/proto/fuXhOW53Im6KI91gNXgFnV/Project-4_Wellness?page-id=272%3A856&amp;node-id=272%3A857&amp;viewport=241%2C48%2C0.41&amp;scaling=scale-down&amp;starting-point-node-id=272%3A863">Here</a> is the Figma link to our high-fidelity prototype.</p><p>We did a <strong>Desirability Test</strong> to analyze the emotional response our users have to our design and lastly, we did another <strong>Usability Test</strong>.</p><h3>Next Steps</h3><p>Here are the next steps we would take:</p><ul><li>Add the other categories (vegetarian, vegan, etc.) and create the other flows</li><li>Iterate: keep testing and iterating the high-fidelity prototype</li><li>Product Viability: Analyze the viability of the product with the National Wellness Institute</li></ul><h3>Key Learnings</h3><p>During this project, we learned many things.</p><p>For example, we learned how to <strong>make an app more accessible </strong>by checking the contrast, how to use a <strong>value proposition canvas to understand what jobs our product is able to hold</strong>, how to <strong>make multi-state screens</strong> and <strong>apply micro-interactions</strong>, and how to conduct <strong>desirability testing</strong>.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cdfa2d695bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Connecting with Friends on Netflix]]></title>
            <link>https://medium.com/@lobet.c/case-study-connecting-with-friends-on-netflix-daeb66bff1b9?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/daeb66bff1b9</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Sun, 09 Jan 2022 17:23:21 GMT</pubDate>
            <atom:updated>2022-01-09T17:23:21.798Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Project n°3: Add a Feature</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UoKHTQQ_eM2iE1FhcfmXOg.jpeg" /></figure><p><strong>Role</strong>: UX/UI designer</p><p><strong>Duration</strong>: 4 days (01/03/2022 to 01/06/2022)</p><p><strong>Platform</strong>: iOS</p><p><strong>Tools</strong>: Figma, Figjam</p><h3>Overview</h3><p>For this project, I had to find ways to <strong>incorporate a new feature into an existing platform based on user needs </strong>and quickly iterate on proposed solutions <strong>under tight timelines</strong>.</p><p>I chose to work on the <strong>Netflix mobile app </strong>and suggested adding a new feature<strong> </strong>to<strong> connect with friends within the app </strong>(see what they are watching, what they recommend, etc.).</p><h3>User Research</h3><p>For the user research, we were asked to conduct <strong>guerrilla research </strong>and develop some insights in order to <strong>refine the proposed feature</strong>.</p><p>My assumptions were that:</p><ul><li>People using Netflix want to share online what they are watching and what they liked with their friends.</li><li>They want to be able to see this information directly on the platform.</li></ul><p>I first started with <strong>market research</strong> and did some <strong>competitors’ features research</strong>. I compared Netflix with its main competitors Amazon Prime Video and Hulu and I noticed that <strong>none of them had a feature to connect with friends</strong>. So I turned to other platforms such as Spotify which has the function to add friends and share content with them to make a comparison.</p><p>After that, I had to validate the user pain points so I performed a quick 5-question interview to learn about the desirability of the feature. When doing the affinity map, I found out that <strong>people would really enjoy having this kind of feature</strong>. However, they would also want to <strong>be able to manage the content they share</strong> with others.</p><p>Here are some quotes from the interviews:</p><ul><li>“It would be a <strong>good source of inspiration</strong> when I don’t know what to watch.”</li><li>“If I can decide what I want to share and who I want to share it with, I would like this kind of feature. It would make it <strong>easier for me to know what to watch next</strong>, especially<strong> </strong>if I know that this person has the same tastes as me.”</li></ul><p>Then, I created a Proto-Persona and his journey to develop an accurate picture of my target user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*c5omxg0yB-ZWzYSfEmh0pw.png" /><figcaption>Proto-Persona</figcaption></figure><p>It was now time to define the problem based on my research.</p><h3>Problem Statement</h3><blockquote><strong>Active Netflix users</strong> who enjoy being socially connected need to find a way to <strong>get some inspiration from friends</strong> who have the same tastes as them because <strong>they don’t know what to watch next</strong>.</blockquote><h3>Ideation and User Flow</h3><p>I started to ideate to figure out the details of my feature and created the user flow of the feature (Happy Path).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*avts_r5MDRyeLw_EyMvV3w.png" /><figcaption>User Flow</figcaption></figure><h3>Wireframes</h3><p>Now that I had the user flow figured out, I created the low-fidelity wireframes and a prototype with mid-fidelity wireframes using Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tefkMeQBHHr5hj29WN5fCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QDn7hz7PpSCs9MwN357cEA.jpeg" /><figcaption>Low-fidelity wireframe</figcaption></figure><h3>Usability Testing and Mid-Fidelity Prototype</h3><p>Using my mid-fi prototype, I conducted <strong>5 usability tests</strong> <strong>to validate the concept</strong>. All the testers thought the concept and prototype were good as is except for the friend’s profile page where the <strong>majority of testers preferred having carousels</strong> instead of columns to display the movies and TV shows. This is why I iterated the design with carousels.</p><p>Below are the wireframes with the 2 versions of the design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*16-eRmHgniyMmbKFHhWR0A.png" /><figcaption>Mid-fidelity wireframes</figcaption></figure><p>Link to <a href="https://www.figma.com/proto/2gitHLE5hUVJcMNzV58e0w/Netflix---new-feature?page-id=0%3A1&amp;node-id=5%3A47&amp;viewport=241%2C48%2C0.26&amp;scaling=scale-down&amp;starting-point-node-id=5%3A45">mid-fidelity prototype</a>.</p><h3>High-Fidelity Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ov-HruLYjxRXFIMGWzvOlA.png" /><figcaption>High-fidelity wireframes and one screen of the desktop version</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbYCNaqsa0hc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbYCNaqsa0hc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbYCNaqsa0hc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7caaaed9c4d93842faa515cd17df4614/href">https://medium.com/media/7caaaed9c4d93842faa515cd17df4614/href</a></iframe><p>Link to <a href="https://www.figma.com/proto/2gitHLE5hUVJcMNzV58e0w/Netflix---new-feature?page-id=46%3A951&amp;node-id=71%3A1524&amp;viewport=241%2C48%2C0.47&amp;scaling=scale-down&amp;starting-point-node-id=71%3A1334">High-Fidelity Prototype</a>.</p><h3>Design Critique</h3><p>After creating the high-fi prototype, we had a 15-minute design critique session.</p><p>A design critique refers to analyzing a design and giving feedback on whether it meets its objectives.</p><p>From this session, I learned that the following things could be improved in my design:</p><ul><li>“On the page to search for a profile, there are some gaps between the profile pictures, the usernames, and buttons.”</li><li>“The button below the search bar might suggest that the user can select both Movies and People. And I think the case is choosing one OR the other. That can be taught by interaction (when selecting one, the other unselects) or by affordance (looking for another component that suggests that behavior better, as ‘combined toggle’ or tabs)”</li><li>“Do we really need to select that we want to look for profiles? Facebook gives you different types of results that you can filter when you look for something.”</li></ul><h3>Next Steps</h3><p>The next steps would be to keep iterating the prototype based on feedback and add the other user flows.</p><p>I had to limit the prototype to only one user flow but the whole idea was:</p><ul><li>To <strong>use an algorithm:</strong> the order in which the movies and TV shows are displayed in the “Recommended by Friends” section on the first screen would be defined by the number of friends recommending a certain movie or TV show.</li><li>To have a <strong>privacy settings</strong> section in the user profile: the user can decide what content to share with other users and who to share it with.</li><li>To maybe add a <strong>matching percentage</strong>: the user can quickly see which of his friends have the same tastes as his.</li></ul><h3>Key Learnings</h3><p>I learned how to identify design opportunities based on user insights, how to analyze an already existing visual design identity, how to use mental models and patterns to enhance usability, how to respect navigation patterns and fit a new feature into an already existing product, and how to design for different scenarios and use cases.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daeb66bff1b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Redesigning a vinyl record store’s website]]></title>
            <link>https://medium.com/@lobet.c/case-study-redesigning-a-vinyl-record-stores-website-a3cdb785bc4c?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3cdb785bc4c</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Sat, 25 Dec 2021 14:28:06 GMT</pubDate>
            <atom:updated>2021-12-25T15:05:48.720Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Project n°2: e-Commerce/Practitioners Website</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XsIAatv2-HGfW2RhwBg-Ng.jpeg" /></figure><p><strong>Role</strong>: UX designer</p><p><strong>Duration</strong>: 1 week (12/9/2021 to 12/17/2021)</p><p><strong>Team</strong>: <a href="https://medium.com/@watsmyname">Ludovic</a>, <a href="https://medium.com/@zuninogreta">Greta</a>, and I</p><p><strong>Platform</strong>: Desktop</p><p><strong>Tools</strong>: Figma, Figjam</p><h3>Overview</h3><p>Our challenge this time was to <strong>design a desktop website</strong> for a <strong>local business</strong> or a professional to help him <strong>improve his online presence</strong> and to be <strong>more competitive</strong> in the actual market.</p><h3>Client and Business</h3><p>Our first mission was to find a client. My teammates and I chose to help a <strong>vinyl record store</strong> where one of my teammates often shops for vinyl records. The store is called <a href="http://www.betinos.com/">Betino’s Record Shop</a> and is located in Paris.</p><p>First, we thought about the most relevant questions we could ask the owner to better understand his business, his needs, and his customers&#39; needs. We then went to the store and interviewed the owner, Betino.</p><p>Our client has <strong>over 20 years of experience</strong> in the field, he owns both a <strong>physical and online store</strong>, his <strong>last website update was made in 2009</strong> (except for products), and his goal is to have regular customers.</p><p>The goals for his website were to:</p><ul><li>Reorganize the content</li><li>Modernize the design</li><li>Offer/display a larger catalog</li></ul><p>Below is a screenshot of Betino’s Record Shop current website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z6JZvvH1ORhKOPR1f6xi8g.png" /><figcaption>Betino’s Record Shop current website</figcaption></figure><p>We wanted to understand what exactly wasn’t working and what could be improved on his website so we conducted a <strong>Heuristic Evaluation </strong>to find the usability problems in the user interface design.</p><p>Here are the different problems that we have found:</p><ul><li><strong>Aesthetic and minimalist design problems</strong> (the<strong> </strong>colors used in his website, the title is difficult to read, too much description below each album, etc.)</li><li><strong>Flexibility and efficiency of use</strong> <strong>problems</strong> (not convenient to search for an artist, too much text, etc.)</li><li><strong>Consistency and standards</strong> <strong>problems</strong> (mix of English and French throughout the website, etc.)</li></ul><h3>Competitive Analysis</h3><p>After that, to better understand where our client currently stands on the market and what could be missing on his website, we decided to do a SWOT (strengths, weaknesses, opportunities, and threats) analysis and also to compare his website with the <strong>most popular vinyl records online stores</strong>.</p><p>We found out that our client’s website fulfilled most of the evaluation criteria but that many <strong>elements on his website were disorganized</strong>.</p><p>And curiously, the website doesn’t show Betino’s strength: <strong>reviews and recommendations</strong> from an expert</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IDGAp7jM_w4BAZZCIFYYxw.png" /><figcaption>Competitive analysis</figcaption></figure><h3>Secondary Research</h3><p>After benchmarking and market research, we did secondary research to learn more about the vinyl record industry. Here are some interesting facts that we have found:</p><ul><li>“Driving force behind this vinyl revival is <strong>Millennial and Gen Z consumers</strong>” (source: <a href="https://www.readersdigest.co.uk/culture/music/why-is-vinyl-making-a-comeback">Readers digest</a>)</li><li>“In France, the vinyl industry only represented 1% of the physical market in 2012; this number reached <strong>20% in 2018</strong>” (source: <a href="https://www.diggersfactory.com/fr/blog/120/the-growing-market-of-vinyl-records">Diggersfactory</a>)</li><li>“Vinyl records have become a <strong>decorative object</strong>. <strong>41%</strong> of the buyers in the UK are not using their turntables and <strong>7%</strong> of them don’t even own a turntable but <strong>buy vinyl records.</strong>” (source: <a href="https://www.diggersfactory.com/fr/blog/120/the-growing-market-of-vinyl-records">Diggersfactory</a>)</li></ul><h3>User Research</h3><p>Then we started our user research with a <strong>CSD Matrix</strong> (Certainties, Suppositions, and Doubts) to define the scope of the challenge, considering: 1) what we know; 2) what we think we know and 3) what is still unknown but needs to be investigated.</p><p>From that, we prepared questions to create a survey and to conduct interviews to have a <strong>clearer vision of the behaviors and needs</strong> of our target users, the <strong>vinyl record buyers</strong>.</p><p>We used the <strong>Affinity Diagram</strong> tool to <strong>find patterns</strong> within all the data we collected.</p><p>The results of our survey showed us that <strong>most people buy vinyl records in both physical and online stores, many people buy in physical stores only, and very few people buy online only</strong>. Also, the <strong>two main reasons</strong> <strong>why people buy online</strong> are that online stores often <strong>offer a larger catalog</strong> and buyers can also <strong>compare prices</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/1*VrUX1J_AqM8kmIk9Aow-yw.png" /><figcaption>results of the survey</figcaption></figure><p>We also had interesting insights when interviewing vinyl record buyers.</p><p>Here are some quotes from our interviews:</p><ul><li>“<strong>I buy online when I cannot find the vinyl record</strong> I am looking for anywhere else.”</li><li>“Sometimes <strong>web pages are not clear</strong> about what kind of music they sell and it <strong>takes time</strong> <strong>to understand</strong> whether the record I am looking for is <strong>available or not</strong>.”</li><li>“A <strong>nicely sorted record shop</strong> is always making it <strong>more pleasant to <em>dig</em></strong>. I like when <strong>genres are easy to distinguish</strong> from one another.”</li></ul><h3>Persona</h3><p>Based on the results of our user research, we created a <strong>Persona</strong> to <strong>help us define and understand our users’ needs, pain points, and goals</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kti-lAIZ4ONyr3c6baBYjw.jpeg" /><figcaption>Our Persona</figcaption></figure><p>His <strong>Journey Map</strong> also revealed that his main <strong>pain points</strong> are:</p><ul><li>Browsing through the catalog to find a specific record is <strong>time-consuming</strong></li><li><strong>Lack of information</strong> about the record prevents him from completing his task of buying a record</li><li><strong>Struggling with the buying process</strong> because of the <strong>complexity of the website</strong> leads to frustration</li></ul><p>With all our previous research, we are now able to define our problem and start thinking about how to solve it.</p><h3>Our Problem Statement</h3><blockquote>Music lovers who buy vinyl records need to find a way to <strong>research and finalize the purchase online</strong> because they feel lost and frustrated about the <strong>lack of organization</strong>.</blockquote><h3>Our Hypothesis</h3><blockquote>We believe that <strong>creating a website with structured information</strong> for <strong>vinyl record buyers</strong> will <strong>simplify their online buying process</strong>. We will know we are right when <strong>online sales increase and users can complete the purchase more quickly</strong>.</blockquote><p>During the <strong>ideation</strong> process, we came out with <strong>two essential features</strong> that we wanted to incorporate into the new website:</p><ul><li><strong>Advanced Filtering System</strong>: To find vinyl records regarding specific criteria such as genre, year, condition, and format.</li><li><strong>Structured Information</strong>: A logical and well-organized content allowing users to make successful predictions about where to find things.</li></ul><h3>User Flow</h3><p>We created a <strong>User Flow</strong> before starting our wireframes. We focused on the single main flow that will solve our Persona’s problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fVdByibxB3nCNbZvY6hkdA.png" /></figure><h3>Usability Testing</h3><p>After creating wireframes and the first mid-fi prototype, we wrote a scenario for the <strong>Usability Test</strong>. The goal was to test how easy our design is to use with a group of representative users.</p><p>The tasks for our testers were the following:</p><p><strong>1 — Look for a vinyl record of a specific genre and decade</strong></p><ul><li>Search for Soul music from the 70s</li></ul><p><strong>2 — Listen to an album preview</strong></p><ul><li>Listen to the first choice you see in the results</li></ul><p><strong>3 — Buy the album</strong></p><ul><li>Check the information page and buy the album</li></ul><h3>Feedbacks from Usability Tests</h3><p>Here are some recurring feedbacks we had from our different testers:</p><ul><li><strong>The “Explore” button was not highlighted</strong>:<strong> </strong>users first <strong>browsed the whole Homepage to find it</strong> in order to do a search on the website</li><li><strong>An in-store experience online</strong>:<strong> </strong>Users want a <strong>more personalized experience</strong>. They are expecting to have <strong>recommendations and reviews from the staff</strong> on the website</li><li><strong>Filters</strong>:<strong> </strong>Users wished some of the filters were <strong>organized and displayed differently</strong></li></ul><h3>Final Mid-Fi Prototype</h3><p>After taking into account the usability testers’ feedbacks, we iterated our mid-fi prototype until it reached its final version. Here is a recording of the main flow:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOREKT5I75yg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DOREKT5I75yg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOREKT5I75yg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b18e6e7bf0d40fd5ec7edc444e6bbe3f/href">https://medium.com/media/b18e6e7bf0d40fd5ec7edc444e6bbe3f/href</a></iframe><p>Here is also the link to our <a href="https://www.figma.com/proto/nS1mjtX23TKOlagMTP1ARz/Record-Store-Mid-Fi-Prototype-(Final)?page-id=0%3A1&amp;node-id=2%3A2&amp;viewport=241%2C48%2C1.07&amp;scaling=scale-down-width&amp;starting-point-node-id=2%3A2">final mid-fi prototype</a> on Figma.</p><h3>Next Steps</h3><p>The next steps of our project would be to:</p><ul><li>Create a <strong>functional prototype</strong>: Once the mid-fi has been tested, develop a hi-fi prototype</li><li><strong>Iterate Usability Test</strong>:<strong> </strong>Real testing of the hi-fi prototype with Betino’s Record Shop customers</li><li><strong>Business Viability</strong>:<strong> </strong>Analyse the viability of the online business model with the store owner resources</li></ul><h3>Key Learnings</h3><p>During this project, we have learned how to do a <strong>business analysis</strong> and how we can help not only the end-users but also the client to <strong>reach his business goals</strong> <strong>through a well-designed web application</strong>.</p><p>We also learned how to <strong>logically organize, structure, and label the content</strong> of a website following the principles of <strong>information architecture</strong> so that the end-user naturally finds what he is looking for.</p><p>We used <strong>UI components and Atomic Design methodology </strong>to help us create consistency throughout the website.</p><p>And finally, we learned about <strong>Usability Testing. </strong>Through <strong>observation</strong> <strong>of the user interacting</strong> with the prototype, we could validate if we were moving in the right direction. This helped us<strong> iterate our prototype </strong>to find the<strong> best design possible </strong>for the website.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3cdb785bc4c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Paperwork to study abroad made easier]]></title>
            <link>https://medium.com/@lobet.c/study-case-paperwork-to-study-abroad-made-easier-96a07765e5a?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/96a07765e5a</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Thu, 09 Dec 2021 22:01:34 GMT</pubDate>
            <atom:updated>2021-12-29T17:28:52.871Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack Project n°1: Wicked problems</p><p><strong>Role</strong>: UX designer</p><p><strong>Duration</strong>: 1 week (11/30/2021 to 12/8/2021)</p><p><strong>Team</strong>: <a href="https://medium.com/@Awa.Camara">Awa</a>, <a href="https://medium.com/@malloryagoumba">Mallory</a>, <a href="https://medium.com/@zuninogreta">Greta</a>, and I</p><p><strong>Platform</strong>: mobile</p><p><strong>Tools</strong>: Figma, Miro</p><h3>Overview</h3><p>As part of the Ironhack bootcamp, we had to design a solution for a given problem. Here is the brief that my teammates and I had:</p><blockquote><strong>How might we help migrant people find the information, complete the tasks and successfully get their paperwork done to start their life in a new city.</strong></blockquote><p>Starting from that, we had to reduce the scope and define our end-users.</p><h3>User Research</h3><p>We used the <strong>Research Learning Spiral</strong> to plan our user research.</p><p>We first thought about covering the subject by destinations and targeting people moving to France or French people moving abroad but we quickly realized that it was still too broad and difficult to cover so we decided to narrow it down and we chose instead <strong>people who want to study abroad as end-users</strong>.</p><p>Once the end-user was defined, we did <strong>secondary research</strong> on the topic and created a <strong>CSD matrix</strong> to identify the doubts and assumptions to be addressed in further research.</p><p>Our first assumptions were:</p><ul><li>There is <strong>no existing app</strong> helping users to complete this task</li><li>There is a <strong>lot of information</strong> <strong>to look for</strong> in order to immigrate successfully</li><li>Information about immigration can sometimes be <strong>difficult to understand</strong></li></ul><p>We then used <strong>quantitative and qualitative methods</strong> to clarify these and created a questionnaire for our survey and an interview script. The survey was helping us get objective measurements and the interview was helping us empathize more with the user and get anecdotal evidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*02zFDO37I_SfuM6Xyp6KFQ.png" /><figcaption>Insights from survey</figcaption></figure><p>From the results of our survey, we could see that finding information about the paperwork wasn’t easy for everyone.</p><p>After that, we interviewed 8 people and their answers were even more insightful. We analyzed the data we collected from the survey and interviews and looked for patterns using an <strong>affinity diagram</strong>. That is when we could clearly identify the main <strong>pain points</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tMFqN4mZkQIvND16RnrTw.png" /><figcaption>Insights from interviews</figcaption></figure><p>Our next step was to develop a <strong>persona</strong> based on our research findings to create understanding and empathy with the end-users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/951/1*RDzwHPZnEWmA8Izr7qIcrw.png" /><figcaption>Persona</figcaption></figure><p>We also built a <strong>journey map</strong> to better understand Julie’s struggles and how we could help her. Below is the whole process she has to go through to get her paperwork done to be able to study abroad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*2byd-7lWTRlUSqMhmXxMSg.png" /><figcaption>Journey map</figcaption></figure><p>We can see that there are two phases in her application process (research and application) and we thought that we had to <strong>focus on one phase</strong> to make sure our solution will be the most refined possible.</p><p>For that, we had to re-define our scope:</p><ul><li>The <strong>research</strong> being the <strong>main pain point</strong>, it is the one we have to solve first.</li><li>We need to <strong>facilitate the research</strong> of information for people going to study abroad.</li><li>If we make the research easier, the <strong>whole application process will be smoother.</strong></li></ul><p>Now we had to give a <strong>clear and concise</strong> description of the issue that need to be addressed with a problem statement.</p><h3>Our Problem Statement</h3><blockquote><strong>People who want to study abroad</strong> need to <strong>find accurate information to do their paperwork</strong> because <strong>the lack of clear information and support makes this process difficult and stressful</strong>.</blockquote><p>We also wrote a hypothesis statement to help us think about what <strong>results we should look for</strong> in this experiment and define <strong>clear criteria for success and failure</strong>.</p><h3>Our Hypothesis</h3><blockquote>We believe that <strong>providing accurate information and connecting people who want to study abroad with people who already had the same experience (in the same country) </strong>will make<strong> the immigration paperwork smoother</strong>. We will know we are <strong>right</strong> with <strong>the reduction of paperwork application time and with positive feedback from users</strong>.</blockquote><h3>The solution</h3><p>After using many brainstorming techniques with my team, we came up with 2 solutions to our problem that we decided to combine.</p><p>1- An <strong>app</strong> helping students to know the right procedure to go to the country of their choice with an <strong>up to date checklist</strong> <strong>of the required documents</strong>. Some of the main features would be:</p><ul><li><strong>Detailed information</strong> about each document using a <strong>simplified wording</strong></li><li><strong>Samples</strong> showing how to fill out the documents</li><li><strong>Average timeline</strong> of the whole procedure</li><li><strong>Document names translated</strong> in the language set in the app</li></ul><p>2- <strong>A matchmaking tool</strong> to connect people wanting to study abroad with people who already had the same experience: mentors.</p><ul><li><strong>Rating option:</strong> so that the student knows the mentor is trustworthy</li><li><strong>Filters to select the mentor</strong> of our choice: hobbies, university, etc.</li></ul><h3>The Wireframe</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QmL9T-PwyTZoSQRl5zI6Q.png" /><figcaption>Sign Up screens</figcaption></figure><ul><li>On the first screen, the user selects his language.</li><li>Next, he enters his email address and sets up his password to Sign Up.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*btw728KeZeOwh-Je7lc7LQ.png" /><figcaption>Registering as a prospective student</figcaption></figure><ul><li>The user then selects whether he is a prospective student or a mentor. In this case, he will select “Student”.</li><li>He enters some necessary personal information such as his citizenship and his country of destination in order to get the right information about paperwork according to his situation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1alhXLer0lIY-JYTD5QfzA.png" /><figcaption>Documents checklist and matchmaking feature</figcaption></figure><ul><li>On the next screen, the result of his search appears with <strong>all the next steps</strong> he has to do in order to get his paperwork done and an <strong>official and updated</strong> <strong>checklist of the required documents</strong> for his application. Next to each required document name, the user can find <strong>information in plain English</strong> and with <strong>samples</strong> to better understand how he should fill out some documents. If the user needs more help he can connect with a mentor by clicking on the button at the bottom of the screen.</li><li>After clicking on the button “Need more help? Connect with a mentor!”, the user lands on the matchmaking page where <strong>he can choose a mentor among people who had the same experience as his</strong> and can provide support. He can <strong>use the filters to find a mentor</strong> with a high rating, a mentor who went to the same university as his abroad, etc.</li></ul><h3>What’s Next</h3><p>For this project, that would be the next steps we would have taken:</p><ul><li><strong>Expand our offer</strong> to more countries</li><li>Add <strong>more languages</strong></li><li>Wireframe our <strong>chat option</strong> with mentors</li></ul><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96a07765e5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing Spotify]]></title>
            <link>https://medium.com/@lobet.c/wireframing-spotify-92a861a4b00d?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/92a861a4b00d</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 10:44:59 GMT</pubDate>
            <atom:updated>2021-10-31T11:01:39.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack’s Prework — Challenge 2: Wireframing</h3><h4>What is a Wireframe?</h4><p>Wireframes give a simple visual representation of how the flow of the app or website we are creating will be. They are the basic structure that we use to build upon.</p><h4>The Challenge</h4><p>My task for this challenge was to create a wireframe version of the user flow of a chosen app based on screenshots and using Figma.</p><p>I have chosen Spotify for this challenge because I often use this app myself and it is probably the most popular digital music streaming service so many people can relate to it. The other reason why I chose this app is that its use is pretty straightforward, and it is intuitive.</p><h4>The User Flow</h4><p>The next step was to choose a user flow. I decided to go for the search of an artist and then play one of his popular songs. I think it is one of the most basic user flow within this app.</p><p>Below are the screenshots of this user flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ynr91nxlykh2bBWQL2za3g.png" /><figcaption>Spotify’s basic user flow example</figcaption></figure><p>Below are the wireframes of this same user flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PUDcRJvfLIE-MspFgu7ZeQ.png" /><figcaption>Wireframe of the user flow</figcaption></figure><h4>What UI elements can we see in this app?</h4><ul><li><strong>Icons</strong>: such as the notification bell, the history, and the settings. In this case, they trigger a specific action.</li><li><strong>Tab bar</strong>: allow the user to move back and forth between “Home”, “Search”, and “My Librairy”</li><li><strong>Buttons</strong>: such as the images of playlists, albums, and podcasts that are linked to more content.</li><li><strong>Cards</strong>: cards are containers displaying different kinds of content side by side and the user can tap on them. In Spotify, cards often contain a cover and a text.</li><li><strong>Input field</strong>: the search bar is one of the main features of the app</li><li><strong>Carousel</strong>: allow the user to browse through a set of content such as the “Featuring” section in Spotify</li><li><strong>Toggle</strong>: such as the “play” and “pause” button, the “following” button to follow an artist, playlist, or podcast, and the heart icon to like a song. The user can turn them on and off.</li><li><strong>Lists</strong>: the user can choose one item at a time from a list of options (songs, artists, playlists, etc.)</li><li><strong>Notifications</strong>: there are blue dots in Spotify indicating there is something new to check out</li><li><strong>Slider controls</strong>: The user can adjust a value. In Spotify, the slider is used as both a progress bar and a controller for the songs.</li><li><strong>Tags</strong>: they help the user find content in the same category quickly. In Spotify, we can see tags such as “Top”, “Artists”, “Songs”, “Playlists”, etc.</li></ul><h4>Task analysis of the flow</h4><p>Regarding the task analysis of the flow I chose to work with, first, there is the Home screen where the user taps on the “Search” button on the tab bar, then he taps on the search bar at the top of the screen and inputs his search using the keyboard. The search box already makes suggestions based on what the user is typing and all the user has to do is click on one. In this case, we tap on the artist&#39;s name and then we land on the artist page with his popular songs listed first followed by his popular releases.</p><p>Then we tap on the most popular song and it plays the song. We can see the progress bar of the song, and other changes on the screen indicating that the song is currently playing. Lastly, if we tap on the fixed bar with the name of the artist and the song title at the bottom, it opens up a page with an extract from the video clip or the album cover, more details about the song, and more interactions with it such as sharing it or liking it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*LH-fjuKucKjNgOQ7d3L3GQ.png" /><figcaption>Flow of the prototype on Figma</figcaption></figure><p>Here is the <a href="https://www.figma.com/proto/ZoyqX0yvwABpMYQRVaUD4W/Ironhack-Prework---Challenge-2---Wireframing?page-id=0%3A1&amp;node-id=2%3A11&amp;viewport=241%2C48%2C0.13&amp;scaling=contain&amp;starting-point-node-id=2%3A11">link to my prototype</a>!</p><h4>Conclusion</h4><p>I am new to UX/UI design but having already experience with coding, it was quite easy for me to see the components that were used to create this app before wireframing it. However, it was interesting to see how Spotify created a UX flow that leads to a seamless user experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92a861a4b00d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a new feature for Citymapper]]></title>
            <link>https://medium.com/@lobet.c/designing-a-new-feature-for-citymapper-1b6eb0b1ef12?source=rss-cd7aa99fed98------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b6eb0b1ef12</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Célia Lobet]]></dc:creator>
            <pubDate>Wed, 20 Oct 2021 15:06:16 GMT</pubDate>
            <atom:updated>2021-10-20T15:29:37.447Z</atom:updated>
            <content:encoded><![CDATA[<h4>Ironhack’s Prework — Challenge 1: Design Thinking</h4><p>Hi everyone!</p><p>First of all, let me introduce myself. I’m Célia and I will be attending Ironhack’s UX/UI Design Bootcamp in Paris in about a month.</p><p>I will be posting many other challenges and works in the next few months.</p><p>Here is my first challenge: designing a new feature for Citymapper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qdFzv5Yi8pHVO3V7ZmVBjA.png" /></figure><h4>What is Citymapper?</h4><p><a href="https://citymapper.com/">Citymapper</a> is a public transit app and mapping service which displays transport options, usually with live timing, between any two locations in a supported city. The app includes all urban modes of transport such as walking, cycling, driving, and of course, public transport.</p><h4>The problem</h4><p>Citymapper already solves some of the main problems of urban mobility, however, there is one pain point for many users: the different amount of public transport tickets the users have to purchase.</p><p>Very often buying different public transport tickets is necessary to go from point A to B. And the process of buying these tickets can be very annoying (queues, vending machines that don’t work, etc).</p><p>Finally, things like pricing or purchasing the correct ticket can become a real pain when you are abroad.</p><p>My task for this challenge is to <strong>create a new feature</strong> for this app <strong>using the</strong> <strong>design thinking process</strong>.</p><h3>1. Empathize</h3><h4>Personal Introspection</h4><p>First, I had to ask myself these questions.</p><p><em>What problem am I solving?</em></p><ul><li>The difficulty of purchasing tickets in different places</li><li>Not knowing which tickets to buy</li><li>Not knowing where to buy these tickets</li><li>Not knowing the accurate price of a ticket beforehand</li></ul><p><em>Who is my audience?</em></p><p>Anyone who uses public transport, especially abroad, and who uses their smartphone for daily tasks.</p><p><em>Who is my client’s competition?</em></p><ul><li>Google Maps</li><li>Moovit</li><li>Transit</li></ul><p><em>What’s the tone/feeling?</em></p><p>Easy and trustworthy</p><h4>Interviews</h4><p>After that, I interviewed 5 users from my environment.</p><p>Here are the main pain points that I have found:</p><ul><li>The public transit system is different from a country to another and it is difficult to understand how it works. They don’t know which ticket to buy, where to buy it, and its validity time. And sometimes their language is not available on the vending machines.</li><li>Users have to download different apps to buy different tickets</li><li>Difficulties to recharge their pass with their phone (detection issue)</li><li>They want to limit their interaction with machines or turnstiles for sanitary reasons</li><li>The itinerary suggested by the app is not always the best</li></ul><h3>2. Define</h3><p>The next step was to define a problem statement, focusing on the user’s viewpoint.</p><p><strong>The main pain point is having to purchase many tickets in different places</strong> which leads to confusion, stress, and a waste of time.</p><p>The new feature for this app will solve the pain of having to purchase different public transport tickets by different channels making the buying process easier and more convenient.</p><h3>3. Ideate</h3><p>After using brainstorming techniques to generate a lot of ideas to solve the problem, I came up with 2 solutions.</p><p>To solve this problem, the user should be able to buy all of the tickets needed at once through the app and have them in his phone. Considering the users’ needs and habits, a contactless ticketing system was an obvious choice because it is extremely convenient and allows faster payment and boarding.</p><h4>First solution: NFC Ticketing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ECsLr2ja6kCEtRssWlYxqw.jpeg" /><figcaption>NFC Ticketing</figcaption></figure><p>Near-Field Communication (NFC) ticketing has many advantages:</p><ul><li>Fast, secure, and efficient</li><li>Frictionless tap-and-go experience</li><li>Number of NFC-enabled mobile devices worldwide increasing</li><li>Available even if a phone’s battery is flat</li></ul><h4>Second solution: QR Code</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXXv0zUyjS3hYIdlQFG1mg.jpeg" /><figcaption>QR Code Ticketing</figcaption></figure><p>Quick Reference (QR) Codes also have their advantages:</p><ul><li>Quick and cheap to implement</li><li>Available on any mobile devices</li><li>Can be scanned from a long distance</li></ul><h3>4. Prototype</h3><p>I have chosen NFC Ticketing as a solution for this app because it seemed to be a more viable long-term solution compared to QR Codes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R5FEXY0N6gnRr3tn83GTig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ufXuF5mYpsavcg59TXADjA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oq5a6DM2R92U5l5FNYqjAA.jpeg" /></figure><p>1- The user enters his destination.</p><p>2- The user chooses one of the suggested itineraries.</p><p>3- The user can click on the “Buy Tickets” button to buy tickets for the selected trip.</p><p>4- The user can check one more time the selected trip, the price, and proceeds to payment.</p><p>5- The user can either see the tickets he bought or go back to the itinerary. By clicking on the itinerary, he can check the steps to get to his destination and he only needs to ‘tap-and-go’ at ticketing barriers using his smartphone.</p><p>6- The user can see the itinerary.</p><h3>Conclusion</h3><p>I found the interview part very interesting. I really enjoyed interviewing my friends on topics we would have probably never talked about otherwise. Hearing their experiences with public transport gave me new perspectives on the subject. I could understand their points of view and they also gave me information about things I didn’t know about.</p><p>And when doing my research to find a solution, I had the opportunity to learn more about new technologies, which I really liked.</p><p>In conclusion, Design Thinking is a lot about learning and gathering information and putting everything together to come up with the best solution for the users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b6eb0b1ef12" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>