<?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 Marine BChenais on Medium]]></title>
        <description><![CDATA[Stories by Marine BChenais on Medium]]></description>
        <link>https://medium.com/@marinebchenais?source=rss-65fe2bf6adda------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*5a2fGGUg0RcPy6c-</url>
            <title>Stories by Marine BChenais on Medium</title>
            <link>https://medium.com/@marinebchenais?source=rss-65fe2bf6adda------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:29:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marinebchenais/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[Redesigning Hublo’s Contract Module]]></title>
            <link>https://medium.com/@marinebchenais/redesigning-hublos-contract-module-88179659d907?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/88179659d907</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 11:36:26 GMT</pubDate>
            <atom:updated>2025-07-11T11:40:56.883Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>From admin overload to smart staffing a 2-week design sprint for a healthtech SaaS</strong></p><p>For our last Ironhack project, I worked in a team of three (with Gladys and Julia) on a real-life challenge for Hublo, a French healthtech SaaS that helps hospitals and care institutions manage short-term staff replacements.</p><p>We were asked to redesign one of their key features: the contract module. This tool is used by healthcare managers to generate, send, and track contracts for temporary staff. On paper, it’s just admin. In real life, it’s a source of daily stress, delays, and friction.</p><p>Our mission was to deliver two versions:</p><ul><li>A V0 aligned with Hublo’s new design system and existing features</li><li>A V1 version based on real user research and internal feedback free of technical constraints</li></ul><p>It was our most complex project yet, but also the one that felt the most connected to real needs.</p><p>We conduct a heuristic analysis of the current platform to identify key pain points on UX/UI:</p><figure><img alt="Heuristic analysis summary with key pain points of the current solution" src="https://cdn-images-1.medium.com/max/1024/1*vD2ujx05Wz2lYKO0tGK_hA.png" /><figcaption>Heuristic analysis summary with key pain points of the current solution</figcaption></figure><h3><strong>Listening to the people behind the platform</strong></h3><p>As always, we started with user research.<br> We conducted six interviews with Hublo users and stakeholders: HR managers, cadre de santé, operational leads and customer success managers. We also looked at Hublo’s competitors and mapped key features.</p><p>What stood out quickly:<br> Replacements are constant, urgent and emotionally charged. And the contract process adds an extra layer of stress.</p><p>“I’m constantly interrupted by calls or people walking in… sometimes I make mistakes just because I’m rushing the contract.”<br> Claire, cadre supérieure santé</p><p>“Replacements are tough. We often have to fill 50 roles in one morning.”<br> Hugo, medical team lead</p><p>“The tool is OK, but I never know who has signed or when. It slows everything down.”<br> Nour, customer success manager</p><h3><strong>Key patterns we uncovered</strong></h3><p>After affinity mapping and clustering pain points, we identified 3 major trends that defined the design challenge:</p><p><strong>1. Lack Of Foresight</strong></p><p>Everything happens at the last minute. No reminders, no calendar view, no prioritization. People can’t anticipate they’re stuck reacting.</p><p><strong>2. Fragmented Information</strong></p><p>Users don’t have a clear view of where things stand: who signed, what’s missing, what’s late. Too many emails, too many clicks, not enough certainty.</p><p><strong>3. Administrative Overload</strong></p><p>Users are overloaded with micro-tasks: updating profiles, checking contract fields, merging templates, downloading docs, and chasing signatures.</p><p>As a result, people develop workarounds: phone calls, manual signatures, spreadsheets. This creates even more friction.</p><h3><strong>Meet our persona : Stéphanie</strong></h3><figure><img alt="Meet our persona : Stéphanie — the Overloaded Manager" src="https://cdn-images-1.medium.com/max/1024/1*FHnf_P1UvueGKwNe9ty6Ew.png" /><figcaption>Meet our persona : Stéphanie — the Overloaded Manager</figcaption></figure><p>To guide our design, we created a persona: <strong>Stéphanie Bouduroul, 45, staff manager in a public hospital.</strong> She juggles dozens of contracts every week, while dealing with emergencies, calls, patient needs and pressure from above.</p><p>She’s caring and competent but she’s exhausted.<br>Her biggest need: clarity and confidence that the right contract has been sent, signed and archived, without having to double-check everything herself.</p><p>We defined a journey map, to describe the struggles she might encounter when dealing with contract administrative part:</p><figure><img alt="The user journey map going over contract admnistrative paperwork !" src="https://cdn-images-1.medium.com/max/1024/1*ZirBdHgwY0t0MU_Zh_DXHw.png" /><figcaption>The user journey map going over contract admnistrative paperwork !</figcaption></figure><h3>Framing the challenge</h3><p>From there, we defined our problem statement:</p><p>Hublo’s contract module does not support healthcare managers in tracking, managing and validating contracts efficiently.<br> It lacks visibility, anticipation and guidance, leading to stress, delays and missed signatures.</p><p>To tackle that, we shaped one core question:</p><p><strong>How might we help users stay on top of their contract workflow with better visibility, timely alerts and clear next steps?</strong></p><h3>From insights to features</h3><p>We ran a Crazy 8s session and ideation workshops to explore solutions. We prioritized our ideas using the MoSCoW method, and selected key features for our V0 and V1 designs.</p><p><strong>Our MVP Includes:</strong></p><ul><li>A contract dashboard with real-time status indicators</li><li>Proactive alerts and reminders for pending actions</li><li>Filters and search by contract type, job role, signature status</li><li>Error summaries when information is missing</li><li>A “next action” assistant to reduce decision fatigue</li><li>Better merging, validation and signature flows</li></ul><p>Our goal: reduce uncertainty and admin load, without adding complexity.</p><h3><strong>Testing, Iterating, Adapting</strong></h3><p>We designed low-fi wireframes first and tested them with users. Feedback was clear:</p><ul><li>“I want to see immediately what’s pending”</li><li>“The signature flow needs to be smarter”</li><li>“Don’t add more steps just make the current ones clearer”</li></ul><figure><img alt="Low-fi wireframes for V1 prototype" src="https://cdn-images-1.medium.com/max/1024/1*7_a97PeN7v-5hny9uBmzlA.png" /><figcaption>Low-fi wireframes for V1 prototype</figcaption></figure><p>We refined our flows, aligned the design with Hublo’s recruitment module, and moved to mid-fi and high-fi versions.</p><p>The mid-fi wireframes we developed for the V1 solution, with usability testing results:</p><figure><img alt="Mid-fi Wireframes with usability test results" src="https://cdn-images-1.medium.com/max/1024/1*2tugrjl_tPXuKOfdxkbieg.png" /><figcaption>Mid-fi Wireframes with usability test results</figcaption></figure><h3><strong>The Final Result</strong></h3><p>We delivered two versions:</p><ul><li><strong>V0</strong>: A clean redesign based on current features and structure</li><li><strong>V1</strong>: A future-facing prototype with smarter logic, better contract management, and mobile views</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*OijW7s4dEXvKs5NwuaodfA.gif" /></figure><p>We couldn’t presented everything to the Hublo team as they didn’t be updated from our presentation timeslot unfortunately, but our teacher gave us few feedbacks.</p><h3><strong>What I take away from this project</strong></h3><p>This was my most complete UX/UI project so far. We worked fast, tested often, iterated constantly. We also learned to listen deeply to users under pressure, and to ask: what can we remove, simplify or automate to truly support their day?</p><p>Our team had to present both a V0 and a V1 prototype in just 8 minutes, while also explaining the user problem, our research process and design decisions. It was clearly too short for the depth of the work we produced, and I realized how the Ironhack pitch format wasn’t fully adapted to a dual-solution project like this. Still, I’m proud of what we built and of how we collaborated to turn research into concrete, thoughtful design. In the end, what matters most to me is this: when tools fail, people compensate with time, stress, or frustration. But when tools truly help, people can breathe. That’s the kind of design I want to keep doing.</p><p>Designing for healthcare is about more than features. It’s about restoring time, attention and peace of mind to people whose job is already hard enough.</p><p>I’m proud of what we built and grateful for the collaboration with Julia and Gladys throughout.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88179659d907" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“New Leaf” : Designing a Wellness App to help smokers quit !]]></title>
            <link>https://medium.com/@marinebchenais/new-leaf-designing-a-wellness-app-to-help-smokers-quit-e14442f4bc18?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/e14442f4bc18</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 16:13:03 GMT</pubDate>
            <atom:updated>2025-06-19T16:13:03.531Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>“New Leaf”</em> : Designing a Wellness App to help smokers quit !</h3><figure><img alt="New Leaf Hero board presenting the branding moodboard and the app homepage." src="https://cdn-images-1.medium.com/max/1024/1*Tg6oFu4mE5jGjmAe8W2nbQ.png" /><figcaption>New Leaf Hero board presenting the branding moodboard and the app homepage.</figcaption></figure><h3>During the fourth project of my UX/UI design training at Ironhack, I had the opportunity to work on a health topic that felt both challenging and deeply personal: quitting smoking journey !</h3><p>Over the course of two intensive weeks, I were asked to design with a new teammate an innovative mobile health application that addressed a specific wellness issue. The brief came from the Daily Health Conference, a nonprofit founded in 1983, seeking to modernize their digital offerings and reengage with their users.</p><p>The brief required us to define a health challenge, conduct user research, and deliver a complete high-fidelity mobile MVP, all while developing a consistent visual identity and brand narrative. From the outset, we wanted our project to be both relevant and emotionally meaningful. That’s how <em>New Leaf</em> was born, a digital companion to help users quit smoking with gentleness, empathy, and long-term resilience.</p><h3>Choosing the topic: Stop-smoking issues…</h3><p>When we were invited to choose a specific wellness challenge, my teammate and I immediately aligned on smoking cessation. We are both smokers, and we’ve both thought about quitting several times. The choice wasn’t just practical. It felt honest and relevant. We knew the emotional ups and downs of trying to quit, the social triggers, and the familiar spiral of shame that can follow a relapse.</p><p>I remember feeling both confident about designing for something so close to my own experience. It meant that I had to be objective and empathetic at the same time.</p><figure><img alt="Stop-smoking relief !" src="https://cdn-images-1.medium.com/max/1024/1*JSSD_6Ssiu29C3PZxznM9g.png" /><figcaption>Stop-smoking relief !</figcaption></figure><h3>Understand: Research and strategic framing</h3><p>We began by creating a Lean UX Canvas, a tool that helped us align business needs with user challenges and define our assumptions. The Daily Health Conference wanted to engage users through digital tools that were interactive, personal, and accessible on mobile. For our users, people trying to quit smoking, the challenge wasn’t about a lack of information. It was about lacking support, especially when things got difficult.</p><p>To ground our work in reality, we launched a short survey (25 respondents) and conducted 7 interviews with current and former smokers. <br>What emerged was clear: health concerns were a strong motivation to quit, but they weren’t enough on their own. Most users expressed a deeper emotional need. This mix of qualitative and quantitative data helped us identify behavioral and emotional pain points.</p><p>Many feared <strong>missing out socially</strong>. One participant said, “I’m afraid to stop smoking because my friends smoke. It’s how we bond.” Smoking, for many, wasn’t just a habit but a way to connect with others, take breaks, and manage stress in social contexts.</p><p>Emotional support also came up repeatedly. People weren’t looking for medical advice or behavior tracking. What they wanted was <strong>encouragement</strong>, especially after a relapse. One person told us, “What helped me most was support from my partner,” while another simply said, “I need guidance I can trust.”</p><figure><img alt="Smokers issues : outcomes from the primary research and users interviews with health concern as a priority." src="https://cdn-images-1.medium.com/max/1024/1*5IW1HHUyjpD8Ov2uvV3OwA.jpeg" /><figcaption>Smokers issues : outcomes from the primary research and users interviews with health concern as a priority.</figcaption></figure><blockquote>These insights helped us shape <em>New Leaf</em> not as a quitting plan, but as a <strong>soft space for emotional recovery</strong>, designed to support users at their most fragile moments, especially when they feared they were falling behind.</blockquote><h3>Define: Persona and user journey</h3><figure><img alt="Let’s meet Ash our primary persona: the hype socializer who recently quit-smoking, and it facing some struggles in her journey" src="https://cdn-images-1.medium.com/max/1024/1*iElU_e_6ua7SOa690HGQ0A.png" /><figcaption>Let’s meet Ash our primary persona: the hype socializer who recently quit-smoking, and it facing some struggles in her journey</figcaption></figure><p>We synthesized our research into a detailed persona. We named her Ash Tray, a name that was intentionally playful, but behind it was a well-researched emotional profile. Ash is 28 years old, a communication director: outgoing, ambitious, and trying to quit smoking again. She is almost convinced with the benefits of quitting, but what she lacks is emotional stability in moments of doubt or stress.</p><p>We mapped Ash’s experience not as a simple flow, but as an emotional path: excitement, motivation, craving, social pressure, relapse, guilt, and the hesitation to follow up the journey. Her story reminded us that quitting is rarely linear. It is made of restarts, and restarts require self-compassion.</p><figure><img alt="Ash quitting smoking journey map: she recently had few intense cough attacks while doing daily sport, now she is decided to stop smoking at good. She wants to start now but she is not confident making it by herself alone and is looking for support in her journey." src="https://cdn-images-1.medium.com/max/1024/1*7WvDUjpW64EpG2vMYNNFVA.png" /><figcaption>Ash quitting smoking journey map: she recently had few intense cough attacks while doing daily sport, now she is decided to stop smoking at good. She wants to start now but she is not confident making it by herself alone and is looking for support in her journey.</figcaption></figure><p>She wants to start now but she is not confident making it by herself alone. She is looking for support in her journey of quitting smoking effectively with few weeks while not changing all her social life habits.</p><blockquote>I found myself identifying with Ash’s ups and downs more than I expected. Translating that into user experience design required empathy, yes, but also structure. We had to find the moments where design could actually intervene and create relief.</blockquote><h3>Structure: Ideation, form Problem Statement to Mid-fi wireframes</h3><p>Based on our research, we framed the core design challenge as follows: how might we provide smokers with emotional support when they face obstacles in their quitting journey, especially during moments of craving or relapse?</p><p>Our users were digitally aware and motivated to quit, but often struggled to stay on track without feeling judged or alone. We aimed to create a solution that offered practical yet emotionally sensitive guidance, tailored to each individual’s experience.</p><p>From this, we developed a set of essential features, including a personalized quitting schedule, minimal onboarding friction, access to cognitive behavioral therapy tools, and a supportive environment with group chat and mentoring. We also prioritized data privacy with a clear GDPR-compliant flow for data access and deletion.</p><p>In our low-fidelity concept testing, users appreciated the simplicity and emotional clarity of the process. However, some were uncomfortable with the term “emergency” on the homepage and suggested more soothing language. In response, we refined the tone and interface to enhance emotional safety.</p><p>Our mid-fidelity usability tests confirmed the effectiveness of the user flow and interaction logic. Users described the experience as fluid and encouraging, which validated our decision to combine practical quitting tools with a warm and non-judgmental design system.</p><figure><img alt="Our mid-fidelity wireframes, and the outcomes we get from the usability tests we conducted: content was clear, UI should follow accordingly !" src="https://cdn-images-1.medium.com/max/1024/1*e0EhRDNpP4cIepYsZU4aWQ.jpeg" /><figcaption>Our mid-fidelity wireframes, and the outcomes we get from the usability tests we conducted: content was clear, UI should follow accordingly !</figcaption></figure><h3>Create: Visual identity and graphic intentions</h3><p>Our moodboard was inspired by wellness brands like Headspace, but we worked hard to define our own tone that felt more emotional and grounded.</p><p>The visual identity of <em>New Leaf</em> was crafted to reflect calmness, confidence, and optimism. We wanted the app to feel like a trusted friend. The color palette combined mint green, soft lemon yellow, and forest green. Typography paired Bricolage Grotesque for headlines with Inter for body text. We built a full atomic design system, making sure components could scale while maintaining visual consistency.</p><figure><img alt="Create an impactful visual identity, inspiring calm and trust with solar color mix and with rounded typefaces." src="https://cdn-images-1.medium.com/max/1024/1*z52Py2jQyovf5SA4vZUGDg.jpeg" /><figcaption>Create an impactful visual identity, inspiring calm and trust with solar color mix and with rounded typefaces.</figcaption></figure><blockquote>This part of the process felt lighter and more creative. It was a welcome shift from the more analytical stages, and it gave me the opportunity to express care through aesthetics.</blockquote><h3>Prototype: High-fidelity wireframes</h3><p>With our concept validated through low and mid-fidelity testing, we moved on to developing the high-fidelity prototype. At this stage, our goal was to bring the full user experience to life, both functionally and emotionally.</p><figure><img alt="Our high-fidelity prototype: facing emergency when relapsing, and looking for some immediate support to overcome the issue. We propose a context description and then a breathing exercice to keep back on track." src="https://cdn-images-1.medium.com/max/1024/1*VnA42nYBFS3M-1U95cu-WA.png" /><figcaption>Our high-fidelity prototype: facing emergency when relapsing, and looking for some immediate support to overcome the issue. We propose a context description and then a breathing exercice to keep back on track.</figcaption></figure><p>We focused on translating our design principles into a refined interface that felt clear, supportive, and trustworthy. Every detail, from the iconography and typography to the layout and micro-interactions, was carefully designed to convey a sense of calm and encouragement.</p><blockquote>We prioritized visual consistency using an atomic design system and built screens that not only helped users track their progress but also offered real-time support when they needed it most.</blockquote><p>The result was a coherent and emotionally responsive prototype that embodied the values of <em>New Leaf</em>: empathy, simplicity, and self-paced empowerment.</p><h3>Final Pitch</h3><p>We presented our project to a jury composed of design mentors and health professionals. Our pitch was heartfelt but exceeded the time limit by almost ten minutes. Looking back, I understand that we were too attached to the details. We wanted to explain everything. But in doing so, we lost the rhythm of our delivery.</p><p>The feedback we received was clear, our teacher appreciated the depth of our research, the coherence of the design, and the emotional clarity of our user persona. However, they also advised us to simplify our presentation. The prototype was strong, but we did not let it speak for itself. We were reminded to improve accessibility in some parts of our design, especially color contrasts, and to clearly indicate the platform context, whether iOS or Android.</p><blockquote>That feedback was essential. It reminded me that good design is not only about building a solution. It is also about how you present it, how you pace it, and how you let others experience it without overwhelming them.</blockquote><p>This project was a personal and rewarding experience in my UX journey, with a strong complementary teammate I couldn’t (and wouldn’t) have done without. I learned how to navigate complexity without losing empathy, and I learned the importance of knowing what to leave out…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14442f4bc18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning an App: Vinted !]]></title>
            <link>https://medium.com/@marinebchenais/redesigning-an-app-vinted-23d3a4840741?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/23d3a4840741</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Fri, 13 Jun 2025 13:00:34 GMT</pubDate>
            <atom:updated>2025-06-13T13:35:10.492Z</atom:updated>
            <content:encoded><![CDATA[<h3>Redesigning an App: Vinted !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*dUoBVoFOMB7bABGueiNu1w.jpeg" /><figcaption>Vinted app: my challenge in redesigning an App !</figcaption></figure><h4>As part of my UX/UI Design bootcamp at Ironhack, we were challenged to redesign an existing app and improve its user interface and usability !</h4><p>The brief was clear: conduct a heuristic evaluation, explore visual competitive analysis, and rework the UI of an existing app (from my choice) to align with existing brand identity : and that, within 2 days ! <strong>I felt panic, but finally I did it !</strong></p><p>My choice was immediate, I choose <strong>Vinted</strong>, the second-hand fashion marketplace. While I appreciate the platform and its vast offer, I’ve always found its user experience inconsistent, overwhelming, and visually confusing. This was an ideal opportunity to redesign a product I use and believe in.</p><p>Vinted has a strong mission making second-hand an appreciated choice.<br>But while the <strong>value proposition is clear</strong>, the <strong>interface doesn’t reflect it</strong>. However, its <strong>brand identity</strong> especially the color palette and visual DNA is solid.</p><p><strong>My objective: Let’s make the Vinted experience feeling like “diamond research,” and not felling like going to a “garage sale” !</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WemyokF5q8beinXWWic6dw.jpeg" /><figcaption><strong>Vinted app project: </strong>my challenge &amp; objective, making the experience more qualitative as buying second-hand can be also considered as a gold scavenger hunt somehow !</figcaption></figure><h3>1. Heuristic analysis &amp; Brand audit</h3><p>I started with a <strong>heuristic evaluation</strong> based on Jakob Nielsen’s 10 usability principles. I applied this analysis to four core areas of the app: <strong>Homepage</strong>, <strong>Profile</strong>, <strong>Favorites</strong>, and <strong>Product Page</strong>.</p><p>From this evaluation, I identified recurring issues:</p><ul><li>Lack of <strong>system visibility</strong> (01. Visibility of system status)</li><li>Inconsistent <strong>navigation and layout</strong> (04. Consistency and standards)</li><li>Overly dense, <strong>non-minimalist visual design</strong> (08. Aesthetic and minimalist design)</li><li>Missing <strong>filtering options and shortcuts</strong> (07. Flexibility and efficiency of use)</li><li>No <strong>user control for exploring</strong> (03. User control and freedom)</li><li>Lack of <strong>guidance and support</strong> (10. Help and documentation)</li></ul><p>To support my decisions, I also conducted a visual <strong>competitive analysis</strong> with second-hand selling platforms like <strong>Vestiaire Collective</strong> and <strong>Selency</strong>. <br>These competitors demonstrated they both had a more curated, editorial, and aspirational approach to second-hand shopping, on the overall a more “premium” experience making me feel interesting for Vinted to also get.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-QVz86HYZls5el6ZUaXq0g.jpeg" /><figcaption><strong>Vinted competitors graphic style analysis</strong> : Vestiaire Collective and Selency</figcaption></figure><h3>2. Define: what to keep and what to improve</h3><p>When getting on the design part, I was not sure of what to do, so I started to work with a pragmatic approach, what should I go with (that I like and is “making the job”) and what I should rework and improve !</p><p><strong>The elements to keep were:</strong></p><ul><li>Vinted’s recognizable<strong> graphic identity &amp; color palette</strong>, I could even add the logo more visibly in my proposals somehow (a feedback I get during my presentation from our teacher)</li><li>The <strong>bottom navigation structure</strong>, which provides a good starting framework, but I could make more efficient</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOb4O0ohv7zryNDzDVQwfQ.jpeg" /><figcaption>Vinted graphic chart, and the 4 screens I decided to focus on including Home, Profile, Favorites and Product pages</figcaption></figure><p><strong>The elements to challenge and improve were:</strong></p><ul><li>The <strong>“cheap” perception</strong> of the interface design</li><li>The absence of <strong>brand storytelling</strong> or content hierarchy</li><li>The <strong>overwhelming layout</strong> of pages with little visual breathing room</li><li><strong>of clear feedback</strong> and contextual actions during the shopping journey</li></ul><p>My aim was to reposition Vinted’s digital experience as <strong>smarter, convenient, editorial, and intuitive experience</strong>, while preserving its accessible feeling !</p><h3>2. Design: challenge UX/UI for 4 Screens</h3><p>I focused on four central screens: the <strong>Homepage</strong>, <strong>Profile</strong>, <strong>Favorites</strong>, and <strong>Product Page</strong>. Each one plays a vital role in the user’s journey, from browsing and saving, to buying and managing listings.</p><p>Here’s how I approached each screen through the lens of usability and clarity.</p><h3>Homepage</h3><p>When you first open the Vinted app, you’re instantly hit with an unfiltered stream of items. There’s little sense of direction, no real hierarchy, and no clear entry point into a shopping experience that should feel exciting, not chaotic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lsszTZL-erf047cF52rL5A.jpeg" /><figcaption>Vinted App Homepage: from before to after !</figcaption></figure><p>I introduced a <strong>filter bar with dropdown menus</strong> right below the search bar, helping users quickly narrow results by type or category. This small addition significantly improves <strong>efficiency and control</strong> (Heuristics 04 and 07).</p><p>To transform the home screen into more than just a feed, I added <strong>editorial shopping suggestions, </strong>curated by the brand with specific selections. This begins to tell a story and leads the user through a more intentional journey.</p><p>I also enhanced the <strong>header area</strong>, adding <strong>direct access to the cart and notifications, a </strong>small change that improved the <strong>visibility of system status</strong> (Heuristic 01). Lastly, I restructured product cards to feel lighter and more readable, embracing <strong>aesthetic and minimalist design</strong> (Heuristic 08).</p><h3>Profile</h3><p>The original profile screen felt more like a settings panel than a personal space. Information was scattered across a long list of subcategories, and it wasn’t immediately clear what related to the user’s profile, selling activity, or preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6tbi-P4MvpLyMJVOHNgdeA.jpeg" /><figcaption>Vinted App Profile page: from before to after !</figcaption></figure><p>I simplified the layout into a <strong>clear, personal dashboard</strong>. By reorganizing the hierarchy, I made sure users could see at a glance what mattered most: their messagees, ongoing sales, sellings and wallet.</p><p>I removed <strong>non-essential features</strong> like badges and grouped related functions more intuitively. This improved <strong>consistency and standards</strong> (Heuristic 04) while giving the interface more “space” (Heuristic 08).</p><h3>Favorites</h3><p>Favorites are a crucial part of the shopping process. They’re where users save inspiration, compare options, and revisit decisions. But in Vinted’s original version, the <strong>favorites page was uncovenient and flat</strong>: a basic list of liked items, without any sorting, tracking, or navigation freedom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Avg5LRWqzltCkfysTky2IQ.jpeg" /><figcaption>Vinted App Favorite page: from before to after !</figcaption></figure><p>To improve this, I introduced <strong>filtering and grouping tools</strong> so users could organize their saved items by category, price, or brand. I also made it possible to <strong>track activity on each item, </strong>like price drops or availability changes, improving <strong>visibility and flexibility</strong> (Heuristics 01 and 07).</p><p>One major pain point I noticed was the <strong>lack of user control</strong>. Users couldn’t easily return to their cart or explore more from the same brand. I solved this by adding <strong>navigation shortcuts</strong> and linking <strong>brand names to their related listings</strong>, giving users the freedom to explore deeper (Heuristic 03).</p><blockquote>A feedback I had during my presentation was interesting on that point, highlighting it can be confusing for users if when clicking on brand name they don’t directly access the product associated ! I think it is a mistake I made, and I would correct it in future work.</blockquote><p>Finally, the result is a <strong>wishlist that works as a smart shopping assistant</strong>, not just a passive archive.</p><h3>Product</h3><p>Product pages are where choices are made, but Vinted’s version is confusing. The layout focused too much on the seller and make the product details appears later on. Prices were often hard to read, and there was no easy way to get more information before purchasing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kxMkVO7MWrXFtNiyXD911Q.jpeg" /><figcaption>Vinted App Favorite page: from before to after !</figcaption></figure><p>I began by refocusing the layout entirely on the <strong>product itself, </strong>bringing price, condition, and description up in the pageflow with <strong>clearer hierarchy and spacing</strong> (Heuristic 08).</p><p>I introduced <strong>expandable sections</strong> for additional info like product details and shipping conditions, to give users control over the depth of content they want (Heuristic 07). A prominent <strong>help link</strong> near the purchase buttons allowed access to support before checkout, solving the gap in user reassurance (Heuristic 10).</p><blockquote>During the presentation, I had a feedback on the icon used that I should replace with a message icon to more explain the “discussion help” with the vendor.</blockquote><p>This redesign turns the product page into a place of <strong>clarity, confidence, informed in decision-making, and with no feeling of any confusion.</strong></p><h3>Finally, a nice exercice that I appreciated but…</h3><p>Redesigning Vinted was both a creative challenge and a personal test. I started with a clear vision of what needed improvement but bringing that vision to life wasn’t easy. <br><strong>Learning Figma while designing</strong> was frustrating at times. I struggled with components and prototyping, and often felt blocked by the tool.</p><p>But through that struggle, I grew. I learned to apply heuristics with purpose, and to make design decisions with confidence, from the best I learnt !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23d3a4840741" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Responsive E-commerce: Working on high-end designers furniture collection !]]></title>
            <link>https://medium.com/@marinebchenais/responsive-e-commerce-working-on-high-end-designers-furniture-collection-e62ea73efc98?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/e62ea73efc98</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Mon, 02 Jun 2025 06:52:58 GMT</pubDate>
            <atom:updated>2025-06-02T06:52:58.059Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Responsive E-commerce: Working on high-end designers furniture collection !</strong></h3><h4>When I learned I’d be working with a real client for the next group project focusing on Responsive E-commerce, I felt excited but also a bit anxious. We had just 8 days to research, design, and deliver a high-fidelity prototype from scratch.</h4><p>Unlike previous projects, this time we had to choose our own client. I immediately thought of <strong>Maugoust Chenais, </strong>a interior architecture agency and designer studio I already knew and admired for their aesthetic sensibility, focus on craftsmanship, and timeless designs. <br>I presented the idea to my teammates. We discussed whether it would be the right fit or was it too niche, too artistic, too far from a typical e-commerce case ?</p><p>But in the end, we all agreed: it was a really exciting challenge to take on !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BO5VZjFlRMo_wgmnMsGY4w.png" /></figure><h3><strong>1. The client interview: insight at the source</strong></h3><p>Early in the project, we had the opportunity to interview <strong>Cécile Chenais</strong>, one of the studio’s co-founders. This moment anchored the entire project. She spoke sincerely about their work, <strong>how every object is designed to last, how perennity in design is a core value, and how each piece carries a unique story.</strong> She also shared a challenge:</p><blockquote>“We have low visibility online. Our current site reflects our architecture work, but not our furniture collection. A dedicated space could really help us reach new audiences.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZF_iz8bcWEE69evibQ-Xyg.jpeg" /><figcaption>Maugoust Chenais business résumé: an overview of their positioning and some elements of their furniture collection</figcaption></figure><h3><strong>2. Discovery &amp; research: understanding the context and the users</strong></h3><p>We went then with secondary research on competitors in the high-end furniture market. This helped us understand existing UX patterns, standards, and gaps.</p><p>Then came the challenge of designing our <strong>survey questionnaire</strong>. It took longer than expected. As a team, it was difficult to agree on the tone, structure, and type of questions. Looking back, our final version wasn’t as precise or deep as it could have been, but we launched it anyway.</p><p>To our surprise, it worked. We gathered <strong>45 survey responses</strong>, and the data gave us real insights. In parallel, we conducted <strong>5 user interviews</strong>. While not every participant was perfectly in target, we identified strong themes across the board:</p><ul><li>People love the idea of owning a designer piece</li><li>But they feel hesitant to buy online, and expect a high level of customer service for high-priced products</li><li>They want detailed, transparent information and emotional connection through storytelling</li><li>They value the designer’s background, the materials used, and customization options</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ASbuRgfGg-hACkJ5F9DVzw.jpeg" /><figcaption><strong>Our primary and secondary researches outcomes</strong> and key insights that led us to define clearly the main points we might focus with our responsive solution for Maugoust Chenais</figcaption></figure><p><em>The data was rich, but defining a clear path forward was not easy. I sometimes felt overwhelmed by the pace of the research, lectures, and Figma all at once…</em></p><h3><strong>3. Turning our data into directions</strong></h3><p>We synthesized our research through an <strong>affinity diagram</strong>, defined key user priorities: <strong>product uniqueness &amp; customization, design storytelling, transparent product information, and customer care</strong> !</p><p>We then created our ideal persona: <strong>Eva Laurent</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_FIAYQUNBeSPlg8rHcMIA.jpeg" /><figcaption><strong>Our persona: Eva Laurent </strong>— we introduce her ID, personality, center of interests and goals when looking for designers furnitures</figcaption></figure><blockquote>Eva is a 38-year-old interior designer, stylish and confident in her taste. She just moved into a new flat with her boyfriend and is looking for a <strong>gift for him</strong> that reflects both their preferences. But she wants more than something beautiful, she wants something <strong>unique, meaningful, and built to last</strong>.</blockquote><p>And yet, her purchasing online experience is a nightmare. She scrolls endlessly. Pages are vague, customization is unclear, delivery options are hidden, and nothing fits her expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3xAVEX2If1ulPzVvTzv_tw.jpeg" /><figcaption><strong>Eva Laurent journey map</strong> when trying to shop designers furnitures online … Not a good experience, that we should learn from, and decipher to avoid the pain points highlighted in our responsive e-commerce solution !</figcaption></figure><p>We mapped Eva’s <strong>user journey</strong> from desire to frustration. This emotional map helped us reframe our <strong>problem statement</strong>:</p><blockquote><strong>“Wealthy design enthusiasts who value creative pieces and often shop online need a way to discover and buy high-end furniture with clear, reliable information about the products and its purchasing conditions because online shopping is often confusing and frustrating.”</strong></blockquote><h4>The question then was: <strong>How can Maugoust Chenais meet these expectations when selling their furniture online?</strong></h4><h4>We designed with this question top of mind!</h4><h3><strong>4. Designing the experience</strong></h3><p>With Eva in mind, we moved into ideation. We ran a brainstorming session and prioritized features using the <strong>MoSCoW method</strong>. We then built our <strong>userflow</strong>, defined the core site sections, and began sketching out <strong>low-fidelity wireframes</strong>.</p><p>The website needed to:</p><ul><li>Provide an overview of the brand and designers’ creative vision</li><li>Give access to the furniture collection catalogue</li><li>Offer detailed product information with customization options</li></ul><p>We created a <strong>5-step userflow</strong> to lead customers through a short, clear, and reassuring online buying process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-pLXDyc074lgwWOJ8ruWmg.jpeg" /><figcaption><strong>The MVP &amp; Userflow</strong> defined for Maugoust Chenais website</figcaption></figure><p><em>Then came the hard part: </em><strong><em>Figma</em></strong><em>. As someone still learning the tool, I found it incredibly challenging to start prototyping. I often felt behind and had to ask for help frequently. But I also learned a lot. Every component, frame, and spacing decision was a small victory. I’m still practicing and improving … Figma remains one of my biggest personal challenge, but this project gave me a solid start.</em></p><p>We drafted our low-fidelity wireframes and ran <strong>concept testing</strong>, which gave us helpful feedback for our <strong>mid-fidelity versions</strong>. From there, we realized our solution needed to be really sharp in both content and aesthetics to match the brand’s high-end positioning and we conducted <strong>usability testing</strong> throughout:</p><h4>At the same time, we worked on branding. We asked: <em>How do we visually translate Maugoust Chenais’ identity?</em></h4><p>We defined five brand attributes that became the backbone of our UI decisions: <strong>Creativity, Craftsmanship, Uniqueness, High-end/Premium, Transparency.</strong></p><p>We designed a moodboard, selected a <strong>color palette</strong> and <strong>typefaces</strong>. This step felt grounding it gave us direction and allowed us to align UX structure with visual identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g0KGpHgVhzxRHjUOvEk9GQ.jpeg" /><figcaption><strong>Maugoust Chenais brand universe</strong> including their identity and graphic chart with brand values: Creative, High-End, Materiality, Craftmanship, Uniqueness</figcaption></figure><h3><strong>5. The high-fidelity solution</strong></h3><p>We delivered a <strong>desktop-priority responsive e-commerce prototype</strong>, built around the needs of users like Eva. Here the link to consult</p><p><a href="https://www.figma.com/proto/XDXDmEyvxx8WRoXc5Tkq3W/--P2-Team-4---Design?node-id=3682-558&amp;p=f&amp;t=S8Kf30f7vNJzyaQn-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;page-id=3682%3A557&amp;starting-point-node-id=3682%3A558">https://www.figma.com/proto/XDXDmEyvxx8WRoXc5Tkq3W/--P2-Team-4---Design?node-id=3682-558&amp;p=f&amp;t=S8Kf30f7vNJzyaQn-1&amp;scaling=scale-down&amp;content-scaling=fixed&amp;page-id=3682%3A557&amp;starting-point-node-id=3682%3A558</a></p><h3><strong>Site architecture</strong></h3><p>We created a clear, elegant sitemap including:</p><ul><li>A <strong>homepage</strong> with designer vision and furniture catalogue</li><li><strong>Product pages</strong> with customization and detailed information</li><li><strong>Cart, payment, delivery, and order confirmation pages</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*v0CAWeBPh6VIVbBQJ9oCPw.png" /><figcaption><strong>Maugoust Chenais Homepage</strong> website with designer presentation and new collection products</figcaption></figure><h3><strong>Product page design</strong></h3><p>Each product page was structured to build trust and engagement:</p><ul><li>Full-bleed imagery with zoom</li><li>Customization options (finishes, fabrics)</li><li>Detailed material and production info</li><li>Transparent return policy, no hidden terms</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*4fgzEu8TjqZfgLH5lE7xFg.png" /><figcaption><strong>Maugoust Chenais product page</strong> with clear description of the product and customization options. We include drop down menus to get more detail about the product or the shipping conditions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*4_EE5v5_iz4Pprx8ngtUJg.png" /><figcaption><strong>Maugoust Chenais delivery page </strong>with delivery information forms and delivery options including additional fees</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/503/1*Vqo6T-fFgcNrU8EByIUeNw.png" /><figcaption><strong>Maugoust Chenais payment page </strong>with summary of the purchase and payment options</figcaption></figure><h3><strong>6. Final presentation &amp; feedbacks</strong></h3><p>Our final presentation was well received, the narrative was clear, the solution felt aligned with the brand, and the research grounded our design decisions.</p><p>Some areas for improvement:</p><ul><li>Include a mobile wireframes</li><li>Add a payment info screen to complete the flow</li><li>Show browser UI in desktop mockups</li></ul><p>But overall, we were proud of the outcome.</p><p><strong>What I learned about the project:</strong></p><ul><li>Identifying key outcomes from secondary research helped us define and drive the project objectives</li><li>A well-built <strong>persona and journey map</strong> helped us a lot to go quick at each design step</li><li>More concept and usability testing would have further improved our design</li></ul><p><strong>What I learned about teamwork:</strong></p><ul><li>Following a <strong>Notion roadmap</strong> and working step-by-step helped keep things on track</li><li><strong>Dividing</strong> tasks clearly helped us manage time and reduce stress</li><li><strong>Too much discussion </strong>can lead to delays, sometimes we should had to stop debating and <em>move forward</em></li><li><strong>Don’t overcomplicate</strong>: “The best is the enemy of the good” !</li></ul><h3>This was a great project. I really enjoyed it, and I <strong>definitely learned a lot</strong> from it!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e62ea73efc98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wicked Problem — Culture & Heritage: My First UX Case Study at Ironhack]]></title>
            <link>https://medium.com/@marinebchenais/wicked-problem-culture-heritage-my-first-ux-case-study-at-ironhack-c01df6accc07?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/c01df6accc07</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Sun, 18 May 2025 17:11:40 GMT</pubDate>
            <atom:updated>2025-05-18T17:16:42.188Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Wicked Problem — Culture &amp; Heritage: UX Case Study at Ironhack</strong></h3><h4>During my UX/UI bootcamp at Ironhack, we started the course with a first case from the second day: a week-long team sprint on the topic of Culture &amp; Heritage.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*CeqARZ7CHea2tpLho9SD5Q.png" /></figure><p><strong>The brief was open-ended, and our goal was to uncover real user needs related to accessing and experiencing cultural heritage, and then design a meaningful solution in under 7 days.</strong></p><p><em>It was an intense &amp; collaborative first challenge, and I have made it with an incredible team that I had a lot of pleasure to work with, big up Ana, Donna &amp; Thuy 💛!</em></p><p>The problem we had was pretty challenging: <strong><em>how might we help people reconnect with cultural heritage in modern, accessible ways?</em> </strong><br>In a world increasingly shaped by screens, speed, and short attention spans, culture often feels distant, formal, or outdated. We wanted to explore this tension and understand:</p><ul><li>What makes people feel connected (or disconnected) from cultural heritage?</li><li>What prevents them from exploring it more often?</li><li>How could technology actually enhance cultural engagement, without replacing the essence of it?</li></ul><p><strong>The objective was to define a solution following several UX research steps from Secondary research to wireframe testing: each step discovered day after day during the class! </strong><br>Finally, we entitled our team project <strong>GoMuse</strong>, a mobile app to help people discover cultural activities spontaneously, based on time, mood, and curiosity. But getting there? That was a journey in itself !</p><blockquote><strong><em>How we did to succeed in our project: all about teamwork!</em></strong> <br><em>It’s important to point out that we always worked as a solid team, that was our method along all way! <br>Even though some of the steps were made individually, we brainstormed, we voted and we made every decision together!</em></blockquote><h3><strong>Step 1: Research, Interviews &amp; Affinity Mapping</strong></h3><p>We kicked off the week with theory course in Agile methodologies like Scrum and Kanban. That same day, we jumped straight into user research. No time to overthink, just dive in.<br>To start, we first go on secondary research and working with <strong>1 method</strong>:</p><ul><li>Search by our side, get insights</li><li>Share !!!</li><li>Discuss and select best options all together</li><li>Build a common version</li></ul><p>Seconde step was to built an interview guide collaboratively and split tasks to conduct both group and individual user interviews. <strong>We’ve done 6 interviews</strong> with other student of the course and then additional people from or personal environnement. <br><em>The biggest challenge was agreeing on the right questions in a short amount of time, while ensuring it would enable us to get meaningful answers.</em></p><p>Then, all was about making sense of our data. We learned how <strong>to</strong> <strong>create affinity diagrams grouping raw interview insights by theme</strong> and used dot voting to prioritize the most relevant problems.<br><em>I was surprised of how quickly we had to move from theory to action. Within hours of learning how to conduct interviews, I was already applying those techniques in real conversations.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6Vx6PJgUuHvA1rmIP2nLw.png" /><figcaption>Affinity diagram</figcaption></figure><p>What stood out was the balance between logic and intuition. Clustering ideas felt a bit chaotic at first, but slowly, patterns started to emerge. <br><strong><em>We then identify that we were looking for a solution that would be personalized, providing an experience, and that would be digital and interactive in its usage.</em></strong></p><h3><strong>Step 2: Personas &amp; User Journey Map</strong></h3><p>Once we had enough insights, we moved into persona creation. I personally created one of our team’s personas and presented it to the group and she was finally part of our common persona : Ilona Live ! <br><em>It helped us narrow our focus to one central user with real struggles someone curious about local culture, but unsure where or how to engage with it meaningfully.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bz_bJ8rE4-DGzIwU0jViHQ.png" /><figcaption>Ilona Live Persona</figcaption></figure><p>From there, we built a User Journey Map (UJM), identifying key frustrations, emotions, and opportunities along their cultural experience. Our goal was to add emotional depth to the journey — not just a logical flow, but one that felt human and relatable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sNBlSrZBs07w24jmeMKKXw.png" /><figcaption>User Journey Map</figcaption></figure><p><em>What we wrestled with was making the journey emotional and consistent as a team. Everyone had different ideas about tone, storytelling, and what parts of the experience to dramatize. Using timers really helped avoid endless debates and keep us moving forward.</em></p><h3><strong>Step 3: Problem Statement, MVP &amp; User Flows</strong></h3><p>This was one of the most “delicate days” of the sprint.We began with a Problem Statement, then used tools like Crazy 8’s and MoSCoW prioritization to brainstorm and structure our ideas. By the end of the day, we had agreed on:</p><ul><li>A clear Problem Statement</li><li>A list of must-have features for our product</li><li>A rough Minimum Viable Product (MVP)</li><li>And our first global user flow</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K3xFzdJLWHbXT4-8ILI1Wg.png" /><figcaption>Moscow Method</figcaption></figure><p><em>Writing the problem statement was more difficult than expected. Finding the right words to capture both the user’s need and the design opportunity was a real exercise in clarity.</em></p><h3><strong>Step 4: Wireframes, Concept Testing &amp; Presentation Mode</strong></h3><p>Time to bring everything more real. We learned how to sketch out wireframes, created our first digital layouts, and even tested the concept internally. <br>We succeeded in drafting first low-fidelity wireframes, and design a global low-fid consolidated wireframe made from parts of each of our personal drafts. <br>Then we’ve bee throught a mid-fi wireframe and we could done testing with feedbacks three time with some classmates ! We appreciated their feedbacks, great way to improve our solution in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0nqzZIezmGK7sRS9bGhRFQ.png" /><figcaption>Testing our wireframes</figcaption></figure><p>Meanwhile, we started assembling our final presentation deck not an easy task when everyone is tired and racing against the clock !</p><p><em>I learned managing time between user flows, design, testing, and storytelling is a real challenge. We had so much material, but limited time to refine it all. Still, we found a balance and built a story we all felt confortable with.</em></p><h3><strong>Final Day: Presenting our project GoMuse</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vo-1hEsXPOqcFIxWe8lt_A.png" /></figure><p>On the last day, we finalized our pitch, divided speaking roles, and presented our project to Neil, our Ironhack teacher and other teams. <br><strong>We find out the name of our solution “GoMuse” really easily, and we were pleased to present our final wireframes!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1JmjfMHlNGdv9acqVRPeQ.png" /></figure><p>We knew our concept wasn’t perfect, but it was real, and it reflected days of collaborative work, honest feedback, and creative compromise. The presentation came together really nice, and I genuinely enjoyed seeing how our collective vision had evolved.</p><h3>In the end …</h3><p>This first UX challenge taught me:</p><ul><li>How to listen deeply to users</li><li>How to co-create with a team under time pressure</li><li>How to bring clarity from uncertainty through structure, tools, and iteration</li></ul><p><strong><em>But more than anything, it reminded me why I chose UX in the first place: to design with empathy, purpose, and a touch of storytelling. <br>I enjoyed this first challenge, and definitely doing it with my teammates 🙂 !</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c01df6accc07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Pre-work Challenge 2 : Wireframing]]></title>
            <link>https://medium.com/@marinebchenais/ironhack-pre-work-challenge-2-wireframing-7f410519b1c9?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f410519b1c9</guid>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 11:25:50 GMT</pubDate>
            <atom:updated>2025-04-24T11:27:26.060Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Pre-work Challenge 2 : Wireframing</h3><h4>As part of my UX/UI design training, and for the exercise of creating a wireframe, I chose to work on an app that I use and genuinely appreciate: <strong>Vestiaire Collective</strong>.</h4><p><strong>Vestiaire Collective</strong> is a second-hand sales platform specializing in fashion. The Vestiaire Collective app is a very intuitive platform where users can search for and purchase unique second-hand pieces from various sellers around the world. It is often difficult to find second-hand items that are both high-quality and available from resellers located globally. Other apps exist, but are far less fluid in their user experience and interface design (such as Vinted or Amazon).</p><p>The Vestiaire Collective app offers a selection and authentication system that ensures the origin and quality of items. I therefore chose to analyze this app and create wireframes of the <strong>purchase journey</strong>, which I find simple and highly accessible.</p><p>The app is structured in a very intuitive way with a straightforward user journey, including the following elements:</p><ul><li>Global design: minimalist and premium style, using white, black, grey, and green or coral accents; sans serif font; clear typographic hierarchy</li><li>Navigation: bottom bar with icons (home, search, sell, favorites, profile), clear side menu with categories and filters</li><li>Product selection: large image including brand, title, price, and “authenticated” badge</li><li>UI flow: well-structured grid, smooth layout, thin uniform icons, clear filters (checkboxes, sliders, labels)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OkVMVacVPQFEQZLAus33cw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4PMsegVFws-bfnKFtJGw7Q.png" /><figcaption>Vestiaire collective application</figcaption></figure><p>I analyzed this task and broke down the flow as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQBj9ZjrIztWHQwXZHyF5A.png" /></figure><p><a href="https://www.figma.com/proto/XVAFtp0bRTYmPu0ZqthmkH/VESTIAIRE-COLLECTIVE?page-id=6%3A342&amp;node-id=6-343&amp;p=f&amp;viewport=101%2C-363%2C0.55&amp;t=nwL2MgnkgvVmy6ol-1&amp;scaling=min-zoom&amp;content-scaling=fixed"><strong>Here is my wireframe prototype:</strong></a></p><p>First, I tap on the search button in the top navigation bar or select a product category from the suggested “carousel.”<br>I find the product I’m looking for and select it. <br>I access the product page with all available details, including information on the seller and product authentication. <br>I add the product to my <strong>cart</strong>, access delivery options with a price breakdown, and choose my preferred payment method. <br>I then get a summary of the total order amount including delivery fees. <br>I can proceed to payment using the selected method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Adx19nFxhrYVh-aFH8tDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M72rLbeaV7Bpnc3R3uPdMQ.png" /></figure><p>I first listed the <strong>user interface components</strong> to help me build the wireframe faster and more consistently.<br> This challenge helped me understand how users navigate an app’s content and the importance of simplifying the user journey as much as possible while staying efficient in how key information is accessed, step by step.</p><p>I’ve come to understand the importance of having an <strong>analytical approach</strong> to interface structure before moving into design! Looking forward to creating even more exciting projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f410519b1c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Challenge 1 Design Thinking]]></title>
            <link>https://medium.com/@marinebchenais/ironhacks-prework-challenge-1-design-thinking-2291ba40e40c?source=rss-65fe2bf6adda------2</link>
            <guid isPermaLink="false">https://medium.com/p/2291ba40e40c</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Marine BChenais]]></dc:creator>
            <pubDate>Wed, 16 Apr 2025 13:15:51 GMT</pubDate>
            <atom:updated>2025-04-17T09:47:47.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*zVHahVfhxNK3s01bapCRXQ.png" /></figure><h3><strong>INTRODUCTION TO PROJECT OBJECTIVE</strong></h3><p>I grew up in Paris and have been using public transport since my teenage years. Over the years, I’ve witnessed the growing number of innovative mobility solutions designed to reduce congestion in the city. <br> Getting around Paris remains tricky — it feels large yet is densely populated, especially within the inner city.</p><p>• In 2022, <strong>52% of trips in Paris were made on foot, </strong>32% via public transport, 10% by car, and 5% by two-wheelers.<br> <strong>On average, Parisians spend over 92 minutes a day on public transport.</strong></p><p>• The metro remains the most reliable option for avoiding delays: <strong>97.9% of trains are on time or within 5 minutes of schedule.</strong></p><p>Today, the transportation offer in Paris ranges from <strong>the simplest (walking), to the fastest (metro), and includes eco-friendly or personal solutions such as bikes, scooters, taxis, and private vehicles.</strong></p><p>CityMapper is currently the most effective app for evaluating transport options based on location, modes available, and estimated travel time.<br> While it offers an optimized navigation experience, <strong>the app lacks a centralized payment solution</strong> — users are redirected to individual transport providers to buy tickets, which often means multiple purchases for a single journey.<br> <strong>There is no all-in-one solution that connects route selection to ticket purchase.</strong></p><p><em>How can a user choose the most efficient mode of transport depending on their destination, context, and desired experience?<br> <br> </em>A Parisian commuter rushing to work at 8 a.m. won’t have the same needs as a tourist, a provincial visitor, or a retired person with more time flexibility. <br>CityMapper competes with Google Maps, Moovit, and partially integrated platforms such as RATP Paris or TFL in London, as well as ride-hailing apps and aggregators.</p><h3><strong><em>STEP 1: EMPATHIZE — LEARN ABOUT THE AUDIENCE</em></strong></h3><p>The goal is to create a seamless in-app solution to purchase all necessary transport tickets without redirection, and in the <strong>most intuitive, simplified way possible</strong>, especially for multimodal journeys requiring different tickets.</p><p>I conducted 5 interviews with different CityMapper users profiles:</p><ul><li><strong>Marie</strong>, 33, Parisian, daily commuter for 15 years within Paris</li><li><strong>Christophe</strong>, 65, retired, lives in Vanves, uses transport for daytime cultural outings or family visits</li><li><strong>Isabelle</strong>, 58, lives in the provinces, comes to Paris a few times a year to visit family or explore the city</li><li><strong>Julia</strong>, 32, lives in Barcelona, visits Paris occasionally for work or to see friends</li><li><strong>Louis</strong>, 30, Paris-based, rarely uses public transport unless absolutely necessary — mostly travels by car or scooter</li></ul><h3><strong>Interview questionnaire:</strong></h3><ul><li>What types of transport do you usually use? (metro, bus, RER, tram, bike, scooter, train, etc…)</li><li>Do your trips often involve multiple transport modes?</li><li>How do you currently buy your transport tickets? Do you find it practical? Why?</li><li>Do you ever need to use multiple channels to buy different tickets for a single journey? Is this a problem for you?</li><li>Have you ever missed a train or wasted time due to a ticketing or payment issue?</li><li>Would you like to centralize all ticket purchases in one app? Why?</li><li>Have you used any app or system that lets you buy a single ticket for a whole trip?</li></ul><h3><strong>STEP 2: DEFINE — CREATE A POINT OF VIEW BASED ON INSIGHTS</strong></h3><h3>• <strong>INSIGHTS</strong></h3><p><strong>Marine:</strong> Frustrated by switching between Navigo, SNCF App, and ticket machines. Wants an “all-in-one” feature, especially for trips beyond her usual zone.</p><p><strong>Christophe:</strong> Prefers buying tickets at counters or kiosks. Finds multi-modal trips (RER + metro + bus) confusing if he has to buy several tickets. Would use a pass if it’s simple and well-explained.</p><p><strong>Isabelle:</strong> Finds the ticketing system unclear, especially when multiple transport types are involved. Often needs help choosing the right ticket. Would feel reassured by an all-in-one purchase option, provided there’s no extra cost.</p><p><strong>Julia:</strong> Loves the app, but in Paris, she’s unsure which ticket to buy or where. Has missed transport because she didn’t understand the Navigo/T+ system. Fully supports an integrated solution, especially with international card support.</p><p><strong>Louis:</strong> Not comfortable with ticketing systems and doesn’t have a transport pass. Wants a fast and effortless experience: “Click, pay, done.” Would adopt the feature if it’s smooth, with no extra sign-ups.</p><h3>• <strong>DEFINE</strong></h3><p>A built-in payment system within CityMapper is a <strong>clear user expectation</strong>, based on key needs:</p><ul><li>Simplify multi-ticket purchases with <strong>as few steps as possible</strong></li><li>Regular users with subscriptions still encounter <strong>non-routine cases</strong> requiring flexible ticketing</li><li><strong>Less tech-savvy users</strong> need guidance and a simple, low-friction system</li><li><strong>Occasional users</strong> lack context and benefit from a <strong>turnkey, stress-free solution</strong></li><li><strong>International visitors</strong> want a <strong>unified, intuitive, and instant process</strong>, without navigating local complexity</li><li>Users who rarely use public transport may <strong>avoid it altogether if the experience feels too complex</strong> — they prefer an on-demand pass, easy to activate with no setup</li></ul><h3><strong>STEP 3: IDEATE — BRAINSTORM CREATIVE SOLUTIONS</strong></h3><p>I explored several options based on critical experience touchpoints:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IUj-UiUVBRxnuCMNIfIaCQ.png" /></figure><p><strong>Option 1: CityMapper Ticket</strong></p><ul><li>A <strong>smart ticket</strong> automatically generated per journey</li><li>After route selection, a new button appears: “Buy tickets”</li><li>User confirms with <strong>one click</strong> (payment info pre-saved)</li><li>A <strong>QR code/pass</strong> is generated for the full multimodal route</li><li>Stored in the “My Journeys” section and available offline</li></ul><p><strong>Option 2: CityMapper Pass</strong></p><ul><li>A <strong>personalized pass</strong> with a <strong>rechargeable wallet</strong></li><li>User profile has an option: “Recharge my pass”</li><li>A unique <strong>QR code</strong> is generated, valid across all transport, depending on available balance</li><li>User <strong>confirms balance</strong> or recharges instantly with saved details</li><li>Upon route selection, a button appears: “Use my Citymapper Pass for this trip”</li><li>The pass integrates the full route and all tickets into a single <strong>dynamic QR code</strong></li></ul><h3><strong>STEP 4: PROTOTYPE — REPRESENT THE BEST OPTION</strong></h3><p>The <strong>simplest and most versatile solution</strong> based on all user needs is “<strong>CityMapper Ticket”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*3b6CxySFLxQOAAc7p5N5uQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*Gq3dVAweZ9GbdV2kOeQD4g.png" /></figure><h3><strong>KEY TAKEAWAYS FROM THIS EXERCISE</strong></h3><p>This challenge allowed me to experience the <strong>full Design Thinking process</strong>. I particularly enjoyed crafting a targeted questionnaire and collecting <strong>actionable insights</strong> to guide solution development.</p><p>The ideation phase helped <strong>broaden the solution space</strong> creatively based on user pain points — it felt like a treasure hunt with multiple right answers.<br> This creative process is a core strength of Design Thinking.</p><p>Prototyping was straightforward thanks to the previous steps. It served as a <strong>visual synthesis of key insights</strong>.<br> Each phase built naturally on the previous one, showing the value of structuring and aligning with user needs at every stage.</p><p>Ready to do more !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2291ba40e40c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>