<?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 Maddy Eagle on Medium]]></title>
        <description><![CDATA[Stories by Maddy Eagle on Medium]]></description>
        <link>https://medium.com/@meagle97?source=rss-69bdd57dae4f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FRrX_Cxpkz_huWmYXMCaxg.jpeg</url>
            <title>Stories by Maddy Eagle on Medium</title>
            <link>https://medium.com/@meagle97?source=rss-69bdd57dae4f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:17:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@meagle97/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Case Study: Remotionist — Empowering Creators to Connect, Share, and Grow]]></title>
            <link>https://medium.com/@meagle97/case-study-remotionist-empowering-creators-to-connect-share-and-grow-8e7651db5eb8?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e7651db5eb8</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-bootcamp]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Fri, 10 Oct 2025 22:40:57 GMT</pubDate>
            <atom:updated>2025-10-10T22:40:57.426Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study: Remotionist — Empowering Creators to Connect, Share, and Grow</h3><p>Designing a platform that supports mentorship and collaboration in the creator economy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FWQtKu7tGl91DiYizql7SQ.png" /></figure><h3>The Spark</h3><p>If you’ve ever fallen down a YouTube or TikTok rabbit hole, you’ve probably noticed how much the creator world has changed. Creators aren’t just entertainers anymore — they’re educators, mentors, and business owners all rolled into one. But as the creator economy continues to grow, so does one big challenge: <strong>where can creators actually connect, learn from one another, and make their time and knowledge sustainable?</strong></p><p>That’s where <strong>Remotionist</strong> was born — a concept for an MVP platform designed to bring together established and aspiring creators on one single space. Our mission was simple (but definitely not easy): to create a digital space that empowers creators to connect with mentors, learn, and monetize their expertise, without needing to juggle ten different platforms.</p><p>This was my <strong>final project at Ironhack</strong>, and also one of my favorites — equal parts challenging, creative, and deeply rewarding.</p><h3>The Brief</h3><p>Remotionist is a <strong>Hamburg-based startup</strong> with the vision of connecting young professionals and creators with mentors to accelerate their careers. Initially, the founder envisioned a space focused on content creators, but she was open to exploring other potential audiences depending on our research.</p><ul><li><strong>Objective: </strong>To validate the Remotionist concept, define the target audience, and design a responsive MVP prototype that demonstrates a key user flow connecting creators and mentors.</li><li><strong>Timeline:</strong> 2 weeks</li><li><strong>Tools:</strong> Figma, Trello, Notion, Google Forms, and ChatGPT</li><li><strong>Team:</strong> 2 designers — <a href="https://medium.com/u/b6b6db7b599e">Niamh AC</a> &amp; myself</li><li><strong>Roles:</strong> UX researcher, UX/UI designer</li><li><strong>Deliverables:</strong> Research insights, user survey, user interviews, user persona, user journey, user flows, mid-fidelity wireframes, high-fidelity</li><li>prototype, and usability testing.</li></ul><h3>Digging Deeper</h3><p>Before we could design anything meaningful, we needed to understand the world of creators: their challenges, motivations, and goals.</p><h4>Research &amp; Insights</h4><p>We kicked things off with a <strong>Lean UX Canvas</strong>, which helped us narrow down the business goals and identify our biggest unknowns:</p><ul><li>Do young people actively seek mentorship for unconventional careers?</li><li>Is the creator market large and sustainable enough?</li><li>Can mentorship actually influence career growth for creators?</li></ul><h4>Competitor Analysis &amp; Market Research</h4><p>Our competitor research spanned platforms like <strong>ADP List, MentorCruise, and Skillshare</strong>, which are great for professional mentorship, but they often weren&#39;t fitting the creator space. Creators need flexibility, personality, and relatability, not corporate polish.</p><p>We also looked at how the creator economy itself is evolving — a $480B industry by 2030 (according to Business Insider). That stat alone showed us that building for creators isn’t just a passion project; it’s an opportunity.</p><h4>Surveys &amp; Interviews</h4><p>To understand the real people behind the content, we created an online survey that reached 30 respondents and followed up with 1:1 interviews.</p><p>Here’s what stood out most:</p><ul><li>Established creators want to share their expertise but struggle to find time or ways to monetize it.</li><li>Aspiring creators value authentic mentorship but worry about cost and compatibility.</li><li>Everyone feels fragmented between multiple tools and platforms.</li></ul><p>From the survey responses, a few statistics stood out:</p><ul><li><strong>100%</strong> of creators got their start <strong>self-taught</strong>, with <strong>21%</strong> also using online courses.</li><li><strong>73%</strong> of creators said they would consider mentoring others, but only <strong>26%</strong> would do it for free.</li><li>The biggest challenges identified were <strong>time commitment (95%)</strong> and <strong>balancing mentoring with their own work (68%)</strong>.</li></ul><p>We visualised these insights with an <strong>affinity diagram</strong>, helping us organise feedback into themes: time, monetisation, accessibility, and trust.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zI1tndReAUK18hnr-QeDJw.png" /></figure><h3>Defining the Path Forward</h3><p>With research insights in hand, the next step was to define the problem clearly and understand the people we were designing for.</p><h4>User Persona &amp; Journey Map</h4><p>After synthesizing our findings, we crafted our <strong>primary user persona</strong>, <em>Mia Morita</em> — an experienced creator who loves sharing knowledge but struggles to balance her workload with mentoring others. We decided to focus on the current creator and mentor perspective due to time constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sN2CEmmflGznCZg8-hc7A.png" /></figure><p>Her <strong>user journey</strong> highlighted critical touchpoints and frustrations, from discovering mentorship opportunities to providing guidance. This journey, along with several “<strong>How Might We” statements</strong>, helped define <strong>pain points</strong>, including:</p><ul><li>Time management for mentoring tasks</li><li>Monetizing expertise efficiently</li><li>Accessibility and trust when engaging with mentees</li></ul><h4>Problem Statement</h4><p>Mia helped us visualize our main challenge: how might we make mentorship <strong>efficient, affordable, and rewarding</strong> for both sides? This allowed us to form our consolidated problem statement:</p><blockquote><em>“Full-time content creators seeking </em><strong><em>sustainability and growth</em></strong><em> in their career need to find a way to </em><strong><em>monetize their time </em></strong><em>while addressing the common and individual </em><strong><em>needs of their community</em></strong><em> through sharing their </em><strong><em>existing content</em></strong><em>, answers to </em><strong><em>frequently asked questions</em></strong><em>, and </em><strong><em>1:1 guidance, </em></strong><em>as they often spend excessive time addressing repetitive questions and currently, there are no </em><strong><em>affordable and consolidated</em></strong><em> platforms available, causing difficulty managing multiple revenue streams.”</em></blockquote><h3>From Insights to Action</h3><p>With the problem defined, we began generating solutions.</p><h4>Ideation</h4><p>From the research and problem framing, we defined an <strong>MVP</strong>:</p><blockquote>At a bare minimum our product should allow users to customize their profile based on their expertise and credentials, link existing content from other platforms, answer questions, manage their displayed calendar and host 1:1 sessions, receive payments, and search &amp; filter for other users.</blockquote><p>We explored user interactions through <strong>user flows</strong>, defining users as either:</p><ul><li><strong>Explorers:</strong> Aspiring creators discovering content, learning via FAQs, Q&amp;A, and 1:1 sessions.</li><li><strong>Creators:</strong> Industry experts consolidating content, managing their community, and hosting 1:1 sessions.</li></ul><p>Rapid ideation techniques and the <strong>MoSCoW method</strong> helped prioritize features for technical feasibility and business viability.</p><h4>User Flows</h4><p>To make our ideas tangible and ensure the platform supported real user needs, we mapped <strong>key user flows</strong> for both Explorers and Creators. Below our user flows capture these core paths, highlighting the critical touchpoints that informed both the structure and design of our platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tPWKblNKXrUuA7y80KNkQ.png" /></figure><h4>Sitemap</h4><p>Once the user flows were defined, we built a <strong>sitemap</strong> to visualise how all the pages and features would connect. This helped us confirm that each user — whether exploring mentors or managing sessions — could <strong>navigate the platform intuitively</strong> and always know where they were in the journey.</p><p>The sitemap also clarified our content hierarchy early on, ensuring we designed each screen with purpose before moving into wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBs20nDVQ5NZQG3aknJ1JQ.png" /></figure><h4>Mid-Fidelity Wireframes</h4><p>With a clear structure in place, we moved into <strong>mid-fidelity wireframing</strong> to bring our sitemap to life.</p><p>This stage focused on <strong>layout, hierarchy, and usability</strong> — making sure to get our wireframes right before visual design entered the picture. We kept things in grayscale to stay focused on how users would navigate, interact, and achieve their goals without the distraction of color or branding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HvWhp5Ctyt-wfUfYzDi9_Q.png" /></figure><h4>Testing</h4><p>Usability testing of the mid-fidelity prototype led to the following improvements:</p><ul><li>Simplifying search filters for clarity</li><li>Enhancing homepage onboarding steps</li><li>Elevating primary actions visually</li><li>Highlighting Terms &amp; Conditions and trust signals during payment flows</li></ul><p>These iterations resulted in a more intuitive, accessible platform.</p><h3>Bringing Ideas to Life</h3><p>Once we had a clear direction, we translated our ideas into tangible designs.</p><h4>Visual Design</h4><p>We explored visual branding to differentiate Remotionist from corporate-style competitors. Our approach:</p><ul><li><strong>Brand attributes:</strong> Bold, playful, trendy, inclusive</li><li><strong>Typography:</strong> Climate Crisis for headlines, Poppins for body text</li><li><strong>Color palette:</strong> Vibrant warm tones with neutral support for hierarchy and creator focus</li><li><strong>Components &amp; UI Kit:</strong> Supporting clear content hierarchy while keeping the platform fun and creative</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6L_IzKgC0N-6eBeqhCg31A.png" /></figure><h4>High-Fidelity Prototype</h4><p>The desktop prototype demonstrates a complete Explorer workflow:</p><ol><li>Searching for a mentor in photography/video editing</li><li>Booking a 1:1 session</li><li>Managing bookings through the profile page</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2FFKR3p7E3GTm6l3whKbCkpq%2FRemotionist_DesignFile_-SHARED-%3Fpage-id%3D116%253A10%26node-id%3D6197-892%26viewport%3D697%252C-886%252C0.08%26t%3DCW9gYRPOKOgeBfzm-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D6197%253A892&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FFKR3p7E3GTm6l3whKbCkpq%2FRemotionist_DesignFile_-SHARED-%3Fpage-id%3D116%253A10%26node-id%3D6197-892%26viewport%3D697%252C-886%252C0.08%26t%3DCW9gYRPOKOgeBfzm-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D6197%253A892" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/dddf9c260a98c04fbb7fd5ded56c8797/href">https://medium.com/media/dddf9c260a98c04fbb7fd5ded56c8797/href</a></iframe><p>Key design elements:</p><ul><li>Clear onboarding and progression steps</li><li>Creator credibility and expertise highlighted on profile cards</li><li>Transparent payment and booking flow</li><li>Easy navigation between Content, FAQ, and Booking tabs</li></ul><h3>Summary &amp; Future Considerations</h3><p>Remotionist centralises content, community interaction, and revenue management for creators, while helping aspiring creators discover and learn from experts.</p><p>Potential future improvements:</p><ul><li>Video call and chat integration for 1:1 mentoring</li><li>Flexible payment options</li><li>Fully responsive mobile design</li><li>Creator verification and extended trust messaging</li></ul><p>The project reinforced the importance of <strong>early-stage research</strong> in building a platform that truly addresses user needs, rather than jumping straight into UI and branding.</p><h4>Final Reflections</h4><p>This project was one of those special ones that changes how you see design — and yourself as a designer. From the very start, it pushed me to lean into <strong>research, empathy, and real human insight</strong>, shaping how I now approach every problem I design for. The research-heavy nature of Remotionist didn’t just teach me new methods, it deepened my passion for understanding people and translating their needs into meaningful, user-centered experiences.</p><p>I also couldn’t have asked for a better teammate than <strong>Niamh (</strong><a href="https://medium.com/u/b6b6db7b599e"><strong>Niamh AC</strong></a><strong>)</strong>. She’s someone I deeply admire: a designer, collaborator, and mentor all in one. Her support, guidance, and generosity throughout this and other projects have left a huge mark on how I work and think. I’m genuinely grateful for everything I’ve learned from her.</p><p>At the time of writing, the <strong>Remotionist founder is still exploring the next steps</strong> for bringing the concept to life. If the opportunity arises to collaborate again in the future, I’d be honored to help carry this vision forward and continue creating something that empowers and connects creators worldwide.</p><p>At the heart of my process, and every design I create, is empathy. It’s what drives my curiosity, shapes my decisions, and reminds me why I love doing this work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e7651db5eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Nurturing Growth — Creating a Child Development Tracking App]]></title>
            <link>https://medium.com/design-bootcamp/case-study-nurturing-growth-creating-a-child-development-tracking-app-96421562332f?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/96421562332f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[application-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[child-development]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Mon, 05 Aug 2024 17:14:33 GMT</pubDate>
            <atom:updated>2024-08-06T11:59:03.986Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study: Nurturing Growth — Creating a Child Development Tracking App</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lh6b--5BurhyxpHW_2QsGQ.jpeg" /></figure><p>Parenting isn’t a walk in the park, especially when you’re juggling busy schedules and the rapid growth of your little ones. From the “Terrible Twos” with their infamous tantrums to the whirlwind of milestones that seem to happen overnight, children grow and change in the blink of an eye.</p><p>While parenting is one of the most natural and universal experiences, it often leaves parents feeling stressed, anxious, and completely exhausted. In a world where life moves fast, how can parents possibly keep up with everything on their own?</p><p>The solution: our child development tracking app — an application designed to bring peace of mind and support to diligent parents navigating the beautiful chaos of raising children.</p><h3>Project Overview</h3><p>Project 4 in the IronHack Bootcamp was to create a wellness mobile application that would help users to track an aspect of their health/wellbeing. My partner, <a href="https://medium.com/@arozhkova84">Anastasia</a> and I began discussing topics for us to focus our project on. We began by agreeing that a journal or tracking application would be great to start. However, the decision to focus on a child development app was not easily made.</p><h4>The First Challenge</h4><p>We started by discussing mental health, mindfulness, daily journals, and sleep journals, but we were not feeling inspired. In fact, we were feeling quite stuck. This is when I started to worry, as staying on track and on time is something that I value a lot. However, I also wanted to make sure that we were choosing a topic that we wanted to commit to, and that users would find valuable and accessible.</p><p>After many competitive analysis and a talk with our teacher, we discovered something that seemed to stick with us, and that wasn’t as heavily saturated in the mobile application market as mental health and mindfulness journaling. Therefore, we headed on to child development tracking and re-did our competitive analysis for probably the fifth time…</p><h3>Getting Started</h3><p>Once we had our topic sorted, we felt much more confident diving into user surveys and interviews. We focused on identifying what our potential future users were doing to track their children’s milestones and development, what they were tracking / what was important to them, and what pain points they were facing that was preventing them from tracking.</p><p>We struggled to find our target user to interview, as we did not have too many personal connections to parents with young children. Our target demographic was parents of children under the age of 5. I do not have any children, and Anastasia’s children are teenagers. Therefore, we shared the survey onto Facebook groups for parenting, personal social media posts, reaching out to friends and family, our bootcamp’s slack channel, and we exhausted every channel we could think of. Thankfully, in the end we got enough survey data to take key valuable insights in order to keep moving on our project.</p><h4>Survey and Interview Results</h4><p>The results of our survey and interviews showed us the following insights:</p><ul><li>Parents find <strong>value</strong> in tracking their children’s developmental milestones</li><li><strong>Language development</strong>, <strong>physical growth</strong>, <strong>cognitive skills</strong>, and <strong>motor skills</strong> are the most important milestones to track for parents</li><li><strong>Forgetting to update</strong> milestones is the biggest challenge parents face</li><li><strong>Information and guidelines</strong> on developmental milestones, <strong>alerts/reminders</strong> for upcoming milestones, and tools to <strong>record and visualize progress</strong> are the most helpful support that parents desire when tracking milestones.</li></ul><p>This data gave us the resources to focus our design into a user-centered approach, so that parents would find value in our final product instead of it disappointing them as some of their current methods have done. We created an affinity diagram and an empathy map to focus those insights.</p><p>The affinity diagram gave us a real tough time, and we spent much more time on it than we anticipated. Instead of focusing our insights, the diagram became on big blob of user feedback. New data kept getting added, causing it to be almost impossible to organize/clump. I started to see it as a big angry monster instead of a tool to help us narrow or research. The only solution we could think of was to stop, organize our findings, and reevaluate. This took less time than we anticipated (thankfully) and we were back on track with focused insights in no time.</p><h4>User persona</h4><p>Now that we knew what our user’s experiences were and what they valued, we could focus on our user persona. The photo below shows our user persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjZgFp4FOwbPd07B4SbI_Q.jpeg" /><figcaption>Our user persona of Emily Stevans, The Multi-tasking Caregiver</figcaption></figure><p>This is Emily Stevens. She is the ‘Multi-tasking Caregiver”. Emily is a busy professional mom of two young children, Jimmy and Alice, who are 2 years old and 6 months. Emily’s days are chaotic to say the least, filled with organizing her children’s daily activities, taking them to and from school or day care, working full-time as a marketing manager, and maintaining a social life all while thinking about what is best for her children’s well-being.</p><p>With her busy schedule, Emily has found it practically impossible to properly track her children’s milestones and development and she is constantly worrying about missing important appointments or missing vital information about their wellbeing. Emily just wants her family to be happy and healthy, while also having reassurance and peace of mind that she is doing just fine. After creating Emily’s journey map, we created ‘How Might We’ statements to assess in what ways we can improve Emily’s experiences with tracking her children’s milestones.</p><p>This led us to defining our problem statement:</p><blockquote>“Concerned/diligent parents worried about their children’s development need to find a way to ensure their children reach their full potential and are development because balancing their busy schedules with the demands of parenting often leaves them feeling overwhelmed and worried about missing important milestones and developments.”</blockquote><p>We created our mood board based on how we wanted to represent our final product. I was inspired by soft, bohemian, and calming themes. Our brand attributes were <em>familial</em>, <em>supportive</em>, <em>nurturing</em>, <em>trustworthy</em>, and <em>friendly</em>. Take a look at our mood board below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmM8dWn9f01yudjWQYgWcQ.jpeg" /><figcaption>The mood board for our final hi-fi prototype</figcaption></figure><h3>Ideation and Wire framing</h3><p>We then began ideating solutions to take us one step closer to our final product. Sorting out our ‘must haves’ from our ‘should haves’, ‘could haves’, and ‘won’t haves’ was something we had to go back to several times into our next step, which was site map and user flow creation. There were certain aspects that we preferred to focus on and found value in, but were not the top priorities of our users from our initial insights, so this often lead to long discussions about what we would incorporate and eventually mock-up in our final design.</p><p>Some frustrations were felt, and we had long conversations about what was best, and eventually we reached amicable conclusions, allowing us to continue pushing forward.</p><p>So far into this project, I took charge and lead our team through a lot of the exercises and tasks. I was always conscientious of our time management, and I felt very confident in my abilities in interviews, user focused tasks and creation, ideation, etc. However, I realized that I needed to take a step back and allow Anastasia to meet me at the leadership role. I had discovered that in my pursuit to create the best project, that I can get caught up in the time constraints and become too focused on moving forward instead of ensuring that Anastasia is on the same page.</p><h4>Mid-Fi Wireframes</h4><p>Therefore, when it came time to wire framing, we spent split the wireframes from our user flow to work independently, while simultaneously asking the other for support, feedback, and integration. It was important to us that our design flowed and was cohesive, so we made sure to personal opinions and tips along the way, which we appreciated and took on with gratitude. Please take a look at our final wireframes below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZQdnlUXFwYHUsbYgQ5cGQ.jpeg" /><figcaption>Our projects mid-fi wireframes</figcaption></figure><h4>Hi-Fi Wireframes</h4><p>Once our wireframes were completed, we needed to transfer our mid-fi to a hi-fi copy. This is something we struggled with, as Anastasia and I both were have Figma issues, and our prototyping was not transferring properly to the hi-fi format.</p><p>We spent a loooong while sorting out issues, and a lot of support inquiries were sent. Eventually, we collaborated to create our final hi-fi wireframes and to create the final design. So now, I present to you below, our prototype for our child development tracking application: Little Landmarks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F7904455cbb3a4bef94a86ba496f32123&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F7904455cbb3a4bef94a86ba496f32123%3Fsid%3D33cf5cb3-3a2f-4abd-a017-08d2747460fd&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F7904455cbb3a4bef94a86ba496f32123-9e5a249ae886bcb7.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1152" height="864" frameborder="0" scrolling="no"><a href="https://medium.com/media/4e341f9f66f82ad01bb65322c906237d/href">https://medium.com/media/4e341f9f66f82ad01bb65322c906237d/href</a></iframe><p>The brief mentioned that the final design should not include aspects like login, sign-up, onboarding, account/user Management, registration consent and cookies, therefore these features were not included in the final design.</p><h3>Final Thoughts</h3><p>Each project in the IronHack bootcamp has new challenges, and the difficulty increases each time (as to be expected) but with that, I always finish a project feeling proud and accomplished. Anastasia and I both are not experts in Figma, and we had some disagreements along the way, but we created a final product together that took a lot of hard work, determination, collaboration, and patience.</p><p>I learned so much in this project, both hard skills and soft. The journey was a tough one at times, but it was a success in the end, and with our final presentation complete, Anastasia and I had a moment to reflect on our overall project, giving each other feedback. We complimented each other’s strengths and encouraged each other to keep going and gain more confidence as the time goes by. Our next project will be our final project, and we both reflected on how quickly the time has gone and that we have done so much so far. Through the ups and downs of this bootcamp, I know that all of my cohorts and I will walk away from this experience as better designers, empathizers, and teammates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96421562332f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-nurturing-growth-creating-a-child-development-tracking-app-96421562332f">Case study: Nurturing Growth — Creating a Child Development Tracking App</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Box, Bike, Ballet — The B3B App Redesign]]></title>
            <link>https://medium.com/@meagle97/case-study-box-bike-ballet-the-b3b-app-redesign-36b6bc5367f7?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/36b6bc5367f7</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[redesign-challenge]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Sun, 28 Jul 2024 21:21:43 GMT</pubDate>
            <atom:updated>2024-08-01T07:10:47.147Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study: Box, Bike, Ballet — The B3B App Redesign</h3><p>Pedals, Punches, Pirouettes. What do these three things have in common? Well, they are fundamentals when it comes to the brand <a href="https://b3bwomanstudio.com/en/">B3B</a>, a woman’s workout studio with several locations in Madrid and Barcelona, Spain.</p><p>Their interval bike, box, ballet classes are a killer workout and will get your blood pumping, heart racing, and sweat dripping in just 45 minutes. B3B inspires woman to get active and love who they are in whatever body or shape they come in.</p><p>They are a highly beloved and successful business, however there is only one main issue holding them back: the B3B app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxFevmMXDvKKSIl93aZbQQ.png" /><figcaption>Hero Image of the B3B redesign</figcaption></figure><h4>The Warm Up</h4><p>So the B3B app could use some love. And that is something that my partner and I discovered early on. I was working with <a href="https://medium.com/@einfante2004">Elvira</a> on this project, and we began by looking at some apps that we both had in common to decide what both interested us, and would be a useful re-design. I then remembered some pain-points I had experienced while using the B3B app, as I am a loyal member at B3B. After taking a look at their current app, we agreed that it would be a fun re-design with a lot to work with.</p><p>We started by taking screenshots of the current app’s screens and then picking out 4 specific screens to work on. We decided it made most sense to choose 4 screens that could follow a flow, even though we wouldn&#39;t be prototyping on this project. Our <strong>brief</strong> was to select an app of our choice and our teacher asked us to re-design 4 screens. No cheating was allowed, meaning that the use of UI kits was prohibited and everything needed to be made from scratch.</p><h4>Our He(u)ro</h4><p>The <strong>Heuristic Design Principles</strong> were vital our redesign of the B3B app. We used this technique to experience-based problem solve, learn and discover exactly what was missing from the current app’s design. Elvira and I individually analyzed the screens, and when we came together to discuss what we found, we realized we had the same conclusions. Our main principles that we focused on throughout the redesign were:</p><ul><li>Aesthetic and minimalist design</li><li>User control and freedom</li><li>Recognition rather than recall</li><li>Consistency and standards</li><li>Flexibility and efficiency of use</li><li>Match between system and the real world</li></ul><p>The current B3B design is consistently inconsistent — unclear icons and labels, inconsistent design elements, and overuse of bold primary colors. User efficiency was also a concern, highlighted by the need to exit and re-enter credentials to change studios and the cumbersome navigation. Additionally, the app lacked essential help features and status indicators, making it difficult for users to find support and understand their current location within the app. Lastly, redundant and missing information further complicated the user experience.</p><h4>Prep to Sweat</h4><p>In order to create a redesign that addressed these concerns, we made our game plan.</p><p>We decided that the redesign should incorporate more intuitive terminology, consistent typefaces, colors, and layouts, and use accent colors sparingly. Integrating streamlined navigation options and dropdown menus were crucial. Adding a help button, clear status indicators, and simplifying the menu would enhance overall usability. And tackling the need for clear, concise, and well-organized content throughout the app would improve user satisfaction.</p><h4>Rising to Competition</h4><p>Once we had an idea of where we wanted to take the redesign, we took some time to assess the competition. We dove into a <strong>visual competitor analysis, </strong>focusing on brands like Peloton, Nike Running Club, Soul Cycle, and Pure Barre.</p><p>We made good use of our handy dandy friend <a href="https://mobbin.com/browse/ios/apps">Mobbin</a>, which is a a mobile and web app design reference site (Thanks Niamh for the introduction!) This way we could analyze actual screens of B3B competitor’s applications, allowing us to see what we like and disliked about their current designs.</p><h4>Sweat, Smile, Repeat</h4><p>Next, we pulled our resources from the current app and the business website to create a <strong>mood board. </strong>Capturing and maintaining an authentic, recognizable, and consistent style was vital in our redesign process for B3B. We wanted to redesign the app, not the entire brand. So we started by pulling some <strong>brand attributes</strong> from the website to focus on.</p><ul><li>Vitality</li><li>Positive</li><li>Feminine</li><li>Unique</li><li>Mindfulness</li><li>Empowerment</li></ul><p>These 6 words were B3B and everything that they represented.</p><p>We followed our mood board with a color and typography style tile and we created a style guide in our project to maintain consistency throughout our design. We pulled the bold 3 main colors from the current design- Bright pink, orange, and purple and focused them into accent colors instead of primary. Here is our mood board below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_KKp6nZd-NKpaAN3EgB5w.png" /><figcaption>The mood board we created for our B3B redesign</figcaption></figure><h4>Punching Above My Weight</h4><p>Finally, we were able to move on to wire framing. The screens we were redesigning were a registration/login, homepage, classes, and reservations screens. We split the screens and tackled the work, helping one another and asking loads of questions, which allowed us to create something independently but that was consistent and harmonious.</p><p>During this point, I started to feel a bit overwhelmed. My experience with creating mobile app wireframes wasn’t extensive, and I was starting to doubt my designs and capabilities. I felt like some parts were taking me a long time to complete, and I was questioning a lot of the decisions I was making whether they were good enough or not.</p><p>I had a one-on-one with my teacher and confessed to him my struggles and growing imposter syndrome. I even told him that I was embarrassed to present my work. After some solid advice and assurance, I went back to my wire framing feeling a lot more confident and relaxed, knowing that my best effort reflects my work, and that is all that matters.</p><h4>Finding the Rhythm</h4><p>With the pedal to the metal, we finished our wireframes and prepared to present our work. And now, we present in the following photos, our final redesign:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nCV3DVj4EiKbjvBSWL-Qvw.png" /><figcaption>Before and After Registration/Login screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zrr9Lu1QXi4UiS38isY61Q.png" /><figcaption>Before and After Homepage screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tu2etYPVq6gQ3TRBiXlX6w.png" /><figcaption>Before and After Classes screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CABxQ9noO7ZteCbSJ0oC4g.png" /><figcaption>Before and After Reservations screen</figcaption></figure><h4>Cool Down</h4><p>This project was a fun and creative opportunity to sharpen our design skills and step a way for a moment from the UX principles we have come to know very well. I learned a lot from this experience, both in the hard skills I worked on in creating our screens in Figma, and about myself.</p><p>I know that there will be many more times throughout my career where I will experience imposter syndrome and doubt myself. Coming from a completely different background, this is to be expected. But I know that with time, I will gain the confidence in my skills and myself as a whole.</p><p>I am very proud of the work that we accomplished on this project, and it turned out even better than I could have imagined. Our cohort feedback was so kind and the praise and suggestions for improvement we received were invaluable. I am excited to take this new found knowledge into my next projects and I have gained so much confidence in myself since.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36b6bc5367f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IronHack Case Study 2: Crafting Clicks for Brews —  Gibbon’s Brewery E-Commerce Journey]]></title>
            <link>https://medium.com/@meagle97/ironhack-case-study-2-crafting-clicks-for-brews-gibbons-brewery-e-commerce-journey-505c607cb292?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/505c607cb292</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[craft-beer]]></category>
            <category><![CDATA[brewery]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[e-commerce-website-design]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Sun, 21 Jul 2024 14:37:38 GMT</pubDate>
            <atom:updated>2024-08-01T07:09:45.471Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study 2: Crafting Clicks for Brews — Gibbon’s Brewery E-Commerce Journey</h3><p>This is a case study for our second project in the UX/UI IronHack Bootcamp. In this case study, we had the opportunity to work with a stakeholder for <a href="https://biereartisanalegibbon.jimdofree.com/">Gibbon’s Brewery</a>, an organic craft beer brewery located in Bordeaux, France. Our project was to create an e-commerce platform for their existing website. Below is a photo of our final design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ygvi9R8j6rgvJEDP0d2-A.png" /><figcaption>The final design of the Gibbon’s Brewery e-commerce platform</figcaption></figure><h4>Project and Team Overview:</h4><p>So as mentioned before, the brief was to design a responsive website for a local business or professional. Our team was made up of varying skill levels and strengths/weaknesses, and this turned out to be an invaluable asset.</p><p>The team consisted of three people; <a href="https://medium.com/@lucasezcurra95">Lucas</a>, <a href="https://medium.com/@niamh.ac">Niamh</a>, and myself. I thoroughly enjoyed myself in this team and I think our dynamic was fantastic. We admitted our personal work styles and what we could bring to the team in our very first meeting, which allowed us to establish and understand how we could tackle the project most effectively. That set us up to not only empathize with our users but also with ourselves.</p><p>Our project was filled with laughter and jokes and shared recipes or movies. And of course lots of work as well. I learned so much from both of my teammates and although the project wasn’t short of difficulties, I am very proud of what we accomplished.</p><h4>The Stakeholder:</h4><p>Our stakeholder was Matt, a craft brewery owner who opened Gibbons’ Brewery in 2019 with his fellow craft-beer loving buddies. After researching the brewery and a bit of <strong>competitive analysis, </strong>we planned to schedule a meeting with Matt to better understand his company and to gather vital insights. We wanted to focus our questions to better understand Gibbon’s users, problems, goals, and culture.</p><p>Taking a look at the current Gibbon’s website, we realized that there was a lot to work with. The site needed some love, as it appeared to be untouched in several years and lacked updated information. It was disorganized, incomplete, and forgotten (something Matt whole-heartedly admitted) and our team was bright eyed and bushy tailed, ready to tackle it.</p><h4><strong>Our First Challenge</strong></h4><p>However, this led to what would be our first challenge and our first reality check. Matt had been busy with summer pub season and rowdy sports fans, so he needed to take a vacation (can we blame him?). The only problem was: we couldn’t get ahold of him to schedule our stakeholder meeting.</p><p>This brought worried conversations of how to proceed — Do we change stakeholders? Do we continue on without the interview? Do we wait to hear back and risk falling behind in our project? It was a true example of the common challenge many face when working with clients and stakeholders. We decided to wait it out and continue working on our project while hoping we heard back from Matt soon.</p><p>We decided that our <strong>mood board</strong> and <strong>brand attributes</strong> were something that we could focus our attentions on without Matt’s interview. The existing website lacked a lot of inspiration, but their Instagram was active and it gave us great ideas of how we could showcase Gibbon’s character. Take a look at our mood board below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fheJhGy996LtGjfdy9x8YQ.png" /><figcaption>The Mood board we created for Gibbon’s Brewery</figcaption></figure><p>We tried to re-focus our attentions onto <strong>user surveys</strong> to better understand a user’s perspective on craft beer and breweries. Without our stakeholder insights, we dove into what competitors were offering and were successful at, and decided to focus our attention onto portable tap-rental — a product currently being offered at Gibbon’s.</p><p>We surveyed craft beer lovers and regular beer consumers to better understand who are target user group would be and if tap-rental is something they were familiar with our would consider for themselves. We were happily surprised to have received 67 survey responses, and the results as follows:</p><p><strong>Survey Results</strong></p><ul><li><strong>Quality:</strong> surveyors appreciated good quality beer and believed it was better from the tap</li><li><strong>Ability to use tap: </strong>surveyors wanted and expected to use the tap easily with instructions</li><li><strong>Awareness:</strong> surveyors were not aware that tap rental services were an option</li><li><strong>Cost: </strong>surveyors were unsure about cost of tap rental services and this was a priority to them</li><li><strong>Delivery: </strong>surveyors wanted delivery services for tap rental</li></ul><p>This data was crucial in creating a user-centered design, and to better understand our stakeholder’s demand and user’s wants, needs, and goals. Finally, we were able to conduct our stakeholder interview with Matt. He helped us to better understand his business, what it represented, and his business goals, and luckily enough, tap-rental services was something he wanted to expand and focus on.</p><h4>User persona:</h4><p>With our stakeholder and user insights in tow, we were able to create our <strong>user persona</strong>, Théo Bamba.</p><p>This is Théo. His user persona is below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJCcRMUas3Hfj7ykDuwnBQ.png" /><figcaption>Our user persona for Théo Bamba, the Untapped Keg Enthusiast</figcaption></figure><p>He is the Untapped Keg Enthusiast and he is planning a social event, in which he has started to face several challenges: understanding the benefits of tap beer over bottled options, finding and comparing prices to stay within budget, and managing the logistics of beer rentals without relying too heavily on his car. Then came Théo’s<strong> journey map</strong>, where we discovered the specific pain points and the emotions he would be feeling.</p><p>This led us to our <strong>problem statement</strong>:</p><blockquote>“Beer-enthusiasts planning to host an event need to find a way to throw a successful party with quality beer, at an affordable price. Currently, people who drink beer aren’t aware that tap beer can be cheaper per litre than bottled and canned varieties, while also being of better quality.”</blockquote><p>Once our problem statement was defined, we continued to ideate solutions that we could incorporate into our design. Focusing on the user was our main task. Always. Therefore, the consensus was that at the bare minimum, our customers should be informed about our services, and be able to rent /book a portable tap confidently. A clear, end-to-end shopping tool with specified booking criteria, instructions, various payment options, and live availability.</p><p>We then worked on a <strong>sitemap</strong> and a <strong>user flow</strong> to outline where, when, and how the user would access our design.</p><h4>Wireframing</h4><p>As I mentioned before, our strong-suits and skill levels varied on this project. Lucas was <em>the Idea King</em>, I was <em>the Empathizer</em>, and Niamh was our <em>Figma Leader</em>. Therefore, Lucas and I learned a lot from the tips, tricks, and overall technique Niamh had to show us in creating our wireframes and the final prototype. Together, we combined our skills to create a mid-fi wireframe. Check out a mid-fi frames in the following image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RpyuNiNdOzLtv-2EtBxgNA.png" /><figcaption>The Mid-Fi Wireframes</figcaption></figure><p>After the mid-fi wire framing creation, we needed to test our product with some <strong>usability testing</strong>. We asked our personal craft-beer connoisseur, as well as some additional potential users to interact with our wire frame’s flow. Their feedback allowed us to fix any issues or improve any functions, and to confirm that we had addressed the major needs, wants, and goals of the user.</p><h4>The Final Prototype</h4><p>Then came the best part: creating the final prototype. We pulled out our style guide, color charts, created our components, and mocked-up the logo to begin creating the final site. Once we began adding colors, typefaces, images, and revised all elements, our excitement and satisfaction began to soar and we could finally see our design come to life.</p><p>Our team dedicated many hours and long nights of our weekend to make this product come to be, and it was all worth it to have created something that we are proud of.</p><p><strong>The result?</strong> An e-commerce website, crafted from comprehensive user research and key stakeholder insights, in which Gibbon’s brewery customers are at the heart. It offers beer enthusiasts an efficient and understandable experience where they can explore catering options, evaluate the merits of tap-fresh keg beer, find detailed pricing and delivery information, and finalize their purchases, all within a single, user-friendly platform. Feel free to follow along with our prototype in this video below.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F411cad87c7684a958075fa8ac1f40fbc&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F411cad87c7684a958075fa8ac1f40fbc%3Fsid%3D88963046-8325-4caf-89b1-829a5ff1830f&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F411cad87c7684a958075fa8ac1f40fbc-480d87e41aca08ec.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1890" height="1417" frameborder="0" scrolling="no"><a href="https://medium.com/media/67deedd079d05808c5816255d4ef0752/href">https://medium.com/media/67deedd079d05808c5816255d4ef0752/href</a></iframe><h4>Final Thoughts</h4><p>This project was the largest learning process so far within the UX/UI bootcamp. After completing this project, I understand so much more about UX processes. In comparison to the first project, the development and improvements are exponential, and it is clear that progress is being made to not only myself, but to our entire cohort. It is a wonderful thing to be able to watch my team members grow, improve, and succeed, and I feel so lucky to have been a part of this project with them.</p><p>The dynamic was different for me in this project in comparison to our last, as I was able to take into account my teammates feedback from our last project and take a step back from leading this time. I was able to contribute to the team and communicate my ideas and direction without maintaining a leadership role at all times. Instead, I focused more on my empathetic and soft skills, where I feel that my skillset is strongest. Stakeholder/user interviews, ideation, and brand attributes/mood boards is where I felt most confident in this project and I am extremely grateful to have a team that recognized and encouraged that.</p><p>In the end, I am sad to leave behind my lovely team, but knowing that we created something together by combining our skills and passions is one of the most wonderful things I have done so far in this bootcamp. I am excited to see where my teammates and the rest of our cohort will end up next in our journeys.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=505c607cb292" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Iron Hack Case Study 1: Wicked Problems —  Immigration]]></title>
            <link>https://medium.com/@meagle97/iron-hack-case-study-1-wicked-problems-immigration-dba4bf635923?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/dba4bf635923</guid>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[wicked-problem]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Sun, 07 Jul 2024 13:26:07 GMT</pubDate>
            <atom:updated>2024-07-07T13:26:07.628Z</atom:updated>
            <content:encoded><![CDATA[<h3>Iron Hack Case Study 1: Wicked Problems — Immigration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ihOfl0oWnBD1VvMWXT9udw.jpeg" /></figure><p>This article focuses on IronHack’s UX/UI bootcamp project 1: Wicked Problems. This was our first project within the bootcamp, and there was a lot of trial and error throughout it. Certain moments were more clear and smooth, while others had us scratching our heads and frustrated. With that being said, so much was learned and gained in this initial project, and I am excited to share all of it here.</p><h3>The Project Overview</h3><p>Our class was presented with the idea of a wicked problem to be solved by combining collaboration and iteration, focusing on these values which are at the heart of Design Thinking. We were told at the beginning of this project that we would not find a complete solution, so that we would take this project solely to a lo-fi prototype stage for a mobile app.</p><p>The topic of <strong>immigration</strong> was our wicked problem. The brief is summarized as:</p><p><em>“The experience of migrating to a new country and having to adapt to a different culture or language comes with a number of bureaucratic duties that must be completed within a particular timeframe to validate the journey in the host country. </em><strong><em>How Might We Help migrants find information, complete tasks, and get their paperwork done to start their life in a new city.”</em></strong></p><h4>Group dynamics</h4><p>We were divided into our teams to begin tackling our wicked problem. Our team was a group of five IronHack students, including Jakob, Anastasia, Busola, Precious, and myself. We didn’t establish any set roles for our group, and so I took it upon myself to assume somewhat of a leader position. Without the set roles, we often found ourselves feeling different emotions and confusion with responsibility, where some group members were feeling left behind or lost, while others were feeling held back and anxious to advance.</p><p>This experience, combined with our peer-to-peer review, had me assessing my strengths and weaknesses in the team, and notice that although I felt the pressure or need to step up and lead, that I can be patient and allow time for others to move at their own pace and assume leadership roles as well. Therefore, on future projects, I noted that discussing each team member’s personality, preferences, and work styles can lead to a smoother and more effective work environment.</p><h3>Secondary Research</h3><p>To begin the project, it was important to conduct further insights into this problem and how it could effect our potential user. We spent time individually collecting information we found about what was currently available on the market for re-locaters to aid in their migration process.</p><p>The overall themes began to surface and we discovered that there were some resources available to individuals who needed to complete migration processes, but they were scattered across many platforms and in various languages. We also discovered that this was a significant problem for those relocating to European countries.</p><h3>User Interviews</h3><p>Everyone on our team had relocated to another country and we all had our own experiences to share on this topic, however, it was vital to try and eliminate our pre-conceived biases and receive a wider range of data by interviewing our user.</p><p>We created an interview guide based on the research and themes we discovered. Our interviews wanted to answer the questions of:</p><ul><li>How was their overall experience of relocating to a new country?</li><li>What did they need to accomplish and how was the process of completing those requirements?</li><li>What resources, if any, did they rely on to complete migrations requirements?</li></ul><p>We conducted five user interviews, with each team member moderating once, while two others took notes and recorded the responses. We were able to work quickly to schedule our interviews for one afternoon, allowing us to focus more on the results and cluster crucial feedback. We worked on an <strong>Affinity Diagram</strong> to assist in this process. We then began to get closer to identifying who our user could be.</p><h3>User Persona</h3><p>Our team spent time completing an <strong>Empathy Map</strong>, in which we evolved into what we considered to be our Primary User Persona. Meet Anika Khan:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zk-WIab9_N5ape43NTbTXg.jpeg" /><figcaption>Anika is a single representation of the many experiences of our interviewees</figcaption></figure><p>Creating Anika allowed to focus on one imagined scenario that represented many stories of our potential future users. We also decided at this point to narrow down our user target scope to individuals relocating to Germany, as this was a common place for our interviewees.</p><p>Anika is an adventurous professional who is looking forward to starting a new and exciting chapter in her life, and isn’t wanting to get bogged down by the confusing bureaucratic paperwork.</p><h4>User Journey</h4><p>We then created a <em>future</em> user journey map, and a <em>current</em> user journey map to help us to visualize the user’s experience at different levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*82-3l347_gdJxrVnh4pLMw.jpeg" /><figcaption>The journey map establishes the stages of our user persona’s timeline with her various emotions</figcaption></figure><h3>Problem Statement</h3><p>Once we had established who our user was and what she was experiencing, we needed to then define what our problem really was. We realized that a problem statement was much more than just simply stating what the issues were and we found ourselves stuck with how to put everything we were imaging into the statement.</p><p>Each teammate had different ideas of what was necessary and what wasn’t. We decided to pause our statement to try and formulate some “How Might We” statements. The statements were as follows:</p><ul><li>How might we give more understanding and clarification to official sources</li><li>How might we help connect people who are in similar situations</li><li>How might we help re-locators to gather correct documents and create appointments</li></ul><p>This allowed us to reframe the problems as opportunties and prioritize statements. We then re-addressed our problem statement and decided on:</p><p><em>“Professionals who relocated recently to Germany need to find a way to successfully complete their migration process on time because currently information about the immigration process is difficult to find and language barriers cause confusion when trying to complete them.”</em></p><h3>Back on Track — Ideation</h3><p>Now that we were confident in what our problem was, we could continue to move forward on our idea generation. We focused our efforts on the activity “<strong>Crazy 8’s”</strong>, in which we established goals of what to brainstorm and solve, and then spent 8 minute sketching out our ideas.</p><p>At this point, I noted that I was struggling a bit in the project. I was feeling tired and frustrated with how long aspects were taking to decide or explain, and I was getting anxious to start creating our prototype. However, with a bit more patience and understanding, I understood that we were able to focus our ideas and create a better product than what would be if it was rushed.</p><p>We created a <strong>user flow</strong> to establish the architecture of our future app so we could plan the screens that needed to be generated. This was something the team struggled with to agree on, as our own user flows looked very different from one another and we had confusion with which shapes represented what. But eventually we agreed and created one big flow to begin working on our prototype.</p><h3>Wireframing and Prototyping</h3><p>Finally things began to feel like they were coming to fruition, and with our defined goals and expectations, we were able to create our wireframes. We started off with simply pen and paper, and then met a middle ground of creating something simple in Figma to get us started. This was a bit messy, but helped us to get closer to a lo-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJst7SSXnvRvwX5v9yvS9A.png" /><figcaption>Our own ideas of the wireframe homepage</figcaption></figure><p>However, we realized at this point that we were running out of time before our project was due and we were to present, so we split up the team with some members completing the prototyping, and others working on the presentation. I realized at some point that we additionally needed to conduct <strong>concept testing interviews</strong>, which required creating interview questions and set up. This particular afternoon began to feel chaotic, with little time being dedicated to the presentation. So we focused solely on finishing prototyping and concept testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdMAs3l-G7T-77djJEGBEA.png" /><figcaption>The lo-fi wireframes prototyped with blue connections</figcaption></figure><h4>Concept Testing Feedback</h4><p>Our efforts of concept testing allowed us to modify and change any parts of the prototype based on testing feedback. We realized that from these tests that our user wanted a bigger space for the user to click, therefore prototyping a larger area, and that some buttons were crucial to have completed in the prototype to allow the user to flawlessly move from screen to screen.</p><h3>Presentations</h3><p>We completed our project with a single presentation to encapsulate our process, journey, and our final lo-fi product. We spent the morning before the presentation completing it and delegating sections for teammates to present.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLgpsjmXtzLEXXUSZQgP0A.png" /><figcaption>The prototype slide of our presentation</figcaption></figure><p>Once the presentation was completed, we received feedback from our classmates and teacher on our project, and then we completed peer-to-peer feedback on our own teammates based on our experiences throughout the project.</p><h3>Final Thoughts</h3><p>This project was the biggest learning experience, by default, as it was our first project. But with that being said, it allowed us to view UX methodology in a hands-on and realistic fashion, in that we could create something from scratch and experience all the highs and lows involved in the process.</p><p>Our lack of experience, short deadline, and the differences in personalities and opinions all contributed to a unique, but challenging experience that I think was necessary to begin this journey in the UX/UI bootcamp. Overall, I was proud of the feedback received and the efforts my team and I put in to create our final prototype.</p><p>With this new-found knowledge, I am looking forward to growing and learning in future projects, and to looking back one day on the path it took to get here and where it all started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dba4bf635923" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IronHack Prework Challenge 2: Wireframing]]></title>
            <link>https://medium.com/@meagle97/ironhack-prework-challenge-2-wireframing-a606c5e4ae25?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a606c5e4ae25</guid>
            <category><![CDATA[ironhack-madrid]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[wireframe-design]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Sun, 16 Jun 2024 14:53:25 GMT</pubDate>
            <atom:updated>2024-06-16T14:53:25.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*B_iq_RUNBaUakNCAypsUtA.png" /></figure><p>Hello there and welcome back! This is my second IronHack challenge that was about <strong>Wireframing</strong>.</p><p>In this article, I will be diving into my process and experiences with wireframing. In this challenge, we “reverse engineered” a popular app of our choosing to create a wireframe version of the User Flow of the chosen app based on screenshots or high-fidelity prototype screens. Thus creating the final product of <strong>5–7 interactive prototypes built in Figma</strong>.</p><h3>Beginning the Challenge</h3><p>The app I chose for my challenge was the <strong>Urban Outfitter’s</strong> application. I selected 7 screenshots from the application to reverse engineer the layout to create a wireframe. I decided to choose the Urban Outfitter’s app to work on because it is one that I am familiar with and often use, and it also is an application that I have found to be easy to understand and a pleasant experience when using it.</p><h4>User Flow:</h4><p>The user flow I decided to follow and replicate into my wireframes was as follows —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NQ6RsBotIls4CRM3mjnTjw.png" /><figcaption>Example of a typical user flow for the Urban Outfitters App</figcaption></figure><h4>Task Flow:</h4><p>The task flow that I decided to follow and impliment into my wireframes was the following —</p><p><em>Homepage</em> → <em>Shop</em> → <em>New</em> → <em>Item</em> → <em>Shopping bag</em> → <em>Checkout/payment</em> → <em>Submit order</em></p><h4>Inventory of UI Elements:</h4><p>Before I got started, I made sure to keep an inventory of the different UI elements that I was going to implement into my wireframes. Some of th elements were —</p><ul><li>Carousel</li><li>Drop down menus</li><li>Input fields</li><li>Titles</li><li>Block text</li><li>Back button</li><li>Search fields</li><li>Tags</li><li>Icons</li><li>Accordion</li></ul><p>I wanted to be sure that each element was represented and that key items were obvious when creating the wireframes.</p><h3>Lo-Fi Wireframe</h3><p>The next step in the challenge was creating a lo-fi wireframe in order to emulate the user flow of my chosen app. I decided to draw the frames onto graph paper using simply a pen and ruler.</p><p>Because I knew that I was going to be creating a mid-fi mock up in the next step, I chose to keep this part of the challenge simple and quick, as low-fi wireframes are intended.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWFitbdjGoSG9GnxYcZtWA.jpeg" /><figcaption>My lo-fi wireframes</figcaption></figure><h3>Figma User Flow and Prototype</h3><p>The last step of the challenge was to create a prototype of the wireframes in Figma to show the user flow through the application.</p><h4>User Flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HM-IoiE22wwakgdn-VqPbQ.png" /><figcaption>An example of the User Flow I chose</figcaption></figure><h4>Prototype</h4><p>Check out my prototype below to follow the user flow of the application.</p><p>&lt;iframe style=”border: 1px solid rgba(0, 0, 0, 0.1);” width=”800&quot; height=”450&quot; src=”<a href="https://www.figma.com/embed?embed_host=share&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FyNz8uKy6hdmoqZXwr0wHXZ%2FChallenge-2%253A-Wireframing%3Fpage-id%3D0%253A1%26node-id%3D15-770%26viewport%3D122%252C-20%252C0.27%26t%3Ds3alv4CSSoymiXX2-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D15%253A770">https://www.figma.com/embed?embed_host=share&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FyNz8uKy6hdmoqZXwr0wHXZ%2FChallenge-2%253A-Wireframing%3Fpage-id%3D0%253A1%26node-id%3D15-770%26viewport%3D122%252C-20%252C0.27%26t%3Ds3alv4CSSoymiXX2-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D15%253A770</a>&quot; allowfullscreen&gt;&lt;/iframe&gt;</p><h3>Final Thoughts</h3><p>During this challenge, there were both exciting and challenging moments. I learned a lot about the basics and fundamentals of wireframing and why it is a crucial element to product design.</p><p>Something that I really struggled with during this challenge was that I got caught during the prototyping stages after using wireframing kits. The issue was that the kits often had components that were embedded into the elements, and I unknowingly placed them into my wireframes without frames underneath them, which made it much more difficult to prototype.</p><p>I enjoyed learning something new and furthering my abilities in Figma with this wireframing challenge. I am excited to continue growing and improving once I get started in the bootcamp.</p><p>Thanks so much for following along!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a606c5e4ae25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IronHack Prework Challenge 1: Design Thinking]]></title>
            <link>https://medium.com/@meagle97/ironhack-prework-challenge-1-design-thinking-009e3bebce00?source=rss-69bdd57dae4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/009e3bebce00</guid>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[public-transit]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Maddy Eagle]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 10:11:24 GMT</pubDate>
            <atom:updated>2024-06-06T10:11:24.560Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l1CTy1HHFuFau9PT_cxweQ.jpeg" /><figcaption>Citymapper app with new ticket purchasing options directly on the app</figcaption></figure><p>Hello there and welcome to my first prework challenge for the UX/UI Bootcamp at IronHack!</p><p>In this article, I will be explaining my process through this design thinking challenge and showcasing my results that I have created in regards to solving a pain point for public transit users when using the Citymapper application.</p><p><a href="https://citymapper.com/?lang=en">Citymapper</a> is a public transit and mapping application which displays public transport options in many cities across the world. Their goal is to solve the problems of urban mobility by offering the quickest and cheapest public and private transport routes to their users. The app currently has successful features like live timing and location to location mapping.</p><p>However, Citymapper users are experiencing a pain point with the application: the different amount of public transport tickets the users have to purchase and the difficulties that arise with this.</p><h4>THE CHALLENGE:</h4><p>Create a feature for this app that solves the pain of having to purchase different public transport tickets by different channels.</p><h4>DESIGN THINKING PROCESS:</h4><p>Empathize → Define → Ideate → Prototype → Test</p><p><strong>STEP 1: EMPATHIZE</strong></p><p>Before I engaged in any further activity, I asked myself these questions:</p><ol><li>What problem are you solving? <em>Users have to buy multiple public transport tickets with many issues like long lines, malfunctioning machines, confusing interfaces and systems, etc.</em></li></ol><p>2. Who is your audience? <em>Anyone who uses public transport, especially when abroad</em></p><p>3. Who is your client’s competition? <em>Other public transit and mapping companies, public transport kiosks</em></p><p>4. What’s the tone/feeling? C<em>asual, relaxed</em></p><p>I then interviewed 5 public transit users, both locally and abroad, to find out what their main pain-points are (what are users having the most trouble with).</p><p><strong>STEP 2: DEFINE</strong></p><p>The next step was to write the findings of the interviews and define a problem statement, focusing on the user’s viewpoint. Detect the main problem that you want to solve. The findings were as follows:</p><p><strong>Pain points</strong></p><ul><li>Kiosks have many options for what type of ticket to purchase and which direction without explanations, causing confusion for users.</li><li>Most kiosks don’t provide maps for the train/metro lines, and when they do they are difficult to read, so it is hard to know where you are going or which “zones” you will be in, especially when traveling.</li><li>Kiosks don’t always translate into your language properly and it can be difficult to understand instructions, especially when abroad.</li><li>Kiosks often have malfunctions or issues and don’t perform actions well.</li><li>Kiosks have long lines that can cause users to miss their transit.</li><li>Pricing changes for different ages or other criteria and can be confusing when purchasing tickets.</li><li>There are not always attendants at stations for assistance, and they don’t always speak your language and can be hard to understand when abroad.</li><li>Oftentimes special additional tickets are needed for instances like airport transit, which can be unknown to the user and cause hidden additional fees and stress.</li></ul><p><strong>Problem Statement: </strong>Users of a public transit and mapping app, Citymapper, have difficulty purchasing cards and tickets for public transport, especially when abroad, because there is no option to purchase on the app.</p><p><strong>Main Problem to Solve: </strong>the different amount of public transport tickets the users have to purchase.</p><p><strong>STEP 3: IDEATE</strong></p><p>The next step was to brainstorm lots of ideas of how I could solve this problem for users. The goal was to come up with as many as possible and then pick two or three different solutions based on my findings.</p><p>I decided to create a mind map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*yGwe0qqg0ssQsecJyKUjzQ.jpeg" /><figcaption>A digitized version of the mind map I created</figcaption></figure><p><strong>Two possible solutions:</strong></p><ol><li>A feature in the app to purchase tickets in one place that will calculate the amount of tickets and additional fees or accommodations (if necessary) to create 1 ticket that is scannable in app .</li><li>Citymapping cards (both physical and mobile) that users can load money onto from the app and scan for any transit options.</li></ol><p><strong>STEP 4: PROTOTYPE</strong></p><p>The last step of our design process was to choose one of our solutions and develop it in a few hand-sketched screens. The goal wasn&#39;t to create a beautiful drawing, but to be able to put our ideas onto paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fTi5OsNa6nHnRyrYcAyQ9A.jpeg" /><figcaption>The physical paper prototype mock-up of my solution</figcaption></figure><h4>KEY FINDINGS AND CONCLUSIONS:</h4><p>I enjoyed this challenge as I felt it allowed me to enter the mind of the user and use the design thinking process to follow the lifecycle to solve a problem. I found the challenge very applicable as I was able to experience the entire process and understand better why it is such an important part to UX/UI design. I discovered just how important research is to understand the feelings, needs, and goals of users.</p><p>Thanks for following along on the beginning of my UX/UI journey!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=009e3bebce00" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>