<?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 Elise Rocchesani on Medium]]></title>
        <description><![CDATA[Stories by Elise Rocchesani on Medium]]></description>
        <link>https://medium.com/@elise.rocchesani?source=rss-0221ecba0cd5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EztxFe1Mlr3TyH5R2lK36Q.png</url>
            <title>Stories by Elise Rocchesani on Medium</title>
            <link>https://medium.com/@elise.rocchesani?source=rss-0221ecba0cd5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:15:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@elise.rocchesani/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[Designing a mental wellness app for job seekers — A UX/UI case study]]></title>
            <link>https://medium.com/@elise.rocchesani/designing-a-mental-wellness-app-for-job-seekers-a-ux-ui-case-study-f7c3a982fee5?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7c3a982fee5</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[unemployment]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Thu, 03 Apr 2025 15:42:33 GMT</pubDate>
            <atom:updated>2025-04-04T08:31:22.556Z</atom:updated>
            <content:encoded><![CDATA[<h3>Designing a mental wellness app for job seekers — A UX/UI case study</h3><figure><img alt="Cover image displaying a key statistic, branding elements, and mockups of the designed app." src="https://cdn-images-1.medium.com/max/1024/1*f1Q4FJ7XaqrWZzfeMpyCPQ.png" /><figcaption>Overview of our mental wellness app concept.</figcaption></figure><h3><strong>Project Overview</strong></h3><p>This case study showcases my fourth project at the <a href="https://www.googleadservices.com/pagead/aclk?sa=L&amp;ai=DChcSEwi8wJytn7yMAxUdi2gJHbj5DbEYABABGgJ3Zg&amp;co=1&amp;gclid=CjwKCAjw47i_BhBTEiwAaJfPpt9gBqa3kaPB0xDgwTT06LHrUsVG1hyAm8m-p2QNOLCOQOKppmDiLhoCBbcQAvD_BwE&amp;ohost=www.google.com&amp;cid=CAESV-D2w_r2gcr52slW22Rk01UiiKTHLpX9NS4eI5SH9Q7-u1ZvCxcOU34LboGdii9uBF1wE3JphFJJ8BfcK3XA1lKU4sGoBtGae1ybpKsds0HLPJAOBDhblw&amp;sig=AOD64_3XuGt1ibaSKwYTiXev4mT0Gykciw&amp;q&amp;adurl&amp;ved=2ahUKEwisjZitn7yMAxXEVqQEHRFwBv8Q0Qx6BAgKEAE">Ironhack</a> bootcamp, which turned out to be <strong>the most comprehensive and challenging one so far</strong>. Our mission? <strong>Design a health-related app</strong> as part of a competition launched by <em>The Daily Health Conference</em>, a non-profit organization dedicated to promoting wellness worldwide (while also aiming to grow its membership base).</p><p>Together with <a href="https://medium.com/@stephane.gioanni">Stéphane</a>, my UX/UI teammate, we decided to tackle a topic that resonated with us: <strong>mental health support for job seekers and career changers</strong>. This issue affects a large number of people and can have <strong>serious psychological consequences</strong>, making it a crucial area to address.</p><p>This project pushed us <strong>beyond the fundamentals</strong>. In addition to delivering a <strong>high-fidelity prototype</strong>, we incorporated additional steps into our <strong>Design Thinking process</strong>, such as <strong>UX Strategy</strong> and <strong>Empathy Mapping</strong>.</p><p>On a personal level, I had to adapt to working with a new teammate while also gaining <strong>insights into the reflexes I’ve developed over the past six weeks</strong> — and identifying areas for further improvement.</p><p>This case study is a deep dive into that experience.</p><p><strong>Duration:</strong> 2 weeks<br><strong>Team:</strong> 2 UX/UI Designers<br><strong>Tools:</strong> <a href="https://www.figma.com/fr-fr/">Figma</a>, FigJam, <a href="https://zoom.us/fr/signin">Zoom</a>, <a href="https://www.notion.so/">Notion</a><br><strong>Methodology:</strong> Design Thinking</p><h3><strong>Empathy</strong></h3><h4><strong>UX Strategy</strong></h4><p>Our first step was to establish a clear <strong>UX Research Strategy</strong> — a completely new experience for me. We used the <strong>Lean UX Canvas</strong> to structure our approach, defining business problems, user needs, and hypotheses.<br>I found the hypothesis section particularly challenging, as formulating precise and testable assumptions without being too broad wasn’t easy. However, this step helped us refine our concept and gave more structure to a phase I usually find less engaging.</p><h4><strong>Market Research</strong></h4><p>Next, we conducted market research. We knew our topic affected many people and was a major source of stress. However, I hadn’t realized the full extent of its psychological and health-related impact. Some key insights we discovered:</p><ul><li><strong>53%</strong> of job seekers experience a <strong>loss of identity</strong>.</li><li><strong>53%</strong> report increased <strong>anxiety and depression</strong>. <em>(Source: Fuze HR)</em></li><li><strong>19%</strong> of those unemployed for over a year undergo <strong>mental health treatment</strong>. <em>(Source: Banyan Treatment Center)</em></li></ul><p>Seeing these numbers firsthand reinforced how <strong>real and urgent</strong> this problem is.</p><h4><strong>Quantitative Research (Survey)</strong></h4><p>To gain fresh insights, we designed a survey targeting job seekers and career changers. However, despite sharing it within our network, we only received <strong>23 responses</strong> — far from what we had hoped for. This was frustrating, but also a learning experience in <strong>anticipating survey distribution challenges</strong>.</p><p>Still, the results highlighted key struggles:</p><ul><li><strong>75%</strong> cited financial stress as their biggest challenge.</li><li><strong>75%</strong> struggled with motivation and self-confidence.</li><li><strong>67%</strong> found emotional support (friends, family) most helpful in managing stress.</li></ul><p>To improve for next time, Stéphane and I joined dedicated online groups to reach a wider audience.</p><h4><strong>Qualitative Research (User Interviews)</strong></h4><p>Crafting <strong>neutral and balanced</strong> interview questions was harder than expected — I noticed that my previous research was influencing how I framed them. To counter this, we balanced negative questions (<em>What daily challenges do you face?</em>) with positive ones (<em>What does a great outcome look like for you?</em>).</p><p>We conducted <strong>eight interviews</strong>, and I absolutely loved this part of the process. I often took on the observer role, and I was truly grateful for the <strong>openness of our participants</strong>. Hearing their personal stories firsthand made the issue feel much more <strong>real and human</strong> — something statistics alone could never capture.</p><h4><strong>Empathy Map &amp; Affinity Diagram</strong></h4><p>Creating my first <strong>Empathy Map</strong> was an interesting experience. Since we had just finished the interviews, everything felt <strong>fresh and intuitive</strong>, making it easier to <strong>step into our users’ shoes</strong>.</p><p>For the <strong>Affinity Diagram</strong>, I was now familiar with the process from previous projects. The most recurring themes were:</p><ul><li><strong>Uncertainty</strong></li><li><strong>Support</strong></li><li><strong>Financial Stress</strong></li></ul><h4><strong>User Persona &amp; User Journey Map</strong></h4><p>At first, I focused too much on <strong>Leana’s current situation</strong> — being laid off and job searching. I realized a strong persona needs to reflect <strong>who she is beyond her struggles</strong>. Every detail had to be intentional, like her <strong>passion for piano</strong>, which gave insight into her personality rather than being random.</p><p>For the <strong>User Journey Map</strong>, we mapped a key frustration: <strong>applying for jobs and receiving no responses</strong>. (pictured bellow) I initially overlooked the importance of a <strong>timeline</strong>, but adding specific moments made her journey feel more real and helped us pinpoint where our solution could truly help.</p><figure><img alt="User Journey Map outlining the key stages of the user experience, from becoming aware of the need to using the app. The map highlights emotions, pain points, and opportunities for improvement" src="https://cdn-images-1.medium.com/max/1024/1*7n0FsfToKa1ZH8Mg3Go7QA.png" /><figcaption>User journey map to identify friction points</figcaption></figure><h3><strong>Define</strong></h3><h4><strong>Problem Statement</strong></h4><p>We crafted two problem statements — one from the <strong>user’s perspective</strong> and one from the <strong>stakeholder’s perspective</strong>.</p><p>For users, we needed to be <strong>specific</strong> — not just “job seekers,” but <strong>“recently laid-off individuals in their 30s living in Western countries.”</strong> Our statement:</p><blockquote><em>Recently laid-off individuals in their 30s, living in Western countries, need a way to stay confident and feel supported because they currently rely only on themselves or friends/family for daily motivation in their job search.</em></blockquote><p>For stakeholders, I initially misled Stéphane by focusing on <strong>our product</strong> rather than <strong>their existing one</strong>. We corrected this and framed it around <strong>The Daily Health Conference’s</strong> mission:</p><blockquote><em>The Daily Health Conference was created to promote health and wellness. However, its current offering does not meet users’ emotional support needs or align with their digital habits, leading to low engagement and retention.</em></blockquote><h3><strong>Ideate</strong></h3><h4><strong>Crazy 8’s</strong></h4><p>We used the <strong>Crazy 8’s</strong> method, sketching one idea per minute for 8 minutes. For the first time, I felt <strong>genuinely inspired</strong> — my 8 squares were filled before the timer even stopped!</p><p>We then <strong>prioritized our ideas</strong> using the <strong>MoSCoW Method</strong> (Must-have, Should-have, Could-have, Won’t-have). It was <strong>frustrating</strong> to let go of some ideas, but I realized it was better to <strong>focus on essentials</strong> and save extras for future iterations.</p><p>Our <strong>must-haves</strong>:</p><ul><li>A <strong>community channel</strong> for emotional support.</li><li><strong>Relaxation activities</strong> like meditation.</li><li><strong>Personalized routines</strong> to maintain motivation.</li><li><strong>Reminders</strong> to keep users engaged and prevent isolation.</li></ul><p>We also created our first <strong>MVP Statement</strong>:</p><blockquote><em>At the bare minimum, our product will provide a supportive community where unemployed individuals can connect, share experiences, and encourage each other.</em></blockquote><p>I noticed that having a <strong>clear MVP statement</strong> kept us focused and prevented us from <strong>overcomplicating</strong> the user flow.</p><h4><strong>User Flow &amp; Sitemap</strong></h4><p>With <strong>so many ideas</strong>, defining a <strong>cohesive user flow</strong> was tough. I kept asking myself: “<em>How will testers navigate this? What tasks will they complete? Will they get lost?”</em></p><p>We decided to focus on a <strong>key emotional moment</strong>:</p><ol><li>The user feels <strong>alone before a job interview</strong> and opens the app for support.</li><li>They enter a <strong>discussion channel</strong>.</li><li>They read a post recommending <strong>meditation</strong>.</li><li>They <strong>try the suggested meditation</strong>.</li><li>They like it and <strong>add it to their routine</strong>.</li></ol><p>This step was <strong>challenging</strong>, so we took a break and revisited it the next day with <strong>fresh perspectives</strong>. I learned that <strong>stepping back</strong> can lead to <strong>better decisions</strong>.</p><p>Once the <strong>user flow</strong> was clear, creating the <strong>sitemap</strong> became much easier. It provided a <strong>structured overview</strong>, improving collaboration between Stéphane and me.</p><h3><strong>Prototype</strong></h3><h4><strong>Methodology</strong></h4><p>For the lo-fi prototype, defining the pages was easy since our user flow had already mapped out the structure. We tested the 8-page lo-fi prototype without interactions, presenting it verbally to 5 testers. Stéphane and I alternated roles — one observing, the other conducting the interview.</p><p>Working with someone else on Figma was a challenge for me — I love design and struggle with delegating. But we found an efficient process: we each designed two pages, compared, aligned on style, and then split the rest. I focused on the Home Page, Meditations, and Pop-ups, while Stéphane handled the Community and Profile pages.</p><p>For the mid-fi, we prioritized interactions and integrated user feedback. After usability testing, we refined our design and moved on to branding. We built a mood board based on our values of support, motivation, and relaxation, choosing calming yet motivating orange tones and gradients. Finally, we made adjustments based on feedback, and the design evolved as follows:</p><h4><strong>Home Page</strong></h4><p>Our homepage provides access to app features and a personalized routine. During <strong>concept testing</strong>, users suggested <strong>reordering sections</strong> — placing the routine first made more sense, as it helps users start their journey before exploring other features.</p><p>During <strong>usability testing</strong>, users were initially drawn to “Journaling” instead of the “Community” feature they were instructed to test. This was due to how the UI visually emphasized their current task within the routine. We adjusted this in the <strong>hi-fi version</strong>.</p><figure><img alt="Three versions of the homepage design showing its progression from low-fidelity wireframe to high-fidelity prototype." src="https://cdn-images-1.medium.com/max/1024/1*M0yil5rAcpJC8fsdIiVoxQ.png" /><figcaption>Iterating on the homepage — from basic wireframe to polished UI.</figcaption></figure><p><strong>Community Pages</strong></p><p>We debated the <strong>header design</strong>, ensuring users could easily navigate back and understand where they were within the three community levels:</p><ol><li><strong>Global Community</strong> (list of topics)</li><li><strong>Topic Page</strong> (list of posts)</li><li><strong>Post Page</strong> (with meditation suggestions)</li></ol><p>We received positive feedback, particularly about the emotional support aspect of this feature.</p><figure><img alt="Evolution of the community section, showcasing design improvements from lo-fi to hi-fi." src="https://cdn-images-1.medium.com/max/1024/1*BkeqESLK7SpIzc6w8zK1Fg.png" /><figcaption>Enhancing the community experience step by step.</figcaption></figure><h4><strong>Meditation Pages</strong></h4><p>Our first <strong>meditation page</strong> design was quite basic. After researching competitors, I added a <strong>mood tracker</strong> to customize session recommendations based on how users feel. This received great feedback.</p><p>From <strong>lo-fi to mid-fi</strong>, testers suggested adding a <strong>timer</strong> and allowing users to <strong>choose their instructor</strong>, which we implemented.</p><figure><img alt="Progressive refinement of the meditation section, from wireframe to final interface." src="https://cdn-images-1.medium.com/max/1024/1*BSnZwCZ8qeCEEIXgvIFVtw.png" /><figcaption>Designing a seamless meditation experience.</figcaption></figure><h4><strong>Add to Routine Pop-up</strong></h4><p>Initially, clicking “Add to Routine” opened a pop-up and switched the background to the Profile page, creating a poor user experience. Testers pointed this out, so we refined it for the hi-fi version.</p><p>Now, users stay within the session, and pop-ups allow quick interactions without disrupting their focus. The Profile page transition happens only when users click “View Routine,” improving flow consistency and making the feature more seamless.</p><p>I also improved my Figma skills, especially with clickable buttons and component organization. I built a component library, which streamlined updates and maintained consistency. Based on usability feedback, I simplified the day selection to avoid overwhelming users, making the interface cleaner. Seeing this progression gave me a big confidence boost!</p><figure><img alt="Step-by-step development of the “Add to Routine” pop-ups, showing increasing detail and UI polish." src="https://cdn-images-1.medium.com/max/1024/1*x9H7rCLf-uc_8Gz_nhz3Wg.png" /><figcaption>Fine-tuning the “Add to Routine” feature for better usability.</figcaption></figure><blockquote><strong>You can click on </strong><a href="https://www.figma.com/proto/dcwia6IdoSsr1yGzLQpprX/%5B-P4-Team-2-%5D-Design-File?node-id=6209-6943&amp;t=s3UnSjK1UOb0MTsc-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;page-id=6192%3A38476&amp;starting-point-node-id=6209%3A6943">this link</a><strong> to view the hi-fi prototype.</strong></blockquote><h3><strong>Key Learnings</strong></h3><p>This project was an insightful challenge. From dealing with <strong>limited survey responses</strong> to <strong>sensitive interview topics</strong>, I learned to <strong>adapt and refine</strong> our approach.</p><p>One of my biggest takeaways was <strong>collaborative design</strong>. Working with Stéphane made me realize how crucial <strong>flexibility</strong> is — I tend to have a clear vision and push for it, but balancing that with <strong>open-mindedness</strong> is key. Aligning our styles wasn’t always easy, but it taught me to <strong>embrace different perspectives</strong>.</p><p>Beyond teamwork, I sharpened my <strong>Figma expertise</strong>, strengthened my <strong>UX research approach</strong>, and gained a deeper appreciation for <strong>iterative design</strong>.</p><p>The next steps? A <strong>desirability test</strong>, more refinements, and exploring <strong>gamification features and podcast integrations</strong> to further enhance engagement.</p><h3><strong>Conclusion</strong></h3><p>This project helped me <strong>deepen my skills and develop stronger design reflexes</strong>. I now fully grasp the bootcamp’s method of constant practice through new projects — each experience reinforces key concepts and builds confidence.</p><p>One thing is certain: I’ll never get bored in this field. While the <strong>methodology remains consistent, each project brings new challenges and surprises</strong>. This continuous learning process is exactly what I love about UX/UI design.</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7c3a982fee5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Redesigned Uber Eats in 48 Hours — A UX/UI Case Study]]></title>
            <link>https://medium.com/@elise.rocchesani/i-redesigned-uber-eats-in-48-hours-a-ux-ui-case-study-c21d1f6441a3?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c21d1f6441a3</guid>
            <category><![CDATA[redesign-challenge]]></category>
            <category><![CDATA[design-critique]]></category>
            <category><![CDATA[ubereats]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Sun, 23 Mar 2025 18:24:05 GMT</pubDate>
            <atom:updated>2025-03-23T18:24:33.006Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>I Redesigned Uber Eats in 48 Hours — A UX/UI Case Study</strong></h3><figure><img alt="Mockup showcasing an overview of the Uber Eats redesign. The new version features a cleaner, more structured interface for better user experience." src="https://cdn-images-1.medium.com/max/1024/1*bIfkJ8IKmXQFavYhgJ33_w.png" /></figure><p>For my third project in the Ironhack UX/UI Design bootcamp, I was tasked with redesigning four screens of an app of my choice.</p><p>I chose <a href="https://www.ubereats.com/fr?srsltid=AfmBOooveIJMUKDJddW1b23AQMidgjWdWqaDZaRl_foMSkMDZIbI1DNm">Uber Eats</a> because, as a frequent user, I often felt overwhelmed by the excess of information — constant promotions, excessive highlighted content — distracting from the core experience. My challenge? Simplifying the user experience to make navigation smoother and more enjoyable.</p><p>This solo project, completed in just two days, presented a unique challenge: regaining my independence after several collaborative projects. It also pushed me to improve my time management, especially by learning to prioritize and not get stuck on minor details.</p><ul><li><strong>Timeline:</strong> 2 days</li><li><strong>Role: </strong>Solo UX/UI Designer</li><li><strong>Tools: </strong><a href="http://figma.com/">Figma</a></li><li><strong>Approach: </strong>Design Critique</li></ul><h3><strong>Competitive Analysis</strong></h3><p>Before diving in, I analyzed four competitors to identify their strengths and weaknesses:</p><ul><li><a href="https://deliveroo.fr/fr/"><strong>Deliveroo</strong></a>: Similar experience to Uber Eats but also suffers from information overload.</li><li><a href="https://www.just-eat.fr/?utm_source=henoo"><strong>Just Eat</strong></a>: More intuitive interface with a smooth transition between “Delivery” and « Takeaway.”</li><li><a href="https://glovoapp.com/fr/"><strong>Glovo</strong></a>: Playful approach with illustrations. Users first select a category (restaurants, supermarkets, etc.) before browsing options.</li><li><a href="https://bolt.eu/en/food/"><strong>Bolt Food</strong></a>: Ultra-minimalist interface, but sometimes too much so — lacking product categories.</li></ul><p>This analysis provided key insights, even though I hadn’t yet determined which screens to redesign.</p><h3><strong>Heuristic Evaluation of Uber Eats</strong></h3><p>Next, I assessed Uber Eats using Nielsen’s usability heuristics. This deep dive helped reinforce my understanding of these principles, as I hadn’t previously applied them in such detail.</p><p><strong>Challenges faced</strong>:</p><ul><li>Categorizing certain issues correctly, as some overlapped multiple heuristics.</li><li>Staying focused on the selected screens and not getting sidetracked by unrelated elements.</li></ul><p>Here are a few key usability issues I identified:</p><ul><li><strong>Visibility of system status</strong></li></ul><p><strong>Issue</strong>: When a filter is activated, it changes color, but there’s no clear way to reset the view. This can be frustrating.<br> <strong>Solution</strong>: Add an “X” button to clear selections and provide better visual feedback.</p><ul><li><strong>Aesthetic and minimalist design</strong></li></ul><p><strong>Issue</strong>: The interface is cluttered with promotions and unnecessary information, making navigation difficult.<br> <strong>Solution</strong>: Reduce non-essential elements to highlight restaurants and relevant recommendations.</p><ul><li><strong>Flexibility and efficiency of use</strong></li></ul><p><strong>Issue</strong>: Users must scroll extensively to access different categories (Flowers, Alcohol, etc.).<br> <strong>Solution</strong>: Introduce a fixed navigation menu for quick access to key sections.</p><h3><strong>Branding</strong></h3><p>I decided to retain Uber Eats’ existing color scheme since I didn’t see it as the root problem. However, I slightly reduced the size of the tab bar icons to create a cleaner, less imposing look. I also kept the illustrated category icons for restaurants and stores while maintaining a more traditional icon style for other elements.</p><h3><strong>Redesign</strong></h3><p>I selected the four screens that, in my opinion, presented the most usability issues.</p><h4><strong>Homepage</strong></h4><p>Upon opening the app, the interface felt overwhelming, with promotions, featured content, and restaurant listings all competing for attention. I simplified the layout by keeping just one “Special Offers” section before displaying the restaurant list.</p><p>Another confusing aspect: the search bar displayed “Search Uber Eats Help,” which could mislead users. I changed this to “Search for a restaurant” for better clarity.</p><p>Filters were another pain point — too many, poorly organized, and requiring excessive scrolling. Instead, I grouped them under a single “Filters” button while adding a dedicated “Takeaway” shortcut for more intuitive navigation.</p><p>Additionally, the “Grocery” tab was prominently placed in the bottom navigation, despite Uber Eats being primarily a restaurant-focused app. I restructured the navigation, introducing a toggle at the top to switch between Restaurants and Grocery.</p><p>As for the cart, which previously occupied the space of the new toggle, I debated between placing it in the bottom tab bar or using a floating button. I initially chose the tab bar, but after a <strong>design critique session with Nicky (our instructor), I realized a floating button would have been a better choice</strong> — as shopping carts in e-commerce apps are typically located in the top right for quick access.</p><p><em>Here is the before-and-after of the homepage:</em></p><figure><img alt="Mockup showing the Uber Eats homepage before and after the redesign. The new version is cleaner, with fewer promotions and a clearer restaurant list." src="https://cdn-images-1.medium.com/max/1024/1*Hv2VVaDpAaYK5xkNoYb1yg.png" /><figcaption>Before / After — Homepage</figcaption></figure><h4><strong>Grocery Page</strong></h4><p>This page had the same issue as the homepage: too many promotional elements cluttering the view. Additionally, the category bar disappeared when scrolling, forcing users to scroll back up to access it. I made this bar <strong>sticky</strong> so it would always remain visible.</p><p>I also reorganized the sections: each category now features <strong>three highlighted items</strong> followed by a list of stores displayed as icons, improving readability and space efficiency.</p><p>While testing, I initially worried that having a fixed header, footer, and category bar might take up too much space. However, after Nicky’s critique, I realized the issue wasn’t their presence but their <strong>placement</strong>. I had positioned the category bar on the left, which wasn’t ergonomic — most users hold their phone in a way that places their thumb in that area, making navigation awkward. This also disrupted the <strong>visual grid consistency</strong>.</p><p><em>Here is the before-and-after of the grocery page:</em></p><figure><img alt="Comparison of the Uber Eats grocery page. The redesign adds a fixed category bar and a more structured layout." src="https://cdn-images-1.medium.com/max/1024/1*PNg-OEXuponGhxOvsmCN0w.png" /><figcaption>Before / After — Grocery Page</figcaption></figure><h4><strong>Restaurant Page</strong></h4><p>The main problem here was <strong>information overload</strong>, particularly a text link to the restaurant’s location that didn’t appear clickable. I clarified the layout by <strong>turning it into a dedicated button</strong>.</p><p><em>Here is the before-and-after of the Restaurant page:</em></p><figure><img alt="Mockup of the restaurant page before and after. Information is better organized, and the location button is more visible." src="https://cdn-images-1.medium.com/max/1024/1*v3Z-8D3EDNobWP8dxxvEww.png" /><figcaption>Before / After — Restaurant Page</figcaption></figure><h4><strong>Product Page</strong></h4><p>The biggest usability issue was <strong>lack of clarity in the selection process</strong> (sauce choices, side dishes, etc.). There were no step indicators, and users received no warnings if they forgot a required selection.</p><p>To fix this, I added a <strong>progress bar</strong> to guide users through the steps. However, <strong>after Nicky’s feedback, I realized my progress bar looked too similar to the one on the restaurant page</strong>, which could create confusion.</p><p>Another inconsistency was the <strong>image design</strong> — I had used circular images for products, whereas the rest of the app featured rounded rectangles. This lack of visual consistency was a key issue raised in the critique.</p><p><em>Here is the before-and-after of the Product page:</em></p><figure><img alt="Comparison of the product page. The redesign introduces a progress bar to guide users through their selections." src="https://cdn-images-1.medium.com/max/1024/1*8Xm5QW0CQDRIq-z1SJWXIQ.png" /><figcaption>Before / After — Product Page</figcaption></figure><h3><strong>Key Takeaways</strong></h3><p>This redesign was a real challenge, especially with only <strong>two days</strong> to complete it. I finished at 11 PM on the second night, fine-tuning interactions and preparing an interactive <strong>components page</strong> with dynamic buttons. Due to time constraints, I couldn’t redesign every category in the Grocery section but made strategic choices to maximize impact.</p><p>One of my biggest takeaways was the <strong>design critique process</strong>. This was my first time doing a formal critique, writing <strong>critique cards</strong>, and analyzing my work through this lens. Interestingly, <strong>the areas I was unsure about were the exact points Nicky raised in her feedback</strong>. This reassured me that my instincts were correct, but I still need to refine my <strong>methodology and design decision-making</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c21d1f6441a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transforming a Photographer’s website — A UX/UI Case Study]]></title>
            <link>https://medium.com/@elise.rocchesani/transforming-a-photographers-website-a-ux-ui-case-study-303d15705aee?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/303d15705aee</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[e-commerce-website-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[photographer]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Sun, 16 Mar 2025 11:15:19 GMT</pubDate>
            <atom:updated>2025-03-17T08:21:25.216Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transforming a Photographer’s website — A UX/UI Case Study</h3><figure><img alt="Hero image showcasing the hi-fi prototype, booking flow, and calendar for Akemy Mory’s website." src="https://cdn-images-1.medium.com/max/1024/1*gLW-qcBSrUQQ9QpEHK_SCA.png" /><figcaption>Hero image from my latest Ironhack’s project</figcaption></figure><h3>Project overview</h3><p>For my second UX/UI project at Ironhack, I had 8–9 days to design a responsive website for a local professional — this time, <strong>working with a real stakeholder, which brought new challenges</strong>.</p><p>I teamed up with <a href="https://medium.com/@leux_designer">Leticia</a>, a fellow student, and together we chose to revamp the website of Akemy Mory, a Lisbon-based photographer looking to enhance her online presence. <strong>We quickly realized our strengths were complementary</strong> — she thrived in research, while I was passionate about design. Instead of splitting tasks, we worked side by side, <strong>constantly challenging and learning from each other</strong>.</p><p>A major shift was working autonomously — <strong>no daily instructor check-ins</strong>. Using Notion, we structured our workflow, managed interviews, and balanced research, ideation, and prototyping, all under a tight deadline. <strong>Adapting to a new teammate in a fast-paced, English-speaking setting also sharpened my communication skills.</strong></p><p>This project pushed me to navigate the entire design process, from research to high-fidelity prototyping, while also learning to work with a stakeholder’s needs in mind. It reinforced the importance of <strong>collaboration, adaptability, and time management</strong> — all essential skills for a UX/UI designer.</p><ul><li><strong>Duration</strong>: 8/9 days</li><li><strong>Team:</strong> 2 UX/UI designers</li><li><strong>Tools:</strong> <a href="https://www.figma.com/fr-fr/">Figma</a>, Figjam, <a href="https://zoom.us/fr/signin">Zoom</a>, <a href="https://workspace.google.com/intl/fr/products/forms/">Google Form</a>, <a href="https://www.notion.com/fr">Notion</a></li><li><strong>Methodology:</strong> Design Thinking</li></ul><h3><strong>Research Phase</strong></h3><p>We started with market analysis and benchmarking. We researched photographers in Portugal, only to realize that most specialized in weddings, while Akemy’s focus was more on lifestyle and business photography. But we found some inspirations.</p><p>Our secondary research revealed key challenges: <strong>photographers struggle with time management, marketing, and client communication</strong>, while clients often find <strong>pricing unclear and booking frustrating</strong>.</p><h4><strong>User Research</strong></h4><p>To better understand user expectations, we created a Google Forms survey. Leticia introduced me to <strong>conditional question paths</strong>, refining responses for sharper insights.</p><p>Our goal? <strong>Identify what drives or blocks people from booking a photographer.</strong> With 15 responses, we spotted valuable patterns.</p><h4><strong>Stakeholder Interview</strong></h4><p>On Monday, we interviewed Akemy. Her biggest challenge? <strong>Time management.</strong> She handled bookings manually via WhatsApp and email, relying mostly on <strong>word-of-mouth</strong>.</p><p>We also discovered her main audience was <strong>entrepreneurs and small businesses</strong> — not the general public. Our survey had been too broad. <strong>We needed to pivot.</strong></p><p><strong>Lesson learned:</strong> Always align with the stakeholder before launching research!</p><h4><strong>User Interviews &amp; Affinity Diagram</strong></h4><p>We refined our questions to focus on entrepreneurs. Leticia reminded me to <strong>avoid hypothetical questions</strong> — people tend to say what they think is right, not what they actually do.</p><p>Finding entrepreneurs was tough, but we conducted <strong>five interviews in one day</strong>. A big step for me — I felt <strong>much more confident</strong> in guiding conversations.</p><p>Using an <strong>affinity diagram</strong>, we identified key themes: <strong>photo quality, brand alignment, recommendations, and seamless communication</strong>.</p><p>One interviewee summed it up best:</p><blockquote>“For me, the quality of the photos was important, and I wanted to feel comfortable working with the photographer.”</blockquote><p>These insights set the foundation for the next phase.</p><h3><strong>Problem</strong></h3><h4><strong>Persona</strong></h4><p>With research insights, we built a persona: <strong>Manuel, a busy bakery owner </strong>who doesn’t have time to develop his brand and attract more customers.</p><p>At first, we framed his goals around <strong>what he looks for in a photographer</strong> — things like communication and style. But that was a mistake! <strong>His real goal isn’t about photography at all — it’s about growing his business.</strong></p><p>We had focused on <strong>our solution instead of his actual needs.</strong> The right approach? <strong>Start with his problem (more traffic), then recognize that better photos are the solution.</strong><br><strong>Key learning:</strong> Always define the user’s core needs first — before thinking about the product.</p><h4><strong>User Journey Map</strong></h4><p>Next, we mapped out Manuel’s <strong>user journey </strong><em>(pictured bellow)</em>, which was a tricky part in my last project. This time, I revisited my notes and had a breakthrough — I identified a <strong>key emotional moment</strong>:</p><p><strong>Scenario:</strong> Manuel organizes an event at his bakery but is too busy to take quality pictures. At the end of the day, he realizes the photos he managed to take are unusable — he just <strong>missed a huge opportunity to showcase his business</strong>.</p><p>The story immediately resonated with Leticia and our mentor, Neil. I finally <strong>understood what makes a compelling user journey</strong> — it has to create an emotional connection and highlight a <strong>clear pain point</strong>.</p><figure><img alt="Image of Manuel’s user journey map, with the 5 steps of his 5 journey, highlighting the moment he realizes the impact of not having professional photos" src="https://cdn-images-1.medium.com/max/1024/1*B9HjktgTIK1IC05dS4fiWA.png" /><figcaption>Image of Manuel’s user journey map</figcaption></figure><h4><strong>Problem Statement</strong></h4><p>A new step for us: framing the problem from both the stakeholder’s and user’s perspective.</p><blockquote><strong>For Akemy (stakeholder)</strong><br> Akemy’s website should help small business owners book professional photoshoots easily. But unclear booking and an ineffective portfolio mean fewer bookings and missed opportunities.</blockquote><blockquote><strong>For Manuel (user)</strong><br> Small business owners in Lisbon need high-quality photos to attract customers and grow. But finding a photographer that fits their brand is frustrating.</blockquote><p>At first, we debated: should we focus on their experience with photographers or their bigger business struggles?<br><strong>Answer:</strong> Their real concern is business growth.</p><h3><strong>Ideation</strong></h3><p>Next step: ideation! We started with <strong>Crazy 8’s</strong>, sketching one idea per minute for eight minutes each. We came up with creative concepts — like an <strong>“intelligent” booking calendar</strong> or surprise photoshoot sessions where Akemy could spontaneously drop in. While fun, we realized the latter wasn’t practical, as photographers need to plan their sessions.</p><p>We then organized our ideas into an <strong>MVP matrix</strong>, categorizing them into <strong>Must-Have, Should-Have, Could-Have, and Won’t-Have</strong> features. The key takeaways? A streamlined <strong>booking system</strong>, a <strong>questionnaire</strong> for client preferences, an <strong>online portfolio</strong>, and <strong>testimonials</strong>, which our user research confirmed as essential.</p><h4><strong>User Flow &amp; Sitemap</strong></h4><p>Time to map out the <strong>User Flow </strong><em>(pictured bellow)</em>! I had previously confused it with the sitemap and overcomplicated it, so this time, Leticia and I kept it simple. We focused on one clear goal: <strong>booking a photoshoot as a business owner</strong>.</p><figure><img alt="Image of User flow illustrating the seamless process for business owners to book a photoshoot." src="https://cdn-images-1.medium.com/max/1024/1*3ioRwkav9T01gFfHdKzrGw.png" /><figcaption>Image of User Flow</figcaption></figure><p>Then came the <strong>Sitemap</strong>. While I had experience with it, narrowing it down to just one user flow initially threw me off. Luckily, with guidance from Neil, we structured it effectively.</p><h3><strong>Prototyping &amp; Testing</strong></h3><h4><strong>Lo-fi Prototype &amp; Concept Testing</strong></h4><p>Everything started to become clearer! We created our first wireframe: a simple lo-fi prototype. We quickly built it and tested it — this was our <strong>concept testing</strong>. We had three users try it out, and they all found the booking process “<strong>clear”</strong>.</p><h4><strong>Mid-fi Prototype &amp; Usability Testing</strong></h4><p>Since the lo-fi test was successful, we moved on to a more advanced <strong>mid-fi prototype</strong> with interactions <em>(pictured bellow)</em>. This time, we conducted a <strong>Usability Test</strong>, where we gave users a task — booking a photoshoot — without any guidance and observed how they performed. We ran five tests, and four users rated the process as <strong>“easy” or “very easy”</strong>. However, they pointed out some key improvements:</p><ul><li>The calendar didn’t allow time selection, only dates.</li><li>There was no “back” button.</li><li>After confirmation, a button to return to the home screen was missing.</li></ul><p>This made me realize how crucial testing is! Even though our lo-fi prototype was validated, we still found <strong>important UX issues</strong>.</p><figure><img alt="Image of 3 frames (Homepage, booking form and confirmation) of Mid-fi prototype with highlighted areas for improvement based on usability testing feedback." src="https://cdn-images-1.medium.com/max/1024/1*GuG0O7pRRFu9zylXOpr3YA.png" /><figcaption>Image of Mid-fi prototype with highlighted areas for improvement based on usability testing feedback.</figcaption></figure><h4><strong>Moodboard &amp; Branding</strong></h4><p>A fascinating step! We defined our <strong>brand attributes</strong> (<em>soft, natural, authentic, emotional…</em>) and tested our <em>moodboard</em> in class <em>(pictured bellow)</em>.<br> <strong>Great feedback on our visual direction!</strong> But we realized that words like <em>“thrifty”</em> were misinterpreted, leading us to refine our branding choices.</p><figure><img alt="Image of the Moodboard defining the brand’s visual identity — soft, natural, and authentic — Pictures, colors, and words" src="https://cdn-images-1.medium.com/max/1024/1*1b07_kpPM0zSUSW6sVuUsg.png" /><figcaption>Image of moodboard</figcaption></figure><h4><strong>Hi-fi Prototype</strong></h4><p>Time for the <strong>high-fidelity prototype </strong><em>(pictured bellow)</em>!</p><p>I started incorporating <strong>all the necessary refinements</strong>, guided by our <strong>moodboard for colors, imagery, and typography.</strong> I replaced placeholders with real content, polished the UI, and ensured <strong>visual consistency</strong> throughout the design.</p><p>Meanwhile, Leticia explored <strong>Figma plugins</strong> to optimize the <strong>smart booking calendar.</strong> We continuously tested interactions, questioning how <strong>interactive and functional</strong> the prototype needed to be. Should the questionnaire be fully fillable? Should all buttons work? In the end, <strong>Neil reassured us</strong> that our current level of interactivity was sufficient.</p><p>After multiple iterations, we were ready for the final step: <strong>presentation!</strong></p><figure><img alt="Image of High-fidelity prototype showcasing the final design of Akemy’s website — all the frames (from homepage to confirmation page)" src="https://cdn-images-1.medium.com/max/1024/1*I0gUayc7SrBXxVUfiLayKw.png" /><figcaption>Image of High-fidelity prototype</figcaption></figure><p>Feel free to test the prototype <a href="https://www.figma.com/proto/V7uAAb6PANhKPyX0ZBB8IS/%5B-P2-Team-4-%5D-Design-File-(Copy)?page-id=4540%3A146&amp;node-id=4540-147&amp;p=f&amp;viewport=51%2C194%2C0.1&amp;t=n9yF0ElQmuHSGLwI-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;starting-point-node-id=4540%3A147">here</a>.</p><h4>Presentation</h4><p>Leticia had a great idea: starting with a <strong>Pixar-style storytelling</strong> to introduce Manuel’s journey. It immediately engaged the audience! We structured our presentation together — Leticia summarized the content while I designed the slides.</p><p>We were the <strong>first team to present</strong> (6 min 40 in total, split evenly). The feedback?</p><ul><li><strong>What we could improve:</strong> We made the presentation too short, skipping key research data and usability test results. Also, showing the hi-fi prototype as a <strong>video</strong> was a bit rushed — I didn’t give people time to fully absorb it.</li><li><strong>What went well:</strong> Great <strong>design</strong>, strong <strong>presentation skills</strong>, and an engaging delivery!</li></ul><h3><strong>Final Takeaways</strong></h3><p>This project with Leticia was an <strong>amazing learning experience</strong>, covering everything from <strong>user research</strong> to <strong>high-fidelity prototyping and presentation</strong>. It reinforced just how crucial each phase is in building an intuitive and efficient user experience.</p><p>One of the biggest lessons was the <strong>importance of iteration and user feedback</strong>. Even when we thought our designs were clear, testing revealed <strong>unexpected insights</strong> that helped refine the experience.</p><p>After our presentation, we took time to <strong>reflect on our work</strong> through a <strong>Start-Stop-Continue feedback session</strong> together. This was a great way to <strong>give each other constructive feedback</strong> and recognize both our strengths and areas for growth.</p><ul><li><strong><em>Start</em></strong><em>: “You should start a Figma course to go deeper into the tool.”</em></li><li><strong><em>Stop</em></strong><em>: “We should avoid making the presentation too short — next time, let’s highlight more key data and test results.”</em></li><li><strong><em>Continue</em></strong><em>: “Keep up the hard work! You have a real talent for UI design and are great at teamwork.”</em></li></ul><p>Beyond improving my technical skills, this project <strong>confirmed how much I enjoy UI design, problem-solving, and collaboration</strong>. Working closely with Leticia made the whole process <strong>engaging and insightful</strong>, and I truly appreciated our ability to <strong>bounce ideas off each other, challenge ourselves, and refine our approach</strong>.</p><p>I’m excited to <strong>keep learning, take on more complex projects, and push my UX/UI skills even further</strong>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=303d15705aee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making local food more accessible — a UX Case Study]]></title>
            <link>https://medium.com/@elise.rocchesani/making-local-food-more-accessible-a-ux-case-study-665d3df0a62b?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/665d3df0a62b</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[food-sustainability]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Sun, 02 Mar 2025 18:08:28 GMT</pubDate>
            <atom:updated>2025-03-03T08:33:15.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>Making local food more accessible — a UX Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*thTktepot8hMNZfuO6p4Hw.png" /></figure><h3>Project Overview</h3><p>This case study highlights the first project I worked on during my <strong>UX/UI bootcamp</strong> at <a href="https://www.ironhack.com/fr-en/paris?utm_campaign=PAR_France_Paris_Global_Search_Brand_EN&amp;utm_source=google&amp;utm_medium=cpc&amp;utm_content=Brand-en&amp;utm_term=ironhack&amp;adgroup=brand_en&amp;gad_source=1&amp;gclid=Cj0KCQiAoJC-BhCSARIsAPhdfSgHN2mJi5Itub6md19kMaH46Xnivpmco0YBML-bV5VCYcW363qNfzEaAusWEALw_wcB">Ironhack</a>. The task was part of our <strong>“Wicked Problem”</strong> challenge, where we had to solve a real-world issue in just one week. Our team of four UX/UI designers (Alexandra, James, Stephane and me) was tasked with <strong>improving the accessibility of local, seasonal food.</strong></p><p>This project pushed me to <strong>expand my skills</strong> in user research, ideation, and prototyping. On a personal level, it was a <strong>challenge</strong> to work in a professional setting in English and <strong>collaborate</strong> with an international team. It was a week of intense learning, and it helped me grow not just as a designer, but also as a collaborator.</p><p><strong>Duration:</strong> 1 week<br><strong>Team:</strong> 4 UX/UI designers<br><strong>Tools:</strong> <a href="https://www.figma.com/fr-fr/">Figma</a>, Figjam, <a href="https://zoom.us/fr/signin">Zoom</a><br><strong>Methodology:</strong> Design Thinking</p><h3>Problem to Solve</h3><p>In recent years, consumers have become more aware of the importance of healthy eating and the benefits of organic and local food. However, local products remain difficult to access for many people, often due to high prices or limited availability. Traditional food systems also lack transparency, and big supermarket chains continue to benefit more than small-scale, local producers.</p><p>Our challenge was framed as: <em>How might we help people access local, seasonal produce more easily, while also fostering fair and transparent relationships between producers and customers?</em></p><h3>User Research</h3><h4>Secondary Research</h4><p>Before user interviews, we conducted secondary research to understand the broader context of local food accessibility. This helped us identify key barriers that consumers face, which informed our interview approach.</p><p>Key insights from secondary research:</p><ul><li><strong>High prices</strong>: 75% of consumers find local products too expensive.</li><li><strong>Limited availability</strong>: 25% struggle to find local products.</li><li><strong>Lack of transparency</strong></li><li><strong>Lack of knowledge</strong></li></ul><h4>User Interviews</h4><p>We interviewed people from Spain, Netherlands, and Portugal to understand their shopping habits and frustrations with local food. We asked questions to uncover their motivations and barriers around purchasing local products.</p><p>Writing the interview questions made me realize the importance of asking open-ended, neutral questions. At first, I wanted to be more specific, but this could have led to biased responses. Observing the interviews helped me gain deeper insights into participants’ frustrations and needs.</p><p>We then organized the interview data into an <strong>affinity diagram</strong>, revealing three main trends: <strong>Time and convenience, Price, Quality and freshness.</strong></p><h3>Problem Statement</h3><p>After synthesizing our research, we defined the following problem statement:</p><blockquote>Busy health-conscious parents in France need to find a way to feed their family with the healthiest products possible because currently, planning and buying food for a family is time-consuming, and healthy local options are not always easily accessible or affordable.</blockquote><p>We created a single persona (pictured below) to represent our target user. <strong>Olivia</strong>, a busy mom, perfectly encapsulated the challenges we had identified in our research. While developing Olivia, I learned the importance of focusing on the user’s needs and pain points, rather than getting bogged down in too many personal details. We also made sure to choose a culturally relevant name, ensuring the persona felt authentic and relatable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*EmxiKRziYuiumpoU9akMvA.jpeg" /><figcaption>Olivia, a busy mom, represents the target user with challenges in accessing local, seasonal food</figcaption></figure><p>To better understand Olivia’s experience, we created a user journey map (pictured below), which visualized her frustration points throughout the process of shopping for local food. The journey map highlighted key moments where she felt pain points and opportunities for improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gTF0QmjZZjK8NjdCEn1A7g.png" /><figcaption>Olivia’s user journey map, highlighting pain points and opportunities for improvement.</figcaption></figure><h3>Ideation</h3><p>With the problem statement clearly defined, we moved on to ideation. We started with a <strong>Crazy 8’s</strong> session to generate multiple ideas rapidly. After several iterations, we settled on designing an app that would help users access local food and plan meals based on seasonal products.</p><p><strong>Key features of the app:</strong></p><ul><li>A questionnaire to determine food preferences.</li><li>An algorithm to generate personalized meal plans based on local, seasonal produce.</li><li>A meal personalization option to adjust the meal plan to individual tastes.</li><li>A delivery service to make local products easily accessible.</li></ul><p>During the ideation phase, one of my biggest challenges was simplifying the user flow (pictured below). At first, the app had a lot of features and details, but we quickly realized that simplicity was key. The challenge was to focus on the most essential elements to address the user’s core needs. It was interesting to iterate on each other’s Crazy 8’s sketches and refine the features to make them more user-centered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIOLHqaEpO3ZMeZ7ipOq6g.png" /><figcaption>This user flow maps out the intuitive process for users, simplifying the steps to access meal plans.</figcaption></figure><h3>Prototyping and User Testing</h3><p>We created a low-fidelity prototype (pictured below) to bring our idea to life and tested it with several users to gather feedback. This phase was crucial for identifying any usability issues and refining the user experience.</p><p><strong>User feedback:</strong></p><ul><li><strong>Positive:</strong> Users appreciated the meal planning and personalization features and found the app easy to navigate.</li><li><strong>Areas for improvement:</strong> The interface displayed too much information at once, which made it overwhelming. Navigation was confusing at times, and users wanted more clarity on delivery options.</li></ul><p>Testing the prototype with real users helped me understand how to present a product clearly and ask the right questions without influencing the responses. It was important to listen to the users’ concerns and address them immediately. Their feedback directly informed the iterations we made to improve the app’s usability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gBvWJjrEeikQvPC5IyjBmw.png" /><figcaption>A low-fidelity wireframe of the app, designed to simplify local food access and meal planning.</figcaption></figure><h3><strong>Presentation</strong></h3><p>The final presentation (pictured below) summarized our design process, key insights, and the solution we developed to make local food more accessible. We shared our findings, the app’s core features, and our iterations based on user feedback.<br>One of the challenges we faced during the presentation was how to communicate our process effectively. It was important not to overwhelm the audience with too much detail, so we focused on a clear, streamlined narrative. The experience of presenting to an audience also helped me understand how to highlight the most important aspects of the project while keeping the story engaging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jh_JN19en516j0yDo2Iqw.png" /><figcaption><em>Our presentation summarized the project and highlighted the user-centered design approach.</em></figcaption></figure><h3>Key Learnings</h3><p>This project provided me with invaluable experience in the UX design process, from user research to prototyping. Here are my main takeaways:</p><ul><li><strong>Test ideas quickly</strong> to validate assumptions and avoid false conclusions.</li><li><strong>Simplify the user flow</strong> by focusing on core features to meet the user’s needs.</li><li><strong>Collaborate effectively</strong> with your team to refine and improve the design solution.</li></ul><p>Although the project was intense and condensed into one week, I learned so much. I was particularly drawn to the design phase, where we could see our ideas come to life. The collaborative nature of the project allowed me to grow as both a designer and a team player, and I’m proud of the solution we developed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=665d3df0a62b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: EliseRocchesani_Challenge2]]></title>
            <link>https://medium.com/@elise.rocchesani/ironhacks-prework-eliserocchesani-challenge2-5050d7be275d?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5050d7be275d</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[lo-fi-prototype]]></category>
            <category><![CDATA[nike-run-club]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Tue, 04 Feb 2025 14:55:34 GMT</pubDate>
            <atom:updated>2025-02-04T14:55:34.773Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g32A7DBYGgaOdaYLBOoByw.jpeg" /></figure><p>When designing a product, we often focus on aesthetics and branding, but understanding the <strong>core user flow</strong> is what truly makes an experience seamless. To sharpen my UX skills, I decided to analyze <a href="https://www.nike.com/fr/nrc-app"><strong>Nike Run Club</strong></a>, an app I use frequently and appreciate for its clarity.</p><p>Nike has a strong visual identity, which makes it even more challenging to strip the UI down to its essentials. What happens when we remove branding and focus purely on <strong>functionality</strong>? That’s exactly what I explored by creating a wireframe for one of my favorite features: <strong>Guided Runs</strong>.</p><h3>User flow: starting a guided run</h3><p>The goal of this flow is <strong>to start a Guided Run as quickly and intuitively as possible</strong>.</p><ul><li>1️. <strong>Home screen</strong> → The user chooses <strong>“Guided Run”</strong> instead of “Quick Start” to follow a structured run.</li><li><strong>2. Guided runs list</strong> → The user browses available runs (Featured, Completed, Categories, etc.) and selects one.</li><li>3. <strong>Run details</strong> → The user reviews key info (duration, description, coach) and taps <strong>“GO”</strong> to start.</li><li><strong>4. Run in progress</strong> → The app tracks <strong>time, pace, BPM</strong>, and plays <strong>audio coaching</strong> to guide the run.</li><li><strong>5. Post-run summary</strong> → The user sees <strong>performance stats</strong> and feedback on their run.</li></ul><p>This flow ensures a <strong>smooth, distraction-free path</strong> to launching and completing a Guided Run.</p><h3>Wireframing process</h3><p>Before jumping into wireframing, I first analyzed the <strong>key UI elements</strong> present in the flow. Nike Run Club uses a mix of interactive components, including buttons for navigation, horizontal scrolling carousels to browse guided runs, pop-ups for features like music selection, and full-screen overlays with a close button. There’s also a timer selection wheel that allows users to set their target duration, and a map displaying the running route — though I later questioned its necessity. Identifying these elements helped me determine what was <strong>essential</strong> to keep in the wireframes.</p><p>With this in mind, I moved on to wireframing, following a <strong>progressive approach</strong>. I started with <strong>hand-drawn sketches</strong> to quickly explore different layouts. This stage allowed for fast iteration without being constrained by design tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRnGgWbhiaaBFwLvTLg9HQ.png" /><figcaption>Hand-drawn wireframe — Fast iteration on layout and structure</figcaption></figure><p>Once satisfied with the structure, I transitioned to <strong>lo-fi digital wireframes in Figma</strong>, using a wireframe kit to ensure clarity and consistency. The focus remained on <strong>functionality and flow</strong>, avoiding any visual design elements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Il9zWDvpHptNQSQEo5SMSQ.png" /><figcaption>Lo-fi wireframe (Figma) — Digital version focusing on flow</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DlUeAz_dTX17jmlF1GiScQ.png" /><figcaption>Hi-fi version — Final design for comparison</figcaption></figure><h3>Key decisions</h3><h4>What’s essential?</h4><p>The biggest challenge was <strong>deciding what to keep and what to remove</strong>. Nike’s UI is highly visual, but a wireframe should focus on <strong>structure, not style</strong>.</p><p>I realized that removing <strong>non-essential details</strong> actually made navigation <strong>clearer</strong> — a crucial lesson in <strong>prioritization</strong>.</p><h4>The map dilemma</h4><p>Nike Run Club displays a <strong>detailed map</strong> of the run route. Initially, I included it, assuming it was important.</p><p>However, in this <strong>specific flow</strong>, the map <strong>wasn’t necessary</strong> — it added <strong>visual noise</strong> without aiding decision-making. Removing it <strong>improved clarity</strong>.</p><h4>Avoiding UI styling traps</h4><p>Some screens in NRC use a <strong>black background</strong> during runs. At first, I replicated this in my wireframe, but then I realized:</p><ul><li><strong>That’s a design choice, not a structural element.</strong></li><li><strong>Wireframes should remain neutral</strong> — so I switched to a standard white background.</li></ul><p>This helped me <strong>stay focused on functionality</strong>.</p><h3>Final thoughts</h3><p>This exercise reinforced how crucial it is to <strong>prioritize clarity over aesthetics</strong> when designing a product. Stripping away branding and UI styling helped me see the <strong>core functionality</strong> more objectively. The process also highlighted the importance of <strong>decision-making in wireframing</strong> — removing unnecessary elements, like the map, led to a more intuitive user experience.</p><p>Nike Run Club’s guided runs feel seamless because the <strong>flow is designed with intention</strong>. By breaking it down, I gained a deeper appreciation for how thoughtful UI choices contribute to a smooth experience. This approach — <strong>focusing on structure first, visuals later</strong> — is something I’ll carry into future UX projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5050d7be275d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: EliseRocchesani_Challenge1]]></title>
            <link>https://medium.com/@elise.rocchesani/ironhacks-prework-eliserocchesani-challenge1-818e522faa9a?source=rss-0221ecba0cd5------2</link>
            <guid isPermaLink="false">https://medium.com/p/818e522faa9a</guid>
            <category><![CDATA[citymapper]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Elise Rocchesani]]></dc:creator>
            <pubDate>Tue, 28 Jan 2025 18:27:22 GMT</pubDate>
            <atom:updated>2025-01-28T18:27:22.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*zVHahVfhxNK3s01bapCRXQ.png" /></figure><p>Founded in 2011 by Azmat Yusuf, a former Google employee, <a href="https://citymapper.com/paris?lang=fr"><strong>Citymapper</strong></a> has become a global leader in urban mobility. With its multimodal trip-planning features, the app helps millions of users navigate their journeys by combining various forms of transportation (bus, metro, tram, bike, etc.).</p><p>However, one persistent pain point for users is the <strong>complexity and fragmentation of ticket purchasing systems.</strong> My objective as part of this UX project was clear: <strong>to design a feature that would unify and simplify the ticket-buying process directly within the app.</strong></p><p>As a Parisian, this topic resonates deeply with me. The frustrations of public transport users are part of my daily life. No, it’s not a myth: endless queues at ticket machines, technical glitches, and inconsistent ticketing systems are very real. Luckily, UX Design offers a powerful methodology to tackle such issues.</p><p>In this article, I invite you to follow the <strong>four key steps of my Design Thinking process</strong>: <strong>Empathize, Define, Ideate, Prototype.</strong></p><h3><strong>Empathize</strong></h3><p>The first step of any UX process is to immerse yourself in users’ lives to understand their needs, frustrations, and habits. To achieve this, I conducted <strong>user interviews</strong> based on a guide of open-ended questions such as:</p><ul><li><em>Can you describe your usual process for buying a transport ticket?</em></li><li><em>How do you manage ticket purchases when you need to use multiple forms of transport for a single journey?</em></li><li><em>When traveling to a city or country you don’t know, how do you purchase transport tickets?</em></li><li><em>Is there a city or transport system that stood out to you, positively or negatively? Why?</em></li></ul><p>I interviewed <strong>five users</strong> aged between 26 and 54. Three of them travel abroad regularly and frequently use public transport in other countries, while the other two mainly use Parisian transport systems daily. Although this sample isn’t fully representative, it provided <strong>valuable insights</strong> to start the process.</p><p>In a real-world scenario, a broader and more diverse user group would have been ideal for gathering even richer data. Nevertheless, this initial research was sufficient to uncover key user pain points.</p><h3><strong>Define</strong></h3><p>The Define phase focuses on analyzing collected insights and articulating a clear central problem around which to design solutions. Here are the recurring frustrations identified during the interviews:</p><ul><li><strong>Machine glitches and complexity</strong>: Users complained about slow, sometimes malfunctioning ticket machines that required unnecessary inputs, such as the final destination. This leads to significant delays and frustration.</li><li><strong>Lack of pricing transparency</strong>: Prices are often unclear and only displayed at the end of the process, which is particularly frustrating in cities like Paris, where fares can be quite high.</li><li><strong>Inconsistent systems</strong>: For example, Paris users noted that while a single metro ticket allows multiple connections within the system, taking a bus requires an additional ticket — even if it’s part of the same journey.</li><li><strong>Language barriers abroad</strong>: Travelers often struggle to decipher ticket machines in foreign languages. Some users even missed their connections because they couldn’t figure out how to purchase tickets quickly.</li><li><strong>Too many apps</strong>: In several cities, users are forced to download a dedicated app for local transport, creating unnecessary clutter and confusion.</li></ul><p><strong>The main problem I am trying to solve :</strong><br>The central issue I aimed to address was the lack of a unified, user-friendly system for purchasing transport tickets across different modes and cities.</p><h3><strong>Ideate</strong></h3><p>The Ideation phase involves brainstorming as many potential solutions as possible. Using the “How Might We” method, I explored several ideas to address the identified problem:</p><ol><li>Providing <strong>clear, detailed </strong>fare breakdowns and <strong>purchase instructions</strong> directly within the app.</li><li>Enabling users to <strong>buy tickets directly in the app</strong>. These tickets would be stored in a <strong>digital wallet</strong> (similar to Apple Pay) and could be used across compatible systems.</li><li>Introducing <strong>a single, integrated ticket for all transport modes </strong>within a journey, eliminating the need for separate purchases.</li></ol><h3><strong>Prototype</strong></h3><p>The chosen solution was to <strong>integrate ticket purchasing directly into Citymapper</strong>. The concept works as follows:</p><ul><li>Users can purchase tickets for their journeys directly in the app.</li><li>Tickets are stored in a <strong>virtual pass</strong>, similar to a digital payment card.</li><li>For each journey, users simply scan their virtual pass to validate their ticket, removing the need for physical ticket machines.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nO5qny208JP7oIsEBaJALQ.jpeg" /><figcaption>Low-fi prototype of the new Citymapper feature</figcaption></figure><h3>Key takeaways from the process</h3><p>Throughout this project, one key lesson became abundantly clear: <strong>initial ideas are rarely enough</strong>, and each stage of the design thinking process holds unique value in shaping a meaningful solution.</p><p>At the outset, I believed I had a clear understanding of the problem and an idea of how to solve it. But as I immersed myself in the <strong>Empathy</strong> phase, interviewing users and uncovering their frustrations, I realized how much I didn’t know. It’s during this phase that<strong> real insights emerge</strong> — details about their struggles and unspoken needs that I could never have guessed.</p><p>The <strong>Define</strong> phase taught me how to turn this raw data into a precise, <strong>actionable problem statement</strong>. From there, <strong>Ideate</strong> pushed me to go beyond my initial assumptions and <strong>consider a broader range of solutions</strong>. Exploring multiple ideas, instead of focusing on just one, often revealed opportunities to <strong>combine the best aspects of different concepts into something stronger. </strong>For example, enhancing fare transparency could work beautifully alongside the integrated ticket purchasing feature, creating a seamless and informed user experience.</p><p>Each step informed and enriched the next, reminding me of the importance of trusting the process and <strong>staying open to unexpected insights.</strong></p><h3><strong>Conclusion</strong></h3><p>Simplifying the ticket-buying process for public transport is a major challenge, but one that’s essential to improving the user experience. By centralizing this functionality within an app like Citymapper, we can transform a frustrating task into a seamless, intuitive process.</p><p>UX Design is, above all, the art of solving complex problems by keeping the user at the center. This experience reinforced my belief that each stage of Design Thinking is an opportunity to learn, improve, and create solutions that truly make a difference.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=818e522faa9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>