<?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 Aurelie Jean on Medium]]></title>
        <description><![CDATA[Stories by Aurelie Jean on Medium]]></description>
        <link>https://medium.com/@aureliejean.design?source=rss-19e79397ca49------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*86qUDg0Yil9Hrn7UgIeNmw.png</url>
            <title>Stories by Aurelie Jean on Medium</title>
            <link>https://medium.com/@aureliejean.design?source=rss-19e79397ca49------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:15:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aureliejean.design/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 — Optimizing the Riise Quiz: A UX Approach to Boost Completion and Engagement]]></title>
            <link>https://medium.com/@aureliejean.design/case-study-optimizing-the-riise-quiz-a-ux-approach-to-boost-completion-and-engagement-da544a7c486e?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/da544a7c486e</guid>
            <category><![CDATA[health-tech-startup]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design-for-mobile-apps]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[health-technology]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Wed, 12 Feb 2025 19:11:41 GMT</pubDate>
            <atom:updated>2025-02-13T09:44:58.600Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study — Optimizing the Riise Quiz: A UX Approach to Boost Completion and Engagement</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZaNYOWPzG4ig9b60vv4Qw.png" /></figure><h4>Establishing new habits</h4><p>I’m feeling as stressed as excited by the end of this Bootcamp so I started a new habit that I would like to keep: I’m <strong>meditating for 3 minutes</strong> before the beginning of class with Christophe André. It helps me focus on myself and take control over all the rumination. I also started playing some soothing music: <a href="https://www.youtube.com/watch?v=uwEaQk5VeS4">handpan</a> and <a href="https://www.youtube.com/watch?v=53j2gJ21H9w&amp;t=2549s">guitar in the forest</a>. <br>Since this project is the last — especially with a real client — <strong>I want to have the best mindset and set everything up to feel better after the Bootcamp.</strong> When the real world, away from school and the teaching nest, appears, and when I will have to fight to find my place, I want to have 100% of my mental strength to do so.</p><h4>Riise</h4><p>Now, let me introduce our stakeholder: <a href="https://www.weriise.co/?lang=en"><strong>Riise</strong></a>, a supplement brand that provides science-backed, <strong>personalized health solutions</strong>. Their product line is designed to offer tailored recommendations based on individual needs, helping users optimize their well-being through carefully formulated supplements.</p><figure><img alt="Riise — All-in-one personalized supplements — Picture with the logo, the slogan and the process to get your supplement." src="https://cdn-images-1.medium.com/max/1024/1*Eb0CywdNlbWchOa22OjFQg.png" /><figcaption>Riise — All-in-one personalized supplements</figcaption></figure><p>One of their key digital touchpoints is an <strong>online quiz</strong> designed to guide users toward supplement recommendations. However, the quiz faced challenges with<strong> low completion and conversion rates</strong>, indicating <strong>friction in the user experience.</strong></p><p><a href="https://medium.com/@apostolbianca91">Bianca</a> — my partner in crime during this Bootcamp and I, were missioned to <strong>rethink the quiz experience</strong> to make it more engaging, informative, and easier for users to complete, <strong>ultimately increasing conversion.</strong></p><p>First, if we want to be on the same page, you’ll find below the picture that illustrates one flow (Sleep as the focus area) from the first question to the last outcome screen.</p><figure><img alt="Illustration of the current user flow of Riise’s quiz" src="https://cdn-images-1.medium.com/max/1024/1*gNZKlpOy-g5UaLpJoukwFg.jpeg" /><figcaption>Current user flow of Riise’s quiz</figcaption></figure><h3>1. Understanding the Product &amp; the Problem</h3><h4>Secondary Research</h4><p>One month before the launch of this final project, we met one of the co-founders of the brand. Thanks to this informal meeting, we already had an understanding of the issues they wanted to improve.</p><p>While we were waiting for our stakeholder&#39;s first official meeting, <strong>we researched the product, users, and market</strong>. This allowed us to gain a deeper understanding of the<strong> industry landscape</strong>, <strong>user expectations</strong>, and potential <strong>areas for optimization</strong> within the quiz experience.</p><h4>Heuristic Analysis</h4><p>We also took this time to conduct a heuristic evaluation of the existing product. Two things particularly stood out:</p><ul><li><strong>Lack of visibility in quiz progression (1. Visibility of System Status):</strong> There was a progress bar at the bottom, but it was not very visible and was difficult to interpret.</li><li><strong>Limited context and explanation for users (10. Help and Documentation):</strong> The quiz provided little guidance or clarity on its flow and logic, leaving users uncertain about why certain questions were asked.</li></ul><h4>Stakeholder Interview</h4><p>To prepare for this interview, we took a step back to consider the bigger picture. Our goal was to better <strong>understand their brand, target audience, competitors, and overall vision for the future.</strong></p><p>After I led the interview questions, I reflected on this moment and realized how proud I was of myself. Before starting this Bootcamp, I would have been terrified at the idea of doing this. I would have been unsure and might have even avoided it altogether. But now, I am gaining confidence in my English — also thanks to my fabulous teammate, Bianca, who is super helpful and supportive.</p><p>We gained valuable insights that we could later apply in the process:</p><ul><li><strong>Values</strong>: Transparency is key — everything in their product is clear, with no hidden ingredients. They prioritize only efficient additions, without unnecessary extras for flavor or appearance.</li><li><strong>Users</strong>: The typical user is 60% female and 40% male, aged 35–55. Most users engage in sports more than once a week.</li><li><strong>Unique Selling Point</strong>: A blend of personalization and convenience — offering an all-in-one, fully personalized, and transparent solution.</li></ul><h4>Market Research</h4><p>After discussing with the stakeholders, we conducted a competitive analysis using <strong>SWOT</strong> analysis (as illustrated in the picture below) and a <strong>market positioning mapping</strong> to better understand Riise’s place in the industry.</p><figure><img alt="A visual representation of the SWOT analysis for Riise, outlining their strengths, weaknesses, opportunities, and threats in the competitive market of personalized supplements." src="https://cdn-images-1.medium.com/max/1024/1*CTDcw-EMbQiHJmVqHX55Aw.jpeg" /><figcaption>SWOT Analysis for Riise: Key Insights into Strengths, Weaknesses, Opportunities, and Threats</figcaption></figure><h3>2. Understanding the Users</h3><h4>User Research: Surveys &amp; Interviews</h4><p>Given the tight deadline, we focused on reaching <strong>Riise’s actual users</strong> by distributing a survey through their community media. Additionally, we targeted <strong>sports communities</strong> — as the stakeholder mentioned that their audience often includes people who exercise more than once a week — as well as our own contacts. Our goal was to gain a broader perspective on who might be interested in supplementation, the reasons behind their interest, and their struggles.</p><p>In the end, we gathered <strong>51 responses</strong>. The key struggles people shared with us were:</p><ul><li><strong>Lack of Information (76%)</strong> — Many users found it difficult to identify a supplement that truly fit their needs, feeling overwhelmed by the abundance of choices.</li><li><strong>Trust Issues (82%)</strong> — A significant number of respondents expressed concerns about ingredient transparency, scientific backing, product effectiveness, and overall quality.</li></ul><p>We then interviewed 6 of these individuals to gain a better understanding of their <strong>habits</strong>, <strong>lifestyles</strong>, and their <strong>awareness of the supplement industry</strong>. The goal was to identify what motivated them to start taking supplements, as well as their expectations and perceptions regarding such products.</p><h4>Empathy Map</h4><p>Next, we created an <strong>empathy map</strong> to put ourselves in the user’s shoes and ensure we truly understood their thoughts, emotions, and pain points. I find this exercise incredibly valuable and helpful — it shifts our mindset entirely. At that moment, <strong>we were no longer Aurélie or Bianca; we were the user.</strong></p><p>Some key insights that emerged from this exercise included:</p><ul><li><em>“I don’t know if it’s effective.”</em></li><li><em>“I don’t know which brand to trust and choose.”</em></li><li>The main user<strong> needs</strong>: <strong>transparency</strong> about ingredients and scientific backing, <strong>guidance</strong> throughout the selection process, and <strong>clarity</strong> in how information is presented.</li></ul><p>These were just a few of our takeaways. You can explore more in the <strong>empathy map visualization</strong> below.</p><figure><img alt="An empathy map outlining user thoughts, feelings, pain points, and motivations to enhance the design process and create a user-centered experience." src="https://cdn-images-1.medium.com/max/1024/1*sRsS6eOiX7u3ouwhnAqWrg.jpeg" /><figcaption>Empathy map created to align with users’ thoughts, emotions, and pain points, ensuring a deeper understanding of their needs.</figcaption></figure><h4>User Persona &amp; Journey Map</h4><p>Our <strong>persona,</strong> as illustrated below, is Lena, a 40-year-old <strong>Social Media Manager </strong>based in Berlin.</p><p>Recently, Lena switched to a <strong>vegan diet</strong>, and while she is committed to this lifestyle, she has noticed a <strong>decline in her energy levels</strong>. She struggles to maintain the same level of focus and productivity she used to have.</p><p>One key lesson I learned from creating this persona is the importance of <strong>basing motivations and frustrations on the persona as an individual, rather than just the situation they are experiencing</strong>. This shift makes the persona more <strong>realistic and relatable</strong>, ensuring that design solutions address <strong>core user needs</strong> rather than just temporary circumstances.</p><figure><img alt="Illustration of Lena, a 40-year-old Social Media Manager from Berlin, designed to represent the persona in the context of the Riise project." src="https://cdn-images-1.medium.com/max/1024/1*kTpZPhszaM2slpzuro-aeQ.png" /><figcaption>Lena, our ideal user for Riise</figcaption></figure><p>To better understand Lena’s experience and decision-making process, we mapped out her <strong>current journey</strong> — from the moment she decided to participate in a 10K charity run to the point where she gave up on Riise and searched for another solution on her own.</p><p>This <strong>user journey mapping exercise</strong> helped us pinpoint key struggles and identify opportunities for improvement. It raised important <strong>“How Might We” (HMW)</strong> questions, such as:</p><ul><li><strong>HMW guide her through the quiz more effectively?</strong></li><li><strong>HMW help her understand the relevance of each question?</strong></li><li><strong>HMW convince her to complete the quiz?</strong></li><li><strong>HMW keep her engaged throughout the process?</strong></li></ul><p>By addressing these challenges, we can design a <strong>more seamless and engaging experience</strong> for users like Lena. See the image below for a detailed view of her user journey map.</p><figure><img alt="A visual representation of Lena’s journey, outlining her experience from signing up for the 10K charity run to abandoning Riise and seeking another supplement solution." src="https://cdn-images-1.medium.com/max/1024/1*oMDlBk2I04PrtMb9QVWYUQ.png" /><figcaption>Mapping Lena’s journey: From her decision to join the 10K charity run to her frustration with Riise and the search for an alternative solution.</figcaption></figure><h4>Problem Statement</h4><p>We then crafted the following <strong>problem statement</strong> for the user:</p><blockquote><em>Health-conscious mid-lifers in Europe who </em><strong><em>want to maintain and enhance their lifestyle</em></strong><em> need a reliable </em><strong><em>way to reach their wellness goals</em></strong><em> by discovering </em><strong><em>trustworthy sources</em></strong><em> because currently, they </em><strong><em>feel overwhelmed</em></strong><em> by marketing claims, </em><strong><em>struggle to find information </em></strong><em>tailored to their needs, and doubt whether the products will actually work.</em></blockquote><p>We also crafted the <strong>problem statement for the business</strong>:</p><blockquote><em>Our personalized supplements are designed </em><strong><em>to support the wellness</em></strong><em> needs, goals, and overall well-being </em><strong><em>of our users</em></strong><em>. However, we have observed that the </em><strong><em>quiz</em></strong><em> — our key feature for gathering user insights — </em><strong><em>is not meeting user expectations</em></strong><em> in terms of guidance and clarity. Users struggle to understand the importance and relevance of the questions, leading to lower completion and engagement rates, which ultimately impacts our conversion rate.</em></blockquote><p>By combining both <strong>user and business problem statements</strong>, we ensure that our redesign addresses <strong>both perspectives</strong> — enhancing the user experience while also aligning with Riise’s business objectives.</p><h3>3. Ideation &amp; Information Architecture</h3><p>Based on our research, we defined three key focus areas:</p><ol><li><strong>Improve quiz flow &amp; clarity</strong> — by reducing the cognitive load and improving guidance.</li><li><strong>Integrate value-added information</strong> — by showing the users why each question matters.</li><li><strong>Enhance engagement</strong> — by using micro-interactions, visuals, and progress indicators to improve completion rates.</li></ol><p>We also decided to <strong>benchmark competitors</strong> and explore design inspirations. For this, I love using <strong>Dribbble </strong>to gather fresh ideas or <strong>Mobbin</strong> to see what is currently working on the market.</p><p>I also took some time to step away from the screen and let my imagination flow more freely. Instead of focusing only on immediate, feasible solutions, I explored <strong>more creative, out-of-the-box ideas</strong>, even if they weren’t fully implementable within our timeframe.</p><p>For example, I thought about designing a <strong>vortex-inspired loading page</strong>, where all the nutrients swirl around, creating a more immersive and engaging transition for users. This exercise helped me <strong>break out of constraints.</strong></p><h4>User Flow</h4><p><strong>1. Current User Flow</strong></p><p>We illustrated the user flow of the quiz, mapping out the journey from clicking the <strong>CTA to the payment page</strong>. To make our analysis more concrete, we screenshot each screen while focusing on two key areas: <strong>sleep and energy</strong>.</p><p>It was a <strong>long and meticulous process</strong>, but it gave us a clear <strong>overview of the current experience</strong>. The final flow ended with <strong>more than 40 steps</strong>, highlighting how complex and potentially overwhelming the journey was.</p><p>Creating this <strong>visual breakdown</strong> allowed us to <strong>identify friction points</strong> before diving into potential solutions.</p><p><strong>2. Future User Flow (as illustrated below)</strong></p><p>We divided the quiz into three thematic sections: <strong>Goals</strong>, <strong>Habits</strong>, and <strong>Profile </strong>to make the experience feel less intimidating by <strong>clarifying the structure</strong> and informing users about what to expect next.</p><p><strong>Changes we made:</strong></p><ul><li><strong>Sections for clarity:</strong> distinct sections helped users understand <strong>where they were in the process</strong> and what they had left to complete. This also provided a clear <strong>sense of control</strong> as they moved through the quiz.</li><li><strong>Condensed questions:</strong> one of the biggest challenges was reducing the number of questions. We<strong> gathered related questions</strong> together. For example, instead of asking several separate questions about weekly or daily consumptions (Seafood, Meat, Alcoholic drinks…), we combined them into a single screen.</li><li><strong>Question relevance:</strong> we evaluated each question’s relevance to the quiz’s purpose. The aim was to <strong>remove</strong> <strong>anything that wasn’t directly helping Riise</strong> provide tailored supplement recommendations.</li></ul><figure><img alt="A visual of the proposed future user flow, designed to reduce intimidation by providing clear structure and guidance for users throughout the experience." src="https://cdn-images-1.medium.com/max/1024/1*42u9RlKwXf-xMWLbRPj_8A.png" /><figcaption>After User Flow</figcaption></figure><h4>Low-Fi</h4><p>To explore different ideas and approaches for the quiz flow, Bianca and I decided <strong>to each create our own version</strong> of the Low-Fi prototype. We wanted to see where our <strong>design approaches overlapped</strong> and where we could <strong>challenge each other’s thinking.</strong></p><h3><strong>4. Prototype &amp; Iterate Based on Feedback</strong></h3><h4>Mid-Fi</h4><p>Once we had the Lo-Fi version, it was easier to visualize the flow and translate it into a Mid-Fi wireframe. We focused on designing the <strong>main screens and interactions to optimize time</strong>, given the project’s constraints. After conducting <strong>5 usability tests </strong>with users, we implemented several changes based on feedback:</p><ul><li>Removed introductory screens for each step (too many clicks)</li><li>Added an onboarding step for the swipe interaction</li><li>Reworded screens, particularly those about weekly/daily consumption selection</li><li>Made the slider interaction more intuitive</li><li>The biggest change: Moved the profile-related questions to the beginning of the quiz</li></ul><p>We then <strong>tested the Mid-Fi prototype with our client</strong>, who was generally satisfied with the flow and particularly loved the proposition for the portion per week slider input. However, he suggested two changes:</p><ul><li>Requesting the user’s email earlier in the process to gather data and facilitate follow-up if the quiz is incomplete</li><li>Splitting the profile-related questions into two screens to make them more digestible</li></ul><h4>Hi-Fi</h4><p>Next, we moved on to choosing the color scheme. Since Riise’s colors are very intense, we wanted to keep the design simple, smooth, and soft. We <strong>experimented with several combinations</strong> until we found one that was easy on the eyes while <strong>remaining faithful to the brand’s core colors.</strong></p><p>We began by <strong>organizing the Figma file</strong>, incorporating Riise’s brand colors and the nuances we had created from them. The typography and grid were already included from the Mid-Fi phase.</p><p>We also had to <strong>update the user flow</strong>, as it became obsolete after receiving feedback from both our clients and users.</p><p>Then we <strong>created the components </strong>for the screens, small cards that consisted of an icon and title, and then sliders, dropdowns, and rolling numbers for height and weight, as well as the progress bar. We started with one page as a reference point and designed the others accordingly.</p><p>The icons were quite a challenge! To find consistent icons, adjust outline thickness, and occasionally modify their structure. The Icon Set became the largest one I’ve worked on to date, teaching me a lot about <strong>organizing icon content in files</strong> (Icon/Diet/Vegan categories).</p><p>We also paid significant attention to <strong>micro-interactions</strong>, dedicating considerable time to these small but impactful details. For example, we worked on the onboarding effect for the swiping cards and designed overlay animations for the “Why we ask this” section.</p><p>You can find below a short video of the quiz prototype flow from the hero section to the pricing page.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F22oesKMbVYc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D22oesKMbVYc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F22oesKMbVYc%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78af46288f6b3e1a35d5b03435e722f3/href">https://medium.com/media/78af46288f6b3e1a35d5b03435e722f3/href</a></iframe><h3>What Comes Next?</h3><p>While our project focused on improving the mobile quiz experience, there are still key steps to refine and expand our work:</p><ul><li><strong>Transfer the mobile concept to a desktop version</strong> — Adapting the improved quiz flow to a desktop format, ensuring a seamless experience across devices.</li><li><strong>Conduct more usability testing for other screens</strong> — While we tested and iterated on the main quiz flow, further usability testing on additional screens (such as the results page or checkout process) could uncover more opportunities for optimization.</li><li><strong>Prepare handoff</strong> — Finalize documentation and design specs to ensure a smooth transition for developers, including annotations, responsive behavior guidelines, and interaction details.</li></ul><h4><strong>Key Learnings &amp; Challenges:</strong></h4><ul><li><strong>Iterative design</strong>: Moving from Lo-Fi to Mid-Fi and receiving user feedback highlighted the iterative nature of UX design.</li><li><strong>Handling complexity</strong>: Dealing with the quiz’s complex structure and long user flow was a challenge. Simplifying and condensing questions, as well as rethinking how to present them, required careful thought.</li><li><strong>Stakeholder collaboration</strong>: Having the opportunity to get client feedback early and adjust the design accordingly helped ensure the project aligned with their expectations.</li><li><strong>Micro-interactions and visual design</strong>: Creating smooth, engaging transitions helped make the user experience feel more cohesive and less overwhelming. It was challenging but rewarding</li><li><strong>Time management</strong>: Managing the project within the time constraints was difficult. Prioritizing key aspects of the design, like the user flow and essential screens, while still ensuring high quality, was a constant balancing act.</li></ul><p>Congrats, you’ve made it to the end — no progress bar needed! 🎉 Hopefully, this journey was easier to complete than a long, clunky quiz. Thanks for following along!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da544a7c486e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BreakBuddy: Enhancing Workplace Wellness for Desk-Bound Professionals]]></title>
            <link>https://medium.com/@aureliejean.design/case-study-breakbuddy-your-companion-for-your-workplace-wellness-4db8060d7b8e?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/4db8060d7b8e</guid>
            <category><![CDATA[wellness-app]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[app-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-process]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Sat, 25 Jan 2025 10:33:56 GMT</pubDate>
            <atom:updated>2025-01-29T08:08:53.962Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Hero Cover of BreakBuddy App Design" src="https://cdn-images-1.medium.com/max/1024/1*F93eHAuu3z3YnlYksdJgzA.png" /><figcaption>Hero Cover of BreakBuddy App Design</figcaption></figure><p>This week, we kicked off an exciting new project: designing a wellness app. As someone <strong>deeply passionate about wellness</strong>, I couldn’t be more thrilled. I’ve tried countless apps in this space — from meditation and habit trackers to fitness and yoga apps — so diving into this industry feels like a perfect fit.</p><p>I’m teaming up with <a href="https://medium.com/@apostolbianca91">Bianca</a>, my partner for the final project, and it’s an amazing chance to strengthen our collaboration and explore how we can bring out the best in each other.</p><h4><strong>An Overview of Our Design Challenge</strong></h4><p>The Daily Health Conference, a (fictitious) global non-profit promoting health and wellness, aims to expand its impact through two initiatives: a mobile app for members and a modern design system reflecting an innovative approach to wellness.</p><h4>Our Mission</h4><p>(Should we choose to accept it) Design a mobile app that helps users adopt and sustain a health-improving routine, focusing on one key aspect of wellness such as fitness, nutrition, meditation, or time management. The app should <strong>empower users</strong> to set personal goals, track their progress, and maintain control of their data.</p><h4><strong>Core Features</strong></h4><p>The app must include essential functionalities:</p><ul><li>Personalized profile setup and goal-setting.</li><li>Progress tracking and feedback (notifications, error messages, etc.).</li><li>GDPR compliance for user data management.</li></ul><p>From the beginning of the Bootcamp, we have relied on the <strong>Design Thinking</strong> methodology to shape our process — this project was no exception. This human-centered approach enables us to <strong>deeply understand user needs</strong>, generate creative solutions, and craft designs that truly resonate. Let me guide you through this journey and show you how it all came together.</p><h3>1. Understanding our users</h3><h4><strong>First Things First</strong></h4><p>We kicked off the process by <strong>brainstorming</strong> ideas for tackling the challenge of standing out in an oversaturated market. Neil — our lead teacher, reassured us that the idea didn’t need to be groundbreaking — what mattered most was choosing something we were passionate about working on.</p><p>After exploring a variety of concepts, we both agreed on one that truly resonated with us: <strong>wellness in the workplace.</strong> This broad topic immediately sparked our interest, as it could encompass physical or mental well-being, and could take many forms. For example, it might involve a tool for employers to gather insights on employee wellness, or a personal app designed to help individuals feel more peaceful at work.</p><p>The possibilities were endless, but that’s where the UX strategy comes into play. By leveraging <strong>user research</strong> and <strong>focusing on real needs</strong>, we knew we could narrow this vast subject into a clear and actionable direction.</p><h4><strong>Moving Forward with UX Strategy</strong></h4><p>After our brainstorming session, we turned our attention to developing our UX strategy, and to do that, we used the <strong>Lean UX Canvas</strong>. It’s a great tool that helps, both us and the company, figure out if the product we want to create is something <strong>users actually need and want.</strong></p><p>As you can see on the next picture, the Lean UX Canvas helps us focus on the most important things: who our <strong>target users</strong> are, what their <strong>pain points</strong> are, and how our product can <strong>solve</strong> those <strong>problems</strong>. It’s a simple yet <strong>effective way</strong> to quickly <strong>validate ideas</strong> without spending too much time or resources on things that might not work.</p><figure><img alt="Lean UX Survey Canva for our Workplace Wellness App project" src="https://cdn-images-1.medium.com/max/1024/1*SEb2SiEIEb8jEsxq5-v2wg.png" /><figcaption>Lean UX Survey Canva for our Workplace Wellness App Project</figcaption></figure><h4>Tracking Down Desk Workers: The Search for Survey Participants</h4><p>We then launched our Lean Survey Canvas and shared the survey on platforms like Reddit and Slack. Finding the right group of respondents proved to be more challenging than expected. While desk workers aren’t hard to find, it was tough to ensure they were willing to <strong>take the time to answer the survey</strong>. To boost our research, we reached out to personal contacts who, we knew were working long hours at a desk. We managed to gather 32 responses.</p><p>To ensure getting relevant answers, we started the questionnaire by asking if respondents were desk workers, which helped us filter the responses effectively.</p><p>We gathered some <strong>valuable insights</strong>. For instance, over 80% of respondents work between 5 and 10 hours a day sitting, and 100% reported experiencing physical discomfort or mental fatigue during the day. Even more promising, over <strong>80% said they’d be willing to use a workplace wellness app</strong>. These results were really encouraging for the product we’re looking to launch!<br>On a smaller note, I’m also getting more comfortable with Google Forms, so that’s a little victory too.</p><h4>Crafting the Interview Guide</h4><p>Once we got started, the interview process posed its own set of challenges. It was a long day of <strong>brainstorming</strong> questions, and by the end, we were feeling pretty <strong>drained</strong>. However, we stayed organized by creating a checklist with the key points we wanted to cover in the interview. We made sure to carefully check the <strong>logical flow of our guide.</strong></p><p>At the end of the exercise, it was tough to step back and assess, so we asked Neil for feedback. We were really proud (and relieved!) when he confirmed that our questions aligned well with the exercise.</p><h4>User Voices: Real Needs of Desk Workers</h4><p>Booking sessions with interviewees proved to be quite difficult, as we spent a lot of time waiting for people to become available. At this stage, it was tricky because we couldn’t move forward or make progress without gathering all the insights, so the day felt like it was <strong>moving slowly.</strong></p><p>In the end, we <strong>interviewed six people</strong>, and some clear <strong>patterns emerged</strong>. Sitting all day was a challenge for both the body and mind, yet many people found themselves stuck in front of their screens, letting the day pass by without realizing it. They expressed a strong need for more physical activity — mainly <strong>walking, stretching, and getting fresh air.</strong></p><p>What I appreciated was that we didn’t go in with many assumptions. We <strong>let the users share their stories</strong>, their needs, and pain points, which gave us a clearer direction.</p><h4><strong>Synthesizing the Research</strong></h4><p>Next, we completed the <strong>empathy map </strong>illustrated below, which really helped us step into the users’ shoes. Since the survey responses and interview insights aligned, the findings were quite clear.</p><figure><img alt="Empathy Map helping us create a shared understanding of user needs" src="https://cdn-images-1.medium.com/max/1024/1*IB6ZYXrk7u4r3kaf38005Q.png" /><figcaption>Empathy Map Helping Us Create a Shared Understanding of Users</figcaption></figure><h3>2. Pinpointing the Core Problem</h3><h4>Shaping Our User Persona and Journey</h4><p>Next, we focused on creating the user persona and mapping out the user journey. We developed <strong>Maria Martinez</strong>, a marketing manager who’s an ambitious hard worker. However, as she and her partner discuss the possibility of having a baby, she realizes the way she works needs to change to accommodate her new priorities, that’s her journey as illustrated on the next picture.</p><p>One important lesson I learned during this process was to <strong>make the persona imperfect</strong>. It’s much easier to relate to a persona with flaws or struggles, and this helps us <strong>design more realistically</strong>. Another key point was ensuring that there’s an <strong>event or story that triggers the realization</strong> for the persona — something that motivates them to understand they’re not on the right track and <strong>need a change</strong>. For Maria, this was the realization that her work-life balance wasn’t sustainable as her personal life evolved.</p><figure><img alt="User Journey Map of Maria Martinez" src="https://cdn-images-1.medium.com/max/1024/1*1bvs9iT-PRC_piUrUQQuPg.png" /><figcaption>User Journey Map of Maria Martinez -An Eye-Opening Decision</figcaption></figure><p>These <strong>two exercises</strong> were particularly <strong>demanding</strong>. Everything had to be cohesive and logical, with clear connections between her personality, needs, and journey. We had to carefully consider why she would need our product and ensure everything aligned perfectly. It was a challenging process.</p><h4>Understanding the Gaps We Can Fill</h4><p>Based on our user journey map, we were able to refine the following <strong>How Might We</strong> statements:</p><ul><li>How might we help users build their <strong>confidence</strong>?</li><li>How might we help them <strong>carve out time</strong> for themselves?</li><li>How might we support them in improving their physical health?</li><li>How might we help them <strong>prioritize their well-being</strong> during work hours?</li><li>How might we help them avoid <strong>feeling overwhelmed</strong>?</li></ul><p>From this research work we then have defined the following problem statement: <br><em>Desk workers who are navigating a life change need to find a way to establish more consistent and beneficial routines at work because currently they are losing track of time in front of the screens, which is causing negative physical and mental effects to their bodies through fatigue and stress.</em></p><h3>3. Generating Concepts</h3><h4>From Ideas to Priorities: Crazy 8 and MoSCoW in Action</h4><p>Next, we dove into the ideation process using the Crazy 8 method. We started by<strong> listing the key features</strong> we wanted to design and then sketched out different screen concepts to bring those ideas to life.</p><figure><img alt="Bianca’s Crazy 8 Ideation Board" src="https://cdn-images-1.medium.com/max/1024/1*AwEh5IuXybJXCJzhTFpM2g.png" /><figcaption>Bianca’s Crazy 8 Ideation Board</figcaption></figure><figure><img alt="Aurélie’s Crazy 8 Ideation Board" src="https://cdn-images-1.medium.com/max/1024/1*ldXaFEVi0vnRxEedd9_fpA.png" /><figcaption>Aurélie’s Crazy 8 Ideation Board</figcaption></figure><p>Once we had a collection of ideas, we turned to the MoSCoW method to prioritize them. While it was <strong>tough to let go of some concepts</strong>, like allowing users to customize when they receive break reminders or offering complete flexibility in their daily plans, we focused on the ideas that would deliver the most value. Personalizing and altering the UI was another feature we chose to leave out for now.</p><h4>Skipping Steps: A Lesson Learned</h4><p>We jumped straight into creating the low-fidelity wireframes without first designing the sitemap and user flow. <strong>Big mistake.</strong> Our eagerness to dive into the design phase got the best of us, and with Friday upon us, we were in a rush to have something ready for testing over the weekend so we could keep moving forward.</p><p>Let me tell you,<strong> it’s not going to happen again</strong>. Skipping those foundational steps made it so much harder to organize our ideas and maintain clarity in our designs. <strong>Lesson learned!</strong></p><h4><strong>Concept Testing: A Wake-Up Call</strong></h4><p>We tested the concept with users (people who don’t typically prioritize their mental well-being), and to be honest, it was a bit <strong>frustrating</strong>. The person that I tested with, struggled to understand some steps and wanted more guidance. Instead of being asked what habits he wanted to implement, he preferred to be presented with a suggested routine — something tailored to him.</p><p>The essential thing is, that feedback gave us a clearer direction on how to improve the user experience and make the app more engaging.</p><h4><strong>User Flow &amp; Site Map: Simplifying the Complex</strong></h4><p>We found ourselves stuck on the user flow and site map. We were <strong>trying to incorporate too many must-haves into a single flow</strong>, which left us with confusing user flows. We wanted to include everything — like the habit tracker page, the profile, and, of course, the dashboard (the main focus of this project). This <strong>overthinking cost us valuable time.</strong></p><p>At the end, we took a step back and simplified the user flow as you can see in the next picture. We narrowed it down to the core concept: g<strong>uiding the user from receiving a notification to completing their habits and tracking their progress.</strong></p><figure><img alt="BreakBuddy Userflow : From a Push Notification to Tracking Progress" src="https://cdn-images-1.medium.com/max/1024/1*JHgDkFrUWycE7bVYQUe5qA.png" /><figcaption>BreakBuddy Userflow : From a Push Notification to Tracking Progress</figcaption></figure><p>At the same time, we worked on the <strong>site map</strong> as illustrated below. Here, too, we ran into challenges — getting caught up in the depth and number of templates. It took longer than expected, but we finally sorted it out.</p><figure><img alt="BreakBuddy Sitemap" src="https://cdn-images-1.medium.com/max/1024/1*Vx39YW49xPrM4PiZfk3tEQ.png" /><figcaption>BreakBuddy Sitemap</figcaption></figure><h3>4. Transforming Concepts into Tangible Models</h3><h4><strong>Mid-Fi &amp; Usability Testing</strong></h4><p>Next, we shifted our focus to organizing and refining our work for the Mid-Fi wireframes. We began by establishing grids, typography styles, and creating reusable components to ensure consistency and save time when transitioning to Hi-Fi designs. From this point onward, we<strong> prioritized both efficiency and coherence.</strong></p><p>By the end of the day, we made significant progress and had a Mid-Fi prototype ready for user testing. <strong>It was exciting to see everything start to take shape!</strong></p><p>We conducted usability tests, and the results were truly insightful. While some of the feedback was anticipated — given that we hadn’t fully refined the micro-interactions for example — it still highlighted key areas that needed improvement. For instance, certain texts were too lengthy, an alternative screen caused confusion, and one navigation element felt unnecessary.</p><h4><strong>Hi-Fi Prototype</strong></h4><p>We started by applying our chosen colors to Figma’s Style Settings, making it easier to adjust later based on desirability testing. We also conducted <strong>accessibility testing using Figma’s “Contrast”</strong> plugin to make sure our content was readable.</p><p>The biggest challenge was <strong>establishing the branding</strong>. We designed a “buddy” character — central to the brand — who acts as a<strong> supportive companion</strong>, reminding users to stay active, track progress, and stay motivated. Using Adobe Firefly, we created these buddies in 3D and paired them with playful icons and pictograms for our cards. Matching everything visually took time, but it was worth it. We also wanted to strike a <strong>harmonious balance </strong>between the app’s being used during working time, provided by employers, so <strong>stay professional </strong>and <strong>creating a personal space</strong> where each individual feels completely at ease.</p><p>At the end, we managed to achieve what we envisioned, you can have a look on the wireframes below. Of course, there’s always room for improvement, and <strong>we could keep refining endlessly</strong>. But the deadline brought everything into focus — and that’s actually a good thing. <strong>Deadlines </strong>push you to work efficiently, prioritize what matters most, and embrace the imperfections in your design. Sometimes, knowing when to stop is just as important as knowing how to start.</p><figure><img alt="Daily Tasks Screens — From Notification to Completion of Morning Task" src="https://cdn-images-1.medium.com/max/1024/1*pGPyvjPlLem8AyReCUw9ZQ.png" /><figcaption>Daily Tasks Screens — From Notification to Completion of Morning Task</figcaption></figure><figure><img alt="Account Screen — Offering the Possibilities to Change Buddy / Set-up New Goals / Change Setting on Data Privacy" src="https://cdn-images-1.medium.com/max/1024/1*2GeWfJju-rCfNJ7LgWAG3g.png" /><figcaption>Account Screen — Offering the Possibilities to Change Buddy / Set-up New Goals / Change Setting on Data Privacy</figcaption></figure><figure><img alt="Dashboard Screens — Tracking Daily / Weekly / Monthly activities" src="https://cdn-images-1.medium.com/max/1024/1*VUPDZqwpcwhI_mSVDdXRVw.png" /><figcaption>Dashboard Screens — Tracking Daily / Weekly / Monthly activities</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kNKfTyPjpCo-nsASHObIw.png" /><figcaption>Alternative Screens — Loading Screen for the Introduction / System Update Waiting Screen / Connectivity Issues Page</figcaption></figure><h4>What’s next?</h4><p>Looking ahead, we plan to refine our high-fidelity prototype and enhance micro-interactions to ensure a seamless user experience. We aim to conduct <strong>additional desirability testing</strong> and are considering integrating a <strong>voice assistant</strong> to improve accessibility. To boost user engagement, we intend to incorporate more <strong>personalization and gamification</strong> elements, such as allowing users to choose their buddy and theme and introducing challenges to motivate them.</p><h4>Key Learnings &amp; Challenges</h4><ul><li><strong>Balancing Ambition with Simplicity:</strong> Narrowing down features to focus on user needs was a challenge for us, but it was essential to design an MVP.</li><li><strong>Collaboration and Adaptability:</strong> Working as a duo demanded constant communication, compromise, and agility, especially when refining designs in real time. Despite the challenges, it was a very nice experience, and Bianca and I were perfectly in sync throughout the process. Our strength lies in our meticulous attention to detail, though it’s also our <strong>greatest challenge</strong> at times.</li><li><strong>Accessibility Awareness:</strong> Testing with tools like Figma’s contrast plugin emphasized the importance of inclusivity in design.</li></ul><p>Thank you for sticking with me until the end! Your dedication deserves a little <em>BreakBuddy</em> reminder: don’t forget to take a moment for yourself today — stretch, breathe, or maybe even take a quick walk. After all, we all need that balance to keep going strong!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4db8060d7b8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing for learning: Flippy Learn, a vocabulary app makeover]]></title>
            <link>https://medium.com/@aureliejean.design/designing-for-learning-flippy-learn-a-vocabulary-app-makeover-72c021b0c957?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/72c021b0c957</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[app-redesign]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[learning-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Sat, 11 Jan 2025 09:42:46 GMT</pubDate>
            <atom:updated>2025-01-25T08:57:00.125Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Flippy Learn Logo : a smiling robot with an A and a chinese sign gravitating above its head" src="https://cdn-images-1.medium.com/max/1024/1*EdNPiKRWgwLEQZnj_M5SFw.png" /><figcaption>Flippy Learn Logo</figcaption></figure><h4>A two-day challenge</h4><p>Wednesday, December 13th, our instructor gives us a bold challenge: redesign an app or create a few wireframes. The goal? To apply the <strong>10 principles of heuristic design</strong> we had just learned that morning. Challenge accepted, with a tight deadline set for Friday, December 15th. Two days to deliver.</p><h4>Choosing the right project</h4><p>It’s a solo project, and we’re given complete freedom in selecting the app. My first instinct was to explore topics I’m passionate about, like <strong>wellness</strong> and <strong>health</strong>. However, following my instructor’s advice, I decided to dig through <a href="https://github.com/dkhamsing/open-source-ios-apps?tab=readme-ov-file">open-source apps on GitHub</a> for inspiration.</p><p>After some unsuccessful researches, I‘ve found a hidden gem : <a href="https://github.com/misteu/VocabularyTraining">Flippy Learn</a>, a vocabulary learning app . The app’s design was a bit outdated, offering plenty of room for a fresh, modern aesthetic. But what truly hooked me was its concept: an app that allows you to save vocabulary words in any language, create personalized lists, and learn through interactive games. Perfect!</p><h4>Why this app?</h4><p>This choice felt personal. Ever since starting this bootcamp in English, I’ve been writing down every useful new word I encounter in a notebook. This app could streamline my learning process. No more carrying a physical notebook around; I’d have everything at my fingertips. <strong>Super convenient, right?</strong></p><h4>A quick, strategic decision</h4><p>Finding this app was a turning point — it freed up time to focus on the redesign itself. Reflecting on it, I realize that my recent experience on a group project helped me here. By prioritizing efficiently and committing to a direction, I avoided overthinking what might be “better.”</p><h3>Step 1: Capturing key screens</h3><p>The challenge was to create <strong>four wireframes</strong> for the app redesign. Simple enough, right? Not quite. The app’s structure was minimal. Selecting just four screens felt limiting. Instead, I decided to take a more holistic approach.</p><p>Rather than isolating individual screens, I chose to follow a <strong>logical user flow</strong> and design a more cohesive experience, yet not totally finished.</p><p>Below you can find an overview of the user experience showcasing the flow from language creation to interactive word games and word editing.</p><figure><img alt="The overview of the user experience showcasing the flow from language creation to interactive word games and word editing." src="https://cdn-images-1.medium.com/max/1024/1*lo-CWIm7Wspbv9PR_Le8Lw.png" /><figcaption>The entire Flippy Learn journey: from creating a language to playing with words, and even editing them.</figcaption></figure><h3>Step 2: Identifying broken design principles</h3><p>Once the app’s key screens were laid out in my Figma canvas, the real analysis began. It was time to pinpoint the <strong>violated design principles</strong> and identify areas for improvement. As you can see on the following picture, here’s what stood out:</p><ol><li><strong>Aesthetic &amp; Minimalist Design</strong><br>The app lacked visual consistency. Some screens felt incoherent, as if they belonged to different products. There was no clear <strong>brand identity</strong> running through the design. Worse, the experience was confusing: some pages felt too sparse, while others were cluttered, with overwhelming pop-ups that made navigation frustrating. Even the most crucial screen — the game interface — felt messy because of unnecessary overlays, reducing its impact.</li><li><strong>Help &amp; Documentation</strong><br>Users were left to fend for themselves, often guessing what to do next. Buttons lacked clear labels, forcing users to experiment to understand their function. On the rare occasions when guidance was provided, it was often vague or illogical, adding to the confusion.</li><li><strong>Recognition rather than Recall</strong><br>The app offered little in terms of user assistance, like <strong>suggestions</strong>, <strong>autocomplete</strong>, or corrections for minor errors such as typos. This lack of support forced users to rely heavily on memory, creating unnecessary friction in the overall experience.</li></ol><figure><img alt="Collection of app screenshots with annotations pinpointing design flaws and suggesting areas for enhancement." src="https://cdn-images-1.medium.com/max/1024/1*CuuYwHn3MblurYPrevRaQQ.png" /><figcaption>Annotated screenshots highlighting violated design principles and areas for improvement</figcaption></figure><p>Clearly, there was plenty of room for improvement. My goal was to propose meaningful enhancements and rethink the user experience.</p><h3>Step 3: Drawing inspiration from competitors</h3><p>After identifying the app’s weaknesses and potential areas for improvement, it was time to seek inspiration. To do this, I turned to <strong>competitor research</strong>.</p><p>I began by exploring what similar apps in the market were offering. By analyzing their features and design choices, I identified elements I liked and imported them into my Figma workspace for reference. I paid particular attention to <strong>e-learning applications</strong> on Dribbble, which provided a wealth of creative ideas.</p><p>One concept I had in mind was incorporating <strong>flipping cards</strong> to enhance interactivity and engagement. This guided my search and helped narrow down relevant examples.</p><p>With a solid collection of material and ideas, I felt ready to dive into the <strong>creation phase</strong>.</p><h3>Step 4: Establishing a design framework</h3><h4>Colors</h4><p>I started by importing the <strong>Flippy logo</strong> into my Figma canvas. The logo featured fresh, modern colors, which I decided to retain and highlight in my redesign. It felt like a missed opportunity that these colors weren’t emphasized in the original design.</p><p>For the new color scheme, I selected:</p><ul><li><strong>Neon green</strong> as the primary accent color,</li><li><strong>Forest green</strong> as the secondary/subdominant color,</li><li>A <strong>lighter hue of forest green</strong> for backgrounds, creating a soft yet cohesive look.</li></ul><p>To complement these, I developed a subtle <strong>green-tinted palette</strong> of blacks and grays, derived from the forest green base, to maintain harmony across the design.</p><h4>Typography</h4><p>For the typography, I stuck with the original typeface: <strong>Inter</strong>. It’s clean, legible, and highly functional — perfect for this type of app.</p><h4>Grid, Icons, and Buttons</h4><p>To ensure consistency and usability, I consulted<strong> </strong>ChatGPT for<strong> guidelines</strong> on typography sizes, icon dimensions, button standards, and grid systems. This helped me define a framework to keep the design cohesive and user-friendly. You can see how I set up my style tile in the picture below :</p><figure><img alt="Visual style guide showing the grid system, color scheme, icon designs, and font size specifications." src="https://cdn-images-1.medium.com/max/1024/1*RimQTesF28cQJMb8dTacVA.png" /><figcaption>Style guide featuring grid layout, color palette, icon designs, and font sizes.</figcaption></figure><p>Finally, I set up reusable <strong>styles</strong> in Figma, streamlining the design process and ensuring a consistent look across all screens.</p><h3>Step 5: Leveraging atomic design</h3><p>That morning, we had a class on <strong>atomic design</strong>, a methodology for building components — from the smallest elements to fully designed pages. I had already been applying this approach to some extent in my previous projects, but now I was ready to adopt it more intentionally.</p><p>The goal? To create a <strong>coherent, logical, and scalable design system</strong>. This would make future updates more efficient, saving time, energy, and ultimately, costs. Below, you can see an overview of components section.</p><h4>Building components</h4><p>I started by organizing my components in a dedicated section (better to stay organized from the start!). My first task was the <strong>status bar</strong> (time, battery, etc.), which I imported from the iOS library. Since it wasn’t responsive by default, I adjusted it to fit my screen dimensions.</p><p>Next, I imported icons — such as <strong>language</strong> and <strong>chevron</strong> — from Iconify plugin. The challenge here was ensuring consistency across the icon set, paying attention to factors like <strong>filled vs. outlined styles</strong>, <strong>line thickness</strong>, and <strong>rounded corners</strong>.</p><p>I then created input fields with an icon, text, and chevron, followed by buttons with <strong>instance switches</strong> for left and right icons.</p><figure><img alt="Figma workspace displaying components such as icons, buttons, input fields, and cards." src="https://cdn-images-1.medium.com/max/1024/1*5KcWKkxQCryaxdWNuePZZg.png" /><figcaption>Figma component section showcasing icon set, buttons, inputs, and cards</figcaption></figure><h3>Step 6: Designing the pages</h3><h4>Language Page</h4><p>The original design lacked clear calls to action, making it less engaging for users. To address this, I introduced a <strong>guiding question </strong>paired with popular language suggestions to encourage interaction. A <strong>“More” button</strong> allows users to explore additional options if their desired language isn’t listed, leading them to a search field with <strong>auto-complete suggestions</strong>. This simple yet effective modification creates a smoother, more inviting entry point. Below you can find the work I’ve done on these pages.</p><figure><img alt="Side-by-side view of the language choices page, showing the original design and the improved version." src="https://cdn-images-1.medium.com/max/1024/1*cdq4587tA2PpQ2IkOSUjAQ.png" /><figcaption>Before and after: A comparison of the enhanced language choices page</figcaption></figure><h4>Choice Page</h4><p>Previously, this step felt confusing — users needed to select a language before choosing an action (e.g., “Practice” or “Edit”). Additionally, the links were too small, discouraging interaction.</p><p>As illustrated in the following image, to solve this, I reorganized the layout, making the <strong>calls to action</strong> larger and more intuitive. The <strong>wording</strong> was refined to guide the user clearly, ensuring a seamless flow from selection to action.</p><figure><img alt="Two Figma screens showing the original and redesigned versions of the action selection page." src="https://cdn-images-1.medium.com/max/1024/1*N3XGVkCn1SJPLMgPhegJog.png" /><figcaption>Before and after: A visual comparison of the updated action selection page</figcaption></figure><h4>Wordlist Page</h4><p>This step suffered from several issues:</p><ul><li><strong>Inconsistent design:</strong> The UI shifted noticeably from previous steps.</li><li><strong>Ineffective features:</strong> A “Delete Language” button seemed unnecessary and poorly placed.</li><li><strong>Complex interactions:</strong> Editing required sliding a line that wasn’t well-calibrated, and the lack of space made it harder to use.</li><li><strong>Confusing icons:</strong> A button for filtering by alphabetical order or date was unclear and occupied valuable space.</li></ul><p>To address these problems, I introduced the following improvements:</p><ol><li><strong>Consistent design:</strong> Created a unified layout for seamless navigation.</li><li><strong>Intuitive editing:</strong> Users can now edit content by clicking a pen icon.</li><li><strong>New page layout:</strong> Replaced the popup with a dedicated page, reducing the feeling of being confined.</li><li><strong>Enhanced features:</strong> Users can adjust word recurrence probability (e.g., 80% likelihood of reappearance) and, at one glance, find out their personal evaluation with small emoticons for each word.</li></ol><p>Here’s a visual representation of the work I’ve done on these pages:</p><figure><img alt="Figma screens showing the original Wordlist page and the redesigned Word Editing page." src="https://cdn-images-1.medium.com/max/1024/1*_2vDYZqsfZduUL4IFSmYyA.png" /><figcaption>Before and after: A comparison of the Wordlist page and the Word Editing page</figcaption></figure><p>These changes make the Wordlist page more functional, user-friendly, and visually coherent.</p><h4>Play Game Page</h4><p>The original design treated this as an overlay, which felt insufficient for a primary feature. Writing answers was also cognitively demanding, and the “Wrong” button was discouraging.</p><p>I reimagined this experience with the following improvements:</p><ul><li><strong>Playful interface:</strong> Added vibrant colors and a card-based system where users think about their answer and tap the card to reveal its meaning.</li><li><strong>Progress tracking:</strong> Introduced a progress bar to show the remaining questions, keeping users informed and motivated.</li><li><strong>Encouraging feedback:</strong> Replaced the “Wrong” button with a system where users rate how confident they felt about their answer, using the same colors found in the Wordlist page.</li></ul><p>These updates transform the practice experience into something more engaging, less demanding, and encouraging.</p><p>Below is a snapshot of the work I’ve done on these pages.</p><figure><img alt="Side-by-side comparison of the original and redesigned CardGame feature." src="https://cdn-images-1.medium.com/max/1024/1*ApKnELcfLWisw--T9lJ8gQ.png" /><figcaption>Before and after: A comparative overview of the CardGame feature</figcaption></figure><p>I wanted the wireframes to feel a bit more dynamic, so I also created a small <strong>interactive prototype</strong> to bring the experience to life, feel free to interact with it by clicking on the image below (the flow start when you select English language).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FcFMHYa0WrU9WXsCn0fMecn%2F%255B-P3-Aur%25C3%25A9lie-%255D-App-Redesign%3Fnode-id%3D3012-755%26t%3DKBEWap4Gb6T6ELKO-1&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FcFMHYa0WrU9WXsCn0fMecn%2F%255B-P3-Aur%25C3%25A9lie-%255D-App-Redesign%3Fnode-id%3D3012-755%26t%3DKBEWap4Gb6T6ELKO-1&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FcFMHYa0WrU9WXsCn0fMecn%2Fthumbnail%3Fver%3Dthumbnails%252Fab870062-b917-4635-8b69-695514b2aa80%26t%3DKBEWap4Gb6T6ELKO-1&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/f9e99a305ca993cc7a17a9e32e5026c9/href">https://medium.com/media/f9e99a305ca993cc7a17a9e32e5026c9/href</a></iframe><h4>What’s Next?</h4><p>The journey isn’t over yet! Here’s what I’ll be focusing on in the next steps:</p><ul><li><strong>Incorporating feedback:</strong> Refining the design based on our instructor’s input, including adjustments to button, spacing (especially between icons and text) and improving the clarity of the wording.</li><li><strong>Polishing details:</strong> Organizing and naming layers and frames in Figma to eliminate those pesky “Frame 15628303” labels and ensure a cleaner workflow.</li></ul><p>Redesigning this app has been an incredibly rewarding experience — both fun and educational. It allowed me to deepen my understanding of user experience while confirming my passion for tools like Figma.</p><h4>Key takeaways</h4><p>This project has offered invaluable lessons, especially in balancing the independence of solo work with the collaborative perspective of teamwork:</p><ul><li><strong>Balancing independence and structure: </strong>Working solo highlighted the importance of managing time effectively and making decisive choices. Without a team to rely on, I learned to trust my instincts, prioritize tasks, and remain resourceful when facing challenges. However, it also reinforced the value of collaboration for fresh perspectives and constructive critique.</li><li><strong>Applying heuristic design principles: </strong>it provid a strong framework for identifying weaknesses and guiding improvements.</li><li><strong>The importance of a cohesive Design System: </strong>Creating a scalable, reusable design system using atomic design principles was a game-changer. It streamlined the workflow, ensured consistency across screens, and laid the foundation for efficient updates in the future.</li><li><strong>Leveraging tools effectively: </strong>This project deepened my appreciation for tools like Figma. By fully utilizing its features — such as reusable components, styles, and prototyping — I was able to save time, stay organized, and enhance the overall quality of the design.</li></ul><p>I hope this project resonates with you as much as it has for me. Your feedback is always welcome — feel free to leave a comment and let me know your thoughts or critiques.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72c021b0c957" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Yummy Case Study: Designing an E-commerce Website for Venezuelan Pastries]]></title>
            <link>https://medium.com/@aureliejean.design/a-yummy-case-study-designing-an-e-commerce-website-for-venezuelan-pastries-76c1d9c44e82?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/76c1d9c44e82</guid>
            <category><![CDATA[ecommerce-website-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ux-design-case-study]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Sun, 05 Jan 2025 11:10:05 GMT</pubDate>
            <atom:updated>2025-01-27T10:53:02.669Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tA5jUehW6RB2Yq80dNg4bw.png" /></figure><p>Every new project brings an opportunity to learn and create. This time, the goal was clear: develop a <strong>prototype</strong> for an e-commerce website. Undertaken as part of my UX/UI bootcamp at Ironhack, this project stood out for its scope and complexity, culminating in the creation of a high-fidelity desktop prototype.</p><p>We approached this project using the design thinking process, ensuring a structured and user-centered methodology. Below is a breakdown of the key stages we navigated during this intensive 10-day timeline.</p><h4>First, meet the team</h4><p>I had the opportunity to join a new team, working alongside <a href="https://medium.com/@carmenpcdesign"><strong>Carmen</strong></a><strong> </strong>and <a href="https://medium.com/@chek.rodriguez.contact"><strong>Francheska</strong></a>. From the very beginning, we fostered a positive and supportive environment, which I believe made our project smoother to manage. Each of us brought unique skills and perspectives to the table, allowing us to contribute meaningfully to the overall success.</p><p>Working in a team where everyone listens, respects one another, and feels confident sharing their opinions was truly a highlight of this experience. It’s this kind of collaboration that elevates the creative process and drives impactful results.</p><h3>1. Discovering the heart of Venezuelan pastries</h3><h4>Insights from a passionate founder</h4><p>We kicked things off by interviewing <strong>Bane</strong>, the owner of the pastry business : <strong>Bane’s Frosting</strong>. To prepare, we created an <strong>interview guide</strong>, pooling together relevant questions from individual brainstorming sessions. Our goal was to gain a deeper understanding of her project, including her <strong>objectives</strong>, <strong>medium-term vision</strong>, and the <strong>challenges</strong> she encounters in managing her business.</p><p>Although the interview was conducted in Spanish — a language I don’t speak — Bane’s passion was evident through her gestures and tone. She generously shared her <strong>values</strong>, <strong>goals</strong>, and the unique aspects of her products. Her pastries are deeply rooted in her Venezuelan heritage, featuring creations like <strong>Tres Leches</strong> and <strong>Pan de Jamon</strong>.</p><p>This conversation helped us uncover her <strong>unique selling point</strong>: a blend of warmth, attentiveness, and cultural authenticity.</p><h4>Exploring the competitive landscape</h4><p>In parallel, to better understand the market landscape, we conducted an analysis of websites offering similar products, noting key elements that stood out. This included the organization of information (navigation structure, product pages), clarity of shipping method explanations, as well as design aspects such as color schemes, typography, and wording.</p><h3>2. Getting to know the users</h3><h4>Listening at scale</h4><p>For the first time in the bootcamp, we used a <strong>Google Form</strong> to collect quantitative data. The main challenge was recruiting the right participants. We filtered respondents with a key opening question: <em>“Have you ever bought a pastry online?”</em></p><p>Crafting questions for an online survey requires a different approach than developing an interview guide. Since there is <strong>no face-to-face interaction,</strong> the questionnaire must be <strong>clear and self-explanatory</strong>. Additionally, it’s important to respect the user’s time by keeping the survey concise and avoiding an overwhelming number of questions.</p><p>A valuable tool that guided our thought process and the formulation of survey questions was the<strong> Lean Survey Canvas</strong>. Below, you can see an overview of the initial stages of our brainstorming and planning.</p><figure><img alt="An image of the Lean Survey Canvas used on FigJam to organize and refine our user research approach, showcasing key insights and brainstorming outcomes." src="https://cdn-images-1.medium.com/max/1024/1*mGvD92hN8g2tev5vmAweBg.png" /><figcaption>Lean Survey Canvas highlighting the initial stages of brainstorming and question development for our user research</figcaption></figure><h4>Eye-opening conversations</h4><p>I’m always fascinated by user interviews. They’re a chance to learn how to listen without leading or influencing the participant. Staying <strong>neutral</strong> and avoiding <strong>bias</strong> is both challenging and rewarding.</p><p>Some of our questions didn’t land as intended, which highlighted areas for improvement. However, it’s in these moments that unexpected <strong>insights</strong> often emerge.</p><h4>Connecting the dots</h4><p>We synthesized our interview findings into an <strong>affinity diagram</strong>, organizing key insights into meaningful categories. This step helped us pinpoint the areas where our design could have the most impact.</p><p>One key finding was that users need <strong>reassurance</strong> when purchasing pastries online. Concerns about freshness and delivery reliability were recurring themes.</p><h3>3. Defining the vision: persona, goals, and problem statements</h3><h4>Meet Gabriel and his user journey</h4><p>Let me introduce <strong>Gabriel</strong>, our primary persona:</p><ul><li><strong>Profile</strong>: A Latino firefighter living in Chicago, sociable, a food lover, and generous.</li><li><strong>Goal</strong>: To surprise his wife on her birthday with a Venezuelan cake that reminds her of her grandmother’s recipes.</li></ul><p>Below you can see a detailed map of his experience, from exploring options to making the purchase.</p><figure><img alt="A user journey map illustrating Gabriel’s steps to purchase a birthday cake for his wife, including his goals, emotions, and touchpoints at each stage." src="https://cdn-images-1.medium.com/max/1024/1*wCMAaJWWZ0groAz0yKsKoQ.png" /><figcaption>Gabriel’s journey to finding the perfect birthday cake for his wife: a detailed map of his experience, from exploring options to making the purchase</figcaption></figure><p>From Gabriel’s story, we derived our <strong>problem statement</strong>:<br><em>“Residents of Chicago who enjoy Venezuelan pastries need to find a way to order online cake with confidence because they struggle to find sufficient information such as good images, ingredients, size guidance, quantities, and customer testimonials which lowers trust in making orders.”</em></p><p>We then developed several <strong>How Might We </strong>statements to guide our ideation process:</p><ul><li>How might we help users find complete, relevant, and trustworthy information about pastries?</li><li>How might we enable users to order a custom Venezuelan cake online?</li><li>How might we reassure users about delivery times and freshness?</li></ul><h3>4. From ideas to action</h3><h4>Prioritizing what matters most</h4><p>We set out to design an e-commerce website, drawing inspiration from our benchmarking research and enriched by user insights. Using the <strong>MoSCoW method</strong>, we prioritized ideas based on their importance to the end user.</p><p>The most critical elements? High-quality, authentic product photos, clear and <strong>detailed information</strong> about ingredients and cake sizes, customization options (such as adding a message for a birthday), and user reviews. Equally essential were options for <strong>pickup or delivery</strong>, ensuring a seamless and user-friendly experience.</p><h3>5. Designing the experience</h3><h4>Structuring the vision</h4><p>Creating the <strong>sitemap</strong> was a collaborative effort to structure the pages and organize the information hierarchy. Once finalized, we focused on a key <strong>user flow </strong>as illustrated on the image below: navigating from the home page to order confirmation for a signature product — the <strong>Tres Leches Cake</strong> with customization options.</p><figure><img alt="Visual representation of the user flow, illustrating the journey from the home page to order confirmation for the Tres Leches Cake with customization options." src="https://cdn-images-1.medium.com/max/1024/1*UDEtX_BOjTr289qFBIriAw.png" /><figcaption>User flow: From the home page to order confirmation for the customizable Tres Leches Cake</figcaption></figure><h4>Moodboard</h4><p>For the <strong>moodboard</strong>, we focused on the following keywords: <strong>Sweet, Homemade, Friendly, Tasty, Playful</strong>. The visual identity needed to evoke joy and appetite, with warm colors like pink and cream dominating the palette as you can see on the picture below.</p><figure><img alt="A moodboard for Bane’s Frosting website: soft pink and cream tones, featuring flowers, pastries, a diary, and ice cream — capturing the brand’s sweet and playful essence." src="https://cdn-images-1.medium.com/max/1024/1*rtDsQ-U0ncIDUJRRIlyRfg.png" /><figcaption>Moodboard for the Bane’s Frosting website</figcaption></figure><h4>Wireframes and concept testing</h4><p>During this stage, each team member contributed by creating a paper prototype. We aligned on the key elements that needed to be included on each page. Sharing a <strong>common vision and inspirations</strong> allowed us to quickly reach a consensus on a low-fidelity prototype, which we then refined further. You can view the lofi design below.</p><figure><img alt="Low-fidelity wireframe designs created in Figma, showcasing the step-by-step purchase flow from the homepage to the confirmation of a Tres Leches cake order." src="https://cdn-images-1.medium.com/max/1024/1*_VkVN1F7fs7WapDRQEUO5w.png" /><figcaption>Low-fidelity wireframes in Figma outlining the purchase flow, from the homepage to order confirmation for a Tres Leches order</figcaption></figure><p>Once aligned, we conducted concept tests which provided valuable feedback:</p><ul><li>Adding product suggestions on the product page</li><li>Reorganizing categories for clarity</li><li>Including breadcrumb navigation to enhance usability</li></ul><h4>Creating a seamless and responsive prototype</h4><p>Next, we moved on to the high-fidelity prototype, starting with the core branding elements — colors and typography.</p><ul><li><strong>Styling in Figma</strong>: We established styles for typography, colors, shades and grids.</li><li><strong>Components</strong>: To ensure consistency, we created reusable components, including headers, footers, CTAs, cards, form inputs, dropdown menus, and icons.</li></ul><p>One aspect I’m particularly proud of is that, thanks to our efficient team dynamics and being on track with the project timeline, I had the opportunity to experiment with <strong>variables in Figma</strong> for the first time. This allowed us to dynamically adjust prices based on quantity using a counter system.</p><p>Below are the primary screens we focused on, as illustrated in the image.</p><figure><img alt="A display of the high-fidelity pages for the Bane’s Frosting website, including the home page, basket page, product page, tres leches page, payment page, and confirmation checkout." src="https://cdn-images-1.medium.com/max/1024/1*-SpMTXcwDeuHL2ce8ixOxg.png" /><figcaption>High-fidelity mockups of the Bane’s Frosting website</figcaption></figure><p>We also focused on making the design responsive, starting with a mobile version of the homepage, ensuring the user experience was seamless across all devices.</p><h4>Looking ahead</h4><p>This was just the first iteration. A second iteration could focus on conducting additional user testing to evaluate whether the product page meets user needs and whether the reassurance elements effectively build trust in the purchasing process. Additionally, we could expand the content beyond the purchase flow by incorporating content in sections like <em>FAQ</em> and <em>About Us</em>.</p><p>Another key improvement would be to implement a fully responsive design, ensuring the site delivers a seamless experience across desktop, tablet, and mobile devices.</p><h4>Key Learning</h4><ul><li>Working in a <strong>cohesive and supportive team environment</strong> was instrumental in our success. Open communication, mutual respect, and leveraging each other’s strengths enhanced the quality of our work and streamlined the design process.</li><li>Concept testing and feedback loops revealed the importance of <strong>refining ideas early and often</strong>. This iterative approach allowed us to make user-informed adjustments.</li><li>Experimenting with new tools, like Figma variables for dynamic pricing, added a layer of functionality to the prototype while broadening our skill set.<strong> Taking time to test new features</strong> can enhance both the product and personal development.</li><li><strong>A prototype is a foundation to build upon</strong>. Additional iterations, user testing, and expanded features are crucial steps in evolving the product to better meet user expectations and business goals.</li></ul><p>Thanks for following along — I hope this case study leaves you inspired and maybe a little hungry for more creative projects!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76c1d9c44e82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From insight to impact: my UX/UI design journey through the lens of immigration]]></title>
            <link>https://medium.com/@aureliejean.design/from-insight-to-impact-my-ux-ui-design-journey-through-the-lens-of-immigration-e87581447ac7?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/e87581447ac7</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[user-testing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux-research]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Sun, 08 Dec 2024 19:20:53 GMT</pubDate>
            <atom:updated>2024-12-13T18:02:17.434Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I earned a BA in UX/UI design, where I gained more insight into general communication than design itself. Eager to deepen my expertise in UX/UI, I enrolled in the Ironhack boot camp. Two weeks ago, I took part in the pre-workshop, which offered a glimpse of what was to come.</p><p>Today, I’ll share my experience working on our first project, themed <em>Wicked Problems: Immigration</em>. Thank you to my teammates <a href="https://nowrinkf98.medium.com/solving-wicked-problems-redesigning-the-immigration-experience-in-germany-case-study-0d342c0d5af7">Nowrin</a>, <a href="https://medium.com/@apostolbianca91/from-concept-to-creation-a-ux-ui-case-study-from-ironhack-2f395f2ffb33">Bianca</a>, and <a href="https://medium.com/@jicalderon/wicked-problem-case-study-immigration-cd3a034a8eac">Jorge</a> for being part of this transformative journey filled with learning, emotions, and meaningful experiences!</p><figure><img alt="Image of an english newspaper entitled IMMIGRATION in capital letters" src="https://cdn-images-1.medium.com/max/1024/0*bdCfXyXvXQRApEqv" /><figcaption>Photo of an english newspaper entitled Immigration — Image by <a href="https://unsplash.com/fr/@metinozer">Metin Ozer</a> on <a href="https://unsplash.com/fr/photos/papier-imprime-blanc-spFYbCSF-Ec">Unsplash</a></figcaption></figure><p><em>The new century has witnessed a dramatic rise in global mobility. While migration has always been a part of history, never before have there been such diverse destinations, motivations, and circumstances. Along with the challenges of adapting to a new culture or language, migrants must also navigate a range of bureaucratic tasks, often within tight timeframes, to legalize their stay in the host country. So, how can we help migrants access the information they need, complete necessary tasks, and successfully manage their paperwork to begin their new life in a different city?</em></p><p>Immigration impacts countless lives — including those of my team members, all three of whom have experienced it firsthand! This perspective made some aspects of the project easier while adding complexity to others. Personally, I was struck by the subject’s vastness and the societal issues it raises. Fortunately, we embraced the design thinking process, which helped us approach this challenge with structure and creativity.</p><h4>Phase 1 — Getting closer to the user</h4><p>We started our secondary research and gathered a wide range of information to guide the next stage. The challenge was twofold: finding relevant, topic-specific resources among the overwhelming amount available online, and ensuring the credibility of the sources we used.</p><p>Armed with this data, we moved on to creating a user interview guide and recruiting interviewees — real migrants with firsthand experience of moving abroad. This process went smoothly: we quickly found participants and agreed on the interview questions. In hindsight, knowing what the rest of the design thinking process entails, I would have asked more detailed questions, particularly about the step-by-step visa application process.</p><p>Interviewing Jorge was a highlight for me. It’s at this stage that research becomes meaningful — you connect with a real person, perhaps a future user, and explore their motivations and frustrations. It’s also a humbling experience, requiring you to set aside your assumptions and let the person’s story guide your understanding. In the end, it’s all about empathy, right?</p><h4>Phase 2 — From raw data to a defined problem</h4><p>What could we do with all the data we’d gathered? The affinity diagram came to the rescue, helping us organize and categorize key topics. The real debate started when we used dot-voting to select the most relevant issues for the project. Language barriers and bureaucratic challenges emerged as top concerns — but we needed to be more specific. Another round of voting highlighted two key areas: multilingual online support and improved communication with public administration. Below is an image showing the dot voting outcome on our Figjam.</p><figure><img alt="Screenshot of affinity diagram and dot voting on figjam" src="https://cdn-images-1.medium.com/max/1024/1*eO6bnFT2UBS2Uod8r_DDxQ.jpeg" /><figcaption>Screenshot of the outcomes of our affinity diagram and dot-voting on Figjam</figcaption></figure><p>I’m definitely keeping this sorting and voting method in mind for future projects!</p><p>With our focus set, it was time to create our persona — a realistic character representing our target user. Drawing from different personal stories, I initially struggled to create someone believable. Then, we built on Jorge’s suggestion, crafting <em>Anna Nowak</em>, a cheerful Polish dance instructor with a compelling backstory.</p><p>Next came the User Journey Map. When Niel explained the concept, it seemed straightforward — until we started working on it. We quickly realized we were thinking too broadly, considering things like how Anna would find accommodation. But the exercise required us to focus on a specific moment when she faces a challenge, turning it into an opportunity for improvement.</p><p>After refining the journey map, we defined our problem: <em>European citizens emigrating to Germany need a way to complete their legal documents accurately and independently.<br></em>The biggest lesson I took from this stage was the importance of precise wording. Every term shapes how you frame the problem — and ultimately, the solution.</p><h4>Phase 3 — (don’t over ) THINK !</h4><p>We kicked off with the Crazy 8s exercise: eight ideas in eight minutes. I loved it! It forces you to think fast, leaving no room for overanalyzing. You just dive in and let creativity flow. While some core ideas came up repeatedly, each person also contributed unique solutions that enriched our brainstorming.</p><p>With plenty of ideas on the table, it was time to make decisions. As shown in the next image, we applied the MoSCoW method, a prioritization framework, to sort and refine our concepts.</p><figure><img alt="Screenshot of our prioritization choices with the MoSCoW Method" src="https://cdn-images-1.medium.com/max/1024/1*nVjs9YgTlhMBGUBybI1wmQ.png" /><figcaption>Screenshot of our prioritization choices with the MoSCoW Method</figcaption></figure><p>Next, we tackled the User Flow diagram — though this proved tricky. We mixed up ideas and struggled with decision-making, hesitant to commit. Realizing we had to move forward, we focused on the online registration process for obtaining a work permit. We reminded ourselves that the User Flow could evolve as the prototype developed.</p><h4>Phase 4 — Bringing ideas to life</h4><p>Realizing time was running out, we divided tasks based on our individual strengths and worked independently while holding regular team check-ins.</p><p>We listed the key elements for each page, and my part was to focus on creating the first version of the prototype. After reviewing it together, we refined the design — adding features like a dropdown menu for language selection. Once we reached a consensus, we submitted the prototype for user testing. The next image illustrates the user flow prototype on Figma.</p><figure><img alt="Screenshot of the user flow protoype on figma — frome language selection to pending confimation" src="https://cdn-images-1.medium.com/max/1024/1*qZ4-ltDjWotls1t3zuXlmA.png" /><figcaption>Screenshot of the user flow protoype on figma — from the language selection page to the pending confimation page</figcaption></figure><p>The first three screens address a crucial issue: selecting the language in which the chosen documents will be written. Next, the user selects the desired form and begins completing it. At this stage, a stepper appears to guide the user through the process. The user is then asked to upload various documents, such as their proof of identity, before confirming everything. The app then verifies the documents and sends the request to the relevant authorities. This process solves two problems: the language in which the forms are written and the tracking of administrative progress.</p><h4>Phase 5 — Sharing the project</h4><p>We wrote a script to guide testers and gather their feedback effectively. Our classmates kindly participated (thank you all!), testing the app and providing live input.</p><p>Based on their suggestions, we added a stepper to show progress through the registration process, offering a clearer overview of each stage. We also included a back-arrow for easier navigation and redesigned the form screens for better clarity.</p><h4>What happens now?</h4><p>The student project ends here, but if we wanted to go further, the next step would be to iterate by focusing on usability improvements, visual design, and functionality based on testing results.</p><h4>Frustrations</h4><ul><li>I sometimes felt overwhelmed by the tight schedule.</li><li>Working with four minds on the same tasks was challenging. And it was especially tricky because we didn’t know each other — it took time to understand how everyone works.</li><li>Being given the HMW (How Might We) statement from the start felt like a double-edged sword: I feel that it provided direction but also limited our thinking and influenced our research.</li></ul><h4>Learning</h4><ul><li>We’re a team, and decisions are made together. Sometimes that means making personal concessions to move forward, every insight is valuable!</li><li>We tended to think too broadly, when the goal was to focus on a specific problem.</li><li>We jumped into solution mode before fully understanding the problem — but that’s part of the learning process!</li><li>We spent a lot of time discussing every step (sometimes feeling like meetings dragged on) when working more individually could’ve been helpful.</li><li>We should have timed our work sessions better.</li><li>Creating a case study is incredibly valuable — it helps us reflect on how we worked, what we learned, and why we approached things the way we did.</li></ul><p>If you’re still here, thank you so much for following the progression of this case study!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e87581447ac7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: AurélieJean_Challenge1]]></title>
            <link>https://medium.com/@aureliejean.design/ironhacks-prework-aur%C3%A9liejean-challenge1-1979ce52cb6e?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/1979ce52cb6e</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[wireframe]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Sun, 17 Nov 2024 11:21:02 GMT</pubDate>
            <atom:updated>2024-11-17T11:23:40.708Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>How do you organise your journeys when you visit a new city? </strong>It’s always a challenge to know which means of transport is best, especially if you’re in a foreign country. <strong>Citymapper</strong> is <strong>the app</strong> that has saved me an incredible amount of time and taken a load off my mind when it comes to wandering around town.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mEZtOiqg6yO2Bwg7" /></figure><h4>The Problem 🤯</h4><p>Public transport tickets are typically available as paper or plastic cards. However, traveling from point A to B often requires purchasing multiple tickets for different transit systems, which can be <strong>frustrating</strong> due to the <strong>misunderstanding</strong> of how the system works or due to <strong>long queues </strong>in touristic cities.<br>Additionally, when traveling abroad, <strong>navigating ticket pricing and choosing the correct ticket can be particularly challenging</strong> and inconvenient.</p><h4><strong>The Challenge </strong>🚀</h4><p><strong>Create a feature</strong> for this app that <strong>solves the pain of having to purchase</strong> different public transport tickets by different channels.</p><p>In order to complete this challenge, I have used the <strong>Design Thinking Method</strong>. Here is the result of my work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MX9b-nTVYHdL8Xl4.jpg" /></figure><h4>The Process ⚙️</h4><blockquote><strong>1. Empathyse</strong></blockquote><p>I first questioning myself to make sure I understand right the problem :</p><ul><li><strong>What problem are you solving? <br></strong>Getting users/travellers to pay the right price for their tickets while freeing them from the difficulties inherent in booking and paying for tickets (which one to choose, queues, scams, managing physical tickets, etc.).</li><li><strong>Who is your audience?<br></strong>Occasional travellers, tourists.</li><li><strong>Who is your client’s competition?<br></strong>The RATP application in Paris, for example, or any other mobility application specific to the city. The kiosks.</li></ul><p>Then, I wrote an <strong>interview guide</strong> and I asked 3 people to answer few question about their travelling habits, here some of them :</p><ul><li><em>Do you like to travel? If so, where do you go when you travel? Why do you travel?</em></li><li><em>What means of transport do you use most often when you travel? Why or why not?</em></li><li><em>What tools do you use to find your way around?</em></li><li><em>What is your main frustration/problem when you travel?</em></li><li><em>How do you buy your tickets?</em></li><li><em>Can you tell us about a good/bad purchasing experience?</em></li></ul><p>I then gathered some or their relevant responses in a <strong>figjam</strong> :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39S0xv-cGspLbSuZD9RSbQ.png" /></figure><blockquote><strong>2. Define</strong></blockquote><p>The elements that particularly stood out from these interviews was :</p><ul><li><strong>Saving time</strong> on buying tickets and organising the journey.</li><li><strong>A less stressful experience</strong> is needed (language / scared to make mistakes / have a fine) / The desire to have peace of mind : <strong>less mental workload.</strong></li><li>The need for a <strong>clear, efficient, accessible interface</strong> to navigate easily the system.</li></ul><p>From there I have formulated a <strong>problem statement :</strong></p><p>“ How can we save time for occasional users of urban public transport looking to buy tickets, while guaranteeing them an accessible and stress-free experience? ”</p><blockquote><strong>3. Ideate</strong></blockquote><p>I came back on figjam to brainstorm on the white board. I took stickies and I have done the crazy 8 method : generate 1 idea per minute for 8 minutes. Here are the best ideas I thought about :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySVi4nuTsl46lQUiAW2DHQ.png" /></figure><blockquote><strong>4. Prototype</strong></blockquote><p>I first drew quickly a user flow with the ideas that I got and checking the app in the meanwhile to make sure it fits in perfectly with the existing interfaces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLjrd199G0Hczic8M2jlXQ.jpeg" /></figure><p>Then I built an <strong>animated prototype with Canva </strong>to make things more <strong>tangible and “realistic” :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/216/1*LVBw-gl1ZLAirbtC2fWn3g.gif" /></figure><h4>Key Learning 🗝️</h4><ul><li><em>T</em>he <strong>interviews</strong> were very interesting ! People were more talkative when you got away from the framework of pre-established questions. <br>It was also a challenge to remain as neutral as possible in the exchange. I felt how easily you can be biased when you’re talking to someone.</li><li><strong>Design Thinking</strong> is a process that I’ve never used before. And I’m eager to learn more about this method and apply it to my next projects.</li><li>The <strong>prototype</strong> part is very <strong>stimulating</strong>, at first what you have to draw seems clear, but as you’re drawing you realize that some steps can be missing, or other problem has to be questioned. So you’ll have to evaluate the widespread of the problem and to stay into the frame that you have defined.</li></ul><p>I can’t wait for the Ironhack bootcamp to begin and to learn more about user research methods, how to be more empathetic, how to synthezise, improve my drawing skills, among others !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1979ce52cb6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 2: Wireframing — Spotify User Flow]]></title>
            <link>https://medium.com/@aureliejean.design/ironhack-challenge-2-wireframing-spotify-user-flow-60d45be24915?source=rss-19e79397ca49------2</link>
            <guid isPermaLink="false">https://medium.com/p/60d45be24915</guid>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[user-flow]]></category>
            <dc:creator><![CDATA[Aurelie Jean]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 14:09:42 GMT</pubDate>
            <atom:updated>2024-11-14T14:09:42.209Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 2: Wireframing a Spotify User Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qwpbxyoLE5nZZqoW.png" /></figure><p><strong>Here we are</strong>, I’m taking part in the Ironhack bootcamp! <br>And before we even get into these 9 weeks of intensive learning, we’re getting down to the nitty-gritty with this preparatory work.</p><p>Today I’m presenting you with the following challenge: to work as a <strong>reverse engineer</strong> on the wireframe of the application of our choice.</p><p>I chose <strong>Spotify</strong>, a music streaming service used by millions of listeners across the globe. I chose to work on this application because it is known and used by so many people. So its <strong>design</strong> had to be <strong>carefully thought</strong> out beforehand, and its <strong>navigation instinctive</strong>.<br>It’s also one of the applications <strong>that follows me around in my daily life</strong>, so I thought it would be interesting to take a closer look at it.</p><p>I’ve chosen to analyse and dissect the following goal: <strong>add a title to a playlist.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TMXq8rLPlCZ3U_Cazydu6g.png" /><figcaption>These are the screenshots of each stage of the user flow I chosed to analyse.</figcaption></figure><p><strong><em>Step 1:</em></strong> take screenshots of each stage and write down the actions I performed.</p><p><strong><em>Step 2: </em></strong>Import the files into figma and analyse the relevant information to be retained for the creation of the wireframes. The idea is to simplify the screens while maintaining a certain level of understanding of them.</p><p><strong><em>Step 3: </em></strong>Design the wireframes, using a UI kit but also creating my own elements (Nav Bar, Search Bar, Tags, Buttons, Cards with different shapes, Icon for key actions).</p><p><strong><em>Step 4:</em></strong> Add comments and visual indications to show what needs to be done to move from one step to the next.</p><figure><img alt="Outcomes wireframes of “Adding an element to a playlist in Spotify” User Flow." src="https://cdn-images-1.medium.com/max/1024/1*zJPIn39BHEqUwZesgSJ-2w.png" /><figcaption>Outcomes wireframes of “Adding an element to a playlist in Spotify” User Flow.</figcaption></figure><p><strong><em>What I learn</em></strong></p><ul><li>Pick carefully the content we want to display : It is important to <strong>find the right amount of content </strong>to display. You don’t want to waste time on visual considerations and at the same time keep the prototypes understandable.</li><li>The <strong>wireframe</strong> is an <strong>crucial stage</strong> in the construction of an application. It enables us to understand how the app is going to work, and what interaction needs to be thought through to optimise its use.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60d45be24915" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>