<?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 Leonardo Rodrigues on Medium]]></title>
        <description><![CDATA[Stories by Leonardo Rodrigues on Medium]]></description>
        <link>https://medium.com/@leonardopinho27?source=rss-4c44c3485dac------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mJB2C9wXrprW_6bP</url>
            <title>Stories by Leonardo Rodrigues on Medium</title>
            <link>https://medium.com/@leonardopinho27?source=rss-4c44c3485dac------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:51:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leonardopinho27/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[Lights Out: Designing Zzleep to Improve Sleep Quality]]></title>
            <link>https://medium.com/@leonardopinho27/lights-out-designing-zzleep-to-improve-sleep-quality-8aed214d4444?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aed214d4444</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Thu, 04 Apr 2024 21:55:07 GMT</pubDate>
            <atom:updated>2024-06-27T22:09:25.673Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7Tta2KEuwecO83QLeY-xw.png" /></figure><h3>📌 Challenge</h3><p>My team had to design a wellness app, from beginning to end. We would have only 9 days to do primary and secondary research, define the problem to tackle, ideate, implement &amp; test our ideas, and finally produce a hi-fi prototype of our solution.</p><p>During these 9 days, Cristina, Viktoriia and I worked on trying to make the lives of users with sleeping problems a bit healthier!</p><h3>🧘🏻‍♀️Why wellness?</h3><p>The digital health industry is booming. These solutions, potentiated by the increasing penetration of smartphones in the market, and by the advancements and adoption in digital health, <a href="https://www.marketsandmarkets.com/Market-Reports/digital-health-market-45458752.html">made 2023 a record year in market revenue, having reached $180.2 billion globally. The projected revenue by 2028 is $549.7 billion</a>.</p><p>If you look at more concrete examples,<a href="https://swordhealth.com/newsroom/introducing-ai-care"> the Portuguese unicorn Sword Health nearly tripled revenue in 2023</a>, being one of the various success cases within this industry.</p><p>As you can see, this is a market to look out for, and having the opportunity to work on a digital health product, even in a hypothetical scenario, was certainly a unique proposition!</p><h3>🔬 Our Research</h3><p>After deciding on the topic of sleep quality, we started our<strong> secondary research</strong> on articles and scientific papers, which resulted in three information clusters:</p><ul><li><strong>Sleep environment</strong>, related to temperature, noise, light, and other room conditions;</li><li><strong>Mental health</strong>, and how it correlates with sleep quality;</li><li><strong>Routines</strong>, and how they can improve sleep hygiene.</li></ul><p>The results that caught our attention the most and made us more aware of potential avenues to explore were that <a href="https://www.sciencedirect.com/science/article/abs/pii/S0301051100000351">meditation can help with restful sleep</a>, and that <a href="https://www.sleepfoundation.org/bedroom-environment/blue-light">exposure to blue light (screens and lights) before bedtime can have negative effects in health</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p0Y7qEHz7XVY3ZsvX58Nvw.png" /></figure><p>After a brief discussion, and without reaching an agreement, we decided to use <strong>primary research</strong> to solve our dilemma. We had planned to gather data with a quantitative method, a <strong>survey</strong>, and we would use it to uncover which is more relevant to our users: meditation or blue light filtering/distancing.</p><p>We resorted to the <strong>Lean Survey Canvas</strong> and took a long time to structure it. At first we were aiming to gather insights on users who have practiced meditation or blue light filtering/distancing before bedtime over the last month, but after internal discussion and feedback from our teaching staff about the potential sample size and insights we would like to obtain, we opened it to everyone and included minimal open-ended questions to gather suggestions on how an app could help our potential users.</p><p>While waiting for responses, we delves into <strong>competitor analysis</strong>, still not knowing which route to take. With that in mind, we decided to analyse 3 meditation apps, one blue filter app and one phone distancing app. Our key learnings were:</p><ul><li>Blue light filter apps provide features that overlap with native Android/iOS settings;</li><li>Meditation apps offer wide options of reminders, relaxation, music, exercises and reports;</li><li>The phone distancing app we analyzed offers gamification to reinforce behaviors.</li></ul><p>We had to advance with our project due to time constraints, so we decided to analyze the 45 responses obtained in our survey. This is not a significant sample and we would have to be cautious about this in a real-world scenario. However, as this project is in a hypothetical scenario, we were advised to continue with our analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LXxiptqPJMRrQ7KKgDj5Vw.png" /></figure><p>Considering users who practiced blue light filtering/distancing or meditation in their bedtime routines over the last month, we noticed that the majority (65%) practiced blue light filtering/distancing only, followed by users who practiced only meditation (25%) and both (10%).</p><p>Considering the limited time frame we were working with and the present data, and trying to narrow down the scope of this project, we decided to focus solely on blue light distancing/filtering from now on, as it seemed to be the most practiced routine among our potential users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fdbvcRj7MiLogE0ieT8jUQ.png" /></figure><p>When asked which blue light distancing/filtering techniques the users normally use before bedtime, the respondents selected native night modes on Android/iOS as the main one (57%). Another very popular technique seemed to be physically distancing themselves from devices, such as computers, phones, tablets and TVs (40%), while blue filter apps are only used by 9% of the respondents.</p><p>These results, paired with our previous perceptions and competitor analysis, made us understand that focusing on a filtering or dimming solution for devices wouldn’t probably be viable, as the native device features already seem to cover most of the users’ needs. However, physical distancing from devices seemed to be a popular technique where we could create some impact, and where the competition is lacking.</p><p>Analyzing our open-ended question on how an app could improve or help the users’ efforts of blue light filtering/distancing, we received many suggestions, such as reminders, filters that could gradually get darker over time until they force you to stop using the phone, automatic changing phone settings on certain times, but one of these stood out from the rest:</p><blockquote>“Reminding me to get off the phone. Counterintuitive, maybe, but I really think being away from screens in the evening makes a world of a difference”</blockquote><p>We would keep this answer in mind for further stages of this project. But for now, we needed to start narrowing the scope of our project.</p><h3>🎯Defining the problem</h3><p>To start defining what we wanted to solve, we decided to cluster all collected data in an affinity diagram, and after dot voting on the most important topics, we had 4 clusters to work with:</p><ul><li>Blue light;</li><li>Motivation;</li><li>Improving sleep habits;</li><li>App feature suggestions.</li></ul><p>As we were still lacking on sleep routines and blue light information, we decided to do an additional secondary research session. This was very important, as it allowed us to:</p><ul><li><a href="https://www.frontiersin.org/journals/public-health/articles/10.3389/fpubh.2015.00233/full">Understand that the user should avoid blue-light exposure at least 1h before bedtime</a>;</li><li><a href="https://www.frontiersin.org/journals/public-health/articles/10.3389/fpubh.2015.00233/full">Be aware that there are additional struggles of implementing screen “removal strategies” in adults and adolescents, as they make their own choices and are often influenced by peers and work</a>;</li><li><a href="https://www.sbm.org/healthy-living/blue-in-the-face-the-effects-of-blue-light-on-sleep">Read more about preventing the negative effects of blue light on sleep.</a></li></ul><p>With that additional research done, it was time to craft our user persona!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egXi-fKo1dzOz0B_0mSaaQ.png" /></figure><p>Jessica’s age and gender are a result of our sociodemographic questions present in the survey, while her bio, main goal, and frustrations match data from all our generative research.</p><p>We now had a persona to empathize with and keep in mind in all stages from now on!</p><h3>🚩 Problem statement</h3><p>To better understand her problem, we needed to clearly state it. For this purpose, we prepared a <strong>problem statement</strong> that would match Jessica’s main goal and frustration:</p><ul><li><strong>Users with sleeping problems</strong> need to find a way to <strong>create a healthy sleep routine</strong> because <strong>they can’t distance themselves from devices.</strong></li></ul><p>With Jessica’s problem present in our minds, we could start generating and prioritizing our ideas!</p><h3>💡 Ideation</h3><p>Using the <strong>Crazy8</strong> technique, our team thought about some ideas individually in 8 minutes, and then discussed them with the rest of the group. Our ideas included:</p><ul><li>an automatic lullaby song to be played by the phone at bedtime;</li><li>a marathon of hours slept per month, with a goal in mind;</li><li>sleep tracking using smart devices (smartwatch, smartband, etc).</li></ul><p>However, we prioritized other ideas that seemed more relevant and feasible to Jessica first, using the <strong>MoSCoW </strong>method and open discussions, focusing on what would be the MVP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8pWXEo2mO27cotuBQ2UIeA.png" /></figure><ul><li>Reminders were a fundamental feature of the app, to help the user be consistent with bedtime schedules;</li><li>Bedtime routines were also essential to our product, as keeping the user occupied with a routine that wouldn’t involve or have minimal blue light exposure would be a great way of establishing healthier habits and to keep the user away from screens at least 30 minutes before bed;</li><li>Gamification was our way of trying to implement a positive reinforcement loop, that would provide additional motivation to the user and make the hard task of creating new habits something much more fun.</li><li>The community feature would also be a great way for the user to display their achievements, meet people going through the same journey and feel a sense of belonging.</li></ul><p>Having these ideas to help Jessica with her sleeping problems, we had to understand which steps she would take within our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q3PhCPdGDLzzV8_PcqB3nA.png" /></figure><p>This <strong>taskflow</strong> of our happy path would allow Jessica to select a time to go to bed, choose one of the bedtime routine templates, put down her phone to complete her tasks while a countdown starts, and then another screen with a countdown while she sleeps. When she wakes up, she is greeted with a “Good Morning” screen, asking her how she is feeling today, and then she would be informed of how many points she won and how she is progressing on her sleep journey, our gamification system.</p><p>After delving into this taskflow and detailing it into a <strong>userflow</strong>, we started creating individual <strong>lo-fi wireframes</strong> of how we organized or visualized our ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*-1XN5B8yv460GgBQe4iofw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*MkaNoGqFeraFP15Wl0tZnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*xFW7K8fb2G0YxOM7RTqvVg.png" /><figcaption>Lo-fi wireframes for the Routine Selection, Mood Question and Score Progression screens, respectively.</figcaption></figure><p>We had an open discussion and dot voted to understand which elements and overall screens we preferred. It was a somewhat lengthy process, as some of the screens were pretty much a consensus (as the Score Progression screen displayed above) but we lost too much time discussing minor details about the design of others screens, and we weren’t happy with none of the wireframes for the home page. We eventually solved the dilemmas associated with conflicting ideas by just drawing and comparing them visually, combining elements, and setting time limits for our discussions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/266/1*ETq5aKY7v1EnS2aEpeqCow.png" /><figcaption>Lo-fi wireframe of the Home screen that emerged from our discussions.</figcaption></figure><p>With everything settled and our ideas aligned, it was now time to jump into <strong>Figma</strong>!</p><h3>🚧 Prototyping</h3><p>While setting up the <strong>mid-fi wireframes, </strong>we kept being attentive to each others’ work. While building each screen, we kept communicating to keep the wireframe as close to our collective vision as possible, while trying to keep the pages cohesive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*T0hCNxf05CfgMlXtqbIl3w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*mUNdSiP-6WhZhrmhuaBkGA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*APnnm5YNGqVTrWIWTAE2mA.png" /><figcaption>Mid-fi wireframes of the Home, Routine Selection and Score Progression screens, respectively.</figcaption></figure><p>After we finished working on all wireframes, we were ready to connect everything and turn it into our first working <strong>prototype</strong>, for testing purposes.</p><h3>👨‍💻 Testing</h3><p>We started planning our <strong>user/usability testing</strong> sessions, where we wanted to:</p><ul><li>Validate the concept of our app;</li><li>Test the happy path;</li><li>Gather feedback on corrections and potential improvements.</li></ul><p>After planning, we recruited 4 bootcamp colleagues to test our solution in moderated sessions. From these sessions, we had some confirmations, insights and suggestions. The main ones were:</p><ul><li>Users found the solution itself useful and valuable, especially the gamification system and the bedtime routines;</li><li>There was a lot of confusion when the Score Progression screen appeared, as they weren’t aware of any levels or progression until that screen.</li><li>Timers/countdowns in 2 of the screens were not that clear to our testers, as the timer itself was not that noticeable.</li></ul><p>Based on that feedback, our group iterated on potential fixes for these and other problems our testers had experienced, to craft the most pleasurable experience possible for Jessica. We also took into consideration the feedback that we received from colleagues and teaching staff in the design critique session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*gKZAJM1dEPxDXCmRbgrNsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*FJl71NS5xKzBemnGgNJSbQ.png" /><figcaption>One of our testers was confused about where to click to start the bedtime routine, so the option to customize the current routine was removed from the home screen. Instead, we added information or the gamification system, to keep users informed and mindful of their level and the next goal to reach. We also changed our gamification system from “steps” to “journey points”, so it wouldn’t be as confusing, especially for a well-being app.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*JwLgftfX4F9PNMGdetHvUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*ONbpTKTMP2A7RE-fdn_jHw.png" /><figcaption>The countdown was not as clear to our testers, and they felt that canceling the routine would be too definitive and would like to go back and change it. We added an option to change routine, changed from “Cancel” to “Stop” to make it clear they would stop the current routine, and improved the visual hierarchy of the countdown.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*j01k4073ytP4QXFiw_sx5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*qRh7gXCYulbWafmcNGNDLg.png" /><figcaption>The hours in our sleep tracker graph generated confusion for our testers, and having the mood emojis in the same section as the bars confused the testers even more, making them perceive that bars were referring to mood. We decided to create a separate section for mood tracking and added a number to each bar referring to the number of hours slept.</figcaption></figure><p>Having iterated on the feedback, it was now time to delve into UI Design!</p><h3>🎨 UI Design</h3><p>We started by validating our brand attributes, such as serenity, sleepiness, and calmness, with our<strong> moodboard</strong>, by sharing it with our colleagues. It was also at this stage that we brainstormed and had an open discussion on some potential names for the app, and came up with Zzleep.</p><p>We then extracted some colours from the moodboard, starting to combine them, and picked icons and typefaces that would fit well with our product and brand attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h4e-ObLcp7ha3shhpUNhEQ.png" /></figure><p>We wanted to have a darker tone of blue as a primary color for the background, to match with night mode apps and make it a more pleasant experience in the evening/night, which should be the time frame when Jessica would use our app. The icon pack, Material Symbols Light, is clean and light, which also matches with Montserrat, being a simple typeface as well. For our logo, we picked Joesfin Sans mostly because of how pronounced the “Z”s looked.</p><p>We had discovered our style, so it was now time to implement it on our screens! We had to take care of adding some <strong>components</strong> first, and then continued to build on that while designing our <strong>hi-fi</strong> screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*CyvhHkyYYJ6Wb0UN7iZD4Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*epN0nI6vB24TVWmOaQZBcg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ee_trZGK1x2ld3zXKH9zAg.png" /></figure><p>Having everything ready, we linked every page and finally had a working <strong>hi-fi prototype. </strong>The project was now ready to be presented to our class and, which was a crucial moment to obtain some general and specific feedback on the design options we made and on the prototype itself.</p><h3>🔄 Further Testing &amp; Iteration</h3><p>Our peers&#39; feedback was mostly positive overall, but there was a point of improvement that seemed to coincide with our teaching staff’s opinion on our prototype:</p><ul><li>Some of our screens were too crowded, as we didn’t leave much room for some elements to breathe.</li></ul><p>That feedback motivated me to continue improving this project after the course ended, mostly focusing on refining UI.</p><p>Additionally, to gather some more feedback to work on, I conducted other 3 moderated <strong>user/usability testing</strong> sessions with new participants, all based in Portugal, aged between 27 and 34. The most pressing issues we uncovered during these sessions were:</p><ul><li>Users felt the need to check information related to routine and bedtime before delving into their routine;</li><li>There was no functionality to check other weeks’ progression on the Profile screen;</li><li>Users also felt some screens were too crowded.</li></ul><p>With all this feedback (and some other points) in mind, it was time to go back to Figma and improve Zzleep’s hi-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*pNkfOBHNzyDhunaQ6oL9eA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*bRe6BYFGzIdQts9T-YiKzQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*SkCYPzacd7biQIHF_9uvRA.png" /></figure><p>This new version has some improvements, including:</p><ul><li>A reworked navbar, with the main action clearly highlighted, auxiliary text and selected/unselected icons and colours that help figure out the current page;</li><li>A confirmation screen where the user can check the detailed routine, bedtime, and edit both before starting the routine itself;</li><li>A new home page that allows the user to edit their bedtime and routine, with added functionality, and check some details about the currently selected options.</li></ul><p>This last functionality allows the bedtime routine journey to take 1 less click than the previous version, by having preselected bedtimes and routines and checking both on the confirmation screen, but is similar to the element removed during testing. As most screen elements were reworked, further testing would be required to understand if this new relationship between elements still raises problems with our users.</p><p>The iterations done resulted in the most recent prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UWaRTXNdbaeuNxcQLNaaZQ.gif" /></figure><p>Now the app would be ready to be developed, launched and used by Jessica, to help her craft and commit to healthier sleep routines. And, of course, we would improve it along the way!</p><h3>➡️ Next Steps</h3><p>As a hypothetical project, our journey to improve sleep quality ended here. However, if we had the chance to continue with it, we would:</p><ul><li>Design, prototype, and test the community feature;</li><li>Present our solution to relevant stakeholders;</li><li>In collaboration with developers, bring these ideas to life!</li></ul><p>After launching this app, it would be fundamental to track our impact. We would especially keep a close eye on:</p><ul><li>Number of registered users;</li><li>Number of active users;</li><li>Drop rates on app usage;</li><li>Percentages of successful blue light distancing nights per user;</li><li>Percentages for each mood of our mood survey per user;</li><li>Crossing both percentages, to understand if there is any positive correlation between them;</li></ul><h3>🌱 Growth</h3><p>This was a project full of highs and lows, and I’ve learned something about myself, UX/UI, and collaboration every step of the way!</p><p>The first learning I had was to <strong>control my expectations</strong>. Before the project started, we had planned to do user interviews, I also wanted to have a more complete and organized survey to ensure we had the best data we could to analyze, wanted to have more responses to the survey… But at the end of the day, we were constantly dealing with<strong> </strong>time constraints and we had to move on. All this made me feel insecure for a time, but I learned to accept that by understanding that we can never do enough research and that we had quantitative data to analyze and base our designs on. And we also did additional secondary research, which also helped to alleviate some of these thoughts.</p><p>The second learning was that <strong>communication is key</strong>. During some stages of this process, we were not communicating our ideas as effectively as we thought we were, which made us enter discussion loops and spend much more time than needed. When we delegated some tasks between the three of us, our lack of communication also made us roll back and realign, which could have been avoided. With these constraints, we learned to strategize, communicate clearly, and make sure it was understood with verbal feedback. If needed, we would communicate visually (which is especially helpful when discussing design options), and control the time we dedicated to our discussions.</p><p>Overall, it was a good and important experience in my UX/UI Design journey. I look forward to the next one!</p><p><em>Thank you for taking the time to read this case study! Please feel free to clap and leave constructive comments, I’d truly appreciate it!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aed214d4444" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Pinterest: A Dive into Heuristic Principles and Design]]></title>
            <link>https://medium.com/@leonardopinho27/enhancing-pinterest-a-dive-into-heuristic-principles-and-design-214de2648e81?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/214de2648e81</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[heuristics]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Thu, 21 Mar 2024 21:00:37 GMT</pubDate>
            <atom:updated>2024-03-25T08:24:45.213Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This was the third project developed during Ironhack’s UX/UI Design Bootcamp.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*FHPgkogrrg3Dp3hJ.png" /></figure><h3>📌 Challenge</h3><p>We had only <strong>3 class days </strong>to conduct <strong>heuristic analysis</strong> on a popular mobile app using <a href="https://www.nngroup.com/articles/ten-usability-heuristics/"><strong>Jakob Nielsen’s principles</strong></a>, ideate, and then replicate 5 to 7 screens on <strong>Figma</strong> with the changes we would make to improve them. And we would have to do all of it by ourselves.</p><p>In my case, I brainstormed a bit and checked all my installed apps, but had a very particular app in mind because of one specific issue I had experienced: <strong>Pinterest</strong>. I haven’t used it that much, but felt like it would be an interesting challenge.</p><h3>🎴The bigger picture</h3><p>Pinterest, as you might know, is a social media platform designed for discovering and saving images or videos (pins, as the app calls them) to their profiles or virtual pinboards.</p><p>Its development started in 2009 and, since then, it has become one of the go-to hubs for inspiration and creativity, used by <a href="https://business.pinterest.com/en-gb/audience/">498 million people</a> worldwide.</p><h3>🚨Heuristic Violations</h3><h4>For my first screen, the opened image screen, I gathered 3 potential heuristic violations.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/0*Y7BJsQ3gamS8Ke3M.png" /></figure><ul><li>When saving a pin to your profile on your board, you don’t have any option to <strong>undo</strong> your action. Therefore, this would constitute a violation of the <strong>user control and freedom principle</strong>, as users often perform actions by mistake and need an “emergency exit” when these situations appear;</li><li>Saved images on this screen go, by default, to the “Pins” section in the user profile. This might not be entirely comprehensive for new users, as the word “Pin” hasn’t been referenced before in either the feed or search and a new user could assume it goes to a separate section entirely. This could be a violation of the <strong>consistency and standards</strong> principle;</li><li>Clicking on “Saved” button as it is displayed in the photo just pins the same image to the profile as many times as you click it, generating more pins of the same image. Even though there are use cases where this could be useful, like adding pins to different boards, it’s more prone to errors. Therefore, could be a violation of the <strong>error prevention</strong> principle.</li></ul><blockquote>In further stages, I also considered that changing the text from “Save” to “Pin”would also respect the heuristic principle of <strong>making a match between the real world and the system</strong>, as when people want to put something in a pinboard, then say they are going to “pin it” and not “save it”.</blockquote><blockquote>Making significant changes in the nomenclature of the app, even if minor in one screen, would probably raise overall issues across the app. For exercise and practicing purposes, I decided to go through with it anyway, but this would need to be considered with more stakeholders.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JtsyTwA9fC0gsiWt587daw.png" /></figure><h4>On the feed screen, I also detected some heuristic violations, quite similar to the previous ones:</h4><ul><li>Once again, after long pressing the image and saving it to the profile/board, there was no way of <strong>undoing</strong> that action;</li><li>After saving, you would have to go to back to your profile to delete that pin, as saving it again in this quick menu would <strong>pin the same image</strong> again;</li><li>The white pop-up that appears on the top of the screen in the image page, as seen in the first example, doesn’t appear here. Instead, we get a miniature of the added photo on top of your profile icon in the navbar, and a very discrete “Saved! Profile” notice on the bottom left of the added image. This could be a <strong>violation of the consistency and standards</strong> principle.</li></ul><blockquote>For this screen, I also considered adding another violation, of the <strong>visibility of system status</strong>, as the “Saved! Profile” information might not be enough to inform the user of what is happening. However, as it wasn’t a complete violation as the system still informs the user, I decided to leave it out of this analysis.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pm6wiw9Ra1SETGV8bJ8Z-w.png" /></figure><h4>On the settings screen, I also detected a minor violation:</h4><ul><li>There is <strong>no confirmation prompt</strong> asking if the user really wants to sign out when they select that option. The app goes directly to the login screen, and that could be a violation of the <strong>error prevention</strong> heuristic principle.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L9viBP8DGuft6gn9JZW5yg.png" /></figure><h4>Finally, the search results screen made me analyze it more carefully:</h4><ul><li>What you would assume that are filter pills, are only suggestions that <strong>add words to the original search</strong>. So, the user might lose track of the status of their search and how many filters they applied, as the original search keeps being altered and there is no way to distinguish what was added and what was originally searched. This could be a violation of <strong>visibility of system status</strong>;</li><li>The “Profiles” pill, which only appears in some searches, acts differently from other pills, and its function is similar to the video and image filters inside the button on its left side. Also, the other pills are not consistent with what we normally find in other apps, where they normally act as search filters. For those reasons, we might be looking at a <strong>consistency and standards</strong> violation.</li></ul><blockquote>In further stages of this project, I also noticed that we could have a problem with <strong>user freedom and control</strong>, as to exclude a search term that was added by clicking in one of the suggestions, you have to keep clicking the top left arrow or edit the search itself, which limits user control severely. We would consider that during hi-fi design.</blockquote><p>With all these potential heuristic violations in mind, it was time to ideate!</p><h3>✍🏼Sketching</h3><p>As this project was an individual effort, I didn’t feel the need of start the ideation process with producing lo-fi wireframes. I had a clear picture of each screen I was to work on, I wasn’t going to change the screen radically, and I didn’t need to communicate my ideas to other team members.</p><p>So, I decided to first think about different ideas and, when I had a more definitive one, I’d put it on paper. This was done mostly to have a physical wireframe to refer to when putting the new screens together, to communicate my ideas in the design critique session, but also to save some time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*WFkYQqLeik72HRHE.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/882/0*lFmGKj8OBdPmWTZh.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/0*WFMPt0E-rGq2q8Dx.png" /></figure><h4>For the opened image/pin screen, I came up with these 3 solutions:</h4><ul><li>Added the undo function to the top white pop-up bar;</li><li>Changed the text from “Save” to “Pin”, to make it less confusing to the consumer;</li><li>Added a confirmation pop-up to remove the pin or add another one.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/0*2lWW8Bdkj5tcviPx.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/0*Ig-h7C-xDYdFzOY4.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/0*riFgLf6-TkEnDXU6.png" /><figcaption>From left to right: feed; settings/logout; and search results screens</figcaption></figure><h4>For the feed screen, I decided to:</h4><ul><li>“Reverse” the quick menu to help the user with being able to unpin an image without going back to the menu, but didn’t sketch that solution;</li><li>Solve both other problems (adding undo and making the system information more clear) with one solution, by leveraging the white top pop-up bar and adding it to this screen.</li></ul><h4>For the settings/logout screen:</h4><ul><li>I added a confirmation pop-up to prevent accidental logouts.</li></ul><h4>For the screen results page:</h4><ul><li>Remove the “Profiles” pill and leave it on the tune/settings section;</li><li>Highlight or checkmark selected filters, allowing the user to select or deselect them to customize the search without having to edit the search terms themselves;</li><li>Keep the search bar intact.</li></ul><p>With all this in mind, and physically next to me, I could start preparing everything on Figma.</p><h3>🧩 Style tile &amp; Components</h3><p>My first task on Figma was to actually prepare Pinterest’s style tile. I started by looking for the logo, and then extracted the colours, tried to find approximate typefaces and icons, and listed some UI elements for reference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*eFlr5RegBuXrlB3m.png" /></figure><p>After that, I was prepared to build components for the first time! They made it much easier and more effective to build consistent pages, and also make changes to the design itself.</p><p>Of course, I had to come back to this tile and build new components while building the hi-fi design replicas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*toaFv84Dx_xDukBV.png" /></figure><h3>📱Hi-fi</h3><p>Overall, the result of this project was very satisfying, as the produced screens look quite similar to the original screenshots, and the solutions seem to integrate well with the existing screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*04FaqA-EnlkYrZxIFgqfGw.png" /><figcaption>The modified opened image/pin screen, with the undo action and a confirmation pop-up.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LbwixCh4rysk-b39Q89rWQ.png" /><figcaption>The feed screen, with a modified quick menu and a confirmation pop-up, similar to the first example.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynK2A9w1LvEiP5CrSkx2Tg.png" /><figcaption>A confirmation pop-up for the logout action in the settings screen.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhK_5IHKuTyT143JFiIx3Q.png" /><figcaption>An alternative solution to the search results page, with a filtering system that highlight currently active filters.</figcaption></figure><p>I still had some doubts about the proposed solution, mostly the filtering system and the wording changes, but decided to keep them due to time constraints and because we would have a <strong>design critique</strong>. That would be the ideal dynamic to get feedback on these ideas and the project overall!</p><h3>🕵️‍♂️ Design Critique</h3><p>Similar to my colleagues, I had 15 minutes to present the work done over the last 2 and a half days and receive critiques from peers, the teaching staff and an invited UX/UI Designer. The feedback on the project was very positive from all involved, on identifying the heuristic violations, ideation, and quality of the replicated pages.</p><p>I also received feedback from the teaching staff and invited UX/UI Designer on some points I haven’t considered yet and could help me refine my solutions. Keeping that in mind, after the design critique, I decided to take a brief moment to iterate on what had been discussed. This was not mandatory, as the iteration was not a deliverable, but I decided to try it to see if I’d come up with solutions that would consider this feedback.</p><blockquote><em>“Having a big banner on top of the feed page might be distracting. Maybe I’d like something more discrete“</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_cLtSm6e0Ls78XSWjHbPaw.png" /></figure><ul><li>Returned to the app’s original idea, notifying that the picture has been saved/pinned to the Profile on the bottom of the picture itself, but added an icon for extra visual feedback, while maintaining the notification discrete;</li><li>Added an Undo function next to the status text.</li></ul><blockquote>“Filters without text can be confusing, maybe keeping the suggestion words in the search field is a workaround”</blockquote><blockquote>“The Pinterest filters are not proper filters, they are just suggestions”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dcCVcBWYU10Uo-H3-83Yww.png" /></figure><ul><li>Added color coding to each selected filter. That would keep the space for new filters intact while informing the user which filter belongs to each word, supporting the miniature picture frame;</li><li>Kept the original search term in white, to inform the user which is the original search term.</li></ul><blockquote>This solution could represent a problem in accessibility, as the images in the selected filter pills would be the only support for colorblind users.</blockquote><p>With that done, it was finally time to move to another project.</p><h3>🌱Growth</h3><p>This was a very challenging process, as I felt somewhat isolated from my colleagues, and didn’t have their opinion on my work. I did resort to them from time to time, but it wasn’t as present as in other groups.</p><p>It was also a very valuable learning experience, as it made me more aware of the heuristic principles and improved my critical thinking. It was also an excellent opportunity to practice some of my newly acquired Figma skills. Using components was a blast!</p><p>The main takeaway from this project is that no digital product is perfect, but we should strive to improve it, as there is always room for improvement.</p><p><em>Thank you for taking the time to read this case study! Please feel free to clap and leave constructive comments, I’d truly appreciate it!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=214de2648e81" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crafting Experiences: Applying Design Thinking to Wedding Stationery Ordering]]></title>
            <link>https://medium.com/@leonardopinho27/crafting-experiences-applying-design-thinking-towedding-stationery-ordering-b2316d49581f?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2316d49581f</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Sat, 16 Mar 2024 23:17:40 GMT</pubDate>
            <atom:updated>2024-04-02T12:52:01.513Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This was the second project developed during Ironhack’s UX/UI Design Bootcamp.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTeGwUm-FM1HCPVja6eA_w.png" /></figure><h3>📌 Challenge</h3><p>For the second project, we were challenged to partner with a <strong>real business</strong>, in our case a local shop, helping them create or improve their online presence. We would have only 9 class days to meet the stakeholders, empathize with the users, define the problem, brainstorm, implement &amp; test our ideas, and finally produce a hi-fi prototype of our solution.</p><p>During these 9 days, I worked with André and Joana for a local print shop in Portugal, called “<strong>O Principezinho</strong>”. Let me explain more about them…</p><h3>👨‍💼 Context</h3><p>“O Principezinho” is a family-owned graphic services &amp; print shop based in a medium-sized city in Portugal. They provide a wide range of products and services, however, their main focus over the last decade has been <strong>wedding stationery</strong> for couples and wedding reception companies. They have built a solid reputation in that sector and have a strong online presence in wedding-related sites.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*JJ55OK-BNvN5Ttwl.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*j_djIe7owd0lYEE1.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/794/0*HCmHDampHyxLXpcw.jpg" /><figcaption>Some of the wedding invitations done by “O Principezinho”</figcaption></figure><p><strong>Customization</strong> is a big plus of their services. A wedding is a very special event for the couple, and, with that in mind, “O Principezinho” needs to make sure they craft the perfect stationery, that reflects the couple’s vision for the big day. They help choose, provide virtual and physical examples, and put their human touch into every project they work on.</p><p>We wanted to help the company get even closer to its customers, but we were unsure how we could do that effectively. So, we arranged a call…</p><h3>🛣️ The road not taken</h3><p>From the <strong>stakeholder interview</strong>, we were made aware that their website was not their first means of communication with their clients. They normally receive messages through wedding-related networks, social networks or couples just go to the physical store directly.</p><p>Digging deeper during our conversation, we discovered there was <strong>no means of ordering some stationery directly from the site or even submitting a quote/order request. </strong>This was something the stakeholder mentioned as a significant constraint, as requests come from many places, and could be difficult to track. He mentioned he wanted to build a <strong>contact form</strong> with some details for the<strong> client to reach out to them directly</strong>.</p><p>The stakeholder also mentioned their interest in removing the marketplace features from his website, as the sales they make from products there are irrelevant to the business. He was thinking of <strong>turning the site into a portfolio</strong>, making it less busy, and showcasing their past work more effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ts0g4GMxpYjx1aDi.jpg" /></figure><p>It was clear to our group that we had <strong>two options</strong>:</p><ul><li>Preparing a website redesign;</li><li>Enhancing the client-business communication by streamlining the quote request process.</li></ul><p>During the latter stages of our interview, our group asked what would be the priority to work on, so we could have an idea of what to prioritize, and the stakeholder mentioned the quote/order request once more, which made us aware of his preference.</p><p>Our group had an internal discussion after the call (even with the teaching staff) and decided to <strong>enhance the communication between client and business for quote/order requests</strong>, not only because the website already showcases the company’s portfolio, but also because the process of receiving a request and getting a quote seemed to be quite disorganized and much less streamlined than desirable. Also, it matched the stakeholder’s priorities.</p><p>Now that we had decided on the road to take, it was time to start uncovering couples’ main problems when buying wedding stationery!</p><h3>🔬 Our Research</h3><p>During our <strong>secondary research</strong>, we found some emerging themes that gave us a better understanding of the couples’ biggest struggles when buying wedding stationery. Our research consisted of various elements, such as <a href="https://link.springer.com/article/10.1007/s10603-021-09488-y">articles mentioning societal pressures and their impact on potentiating consumption to create a unique wedding experience</a>, <a href="https://www.theknot.com/content/average-cost-of-wedding-invitations">internet articles on the price of wedding invitations according to the printing methods</a>, and even <a href="https://www.reddit.com/r/weddingplanning/comments/35pvrx/picking_wedding_invitations_has_me_in_decision/">forum rants about the amount of options for wedding invitations</a>. All of it resulted in these 4 clusters:</p><ul><li>Budgeting &amp; extra costs;</li><li>Planning &amp; time management;</li><li>Supplier/seller concerns;</li><li>Choice uncertainty.</li></ul><p>To have a better understanding of these topics, we decided to conduct <strong>user interviews</strong>. Our goal was to:</p><ul><li>Have a better picture of the process couples go through when choosing and buying wedding stationery;</li><li>Uncover the main factors that influenced their decisions;</li><li>Be aware of the constraints they experienced;</li><li>Discover potential improvements.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ElJtT86xNXrT1JLGD-NwTQ.png" /></figure><p>We interviewed<strong> 5 participants who had already married or were already preparing stationery for their wedding</strong>. The interviews were insightful and allowed us to empathize with them, and understand their main struggles and goals.</p><p><em>Our generative research had a limitation that our group would keep in mind, especially in the next stage: </em><strong><em>it was not focused on the Portuguese market</em></strong><em>, which is where “O Principezinho” operates. Due to time constraints, we didn’t find information focused solely on Portugal, and we didn’t have the opportunity to recruit and interview Portuguese participants.</em></p><h3>🎯 Defining the problem</h3><p>To make sense of all the information collected during the generative research phase and find common themes in the data, we organized the main insights in an <strong>affinity diagram</strong>. The result was bigger clusters referring to constraints, processes, ideas, and highlights, but our dot voting pointed us to the same direction:</p><ul><li>Budget constraints;</li><li>Time constraints;</li><li>The need for customization options;</li><li>The overwhelming amount of options available in the market.</li></ul><p>With all this information and conclusions in mind, it was time to craft our <strong>user persona</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fz5J4mhOPGOcNNoSE9d7kw.png" /><figcaption>Maria, our Overwhelmed Bride-to-be</figcaption></figure><p>Maria’s goals, needs, and frustrations directly align with our results from generative research (mostly user interviews) and would allow us to empathize with our users more effectively. We were now designing a feature for Maria, keeping her in mind throughout the rest of the project.</p><p>We also did a <strong>Customer Journey Map</strong>, to better empathize with Maria’s experience. That made us more aware of how she feels during the wedding stationery ordering process and allowed us to identify opportunities to help her.</p><p><em>During this process, we also considered having a second user persona for someone who already has their design made and only wants to print it, as this is a pattern that emerged from some of our user interviews. After receiving feedback during the </em><strong><em>design critique</em></strong><em>, we decided to stick with just one persona. The time frame was quite challenging, and even though we would keep those users in mind as well, we wanted to focus on Maria’s needs and frustrations.</em></p><p>At this stage, we decided to break down the main problem into 3 sub-problems to be tackled by our solution, creating our <strong>problem tree</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1NW_ftACAAluohq1b8lxw.png" /></figure><p>Now that Maria’s problems were fully defined, we needed to think about how we could help her with our solutions.</p><h3>💡 Ideation</h3><p>Our team decided to use the <strong>Crazy8</strong> dynamic (8 ideas each in 8 minutes) to brainstorm some solutions for Maria’s problems. The list of ideas generated in this dynamic included special pre-defined matching stationery packages, an AI-powered tool to extract some ideas from the couples’ written text, but we opted for other features that would be more feasible and impactful for Maria:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IlRWpLdfDo_JLowKwdLkcw.png" /></figure><p>The quiz, on top of some form elements, would help Maria, guide the process: by answering some questions about aesthetics and theme, she would have suggestions from the company&#39;s portfolio that match her preferences. It would probably be a less overwhelming alternative that values her ideas for the wedding stationery.</p><p>The estimated total cost &amp; time to deliver trackers are features that would be implemented to help Maria plan her stationery, by having a level of certainty in the order. Of course, these are just estimations and, for them to be more accurate, they would need to be based on many factors to be discussed with the company. However, this would align well with keeping the customization factor, which is a staple of our company, while providing some safety to the couple.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8jHuEkpvXXJ_L5pU7be_Q.png" /><figcaption>Our task flow for the quiz/get our suggestion happy path.</figcaption></figure><p>Our <strong>userflow</strong> considered users who already have their designs ready and only need printing, and users like Maria, who need further guidance and will be suggested pre-made designs with the option of customizing them. Maria would have the option to upload reference photos and let a tool match them with similar-looking stationery in the company’s portfolio, take the quiz for suggestions, or browse the portfolio on her own.</p><p>For this exercise, and because it would be the more challenging and happier path, we decided to focus on the quiz option and elaborate<strong> lo-fi wireframes</strong>, having our thoughts about the features expressed in paper, and deciding on which options we should pick.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*k68jCIXCAHx5TwMjzgVRtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wl3ez42Ne0TiGmq43jcgRQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_7xO5-LIsA2U-42BJ2RsSg.png" /><figcaption>Some of the lo-fi wireframes for: quiz: suggestions; and confirmation screens.</figcaption></figure><p>After some open discussion and dot voting, it was clear that the general structure and progress bar of the first image was the way to go, that it would align well with the card elements from the second one, and the third image, referring to the request confirmation screen with an estimation of delivery and budget, as well as an image of the selected stationery was the way to go.</p><p>It was now time to jump into <strong>Figma</strong>!</p><h3>🚧 Prototyping</h3><p>After some asynchronous efforts and synced corrections to make the prototype cohesive, we had our <strong>mid-fi wireframes</strong> ready to be connected and turned into our first working <strong>prototype</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8tJsuw2yS8C0Fmg6j86-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nH4KHAlSVtoVjPOlVkLStQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wFnaefFQPbsylPwgJX0SHQ.png" /><figcaption>Some of the mid-fi wireframes for: quiz: suggestions; and confirmation screens.</figcaption></figure><p>For testing and due to time constraints, our prototypes would only focus on wedding invitation cards, as they are the main product our company works on, but the features could be extended to other stationery items.</p><p>We were now ready to test our solution with some users and get their feedback and improve on it!</p><h3>👨‍💻 Testing</h3><p>We started planning our <strong>usability testing</strong>, formulating questions and tasks in an open brainstorming and discussion session, around two goals:</p><ul><li>Evaluating the ease of use of the flow;</li><li>Validating the quiz feature.</li></ul><p>After that, we recruited 4 bootcamp colleagues who had planned/were planning their weddings and ran moderated testing sessions.</p><p><em>Once again, the test is conditioned by cultural and selection limitations, but due to time constraints, we felt that having those testing sessions would still be valuable to iterate on.</em></p><p>The users found our solution truly valuable, something that would have liked to use themselves. Some of them also left clues on what we should iterate on, considering their struggles, their train of thought throughout the test, and their suggestions. We also had the opportunity to present our prototype in a <strong>design critique</strong> session, which helped with some additional feedback to work on.</p><p>Here are some of our iterations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8tJsuw2yS8C0Fmg6j86-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0Q3QP2cShP4VHwxxE-s3w.png" /><figcaption>Breadcrumbs were removed and additional sub-steps were added to the progression bar, to help with the sense of progression until getting the wedding invitation card suggestions.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0j0qhXtPWbLTZg-7aMi3PA.png" /><figcaption>A pop-up with a zoomed-in photo of the card was added to the suggestions screen, granting the user the ability to see the card more clearly.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fRxT6gWGHPYlj1kQkvfgdA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bmvr8TZaYbzWrZBWzWo37g.png" /><figcaption>Questions referring to Couple Names and Wedding Date were brought to the top of the page, as the users consider them the more relevant and important ones. The size of the estimation tracker was also reduced, as suggested in the design critique session, making the page more harmonious and lighter.</figcaption></figure><p>With these changes done, it was time to start thinking about creating our final and more polished prototype!</p><h3>🎨 UI Design</h3><p>After validating our brand attributes, such as romance and elegance, by sharing our <strong>moodboard</strong> with our colleagues,<strong> </strong>we started preparing our <strong>style tile</strong>. It was a process that made us test some colour, icon and typeface alternatives, comparing them constantly, but reached a common place after some tries:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CglGDatNWVyENHtxjdkcTQ.jpeg" /></figure><p>We leveraged the floral/herbal elements of bouquets and reception gardens for colors and images, and tried to choose icons and a typeface that would match an informal but elegant look. We also had to redesign the company’s logo, to make it simpler and more efficient.</p><p>We had discovered our style, so now it was time to implement this vision to our screens and prepare the <strong>hi-fi prototype</strong> and<strong> </strong>the <strong>responsive web design </strong>for mobile and tablet!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2WUAtiEnN1eS0SW3sLOEwg.gif" /></figure><p>We added some elements at this stage, such as a scroll bar and additional product questions, to make the prototype as close to a real product as possible, and we were quite satisfied with the results.</p><p>Hopefully, Maria will too! :)</p><h3>➡️ Next Steps</h3><p>With our project concluded and presented to our cohort, our journey ends here. However, if we were in another context, our next steps would be to:</p><ul><li>Test the solution with Portuguese participants and iterate on it;</li><li>Present the solution to the stakeholder;</li><li>Replicate to other stationery items and functionalties;</li><li>(If possible) Improve the website.</li></ul><p>After launching this specific feature, we would want to track the impact of our solutions. We could track:</p><ul><li>The average time between first quote request and stationery sent;</li><li>Number of order requests coming from the feature;</li><li>Compare the number of uses for each option (Quiz, Upload Reference, Browse options &amp; Submit a Design);</li><li>Reviews on wedding-focused sites regarding the new feature;</li><li>Stakeholders’ perceptions of the new feature.</li></ul><h3>🌱 Growth</h3><p>This is the first Ironhack project we did from end to end, and it was a joy to work on! We had the freedom to apply as many tools for each stage of the Design Thinking process as we saw fit, and we had to balance everything considering time and effort (having our informal impact effort matrix in our heads). It allowed us to have <strong>critical thinking </strong>and consider the impact of our actions and plans.</p><p>There were definitely some challenges. <strong>Time management </strong>was the first one we came across and probably the hardest to tackle, not only because we were one of the smaller groups, but also because we had a small time frame to work with. Also, during the style tile elaboration, hi-fi designing, and prototyping, one of the group members had to step away due to personal problems. Our group had to <strong>delegate &amp; prioritize</strong>,<strong> </strong>allocate<strong> </strong>tasks between the two remaining members, and work overtime to be able to complete the project on time. We successfully did it and, even though it was quite stressful, it allowed us to be more strategic and resourceful, while reinforcing the importance of <strong>communication</strong>!</p><p><strong>Focusing</strong> on the tasks at hand was also quite difficult, as we still have the tendency to think about the next steps and want to keep pace with the other groups. We tried to keep in mind that every project has its own timeline, that every step is fundamental and the next steps are, in a way, a result of the current ones, so our creativity and energy should be focused on the tasks we are doing.</p><p>Overall, it was a great experience, and I look forward to the next one!</p><p><em>Thank you for taking the time to read this case study! Please feel free to clap and leave constructive comments, I’d truly appreciate it!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2316d49581f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Case Study 1: Moving abroad made easy (well, easier)]]></title>
            <link>https://medium.com/@leonardopinho27/ironhack-case-study-1-moving-abroad-made-easy-well-easier-2ff229b40213?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ff229b40213</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Sun, 03 Mar 2024 16:10:18 GMT</pubDate>
            <atom:updated>2024-03-13T11:42:12.559Z</atom:updated>
            <content:encoded><![CDATA[<h3>Bureaucracy done right: Moving abroad made easy (well, easier)</h3><p><em>This project was developed during the first week of Ironhack’s UX/UI Design Bootcamp.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/0*QN-4ljLdI4M3FqzR.jpg" /></figure><h3>❓ The Context</h3><p>Starting a new adventure, seeking better job opportunities, finding refuge… There are many different reasons for someone to move abroad. This colossal change comes with different challenges, but perhaps the most unavoidable and necessary might be the multiple <strong>bureaucratic tasks</strong> associated with legalizing the journey to the destination country.</p><p>With that in mind, Ironhack challenged my group (me, Andrew, and Astrid) to <strong>design a solution that might help migrants find information, complete tasks and successfully get their paperwork done to start their lives in the new country</strong>. We had only 6 days to tackle this “wicked problem” and develop a user-centered solution. Throughout this article, I will recount the journey we undertook to arrive there, as well as the key learnings this quest brought us.</p><h3>🫂 Understanding the users</h3><p>We started the project with <strong>secondary research</strong> on the topic of immigration. Our general search made us more aware of the challenges migrants might face, such as:</p><ul><li>Bureaucracy associated with permits to legally work/live in a country;</li><li>Language barriers, that play a key role in integration;</li><li>Searching and securing housing, due to the legal situation and lack of knowledge of the host country legislation;</li><li>Access to healthcare;</li><li>Barriers to employment due to legality and prejudice.</li></ul><p>To understand this phenomenon better and complement our research, we prepared an interview guide that would touch on many of the aforementioned challenges and conducted <strong>user interviews</strong> with 3 bootcamp colleagues who migrated to another country.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-ZulsmVhahOcqj7RVgS7g.png" /><figcaption>Some quotes taken from the user interviews</figcaption></figure><p>Even though they migrated from different countries to either Germany or France, many of their experiences had striking similarities, such as facing language barriers, general confusion with documents and not knowing exactly where to find them.</p><p>At first glance, without analyzing the qualitative data extracted from the secondary research and user interviews, it became obvious that these two themes would be recurrent and we would need to address them.</p><h3>🎯 Defining the problem</h3><p>To make sense of all the information collected during the generative research phase and find common themes in the data, we organized the main insights in an <strong>affinity diagram</strong>. Our clustering resulted in 5 different themes:</p><ul><li>Language barriers;</li><li>Document accessibility &amp; bureaucracy related issues;</li><li>Integration and cultural barriers;</li><li>Accessing services;</li><li>Housing.</li></ul><p>Resorting to dot voting once more, we highlighted Document Accessibility &amp; Language as the most important trends in the collected data. Having that in mind, it was time to elaborate on our <strong>user persona</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17MRugDHB_8N-p-2mfcspw.png" /></figure><p>Helen, our Expat Adventurer, came to life in a very consensual brainstorming process. Our group already had a clear idea of what her goals, needs, and frustrations would be, and all other characteristics were based on our interviewed users. Now, we had a persona to empathize with and keep in mind throughout the rest of our journey.</p><p>The last step to understand how we could help Helen was to clearly state her problem. At this stage, we decided to go for a <strong>problem tree</strong>, as that way we would be able to break down the problem by identifying 3 sub-problems to be tackled by our solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvfBxV_p6VmkLiaLH-C7aw.png" /></figure><p>With Helen’s problems and sub-problems finally defined, it was time to think about actually solving them.</p><h3>⛈️ Ideastorming</h3><p>Using the <strong>Crazy8</strong> activity, each team member tried to think about ideas in 8 minutes. The goal was to have 8 ideas of potential features or solutions for Helen’s problems, even if they sounded farfetched or absurd to us. We did end up using a bit more time to complete the goal and our Leading Teacher’s theory that the best ideas would be the last ones was proven.</p><p>Our list of ideas included some honorable ones such as an exchange matchmaking feature for people moving to each other’s countries, an AI-powered chatbot to help the user with doubts on documents and translation, and even an AR feature to locate certain institutions or translate documents using geolocation and the phone’s camera.</p><p>Some of our more voted and consensual ideas made the cut to the <strong>impact effort matrix</strong>, where we had to make choices on which would be more valuable/impactful to Helen:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soX-HkOLjJYZ_bDVU67yJw.png" /></figure><p>The dashboard felt like an obligatory feature for a hypothetical scenario where we can make assumptions. It would be more difficult to implement, as a simple list would be easier to update and maintain, but having the possibility of having the documents listed, as well as filling or uploading them in the app is much more practical and useful to the user.</p><p>For the other two sub-problems, where we were trying to provide translations and instructions on how to fill documents, we went with the same feature. Hiring and certifying local assistants would require much more time, investment, and maintenance, inside and outside the app, however, in a hypothetical scenario, it’s something that would solve both sub-problems and raise trust in the app and the actions the user needs to take. It would be less prone to errors and much more immediate than Helen having to write their doubts on an online forum, and than relying on translation tools, which are notorious for not providing accurate results.</p><p>Now that we had an idea of which features Helen would like to use in our solution, we had to reach an agreement on <strong>how</strong> Helen would use it, the screens she would have to go through to submit her documents correctly. We put together some individual <strong>userflows </strong>and, after some discussion and understanding of each other’s perspectives, we converged on a common userfow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5dee_1cJktAbDzFgM6n-tA.png" /></figure><p>This userflow puts a big emphasis on filling the information on expatriation right after the registration process, and then arriving to our homepage, which should be the document dashboard. Throughout the process, Helen can ask for help anytime, but we highlighted 2 moments where help might be most needed. The goal is to submit the document successfully and be certain it was well executed.</p><p>Having agreed on this flow, it was now time to start understanding how we could assemble the “bones” of this skeleton. With that in mind, each of us started sketching, using good ol’ pen &amp; paper, our vision for the various screens of our app, always following what had been discussed in the userflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/514/1*88kJ1P5gP_Xwqbi_YeFa_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*St2Nhz0fLJGmONZ3pA2JEQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*4v52POilHGPCt9GQqb3GDA.png" /><figcaption>Lo-fi wireframes for some screens, in order: the expatriation info screen, the confirmation screen and the dashboard.</figcaption></figure><p>After an open-minded discussion on what each others’ <strong>lo-fi wireframes</strong> did better and what we thought were the best ideas, we converged and did a final lo-fi wireframe, to make sure we were on the same page. We had everything we needed to start working on our prototype.</p><h3>🦴 <strong>Assembling the skeleton</strong></h3><p>Using <strong>Figma</strong>, our team coordinated asynchronous efforts to make our solution come to life, replicating the previous screens with more detail, relevant content, and icons, therefore creating <strong>mid-fi wireframes</strong>. Here are some of the screens we worked on, and how they looked after being replicated on Figma:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*NbriqLp195_S46aV0uuGxQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*ojGX5TlQX2EfFPlfEYs0sA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*xFJ-9MAzn1oXwksETSsUyg.jpeg" /><figcaption>Some final lo-fi wireframes for the information confirmation, dashboard and chat screens.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/418/1*p3BiZH6JfpDKP7kVZ_8bYQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*ryfg5U8nxgiSfZSjn_fQMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*arZJhGdETtmpLFzkn_UvKQ.png" /><figcaption>Mid-fi wireframes for the previously mentioned screens.</figcaption></figure><p>After assembling these screens (and 4 others), we discussed our work, made some minor changes (e.g. arrows to help navigation in the dashboard, certified badge next to the local assistant name in the chat) and felt it was the appropriate moment to start connecting everything, which resulted in our first working <strong>prototype</strong>. We were now ready to test our solution with some users and collect their feedback.</p><h3>👨‍💻 Test to Learn</h3><p>We wanted to make sure we would extract the most out of every <strong>usability test</strong> interview we had, so we started by understanding the goals of our tests, which were to evaluate the ease of:</p><ul><li>Finding a document in the dashboard;</li><li>Connecting with a local assistant;</li><li>Filling out required documents;</li><li>Submitting them successfully.</li></ul><p>After defining our testing guide with tasks and questions, resorting to individual brainstorming and dot voting, we recruited 4 bootcamp colleagues who migrated to another country and ran the tests.</p><p>The results were very positive and insightful! Our users felt the solution was very valuable, smooth, and easy to use and would recommend it to family/friends. However, they also left some clues on what should be improved, which we promptly did after all tests had been conducted.</p><p>These were some examples of our <strong>iteration</strong>, all based on how our testers used the app, their struggles, and their direct feedback:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1tMhVUU6w5prVL-Hl3PZog.png" /><figcaption>We added a percentage to make the progress bar more noticeable, and made the “Mark as Completed” button not as relevant as the others, as it wouldn’t be as used or relevant as the other buttons, “Fill” and “Details”.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAqriGGc39Ir34bQMekLAg.png" /><figcaption>We added a period of time in which we intend to provide feedback to our feedback text, and clarified on what the previously named “Return to Home” button did, which was to return to the dashboard rather than the beginning of the flow (the expatriation info screen),</figcaption></figure><h3>🏆 Our final prototype</h3><p>Having iterated on the usability test results, it was time to present our final prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gP4qMUyLXf98GL6DuzK01A.gif" /></figure><p>For this project, we were only required to do mid-fi prototyping, so this is where our journey ended. If we had more time to continue, we would have done another round of testing, to see if our changes would be well received, and then proceed to hi-fi prototyping. Afterward, we would have a final presentation moment of our solution to the appropriate stakeholders, to collect their feedback and work on it, so our product can respond to the users and business goals.</p><p>After launching, it would be interesting to track our impact by the number of registered users, check which ones completed the full list of documents successfully, dropoff rates, time to complete the expatriation process, average number of local assistant requests, and even the validation rates of the documents.</p><h3>🌱 Growth</h3><p>This was our first Ironhack project and the first time we applied the Design Thinking process in a group context. It was definitely a challenge, specially considering the timeframe and the unfamiliarity had with the methods, but it was a very rewarding experience. Building a product that could have such an impact in such an unpleasant experience as expatriation bureaucracy, and seeing people interact with it was an absolute joy.</p><p>During this project, I learned to <strong>trust the process</strong>, even if it felt that we wouldn’t have time or that our efforts in the empathize stage would lead nowhere. I also learned that, during the design process, we need to <strong>make tough choices</strong>, being mindful of the scope, the group&#39;s ideas, and perspectives.</p><p>I hope Helen likes our product too! :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ff229b40213" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Leonardo Rodrigues_Challenge2]]></title>
            <link>https://medium.com/@leonardopinho27/ironhacks-prework-leonardo-rodrigues-challenge2-0509f3c9d421?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/0509f3c9d421</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Thu, 01 Feb 2024 13:10:18 GMT</pubDate>
            <atom:updated>2024-02-01T14:34:41.857Z</atom:updated>
            <content:encoded><![CDATA[<p>This article was written as the second challenge for the UX/UI Design Bootcamp at Ironhack. The goal was to choose an app, identify and detail a user flow, wireframe the screens, and prepare a prototype using Figma.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*unNx88xfBX69SnYD.jpg" /></figure><h3>App &amp; User Flow</h3><h4>The chosen app</h4><p>I started this exercise by browsing through my installed apps to decide which one I should analyze, and picked <strong>Google Maps</strong>. My decision has to do not only with Maps being one of the prime Google products, but also because it was probably one of the first apps I installed when I started using smartphones, and it’s still one of the apps I use regularly, either on foot, when driving or traveling by train. Additionally, I believe the previous challenge, focused on a new feature for Citymapper, also played a “subconscious” role in this decision.</p><h4>The chosen User flow</h4><p>I also had to identify a user flow I wanted to work in, taking into consideration that it should be between 5 to 7 screens long. I decided I wanted to detail a navigation flow, where the <strong>user starts the navigation from his current location towards a certain destination by car</strong>. This is probably one of the most frequent flows I have gone through and seen other users experience as well, especially when traveling to uncommon or unknown locations. What is also frequent, in this scenario, is that the user verifies if the destination he picked is the correct one by analyzing the location details first, as well as the route Maps picks, so I won’t be using the navigation button on the first screen, as it skips some of these details, and will search for the location first, and only then start the navigation. I also needed to practice my wireframing skills with slightly different screens, so this is an ideal scenario.</p><h3><strong>Analysis</strong></h3><h4>UI Elements</h4><p>Analysing the app itself, I identified some UI elements I’d be using in this exercise. For <strong>input</strong>, the app uses mostly buttons and single-line text fields. Of course, you can also select options from lists and, even though I won’t be using it in this task, the app also has date &amp; time pickers for departure and arrival. The main <strong>navigational </strong>element identified is the search field, but the app also has icons and chips. The <strong>information</strong> elements are notifications (but those won’t be used in this exercise) and in a screen we will see <strong>containers</strong> with destination info and photos.</p><h4>Task</h4><p>The selected main task of the user flow is, as previously mentioned, starting the navigation from the current location towards a certain destination by car, quickly verifying the destination and route. With that in mind, I drew the intended user flow in lo-fi. Some details are missing from this first wireframe, but the general idea and flow is present:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2hBhbRaNdLqpeD2Pdf_kEw.jpeg" /></figure><p>To break down this main task, I divided it into subtasks that need to be completed for the main task to be successful:<strong> opening the app: checking current location; searching for the intended location (destination); confirming if the destination is correct; checking the highlighted route information; and starting the navigation itself. </strong>To have a better visual representation, I also drew a task diagram using draw.io and presented it to regular Maps users I know personally, also adding the actions the users would take if the results are not what they intended:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/338/1*s0qCv2uQOLIUQjXV8v5UhA.png" /></figure><h3>Wireframing &amp; Prototyping</h3><p>Using the <strong>Figma</strong> knowledge acquired and developed in previous exercises and <strong>Ironhack’s Wireframe Kit</strong>, I put together 6 screens, intended to be hi-fi wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7MyLwiKQqwrtwWk9ZmT_Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7S088RtRetvUVk4Oj_cg4g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rw37a9EO8DbYxTFHTQc3MQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyDNDAg1rs845uW1ItkPfA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PvHrhrZa6_O3sLnIrAC3IQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Dd7RReZiGasQ8QroV_ZUQ.jpeg" /></figure><p>Then, I connected the screens and UI elements with actions to make it more interactive and a usable prototype, representative of the analyzed user flow specifically. I also played with horizontal scrolling &amp; dragable elements, but that was just out of curiosity and trying to replicate the app’s behavior.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FCVaOl82LEw0YRFS69FqvS2%2FChallenge-2---Ironhack-Prework%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-8%26viewport%3D67%252C521%252C0.05%26t%3DlcS8ndX3bQ5jpiWu-1%26scaling%3Dscale-down%26starting-point-node-id%3D1%253A8%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FCVaOl82LEw0YRFS69FqvS2%2FChallenge-2---Ironhack-Prework%3Fpage-id%3D0%253A1%26type%3Ddesign%26node-id%3D1-8%26viewport%3D67%252C521%252C0.05%26t%3DlcS8ndX3bQ5jpiWu-1%26scaling%3Dscale-down%26starting-point-node-id%3D1%253A8%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F3ca244c2-737e-4638-aad0-e19bc53ca9f1%3Fheight%3D144%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/0d9a7857e580488e515b9b8e31bcf577/href">https://medium.com/media/0d9a7857e580488e515b9b8e31bcf577/href</a></iframe><h3>Conclusion</h3><p>Overall, it was a really interesting and motivating experience! The user flow I picked might not be the quickest way to complete the task, but it is definitely a popular one across the users I personally know and allowed me to have more variety in the screens I wireframed. That enriched the work and made me face different challenges.</p><p>At first, I struggled with my drawing skills while doing the lo-fi wireframes. I know they are not supposed to be beautiful, but I still want them to look good, especially when posting them in an online article. However, they fulfilled their purpose of having a quicker wireframe to work with and providing the basis for a more detailed one. I also struggled with the task diagram, as I had a constant feeling that I was forgetting some detail or action the user does, but after numerous analysis, I believe it’s fairly accurate. Lastly, what I struggled with the most was defining with elements to add to wireframes, as I felt they would be incomplete without some icons for example, even if they were not that relevant. That prioritization is definitely something I need to work on, and is something I didn’t practice that much in this exercise because Ironhack’s Wireframing Kit was very convenient and made adding elements a breeze.</p><p>What I enjoyed the most was exploring Figma and building in it. I tried to be more careful with organization, with spacing and framing, and also felt comfortable and motivated to explore new ways of working, more complex tasks and some of Figma’s features. It was also very pleasurable to see the prototype coming to life, and that is probably why I went a bit too far trying to make the prototype look good, which was not the purpose of the exercise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0509f3c9d421" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Leonardo Rodrigues_Challenge1]]></title>
            <link>https://medium.com/@leonardopinho27/ironhacks-prework-leonardo-rodrigues-challenge1-85afbd058b8d?source=rss-4c44c3485dac------2</link>
            <guid isPermaLink="false">https://medium.com/p/85afbd058b8d</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Leonardo Rodrigues]]></dc:creator>
            <pubDate>Fri, 19 Jan 2024 01:58:50 GMT</pubDate>
            <atom:updated>2024-01-19T16:36:16.622Z</atom:updated>
            <content:encoded><![CDATA[<p>This article was written as the first challenge for the UX/UI Design Bootcamp at Ironhack. The goal was to apply the design thinking methodology to empathize with users, define the problem to tackle, ideate, and create a rapid prototype for a new feature for the Citymapper app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*u1ONyS_-4ychF3JS.png" /></figure><h3>What is Citymapper?</h3><p>Citymapper is a mobile app, developed by a UK-based company, that provides public transportation information, helping users around the globe plan their journeys in urban areas, offering real-time data and multimodal integration. They help users on trains, buses, bikes, scooters, and even on foot find the best routes possible.</p><h3>Empathize</h3><h4>Personal Introspection</h4><p>The assigned task was to create a feature for Citymapper that addresses the problem of having to purchase different public transport tickets from different channels. According to the provided information, the users need help with knowing exactly which tickets they have to buy to go from point A to B, the number of tickets/cards they have to buy and hold, and the process of ticket pricing and purchasing abroad.</p><p>Citymapper’s competitors are all apps that provide travel planning support, such as Google Maps, Waze, Moovit, and many others. Depending on the context, there are also apps for buses, trains and metro (some of them local apps), that allow to check routes and even buy tickets, such as FlixBus, Rede Expresso, Anda, etc.</p><h4>Interviewing</h4><p>Having a better point of view due to the previous introspection, it was time to organize my interview guide. I decided to follow a semi-structured approach to interviewing, having a set of mostly open-ended questions I wanted to ask, but prioritizing the flow of the conversation itself and the points being raised by the interviewee, following up accordingly. I already knew the users I was about to interview, but if I didn’t, this type of interview would have allowed me to build rapport easier. I also practiced active listening, to keep the interviewee engaged.</p><p>For this assignment, I interviewed 5 people from my environment, 3 for them identify themselves as female, and 2 as male. The age range is 27 to 63 years old, and all of them live in Portugal. 4 of them live in the Porto Metropolitan area and use public transportation often, while one lives in a smaller town and normally uses her private vehicle instead of public transportation. 3 of the interviewed users travel abroad at least once per year, and only of them reported not using mobile apps at all for travel planning. This sample is not ideal: I didn’t interview anyone in their 40s or 50s, 2 users don’t travel abroad, they all reside in Portugal and 4 of them in the same metropolitan area. However, for the purpose of this exercise, I was instructed to continue, as the point would be developing good interview skills.</p><p>During the interviews, I asked questions about frequency (e.g. <em>“How often do you use public transportation?”</em> or <em>“How frequently do you travel abroad”</em>), about challenges (e.g. <em>“What challenges do you face when buying public transport tickets?”</em>), about their experiences (e.g.<em> “How did these apps assist you when planning journeys that involve multiple means of transportation?”</em>), and asked for their direct input on features (e.g. <em>“Which features or improvements would make the ticket-purchasing process more convenient for you?”</em>).</p><h3>Define</h3><h4>Analyzing the interviews</h4><p>Taking into consideration the interviews from the last stage, we were able to collect a few insights that reflect the users’ perspectives, not only validating the previously mentioned problems but also providing clues to improve the users’ experience:</p><p><strong>Monthly Pass is a convenient solution</strong></p><p>Users who have monthly passes find the public transport system more convenient, as they work in both buses and the metro and allows them to skip the purchasing process even in multimodal journeys in the Porto metropolitan area. However, there are still instances where<strong> they need to purchase additional tickets</strong> in the machines or in the bus itself, leading to <strong>time-consuming and sometimes dangerous experiences</strong>.<strong> Renovating the monthly pass is also a challenge in itself</strong>, as you have to use either the ticket machines or other services to pay the monthly amount.</p><p><strong>More complexity abroad</strong></p><p>Traveling abroad creates a new set of issues for the user, such as language barriers, unfamiliar transportation and ticketing systems, trouble understanding routes, and even pricing uncertainty, which then leads to stress and frustration. And even though some of these problems can be lessened by using travel apps, used mostly for orientation, <strong>buying tickets is still the biggest challenge.</strong></p><p><strong>App usage while traveling</strong></p><p>Users have and use travel planning apps (e.g., Moovit, Google Maps) to assist with journey planning, either when planning in advance or on the go. They prefer a cleaner interface but also want to have information on the best single or combined routes on a map (highlighting the quickest one), details on the different transports they need to ride to complete their journey, real-time updates, and schedules.</p><p><strong>Integrated purchase</strong></p><p>Users want an app where they can access the previously mentioned information (and mostly use Google Maps for that effect), but also want a solution that <strong>allows them to buy all tickets in the same app</strong>. A solution that allows them to check the route and buy all the necessary tickets in a <strong>quick and easy process</strong>, with flexibility in payment options (MBWay, PayPal, Revolut, Klarna, Debit/Credit cards, etc.) and <strong>somewhere to store bought tickets</strong>. The users currently <strong>resort to multiple apps for the same effect</strong>, or have to carry paper/plastic cards, and that is something that frustrates them.</p><p>The main problem identified by these insights is the ticket purchasing process, as it can be time-consuming, challenging, confusing and is not as streamlined or unified as the users would want. It causes frustration, anxiety and stress, and in contrast, a potential solution could bring satisfaction and security to our users.</p><h3>Ideate</h3><h4>Solution</h4><p>Taking into consideration the main problem our users raised, the focus for this project was to create a feature that allows users to buy tickets from the app, for single transport or multimodal journeys, and, if possible, store them in a virtual “wallet”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2GyA8M36Spgg2wzJ3GgR2w.jpeg" /><figcaption>An incomplete visual brainstorm made to visualize some of the ideas.</figcaption></figure><p>I tried to brainstorm a bit and came up with several ideas that could, hopefully, improve our users’ experience using the new intended features:</p><ul><li>Being able to buy a bundle of tickets for a multimodal journey in only one transaction. The user would specify the start and end of the journey, and have a selection of routes and the total price for each one. Selecting a specific route, the detailed prices would be available, and an option to “Buy All” would appear, as well as removing some of the tickets individually and paying for the others. The app would, then, divide the payment between all channels;</li><li>Being able to store bought tickets in the app, eliminating the need to hold physical cards or access multiple specific apps. Some of the tickets, that would need validation in machines, would display QR codes, barcodes, numbers, or access the NFC functionalities of the mobile phone;</li><li>Being able to renovate the monthly pass in the app, eliminating the need to go to ticket machines or front desks entirely, and having more flexibility in payment methods. Having the possibility of replacing the card with the app itself, with the help of NFC, could also be interesting;</li><li>Display all the tickets for the same journey, if multimodal, in the same “unified ticket”. The idea would be to give the user a map image of the intended route for that journey, display the start and end points, and in another page, detail which tickets were bought for that journey. That could also give the user a feeling of certainty and security in their purchase, and provide the sense of a more unified experience;</li><li>Display clear instructions with images, gifs and videos, making it simple to understand how to validate tickets, navigate specific transportation, other important rules, etc. It would also be important to have that information in the phone’s or account’s predefined language;</li><li>Automatically change the pricing of tickets in foreign currency to match the users’ country, so they can always have an idea of how much they are going to spend on a specific journey. The option to check the price in its’ original currency has to be available too, as a matter of transparency;</li><li>Being able to revisit past journeys made by the user and buy tickets for those once more.</li></ul><p>Although some of these ideas are deeply connected and would need to be included in the final product to make the others work or complement them, I decided to highlight 3 important solutions for the purpose of this exercise, as they are deeply connected:</p><ul><li>Being able to buy a bundle of tickets for a multimodal journey in one transaction;</li><li>Being able to store bought tickets in the app, eliminating the need for physical cards and allowing the tickets to be checked, anytime and everywhere by the user;</li><li>Display all the tickets for the same journey, even if multimodal, in the same “unified ticket”.</li></ul><h3>Prototype</h3><p>The first rapid prototype I developed was for purchasing the tickets in the app itself. I decided to replicate the purchase of a bundle of tickets for a multimodal journey, as a single transport journey would be simpler. As for the Tickets pages, I decided to display how a unified multimodal ticket would look like, as it is also the most complicated scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MLd2z06UjMysy05aEC4Ouw.jpeg" /></figure><p>This prototype starts at the “Selected Jorney” screen, as the user is already interested in purchasing tickets for a certain route they already checking. This is mostly the same screen Citymapper users can see when using the app.</p><p>The user clicks on the “Buy” button and is directed to the “Purchase Selection” screen. Here, the user can check his start and end points, as well as the Date of the journey (which can be changed or not displayed if not applicable) and Departure/Arrival time (the user selects the applicable one or deselects it). They can have a look at the individual tickets they will be buying, checking the price, company and proposed time. They can “Buy All” by default, or click on the “Buy” button in each ticket section to remove them from the bundle of tickets to buy. The visual feedback would be for selected tickets to appear in green, and the deselected ones in grey, for example.</p><p>Clicking in “Buy All” moves to the “Order Details” screen. Here, the user has the opportunity to check the details of his order again, and having a total value of the ticket bundle. If they want to pay, they can click on one of the payment buttons to be transferred to a transactions page, and when concluded, they would be directed to the Tickets page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhd1r-WYJhFHNw9q68fKZw.jpeg" /></figure><p>The first screen here is the “Home” page, which is basically what users see when opening Citymapper. However, I added an icon to the upper-right corner of the screen, that should lead the user to the “Tickets” screen.</p><p>In the “Tickets” page, we can have a look at the proposed Unified ticket, which is only a simplified way of showing a bundle of tickets for the same journey. In this screen, the user has, on the top, an indication of how many tickets for other journeys they have (in this case, 1/3, they can access them by swiping left). They can see a smaller map with the defined route, date of the journey, estimated hours of departure and arrival. They can also check, on the bottom half of the screen, navigation steps concerning that multimodal journey, and continue scrolling to see all of them.</p><p>If needed, they can click on the yellow section (only for prototyping purposes) and be directed to the extended navigation screen, or they could also check timetables and departures, as displayed in the example, by clicking the correct navigation section, market in pink. These screens are already available in Citymapper, the user sees them when checking any route in detail or when consulting timetables, but I replicated them to should how the new future could function with the rest of the app.</p><p>Clicking on the ticket itself, the user is redirected to a “Jorney Tickets” screen, where a bigger map and route are displayed and, on the bottom half of the screen, all individual tickets are listed. Each ticket section has some buttons, one of them to display a QR code / barcode / activate NFC and easily validate when using, a “Details” button and an “Instructions” button, that would accommodate the clear instructions with images, gifs and videos I mentioned in the Ideation stage.</p><p>The “Details” button leads to an “Individual Ticket Details” page, where the user can see the route section that ticket covers and many other specific details. He also has the option of sending that single ticket to someone via e-mail, other avenues, and an option to Change the ticket.</p><h3>Learning Points</h3><p>The process itself was very interesting. It was the first time I tried to follow some steps of the Design Thinking methodology, I can definitely see the value and applicability and I’m happy I got to try it. However, I hesitated a lot in some stages of the process, as I was not very confident about the quality of my work and I still think I could have done much better. I’d say another learning point would be: Practice Makes Perfect.</p><p>Planning the interviews and conducting them was probably the least challenging aspect of this challenge. Coming from a Psychology and Recruitment background, I felt comfortable with this qualitative method, and was fairly used to interview. However, I still felt the pressure, the need to be more focused and empathetic, of asking the right questions and completely understanding the answers. I was deeply invested in understanding the users’ perspectives, and I also knew the outputs/insights would determine the rest of the work.</p><p>The parts I struggled with the most were definitely ideating and prototyping. I was constantly trying to come up with ideas, thinking by myself, browsing, talking to other people, but I also passively and actively attacked everything that crossed my mind, which frustrated me and made me insecure. I learned to be less harsh with my creativity, because I need to let it have some room to grow. Once that happened, some ideas started coming up when brainstorming. As for prototyping, I struggle with trying to organize visual content. I learned that I need to psychologically distance myself from the prototype to let the flaws emerge and some better ideas too. It also helped that I got to show my prototypes to 2 of my interviewed users and did a couple of very rudimentary testing sessions.</p><p>Overall, I’m grateful I was challenged and that I’m more capable now than when I first started!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85afbd058b8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>