<?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 Greta Zunino on Medium]]></title>
        <description><![CDATA[Stories by Greta Zunino on Medium]]></description>
        <link>https://medium.com/@zuninogreta?source=rss-9ebf5c6cdb5b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*q4XdU1VP_yjrRiYgu-dZAw.jpeg</url>
            <title>Stories by Greta Zunino on Medium</title>
            <link>https://medium.com/@zuninogreta?source=rss-9ebf5c6cdb5b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:19:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zuninogreta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Redesigning the registration process of Cherry Pick, a platform for freelancers in tech]]></title>
            <link>https://medium.com/@zuninogreta/redesigning-the-registration-process-of-cherry-pick-a-platform-for-freelancers-in-tech-c21162a56874?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c21162a56874</guid>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Tue, 15 Feb 2022 10:35:19 GMT</pubDate>
            <atom:updated>2022-02-15T16:10:41.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jgQD33nOJnjzaR3Zd2-xxw.png" /></figure><p>Final project for <a href="https://www.ironhack.com/en/ux-ui-design">Ironhack</a>’s UX/UI design bootcamp</p><ul><li>Role: UX/UI designer</li><li>Time: 12 days, 8 hours/day</li><li>Tool: Figma</li><li>Team: <a href="https://medium.com/@lobet.c">Célia Lobet</a> and myself</li><li>Required output: hi-fi prototype of the registration process (desktop format)</li></ul><h3>Our mission</h3><p>For our final project at Ironhack’s UX/UI design bootcamp, my teammate Célia and I had the opportunity to work for <a href="https://app.cherry-pick.io/home"><strong>Cherry Pick</strong></a>, a French platform that matches freelancers in the tech industry with companies that look for a professional to accomplish a project.</p><h4>Who is Cherry Pick and what we did for them</h4><p>When a company who needs a freelancer contacts Cherry Pick, the platform, through an <strong>algorithm</strong> and the <strong>expertise of HR specialists</strong>, <strong>analyse</strong> the registered <strong>profiles and comes up with a shortlist of</strong> ideal <strong>candidates</strong> for the role. These candidates are then presented to the company, who makes the takes the final decision.</p><blockquote>“The more information we have about the freelancer, the better match we can guarantee with a job that responds to his professional goals. It is a win-win situation for both the freelancer and the company recruiting”</blockquote><p>To do so, the registration process should include relevant questions, and the freelancers should take the time to enrich their personal dashboard with extra experiences, technical tests, etc.</p><p>That’s where our Team get into the game; we were asked to <strong>redesign Cherry Pick’s registration process</strong> in order to:</p><ul><li>Include questions that could guarantee freelancers the best possible match with missions;</li><li>Make the procedure friendly and engaging;</li><li>Encourage freelancers to come back on Cherry Pick and update their personal dashboard.</li></ul><h3>Empathizing</h3><h4>Competitive analysis</h4><p>We kicked off the <strong>research phase </strong>by comparing a set of elements demanded in the registration process of five freelance job search platforms in France.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gpN8AWdKk-VprVX0YTVbBg.png" /><figcaption>Competitive analysis of selected job search platforms for freelancers</figcaption></figure><p>We identified four main patterns:</p><ul><li>Some platforms are <strong>intermediaries</strong> between the freelancers and the companies: they select the profiles they consider a good match for the job and forward it to the company who wants to hire. Other platforms do not act as middlemen, but simply provide a space on which demand and offer can meet and match.</li><li>A few platforms select the profiles they are willing to make part of the network through a <strong>screener</strong>. They can either decide to exclude junior profiles (Comet) or analyse each new registration and approve only part of them (La Crème de la crème).</li><li>Some registration process allow professionals to <strong>declare</strong> whether they have <strong>more than one role</strong>, for exemple Web Developer and UX Designer. Others do not.</li><li>Freelancers are usually asked to declare their hard <strong>skills</strong>, but only a few registration process demand a <strong>self-assessment</strong> of the level of proficiency.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T-zcBZblk5rnU8Ae2ceWBA.png" /><figcaption>Cherry Pick competitive assessment</figcaption></figure><h4>Survey</h4><p>We conducted a <strong>survey</strong> among Cherry Pick’s users to understand their professional preferences as freelancers and what they expected from a platform for project hunting.</p><p>The main insight we got is that <strong>daily rate</strong> is the <strong>most important criteria</strong> when choosing a job, followed at short distance by the <strong>possibility to work remotely.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hfDDX5n-R_tBktCYxIwW4g.png" /><figcaption>The daily rate is the most important criteria for freelancers</figcaption></figure><h4>User interviews</h4><p>We conducted <strong>5 interviews</strong>: 4 with Cherry Pick users and 1 with a freelancer who is not registered on the platform, to get an external point of view in our research.</p><p>We discussed job-searching platforms in general, then we focused on the registration process.</p><p>The main point that emerged is that <strong>freelancers do not just want to find a project, but expect </strong>the platform they join to<strong> </strong>get to know their professional figure, valorize it and provide a “<strong>human” support</strong>.</p><p>Freelancers are aware there are hundreds of candidates with similar expertise, but they also know that <strong>each of them is unique</strong>, has specific <strong>preferences </strong>when it comes to the <strong>desired work</strong>, and sometimes the <strong>jobs they are proposed do not match with their professional goals</strong>.</p><p>Freelancers usually decide to take that work path because of the freedom to choose the projects they like, and do not want to find themselves stuck in projects that do not satisfy their personal criteria.</p><p>In terms of <strong>registration process</strong>, we identified three main patterns:</p><ul><li>Freelancers do not want to spend much <strong>time</strong> on it, recalling the fact that most of their key professional information is already available on Linkedin or on their CV;</li><li>Freelancers who practice <strong>more that a profession</strong> (for exemple: Web Developper and UX Designer) <strong>cannot declare </strong>more than one;</li><li>Users are not convinced by the <strong>self-assessment of </strong>their <strong>hard skills</strong>, required in several platforms, as it is perceived as subjective.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyhLk0NQlb-vloRqxDUQVw.png" /><figcaption>Quotes from users’ interviews</figcaption></figure><h3>Definition</h3><h4>Persona</h4><p>We elaborated on the precious information gathered through surveys and interviews to build our project’s <strong>Persona</strong>, Mehdi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WNFfEH5DWmyY5w5zdwPIg.png" /><figcaption>Our project’s Persona, Mehdi</figcaption></figure><h4>Problem statement</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*txyNTmu1K3rN0PHfSZGBtg.png" /><figcaption>Our project’s Problem statement</figcaption></figure><h4>Hypothesis</h4><blockquote>We believe that enhancing freelancers’ opportunities to show their unique profile during the registration process will allow a <strong>better alignment between the projects</strong> they are proposed <strong>and their professional preferences</strong>.<br>We will know we are right when users feel their profile is valued, positive feedback increase and they regularly come back on the platform.</blockquote><h3>Ideation</h3><p>Through <strong>brainstorming</strong> technique, we <strong>listed and selected the questions to include in the registration </strong>form, having in mind that our objective was to keep the process straight to the point while gathering as much relevant information about the freelancer as possible in order to grant a job match in line with his/her skills and expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wldkePHitc7S7ajiuW9ybA.png" /><figcaption>Elements we added to Cherry Pick’s registration process</figcaption></figure><p>With respect to the general structure of the website, these are the main changes we agreed on applying.</p><h4>Overall registration process:</h4><ul><li><strong>User’s registration</strong> is the focus of the flow, so we moved it from the left to the center of the page and made it bigger.</li><li><strong>Testimonials</strong> are important to convince the freelancer to register on Cherry Pick, but they are not the key element, so we decided to move them to the <strong>bottom of the first registration page</strong> and to exclude them from the next steps, as the person is now convinced about pursuing the registration.</li><li><strong>Progress bar</strong>: we moved it to the top center of the page, coherently to the new layout of the page. We opted for a round shape, to make clear steps are just indicative of the current stage of inscription and not interactive buttons.</li><li><strong>Wording, tone</strong>: we harmonized the use of the “<strong>you</strong>” along all the pages, to maintain coherence and a friendly approach. We updated the <strong>text of </strong>“Next” <strong>buttons</strong> into “C’est parti!” and “On y est presque” to increase users’ engagement and reassure them the registration wouldn’t have taken long.</li></ul><h4>Lo-fi</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fnPuZ0MXGDRh5K5tyTmCSw.png" /><figcaption>Lo-fi wireframes of the registration flow</figcaption></figure><h4>Concept testing</h4><p>We submitted our lo-fi wireframes to 5 people; three main points caught our attention:</p><ul><li>The difference between “Catégorie de métier” and “Specialité” (Job sector and specialization) was not clear;</li><li>Daily rate (TJM) was available only for the main job, but people tested highlighted that different roles can have different daily rates, thus the field should be included for each job entered;</li><li>People felt limited when asked to include only 5 main competencies, and wished they could add more, to better show their professional uniqueness.</li></ul><h4>Mid-fi</h4><p>We <strong>iterated</strong> the comments received during the concept testing:</p><ul><li>Changed the field “Catégorie de métier” into “Ton métier”, and included hints about possible inputs in the placeholder;</li><li>Added the TJM field for each job added;</li><li>Added an “Other skills” section, with no limits of possible entries, to allow users to fully express their competences. By clicking on the “i” icon, users can access an explanation of the section.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sl_IgU1sznyllmdsxTiNbg.png" /><figcaption>Mid-fi wireframes of the registration flow</figcaption></figure><h3>Hi-fi</h3><p>We <strong>iterated</strong> the comments received during the usability testing and we moved to the realization of the <strong>hi-fi</strong> <a href="https://www.figma.com/proto/KgrcXelV73H4fpN1Xqnir0/Final-Project---OFFICIAL-11%2F02?page-id=313%3A2227&amp;node-id=327%3A4754&amp;viewport=241%2C48%2C0.24&amp;scaling=min-zoom&amp;starting-point-node-id=327%3A4754">prototype</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F32--86FPb5s%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D32--86FPb5s&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F32--86FPb5s%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f48b43ee25af7409f6c309076b72a4e9/href">https://medium.com/media/f48b43ee25af7409f6c309076b72a4e9/href</a></iframe><h3>Conclusions</h3><p>Célia and I greatly <strong>enjoyed working with</strong> the <strong>Cherry Pick</strong> team, always reactive and supportive, and exchanging with many freelancers who made us discover a way of working that is gaining more and more relevance.</p><p>Finding the right number and the right type of questions to include in order to satisfy the needs of both the freelancer and the recruiter was a <strong>balancing act</strong>, as well as the choices in terms of <strong>UX writing</strong> to make the procedure friendly, engaging but also clear.</p><p>Redesigning the registration process for Cherry Pick was a rewarding, special experience to conclude the Ironhack bootcamp and made me proud, <strong>grateful</strong>, <strong>to have chosen a career in UX/UI design.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c21162a56874" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Piatto, an app for healthy people who want to eat even better]]></title>
            <link>https://medium.com/design-bootcamp/piatto-an-app-for-healthy-people-who-want-to-eat-even-better-f90682e01af0?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f90682e01af0</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Fri, 28 Jan 2022 23:07:15 GMT</pubDate>
            <atom:updated>2022-02-01T07:31:35.618Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jT84NNhNNAX_gh3Y815LA.png" /></figure><p>Ironhack UX/UI bootcamp project n.4</p><ul><li>Role: <strong>UX/UI designer</strong></li><li>Time: <strong>11 days</strong>, 7 hours/day</li><li>Tool: <strong>Figma</strong></li><li>Team: <strong>Célia Lobet and myself</strong></li><li>Required output: <strong>MVP of a smartphone app </strong>(hi-fi prototype)</li></ul><h3>Our mission</h3><h4>A current topic: wellness</h4><p>The concept of <strong>wellness</strong> has gained an <strong>increasing relevance in people’s life</strong>: a research carried out by <a href="https://www.mckinsey.com/industries/consumer-packaged-goods/our-insights/feeling-good-the-future-of-the-1-5-trillion-wellness-market">McKinsey</a> at the beginning of 2021 revealed that in the last year the global wellness market has grown by 5–10%, and that wellness is becoming a priority for an increasing share of the population.</p><p><strong>Technology</strong> had a tremendous impact on the <strong>democratization of wellbeing</strong>. From meditation apps to step counters, the public has endless tools at their fingertips to track progress in practices perceived as good for their health.</p><h4>Instructions: an app to stay up to date</h4><p>In line with these disruptive changes in the wellness industry, for our 4th Ironhack project we were asked to help a fictitious <strong>client, </strong>the <a href="https://members.nationalwellness.org/page/About_NWI"><strong>National Wellness Institute</strong></a><strong>, </strong>which has <strong>lagged behind in taking advantage of the opportunities offered by technology. </strong>The Institution has been recorded a substantial drop in subscriptions and decided to intervene on two axes:</p><ul><li><strong>Developing a digital product </strong>able to attract new clients and get back those who have left</li><li><strong>Updating their visual image</strong> in line with their refreshed approach to wellness</li></ul><p>Each team had to come up with a solution for the two requests and to focus on a specific aspect of wellbeing. My teammate and I opted for <strong>healthy eating</strong>, as we were fascinated by how a basic, primordial need such as food can be interpreted in the modern, digital world.</p><h3>Empathize</h3><h4>Competitive analysis: it’s all about calories</h4><p>The first step in our discovery phase was <strong>research</strong> on <strong>already existing healthy eating apps</strong>. We led a <strong>competitive analysis</strong> by comparing Lifesum, Myfitnespal and Noom around a set of common criteria.</p><p>We found out that diet and healthy eating apps are mostly <strong>based on weight-control, calories count and meal tracking</strong>. In all of the three cases, the objectives made available to users are only based on weight, be it in an optic of loss, gain or maintaining.</p><p>The user is invited to register each meal he/she consumes, while the app calculates the related calories and quantity of nutrients such as proteins, carbs, fats, etc. Results are then compared to the user’s levels of reference, calculated by the app according to his/her objectives in terms of weight.</p><h4>Stakeholder interview: insights from a dietitian</h4><p>Since our client is an Institute which gathers certified wellness experts, our Team thought it was important to <strong>exchange with a dietitian</strong>. The interview with <strong>Ms. Anita</strong> was significant for two main reasons:</p><ul><li>Food is a sensitive topic, and people may lie about what they eat. Experts do not, and can tell us what are the real habits and facts in people’s diet;</li><li>Ms. Anita has an Instagram page in which she talks about nutrition in a simple, engaging way. She is familiar with media, technology and the way they can be used to convey messages, positive or negative, about food.</li></ul><p>Most of her <strong>patients</strong> are <strong>young adults</strong> whose <strong>main goal</strong> is <strong>not losing weight, but learning to eat in a healthier way</strong>.</p><p>Usually, those who <strong>successfully complete the journey </strong>are <strong>those who go to her on their own initiative</strong>, not those pushed by a third person like their doctor or their partner.</p><blockquote>“Patients think good eating is all about privation, while the keyword is balance, variety”</blockquote><p>Usually, those who <strong>successfully complete the journey </strong>are <strong>those who go to her on their own initiative</strong>, not those pushed by a third person like their doctor or their partner.</p><h4>Surveys: I am healthy and I know it</h4><p>We conducted a <strong>survey</strong> to get a quantitative overview of the topic of nutrition from potential users’ point of view.</p><p><strong>85%</strong> of respondents claimed the purpose of their diet is “<strong>being healthy</strong>”; <strong>only 5%</strong> mentioned <strong>weight loss</strong>.</p><p>While people mostly <strong>rated</strong> their <strong>eating habits</strong> as <strong>healthy</strong>, we should be <strong>careful to treat this information</strong>, as the vision of what is “healthy” is highly <strong>subjective</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/543/1*SnPHvTIsx_n5sywfzuD3Rg.png" /><figcaption>People tend to rate their diet positively</figcaption></figure><h4>User interviews: I have never seen a dietitian, but…</h4><p>Our Team interviewed five people, three women and two men, to obtain more “qualitative” insights on the subject we decided to investigate.</p><p>All of the interviewees defined <strong>food</strong> as “<strong>important</strong>” in their life, and four people said it was because of its <strong>key impact onhealth</strong>.</p><p>Answers to the question “How healthy would you rate your diet” mirrored those collected in the interview, with all the interviewees giving a 4 or a 5 as self-assessment.</p><p>The discussion became interesting when we started digging into the reasons, the <strong>drivers behind </strong>their <strong>answers</strong>.</p><p>We discovered that people believe to have an overall good knowledge of what is healthy and what is not, but most of them have never consulted a dietitian. Nevertheless, 4 out of 5 confirmed that dietitians are the source they would trust the most and that they would like to consult one if they had the opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzjCuIhcNK-SouzsjzAKGQ.png" /><figcaption>Some results from our project’s interviews</figcaption></figure><blockquote>“I think I have healthy eating habits, but I have never consulted a dietitian. I trust my gut, but if I had the opportunity I’d like to check with an expert”</blockquote><p>Since they do not follow the guidelines of a professional, our interviewes “trust their gut” when taking eating decisions. They do not take note of what they eat but they <strong>keep track mentally</strong> and <strong>listen to their bodies</strong>: all respondents said they can feel when they exceed or they lack of something nutrition-wise, and take action accordingly.</p><p><strong>None</strong> of the people we exchanged with was <strong>counting</strong> his/her <strong>calorie</strong> intake at the moment of the interview. All of them had quite a negative opinion on the practice, and defined it as <strong>stressful</strong> and not the right tool to reach their objective of having a healthy diet.</p><blockquote>“I used an app in which users track calories and share pictures of themselves before and after dieting. I stopped using this app because it had a negative impact on my mental health”.</blockquote><h3>Definition</h3><h4>Affinity map and Persona</h4><p>Once completed the interviews, we kicked off the <strong>definition phase</strong> by collecting the insights on a whiteboard. We started to look for <strong>patterns</strong> and we created an <strong>Affinity map </strong>by gathering the behaviors, feelings and opinions that resulted similar among interviewees.</p><p>We combined the identified patterns with the insights provided by the dietitian to build the project’s <strong>Persona</strong>, Claire.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9B1U6veDGSnTv1WGPxb7A.png" /><figcaption>Our project’s Persona, Claire</figcaption></figure><h4>Journey map</h4><p>We gave context to our Persona by building a <strong>Journey map</strong> that went through Claire’s experience and allowed us to <strong>better define</strong> her <strong>pain points</strong>. In the graphic below, they are highlighted with a red star.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sa5BeEXyX8KsssPAKcZR1w.png" /><figcaption>Our project’s Journey Map</figcaption></figure><h4>Problem statement &amp; Hypothesis</h4><p>Based on the results of the interviews, the survey and the insights of the dietitian, who meets dozens of patients every year, we decided to <strong>focus on a</strong> precise <strong>category of users</strong>: people who think they already have a good way of eating and a good knowledge of nutrition in general. Once agreed on our target user, we went through the Persona and the Journey map to build our <strong>Problem statement:</strong></p><blockquote>People who have good eating habits need to educate themselves about nutrition because they want to have an even more balanced diet.</blockquote><p>How can people like Claire reach their goal of improving their diet and establishing long-lasting good habits? Brainstorming and discussion brought us to formulate our <strong>Hypothesis</strong> for the project:</p><blockquote>We believe that giving guidance to people who want to further improve their diet will allow them to strengthen their good eating habits and acquire new ones. We will know we are right when the rating of the app increases and people do not drop using it until they get into the practices they have learned.</blockquote><h4>Value proposition Canva</h4><p>The app we create cannot just be pleasant for the eyes and useful to users. They must respond to the needs and the ambitions of the stakeholders they are designed for; they must address a demand that truly exists in the market and they must differentiate from what competitors are proposing.</p><p>A tool to clarify what the product can offer and how it can specifically address customers’ needs is the <strong>Value proposition Canvas</strong>. We created one for our project:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5O5GXieLlTD0fcy2mJrUaQ.png" /><figcaption>Value proposition canva for our project</figcaption></figure><h4>Brand positioning</h4><p>Once we validated how our product would have addressed the Persona’s pains and brought her a measurable gain, we started to think how we wanted to position with respect to competitors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJOO3UulOdt3o-_VOP0Fsg.png" /><figcaption>Brand positioning of our app, Piatto</figcaption></figure><p>While most existing diet apps focus on calorie counting and strict meal tracking, we wanted our product to <strong>shift the focus on how eating well</strong> can make people feel better and improve their health.</p><p>As our Persona has already some knowledge of the principles of good eating and is motivated to build good habits instead of following a rigid program, we decided to make <strong>our app self-paced and </strong>easy going, friendly, <strong>welcoming</strong> towards users. We wanted them to <strong>celebrate their success, more than highlighting their excess </strong>or their shortcomings, while allowing them to keep track of both in order to be aware of how to adjust their behavior accordingly.</p><h4>MoSCoW chart</h4><p>We went more deep into the ideation phase by brainstorming the features that we wanted to include in our app. Then, we ranked them by importance through the <strong>MoSCoW chart</strong>, a tool which helps to prioritize items in different contexts, including design. We considered as “<strong>Must have</strong>” the <strong>features</strong> which we believed as <strong>key to address the problem statement</strong> while remaining coherent to the value proposition and the brand positioning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7GkNXpWS_JmqHmomHxqWg.png" /><figcaption>Features’ prioritization: our project’s MoSCoW Matrix</figcaption></figure><h3>Ideation</h3><h4>Low-fi wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81b1fU6xzloWlcx52YhfRA.png" /><figcaption>Our project’s lo-fi wireframes</figcaption></figure><h4>Concept testing</h4><p>We had our first set of lo-fi wireframes tested by five people. Here’s the feedback we received:</p><ul><li><strong>Homepage</strong>: interviewees believed the “Daily %” was the recommended percentage of proteins, grains, etc. they should have as a share of their overall diet, not the % of their daily goal, as we wanted to show. As a consequence, it was not clear to them that they had to click on one of the categories to add a meal, and instead looked for a “+” or “Add a meal” button across the page.</li><li>“<strong>Add a meal</strong>” page: users struggled to understand the difference between “encouraged” categories, on the top of the page, and “less is better” categories at the bottom. Also, they looked for a “Save” button once they added a meal, to be sure it was well counted.</li><li><strong>Statistics pages</strong>: users believed % referred to the recommended percentage and not to their personal score. They also got confused at seeing % in one part of the page and dots in the other, as units of measurement.</li></ul><p>Thanks from the feedback received from concept testing, we realized we were trying to conveying too many messages on a single page. We iterated and went through a second round of testing.</p><h4>Mid-fi wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IhnQclVmSplUWUrllJF6w.png" /><figcaption>Selected Mid-fi wireframes with comments</figcaption></figure><h4>Moodboard</h4><p>Once we agreed on the structure and the text of our wireframes, we started to think about how <strong>UI</strong> could <strong>help us</strong> better <strong>convey our message</strong>. Our app wanted to convey <strong>positivity</strong>, be <strong>friendly</strong>, focus on health while avoiding being intimidating or too strict. We chose <strong>soft</strong>, pastel <strong>colors</strong> with a reminder to <strong>nature</strong> and <strong>simplicity</strong>, and we put together our <strong>Moodboard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOvaU3nchd2kpKs9S0OkuQ.png" /><figcaption>Our project’s Moodboard</figcaption></figure><h3>Prototype</h3><p>We applied colors, shades, selected fonts to our mid-fi prototype, then we added empty states, error messages and micro-interactions.</p><p>We obtained our <strong>hi-fi prototype</strong>, that you can check <a href="https://www.figma.com/proto/fuXhOW53Im6KI91gNXgFnV/Project-4_Wellness?page-id=272%3A856&amp;node-id=272%3A857&amp;viewport=320%2C48%2C0.16&amp;scaling=scale-down&amp;starting-point-node-id=272%3A863">here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPhik4Tvn37E%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPhik4Tvn37E&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPhik4Tvn37E%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8336e3d8dc3fa12bf12f897ef0f50dd4/href">https://medium.com/media/8336e3d8dc3fa12bf12f897ef0f50dd4/href</a></iframe><h4>Desirability testing</h4><p><strong>What feelings does our app suggest you?</strong></p><p>That’s what we asked to 4 users, to investigate whether the colors and the visual elements we chose conveyed the message we wanted.</p><p>We submitted them a list of around 40 words and we asked them to pick 5, without thinking too much, and to add any other word the screens may have evoked to them.</p><p>We were glad the answers we received, on the right, were in life with the message we wanted to transmit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*AXLZLESycmctc6C76pEdBg.png" /><figcaption>Results of Desirability testing</figcaption></figure><h3>Conclusions</h3><h4>Wrapping up</h4><p>People pay more and more attention to their wellbeing, and they consider their food choices as a key aspect of it. They are willing to have a balanced diet, but only a minority has ever consulted a dietitian in their life: the practice is perceived as not a priority, but still the professional figure is the source of reference they trust the most.</p><p>That’s why we created <strong>Piatto</strong>, <strong>an app to guide healthy people who want to have an even more balanced diet</strong> without stress, while making sure they can trust the indications they are given.</p><p>Our objective was creating an app that granted <strong>autonomy to users</strong>, was <strong>educational</strong>, and <strong>highlighted the good practices instead of</strong> making the user feel guilty for possible <strong>lacks or excesses.</strong></p><p>We tried to convey the message both through the friendly tone of the writing and the visual choices, oriented towards rounded shapes and soft, natural colors which evoke trust.</p><h4>Lessons learned</h4><p>Creating a MVP from scratch, by going through all the phases of the Design Thinking until obtaining a hi-fi prototype in just around 60 hours was a <strong>tough, rewarding experience</strong>.</p><p>While confident in the research and definition phase, we slowed down in the ideation phase, and we had to go through two rounds of testing before our tasks and our message became clear to people tested. We learned that putting too many elements on a single screen creates confusion and diverts the user’s attention from the main task. <strong>Setting priorities and organizing the page accordingly </strong>allowed<strong> </strong>us to obtain a clearer product.</p><p>We made treasure of the experience and we did not repeat the mistake in the elaboration of the UI: make choices that prioritize the user’s tasks, be clean, make it simple were driving principles that allowed us to proceed without the need of multiple revisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f90682e01af0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/piatto-an-app-for-healthy-people-who-want-to-eat-even-better-f90682e01af0">Piatto, an app for healthy people who want to eat even better</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Family cookbooks go digital: a feature for shared recipe folders on Marmiton app]]></title>
            <link>https://medium.com/@zuninogreta/family-recipes-go-digital-adding-a-shared-recipe-book-on-marmiton-website-43c3c685b2de?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/43c3c685b2de</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Sun, 09 Jan 2022 19:17:40 GMT</pubDate>
            <atom:updated>2022-01-09T20:57:29.725Z</atom:updated>
            <content:encoded><![CDATA[<p>Ironhack bootcamp 3rd project: add a feature to an existing app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ky-Qy1s1XfubNyf3-WyELw.jpeg" /></figure><h3>Can you send it again please?</h3><p>I live in Paris, my family in a small city not far from Turin. We’re Italian, Christmas is a big deal for us. My mum and I start planning the menu months before: every Christmas is unique, a moment in which our family has a genuine good time, and food is a key part of it. Planning is more complicated when we’re separated: this year we talked on the phone, then I wrote the menu as a note on my iPhone, including the link to each recipe, and I sent it to her. She opened it and was happy about the good organisation despite the distance.</p><p>A couple of weeks passed, Christmas was approaching and mum wanted to start doing part of the grocery shopping.</p><blockquote>“Can you send me the list again?”</blockquote><blockquote>“I sent you the note a while ago, didn’t you save it?”</blockquote><blockquote>“…I have no clue where it is”.</blockquote><p>I didn’t know it yet, but the experience would have inspired me the topic for my 3rd project at Ironhack’s UX/UI bootcamp.</p><h3>Our mission</h3><p>For this individual project, each student was required to <strong>add a new feature to an existing </strong>native <strong>app</strong>.</p><p>We had to come up with an idea and conduct guerrilla research to assess whether users found the feature valuable. Once obtained a positive feedback, we would have proceeded with designing the new feature, the demanded <strong>output</strong> being a <strong>high-fidelity</strong> (hi-fi) <strong>Figma prototype</strong>.</p><p>We had 4 half-days to get things done. Once completed, our work was submitted to a <strong>Design Critique </strong>session: 5 minutes for the designer to illustrate his/her work, followed by 15 minutes of feedback from peers and teachers.</p><p>As during the last week of class we <strong>focused on UI</strong>, that would have been the main aspect to develop and care about in our project.</p><h3>Discovery phase</h3><p>I decided to investigate a feature allowing people to avoid losing the recipes they share with family and friends and to apply it to <strong>Marmiton</strong>, which in France is a true reference when it comes to recipes. Traditionally they work on a website basis, but they now have a smartphone app too.</p><h4>Competitive analysis</h4><p>With such a short time to finalize the project and focus to be put on the UI, we had to squeeze the research phase on a single day.</p><p>I started with a <strong>competitive analysis</strong>, to understand similarities and differences in the tasks offered by Marmiton and two competitors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9wJF5xyrcaFZ9abnqKV8BA.png" /><figcaption>Competitive analysis of Marmiton app and two competitors</figcaption></figure><p><strong>None of the app</strong> I consulted <strong>offered a feature similar</strong> to the one I intended to develop. This means it could be <strong>a way to differentiate from competitors</strong>, but before jumping to the definition phase I needed to get more information about how people feel about cooking apps and sharing recipes.</p><h4>What’s people attitude towards sharing recipes? Interviews’ results</h4><p>6 out of 7 people I interviewed said they are used to share recipes with family and friends, mostly by sending the link of the recipe by a texting app such as Messenger or Whatsapp.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YecUNihWsaN4KJil30KXsg.png" /><figcaption>Interviews results: recipe sharing channels</figcaption></figure><p>What happens to these recipes once they are shared?In most cases, they are saved both digitally and on paper:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PaAScBpeOUw0HoE-F8C5hA.png" /><figcaption>Interview results: storing shared devices</figcaption></figure><p>I asked people who store recipes on a digital device what tool they recur to. I received a different answer from each of the 4 interviewees, namely Notion, Excel, Pinterest, and a folder in the laptop.</p><h3>Definition phase</h3><h4>Pain points</h4><p>Be them stored digitally or on paper, <strong>recipes shared with family and friends end up becoming a “private” item</strong>, to which only the owner of the book or the computer has access to.</p><p>If the recipe has to be shared again, the person has to look for the link, or take a screenshot, and send it another time.</p><blockquote>While interviewees enjoyed getting the recipe of a dish they liked, the process can be time-consuming and annoying for both the person asking and the person who has to answer.</blockquote><h4>Persona and journey map: meet Louise</h4><p>I gathered interviews’ insights to create the project’s <strong>Persona</strong> and <strong>Journey Map</strong>. These two design tools allowed me to <strong>better frame</strong> the <strong>goals</strong>, the <strong>motivations</strong> and the <strong>pain points</strong> of people who share recipes with their inner circle, my final objective being providing them with a meaningful, fact-based solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqtIxiClY6NGv_Er__6xJQ.png" /><figcaption>The project’s Persona, Louise</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKXlMlQizlvUZ_GMrqf3fQ.png" /><figcaption>The project’s Journey Map</figcaption></figure><h3>Problem statement &amp; hypothesis</h3><p>The definition phase culminated with the delineation of the <strong>problem statement</strong>:</p><blockquote>People who like cooking need a way to <strong>retrieve shared recipes</strong>, because they <strong>do not want to lose them</strong>.</blockquote><p>I walked through this project with the idea of giving families and groups of friends the opportunity to share the recipes they like, that are part of their shared memories and that contribute to make celebrations even more special.</p><p>Enriching Marmiton app with a flow that allows users to <strong>create cookbooks</strong>, give acquaintances access to them and <strong>allow each member to share their recipes </strong>is the <strong>hypothesis</strong> I decided do work on in the ideation phase.</p><h3>Ideation</h3><p>Where should I place the new feature, in the context of the existing app? <strong>Adding a new feature</strong> is a <strong>delicate balance between promoting </strong>something new <strong>and avoid disrupting the users’ habits</strong> and perception of the app itself.</p><p>I started by analyzing the current flow to access a saved recipe.</p><h4>Existing user flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GAvwMQD7azm9QDhxxQNLIQ.png" /><figcaption>Marmiton app — Current user flow to check a saved recipe</figcaption></figure><p>To analyse the existing user flow, we start from the Homepage (screen 1). The automatic settings envisage it in discovery mode (“Mode découverte”), the generic page every user, included those who do not have an account, can see.</p><p>Registered users <strong>can access</strong> their <strong>personal pages in two ways</strong>:</p><ul><li>To their general personal page, by clicking on “Mode personnalisé” in the toggle on the bottom of the screen (screen 2)</li><li>To their saved recipes, “Mon carnet”, by clicking on the heart icon at the bottom right of the footer (screen 3)</li></ul><p>The <strong>first option</strong> gives access to a customized page where the registered user can see a <strong>preview</strong> of 6 of his/her saved recipes, organized in a carrousel. By scrolling down the page, two other categories, structured in the same way, are made available: selected for you (“Rien que pour vous”) and recipes you may like (“Vous allez aimer”). The <strong>titles of these sections </strong>are <strong>not interactive, </strong>as<strong> </strong>the page is intended to just give a preview of the recently added recipes in the carrousel.</p><p>If the user wants to see <strong>all</strong> the <strong>saved recipes</strong>, he/she has to pass through the <strong>“Mon carnet” page</strong>. From there, the user can select one of the categories, for exemple “Dessert”, and access all the recipes he/she saved in the folder (screen 4). As of today, each time we save a recipe, it is automatically added to the relevant category: users cannot create new folders or change the name of the existing ones.</p><h3>Solution</h3><h4>New user flow</h4><p>As I had only 3 half days to design the new feature, I decided to <strong>focus on a single flow</strong>, <strong>“Look for a shared recipe”, </strong>and leave aside, at least for the moment, the “add a new shared recipe” flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1vLbYu8J4StYMGvjFh6OQ.png" /><figcaption>The project’s User flow</figcaption></figure><h4>Mid-fi wireframes of the new feature</h4><p>Here’s the new feature flow, in <strong>mid-fi</strong>, with the new sections marked with a blue rectangle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1O7ApPzEQFpNHX3Dss6zA.png" /><figcaption>Mid-fi wireframes of the new feature</figcaption></figure><p>As the <strong>new feature</strong> is about consulting recipe folders (cookbooks) shared with family and friends, it is <strong>accessible only to </strong>registered <strong>users</strong> who are <strong>logged in</strong>.</p><p>I decided to <strong>adapt the new feature to the present structure</strong> as much as possible, assimilating the shared recipes section (“Recettes partagées”) to one of those already existing, just below the “Dans mon carnet” section.</p><p>The way users can access shared cookbooks and recipes is the same as for saved recipes in the current app:</p><ul><li>By selecting “Mode personnalisé”, they can choose a shared recipe from the carrousel “Mes recettes partagées” (screen 2);</li><li>By clicking on the heart icon at the bottom right of the footer, they can access all the shared cookbooks (screen 3).</li></ul><p>I decided to include a <strong>“Voir tout” button</strong>, just above the carrousel on screen n.2, as <strong>an alternative</strong> way <strong>to the heart icon</strong> to access screen n.3. The button basically allows users to switch from a page where only a few recently recipes are showed to one where all the recipe folders, be them shared or not, are placed. The button is available for both “Dans mon carnet” and “Mes recettes partagées” sections.</p><p>For the sake of <strong>consistency</strong>, the page with shared cookbooks (screen 3) and that of recipes within a certain cookbook (screen 4) are <strong>structured</strong> exactly <strong>as the equivalent for saved recipes in the existing app</strong>. The only difference is at the top of screen 3: I decided to allow users to switch from saved recipes (Mon carnet, on the left) to shared recipes (Recettes partagés, on the right) without having to go back to screen 2.</p><h4>Usability testing</h4><p>To validate the way I decided to develop the new feature, I conducted a round of <strong>usability testing</strong> of the mid-fi prototype. Volunteers (thank you!) were given the following instructions:</p><ul><li>Assume you have a Marmiton account</li><li>On the app, you have a shared folder with your family in which each member store the recipes traditionally cooked on July 14th (National Day)</li><li>Access the folder!</li></ul><p>Each person tested clicked on the user icon on the top right of the homepage, believing it was the right way to access the personalized section of the app, while in reality it was the button to access the general settings.</p><p>Only after checking the whole page they noticed the toggle Mode découverte/Mode personnalisé, and correctly selected the latter to access personal content. Once on the second screen, half of the users clicked on the title of the section “Mes recettes partagées”, while the other half noticed the “Voir tout” button and clicked on it. Eventually, each person tested found his/her way to the demanded folder by taking less than 3 wrong paths.</p><h4>Hi-fi wireframes</h4><p>As per instructions of the exercise, the <strong>changes applied after usability testing </strong>had to <strong>focus on the new feature, not on other aspects of the existing app</strong>. For this reason I renounced to modify the toggle Mode découverte/Mode personnalisé on the Homepage, even if all the interviewees failed to see them. On the other side, I decided to replace in the new section I developed, that of shared recipes, on screen n.3.</p><p>Similarly, I did not intervene on the titles of sections, which interviewees expected to be interactive. On the other hand, I decided to increase the size of the “Voir tout” button, as usability testing revealed it was little visible to a considerable part of users.</p><p>Here’s the final wireframes, the link to the Figma <a href="https://www.figma.com/proto/x1HsOX0zAVhVUpjyEopy05/Design-Critique-(Personal)?node-id=124%3A399&amp;scaling=scale-down&amp;page-id=124%3A388&amp;starting-point-node-id=124%3A399">prototype</a> and a recording of it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2U-t4wDeT1e2EjCV4DIrUg.png" /><figcaption>Hi-fi wireframes of the new feature</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_XQXyBfscG3iWBUvLpJTA.gif" /><figcaption>Recording of new feature’s flow</figcaption></figure><h3>Conclusions</h3><h4>Next steps</h4><p>How many times did you have to ask for the same recipe over and over because you lose the link to it? Or how many time you were asked to provide that link again? The new feature I designed for the 3rd project of Ironhack UX/UI bootcamp wants to find a solution to this annoyance.</p><p>The time we had allowed me to design a single flow, that of searching for a shared folder, but there <strong>many other flows </strong>that <strong>could be developed, </strong>provided adequate research validates them<strong> </strong>: adding a recipe to a shared book, allow users who have access to a cookbook to write private or group comments of recipes, just to name two.</p><h4>Lessons learned</h4><p>In the context of the bootcamp, this project was a “first time” under 3 points of view:</p><ul><li>The first prototype we develop until the high-fidelity phase: a tough test for our Figma skills!</li><li>The first project on which we work remotely, as our campus was closed due to covid.</li><li>The first time we work alone on a project, not in a team. Well, this is only partially true: as aspiring designers, we can’t help asking for feedback, comparing our job, teaching each other. We spent a lot of time discussing our projects on Zoom, to be fair :)</li></ul><p>I enjoyed focusing on UI and appreciated the opportunity of working remotely. The job market requires professionals able to work in a team even at distance: this exercise allowed me to test my skills in this sense, and I am proud of the result. I could feel the difference in efficiency between the first and the last day, and I adopted some good practices that allowed me to stay focused and get things done while also enjoying the support and the kindness of my schoolmates.</p><h3>Conclusions</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43c3c685b2de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping students with their paperwork to study abroad]]></title>
            <link>https://medium.com/@zuninogreta/helping-students-with-their-paperwork-to-study-abroad-9e419569e982?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e419569e982</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Fri, 31 Dec 2021 09:43:06 GMT</pubDate>
            <atom:updated>2021-12-31T09:43:06.995Z</atom:updated>
            <content:encoded><![CDATA[<h4>A UX case study for Ironhack bootcamp</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Ub60sPHXmfgZ_Xi50to0A.jpeg" /></figure><p>Immigration is a phenomenon as old as mankind. People move away from their place of birth to seek a different life: better work or studying opportunities, joining loved ones, opening their mind and trying new experiences.</p><p>No matter what’s the reason behind, moving abroad implies completing a certain amount of paperwork to allow the relocation and regularize the person’s status in the new country.</p><h3>Our mission</h3><blockquote>For our first group project at the UX/UI Ironhack bootcamp, we were asked to think about a solution to help people who move abroad with their papers, from the research of necessary documents to the application itself.</blockquote><p>The required output was a lo-fi prototype of an app.</p><p>Thank you to <a href="https://medium.com/@lobet.c">Célia</a>, <a href="https://medium.com/@Awa.Camara">Awa</a> and <a href="https://medium.com/@malloryagoumba">Mallory</a> for their great job. The first project of a bootcamp can be overwhelming, but together we learned a lot while also having fun.</p><h3>Kicking off the design thinking process: problem discovery</h3><p>The way we structured our project followed the <strong>design thinking process</strong>, one of the most common <strong>tools for defining a problem and </strong>then <strong>a solution</strong>, in a context that sees <strong>creativity</strong> and team participation as the key to success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t8Q0N96TdzxC3q8DK4t2FA.png" /><figcaption>Design thinking process of our case study</figcaption></figure><h4>Secondary research</h4><p>What do we know about the topic?</p><p><em>A lot</em>, since all of us had the experience of living abroad. <em>Still, we are here as designers, and the designer’s mantra is to design for the user, not for ourselves.</em></p><p>We put aside our personal stories and started our <strong>secondary research</strong> from scratch; we checked:</p><ul><li>Embassies’ websites to get some examples of procedures to get a VISA, for instance to the <a href="https://www.usa.gov/travel-and-immigration">US</a> and to <a href="https://france-visas.gouv.fr/web/france-visas/">France</a>;</li><li>Dedicated blogs to see what migrants were discussing;</li><li>If any product similar to the one we were asked to design had already been created.</li></ul><p><strong>CSD matrix</strong></p><p>We gathered our first findings in a <strong>CSD</strong> (Certainties, Suppositions, Doubts) <strong>matrix</strong>, a good tool to put together the Team’s first ideas when kicking off the design thinking process. On Miro, each of us wrote down his/her certainties, suppositions and doubts about the topic we were assigned.</p><p>We quickly realized that there are <strong>endless possible cases </strong>when it comes to immigration and related paperwork: there are close to 200 possible countries of origin, as many possible countries of destination, and a wide range of possible status/reasons for moving: working, studying, asylum seekers, family reunification, etc.</p><blockquote>We agreed on narrowing down our scope by targeting a specific category: people who move abroad for studying.</blockquote><p><strong>Opening Pandora’s box: surveys and interviews</strong></p><p>Time to finally get to know the experiences and feelings of potential users!</p><p>We agreed on starting with an online survey and then continuing with interviews, in order to grant our work both a strong quantitative and qualitative basis.</p><p>To better guide our respondents, we <strong>structured</strong> our <strong>questions in 2 categories: research-related and application related.</strong></p><p>As our project was intended for students, we made sure to screen survey’s respondents and interviewees accordingly.</p><h4>Survey</h4><p>Surveys’ results suggested that <strong>while</strong> <strong>governmental</strong>, official<strong> websites are those consulted more often </strong>(70% answers), <strong>a large chunk of international students also checks non-official sources</strong> such as blogs and social media (45% of answers each) in the research phase of their immigration process.</p><p>Similarly, half of respondents said that they did the paperwork on their own, but <strong>when seeking help, they preferred to ask family/friends</strong> <strong>rather than an official institution</strong> such as an immigration office or the school.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FsUdSi_hh_COrP6wgwFkQ.png" /><figcaption>Survey’s results: people prefer asking for help to family/friends</figcaption></figure><h4>Interviews</h4><p>Interviewees remember the <strong>immigration paperwork</strong> as an <strong>unpleasant process</strong> in the context of an experience, that of moving abroad for studying, usually perceived as positive and exciting. Students spontaneously started to talk about their misadventures, a gold mine for better defining their pain points and, at a later stage, shaping a valuable solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jkJXr76uxxZWABPTa5Qxew.png" /><figcaption>Interviews’ results: different obstacles in the VISA paperwork</figcaption></figure><h3><strong>Converging: problem definition</strong></h3><h4>Affinity map &amp; users’ pain points</h4><p>We gathered the insights collected through online research, the survey and the interviews on a whiteboard, as random stickers. We started to look for patterns, grouped those who expressed similar ideas and built an <strong>Affinity map</strong>.</p><p>Three main pain points emerged, no matter the destination country:</p><ol><li><strong>Lack of clear information about required documents</strong>: Embassies’ websites usually show the procedure and the list of documents needed to study abroad, but do not provide further explanation about the format or the exact paper required.</li></ol><blockquote>“To complete my VISA, I need a paper from my bank stating I had enough resources to maintain myself during my semester in the US. No hint was given on the specific document required nor the minimum amount of money considered as acceptable. Luckily, my bank advisor got it right and I had no problem with my application” — <em>An exchange student in the US</em></blockquote><p><strong>2. Lack of support from official organisms</strong>: when needing information or help in the procedure, interviewees didn’t find support in the official institutions. Universities limit themselves to providing the list of required documents to start the VISA procedure. Students usually do not have the chance to communicate with the Consulates/Embassies before the appointment during which they are supposed to hand off all the required documents. Dealing with these institutions was described by our respondents as unpleasant and frustrating.</p><p><strong>3. Language barrier</strong>: dealing with paperwork in a language different from its mother tongue can be extremely difficult, especially as in this context the vocabulary is specific, technical.</p><blockquote><em>Lack of accuracy and lack of support from the institutions while using a foreign language can cost time and resources to the person applying for a VISA, cause several back and forth between the research and the application process, make the whole process stressful and frustrating.</em></blockquote><h4>Persona and journey map: meet Julie</h4><p>To go forward in our definition stage, our Team created the project’s p<strong>ersona. </strong>Drawing on the insights gained through primary research, designers create personas to provide an exemple of the “average user”, with his/her <strong>goals, motivations, needs</strong> and <strong>frustrations</strong>. Creating personas makes all these points easier to remember, as they are turned into a story and can be associated with a person and his/her picture.</p><p>For our case study, our persona was Julie:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-DwrSj726Zjo_y44b4tkUA.png" /><figcaption>Our Persona, a synthesis of the patterns emerged from primary research</figcaption></figure><p>We then proceeded to the <strong>journey map</strong>, a design tool that retraces the Persona’s steps in his/her way to accomplish his/her goal, and the related feelings. In this case, we covered Julie’s experience from the acceptance at the university to the granting of the VISA:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cc22di7wD_h0ZSvzMOcGVg.jpeg" /><figcaption>Julie’s journey map for her student VISA application</figcaption></figure><h3>Converging: taking a design direction</h3><p>Visualising the journey map made us understand that <strong>by focusing our efforts on the research part, we could have simplified the application too</strong>. If the students were well aware of the procedure and the required documents from the beginning, gathering and filling them out would be quicker and less stressful.</p><p><em>“I used to study in Montpellier and I had to go back to Paris twice cause I was missing a document that was not mentioned on the official list” — </em>An exchange student in Mexico</p><h4>Problem statement &amp; hypothesis</h4><p>In shaping our hypothesis, we had to keep in mind the interviewees’ <strong>preference towards “in person” solutions</strong> when needing help in their immigration paperwork.</p><p>As a team, we agreed that providing accurate information and connecting people who want to study abroad with people who already had the same experience in the same country would make the immigration paperwork smoother.</p><h3>Solution discovery &amp; definition</h3><h4>Brainstorm and worst ideas techniques</h4><p>How to give shape to an app able to help Julie and the thousand of students who, each year, experience a similar journey to obtain their VISA?</p><p>Through the <strong>brainstorm</strong> and “<strong>worst ideas</strong>” <strong>techniques</strong>, our team came up with a <strong>list of “key features” and</strong> one of <strong>“nice to have”</strong>.</p><p>Worst ideas is a solution discovery tool in which each team member writes down a few bad solutions (impossible, illegal, nosense.. everything is accepted!) to solve the problem statement. Every idea is then reviewed and turned into a feasible one. The technique aims at stimulating designers’ creativity and, by going through unrealistic suggestions, pushing them to bring on solutions they would have not considered by thinking in a “politically correct” way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOb3hP8UEC3YtL5PJh16RA.png" /><figcaption>Our worst ideas turned into good ideas whiteboard</figcaption></figure><h4>Our solution</h4><p>We assumed the user was at his/her first access to the app, thus the login interface, <em>screen 1–2</em>. We structured our solutions in two parts:</p><ol><li>A short <strong>form</strong> that, once filled, <strong>displays</strong> an up to date <strong>list of actions and documents required </strong>to immigrate as a student <em>(Screen 3–4)</em>;</li><li>A <strong>matchmaking tool</strong> to connect people wanting to study abroad with people who already had the same experience: mentors <em>(Screen 5–6)</em> .</li></ol><p>As research highlighted language as a potential barrier in the paperwork, we decided to give users the possibility to <strong>choose the language</strong> of the app in the very first screen and to visualize each required document in the country of destination’s language, by clicking on the small “i” icon close to each paper of the list.</p><p>To address the issue of reliability of information provided, we decided to clearly state the <strong>source of the information</strong> provided and the date of the last update.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*90xZVL8FYQ05AUXYwGXuNQ.png" /><figcaption>Our Figma lo-fi solution, with explanations</figcaption></figure><h3>Metrics of evaluation and next steps</h3><p>While our project stopped at the lo-fi wireframes stage, our team agreed that in case of full development of the product, <strong>user feedback</strong> and <strong>reduction of</strong> the VISA <strong>application time</strong> would be the <strong>metrics</strong> to evaluate the success of our creation.</p><p>There are a few areas of our project we may want to further develop in future. First and foremost, the <strong>mentor flow</strong>. We may create a personal page in which the mentor gives information about him/herself, his/her experience abroad, to allow tailored-made matching with upcoming students.</p><p>Elaboration of a <strong>mid-fi version</strong> and <strong>user testing</strong> would follow.</p><p>While the app could potentially be built around any country of destination, we assumed that the beta version would cover only a few. A pillar of the product is the reliability of information, and with limited resources this can be assured only for a handful countries. App’s further development may offer <strong>a larger pool of countries</strong> to choose from.</p><h3>Retrospective: lessons learned</h3><p>Working for long hours with people we don’t know, putting in practice a whole set of new skills, at a high pace with new tools.. as a Team, we were amazed by the amount of work we put together in our first week of Bootcamp and proud of our first deliverable!</p><p>We had the opportunity to reflect on our work, and learn some <strong>valuable lessons </strong>we are looking forward to applying from now on.</p><ol><li>Some of our <strong>survey questions</strong> were not formulated clearly, and we couldn’t integrate the answers in our research. <strong>Choice of vocabulary and accuracy</strong> in the way the question is asked is something we will pay more attention to in next projects.</li><li>Rookie mistake: wanting to design for everyone. We did not understand the importance of <strong>narrowing down the scope</strong> of our work to a specific category (students, in this case), and this caused a little delay in our roadmap. It was not wasted time though: it allowed our group to discuss a lot, better understand our personal way of thinking and work better together in the next steps of our project.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e419569e982" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case study: Redesigning Skyscanner app to make it friendlier to non-digital native users]]></title>
            <link>https://medium.com/design-bootcamp/redesigning-skyscanner-app-to-make-it-friendlier-to-non-digital-native-users-a04ec75165f6?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a04ec75165f6</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Sun, 07 Nov 2021 18:41:39 GMT</pubDate>
            <atom:updated>2021-12-12T18:14:24.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*oaDt4dgaDaysnCILOBRVUw.jpeg" /></figure><p>Despite the name, the travel comparison app Skyscanner offers users not only the possibility to search and book flights, but also hotels, making it an appealing option to organize a travel from A to Z on a single platform.</p><blockquote>How well does it perform in this task? Is Skyscanner app a good tool for users who are not digital native?</blockquote><p><strong>A generation booking online for the first time</strong></p><p>To fully assess Skyscanner as a travel comparison and organization app, I focused on a user type that is neither digital native nor used to travel often. I interviewed 4 people, aged between 50–55, who regularly use smartphones but have never booked a travel online, as preferring to turn to physical travel agencies, considered « more reliable ».</p><p><strong>Testing the existing app</strong></p><p>I asked the 4 interviewees to perform a series of actions, with the objective of:</p><ul><li>Identifying the tasks/designs that resulted more difficult to them;</li><li>Redesign these items according to the interview’s results and in line with Nielsen’s Usability Heuristics.</li></ul><p>Here’s the scenario I created for the exercise:</p><p><em>“You are taking the lead to organise a well-deserved travel with your life-long friends in Rio de Janeiro. You are a busy person, so you are looking for an easy way to access both the flight and hotel options on the same platform.</em></p><p><em>From the app Homepage, please:</em></p><ol><li><em>Create a Travel folder, where stocking, at a later stage, Favorite flights and hotels</em></li><li><em>From the Travel folder just created, select and add:</em></li></ol><ul><li><em>A round trip flight for 4 people, with one layover max;</em></li><li><em>Two hotel rooms close to the city center”.</em></li></ul><p>The images included in this article show, from left to right: the original screenshot of the page, the page redesigned on Figma, the list of changes/additions applied.</p><p><strong>Step 1: creating “You Travel” folder</strong></p><p>A single folder for gathering favorite items is a great tool to save time when organizing a travel, especially if it is the first time a user performs such a complex task. The Skyscanner app includes such a tool, but interviewees found quite difficult to find and deal with it.</p><p>Their attention was grabbed by the « COVID-19: information on travels » paragraph; it took them a long time to find the main menu, at the bottom of the page, from which they could accomplish the demanded task, by clicking on the «Travel icon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qpKY7kYWuZKK5DiV24jE0A.png" /><figcaption>Skyscanner app: original and redesigned homepage, with changes applied</figcaption></figure><blockquote>Later discussion brought out that interviewees judged the covid paragraph important, in this time of uncertainty about physical movement, but not to the point to divert attention from the app’s main goal: searching and booking flights and hotels.</blockquote><p><strong>Step 2: adding items to Your Travel folder</strong></p><p>Once created a Travel folder, I asked interviewees to add a flight and a hotel.</p><p>None of them noticed the Plus button on the bottom right, the correct way to accomplish the task without leaving the Your Travel page. Instead, they all clicked on the search icon in the Menu, which allows to visualize the demanded options, but by leaving the Your Travel folder and requiring users to take additional actions to add the chosen flight/hotel to the personal folder.</p><p>At a later stage, when I asked users to add a specific flight/hotel to their favorites, they could not remember how to do it, as the explanation on the page was not catchy in its call to action purpose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*je1F_Hxdyu2WCa87M3PROg.png" /><figcaption>Skyscanner app: original and redesigned Travel page, with changes applied</figcaption></figure><p><strong>Step 3: searching a flight for 4 people with no more than a layover</strong></p><p>Flight search is Skyscanner’s core goal. I tested my interviewees to check if the task was easy to accomplish.</p><p>They had no issue with choosing the destination and the dates, but had a hard time finding for how many passengers they were doing their research, how to filter flights by number of layovers and how to add a flight to Your Travel folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G2CxIkWDn24DmR1s-KeGDg.png" /><figcaption>Skyscanner app: original and redesigned Flights page, with changes applied</figcaption></figure><p><strong>Step 4: searching a hotel room close to the city center</strong></p><p>Interviewees were asked to accomplish the task starting from the flight page. Only two out of four noticed it was possible to switch to hotels directly from the top of the page, while all of them were correct in clicking on the “Order and Filter” button to filter only hotels close to the city center.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*as0EYZF5HCGwEAAwkkTLow.png" /><figcaption>Skyscanner app: original and redesigned Hotels page, with changes applied</figcaption></figure><p><strong>Search for a flight and a hotel: redesigning a consistent system</strong></p><p>On the original app, flights and hotels search pages present identical tasks in a different way, while users tend to look for the same thing in the same place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEuVA67AztIMW-AzawEHFg.png" /><figcaption>Main differences affecting the consistency of Skyscanner app</figcaption></figure><p>I redesigned some elements of the two pages to grant an higher level of consistency, notably:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HMzoqmAIrJFsDo4AWu0Ghw.png" /><figcaption>Corrections to increase Skyscanner app consistency</figcaption></figure><p><strong>Conclusions</strong></p><p>While until a few years ago, booking travels online was a prerogative of young people, the audience is rapidly and increasingly attracting non digital native users.</p><p>This category may find a valuable tool in Skyscanner, as the app simplifies the task by allowing users to save favorite flights and hotels in a single folder.</p><p>Testing made clear that some key actions were difficult to accomplish for the user group under analysis, but easy to fix through UI revision and an increased level of consistency among similar pages.</p><p>Inclusion is a key principle of good design, and I think that it is in travel apps’ interest finding solutions to attract customers that are not experienced users but are willing to try and possibly stick to the product.</p><p><strong>Key learnings and possible further developments</strong></p><p>Evaluating an app’s usability and redesigning it seems an overwhelming task at first, that becomes feasible once broken down into smaller tasks.</p><p>It was the first time I completed the exercise, and there were two aspects I found tricky:</p><ul><li>Conducting the tests/interviews without giving the interviewees hints about the right answer;</li><li>Focusing only on a few pages/tasks: I had dozens of possible changes in mind, but after an hour I was overwhelmed and I realized I would have never completed the exercise unless I focused on the aspects I defined as priorities. I wrote the 3 key actions I wanted to focus on on sticky notes and looked at them every time I realized I was going out of the track.</li></ul><p>That’s what the final prototype looks like, keeping in mind that I worked only on the items described in the article: <a href="https://www.figma.com/proto/z0xdFqIkomsMp1zQPMZKx3/Challenge-3_Skyscanner?node-id=16%3A90&amp;scaling=contain&amp;page-id=16%3A89&amp;starting-point-node-id=16%3A90">Figma Prototype</a>. If I had more time, I would have like to work on the “Share” option: all of the four interviewees asked to include the tool, as it would make easier the travel organisation among friends.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a04ec75165f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/redesigning-skyscanner-app-to-make-it-friendlier-to-non-digital-native-users-a04ec75165f6">Case study: Redesigning Skyscanner app to make it friendlier to non-digital native users</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s behind your research on Pinterest? A UX analysis]]></title>
            <link>https://medium.com/@zuninogreta/whats-behind-your-research-on-pinterest-a-ux-analysis-7b3fc0d53993?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b3fc0d53993</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[pinterest]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Wed, 03 Nov 2021 16:36:16 GMT</pubDate>
            <atom:updated>2021-11-03T16:36:16.738Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTL9AHrIEjudBEAHQh2fVA.png" /></figure><p>Pinterest is a gold mine for new ideas, or « Pins », whatever the user’s centers of interest: from baking to gardening, from interior design to travelling. The app’s core objective is suggesting Pins based on the user’s previous researches, saved pins and folders created. Additional options allow to save, organise and share pins.</p><p>I spend quite a lot of time on it, and as a UX/UI design student I started to look at it with a critical eye.</p><blockquote>I realized that there are two main paths to reach a Pin: the first directly from the Homepage, the second through the Search option. In this post I will go through the two paths and I will try to explain what are the reasons behind the designers’ choices with regards to the differences between the two paths.</blockquote><p><strong>Path 1: selecting a Pin directly from the Homepage</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MjIM3vbtk3s4j75Vl8IynA.png" /></figure><p><em>Home page</em></p><p>When we open the Pinterest app, the body of the page shows a long list of Pin’s suggestions, that the user can scroll down endlessly (1st screen).</p><p>By default, on the top bar, the option « Suggested» is selected: the Pins showed are chosen by the app on the basis of the user’s previous researches and saved Pins. On the same bar we see the folders created by the user: by clicking on them, he/she can see new suggestions that belong to the relevant category.</p><p>On the bottom of the Homepage, the user finds a menu with four icons: Home, Search, Messages and the User’s page.</p><p>Through a nice micro interaction, the icon of the page we are on is colored in black, while the other icons are light grey.</p><p><em>A Pin’s page</em></p><p>From the Homepage, the user can directly click on a Pin.</p><p>A Pin’s page (2nd screen) is mostly occupied by a picture representing the Pin, equipped with several buttons which allow the user to interact with the Pin. In this post, I will focus on three of them, corresponding to the three last screens on the image above: the Save button, the Send button (on the bottom right) and the Visual research button, on the right corner of the Pin’s image.</p><p><em>Save a Pin</em></p><blockquote>On the Pin’s page, the Save button is the most important, the « call to action », and thus the only colored in black. Saving a Pin not only adds it to the user’s library, but also impacts the Pins that will be suggested to him/her in future. If a user saves dozens of Pins on jewelry, his/her Homepage will suggest more items related to the category.</blockquote><p>Once clicked on « Save » (3rd screen), the user can choose whether saving the Pin among the favorites, without categorizing it, or saving it in a folder, either new or existing.</p><p><em>Send a Pin</em></p><p>The icon at the bottom right of the Pin’s page allows the user to send the Pin. Two options are available:</p><ul><li>Send it through a media other than Pinterest: Messenger, WhatsApp, SMS, Email and Copy link are some of the possibilities;</li><li>Sending it via Pinterest itself: a list of users is suggested, as well as the search button to find others.</li></ul><p><em>Visual Research</em></p><p>The squared icon at the bottom right of the Pin’s image focuses on the image itself, recognizes the object(s) and suggests some Pins related to it, through artificial intelligence (5th screen). The User can move the rectangle that pops up on the image to focus on a certain part of it and narrow the research.</p><p><strong>Path 2: the Search option</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fC2b4S0yaGhDXJwZuTKxPg.png" /></figure><p>Another way to reach a Pin’s page is through the Search icon, the second in the bar menu at the bottom of the Homepage — the magnifier. After clicking, the user lands on a Search page (2nd screen) in which two sets of categories are shown:</p><ul><li>On the top, the categories chosen by the app based on the user’s previous researches, saved Pins and folders created;</li><li>Below, a selection of categories popular on Pinterest.</li></ul><p>On the top of the page the user can search for a category by typing a keyword, while at the bottom we still have the menu bar that allows the user, among other things, to come back to the Home Page.</p><p>When clicking on a category, the user lands on a page (3rd screen) showing many Pins belonging to it. By selecting one of them, the user lands to a Pin’s page that looks exactly as the one described in the Path 1 paragraph, including the Save, Send and Visual Research options.</p><p><a href="https://www.figma.com/proto/S8GqqpbgmLWmUD4muxeqRq/Challenge-2---Wireframing?node-id=36%3A1189&amp;scaling=scale-down&amp;page-id=36%3A1188&amp;starting-point-node-id=36%3A1189">Link to Figma prototype</a></p><p><strong>The difference between the two Paths</strong></p><p>The difference between the two Paths becomes clear when, from the Pin’s page, the user wants to come back to the previous page through the chevron arrow on the top left of the page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ut_VsKqxr_-R6aqQ0nSZ5A.png" /></figure><p>In Path 1 (Pin selected from the Homepage, on the top), clicking on the chevron arrow brings the user back to the Homepage, where Pins of different categories are shown.</p><p>In Path 2 (Pin selected through the Search option, on the bottom), on the other hand, the chevron arrow brings the user back to the Category page, and the category of the Pin previously selected continues to appear in the search bar until a new keyword is typed in.</p><blockquote>Why Pinterest’s designers decided to make this difference?</blockquote><blockquote>In my opinion, the two paths show two different user’s attitudes towards the research.</blockquote><p>In the first case, when the user selects a Pin from the Homepage, his/her attention is caught by the item, but there is no intentioned, pinpointed research behind the decision to click. When he/she wants to come back to the previous page, he/she wants to find again a wide selection of Pins, not necessarily related to the one he/she has just viewed.</p><p>On the other hand, when the user selects the Search icon, he/she has already an idea of what he/she is looking for, and either writes the keyword on the search bar, either he/she finds the category he/she had in mind directly on the Search page. After having viewed a specific Pin, the user is probably willing to see more ideas belonging to the same category: by clicking on the chevron arrow he/she is thus redirected to a list of similar Pins, where he/she will we able to pursue his/her specific research.</p><p><strong>A valuable teaching</strong></p><p>Producing the first wireframes was challenging, but also funny and rewarding.</p><p>I had a hard time dealing with components and wireframe kits. They are often made by several parts and I find difficult to modify them as a whole. They are an essential part of Figma and I am willing to learn how to master them.</p><p>On the other side, I feel that the previous exercises and challenges allowed me to work quicker and straight to the point. Before starting to work on Figma, I made sure my lo-fi design was clear on paper, reviewed and validated.</p><p>I have the feeling my analysis skills are improving: when I visit a website or I open an app, my instinct is that of studying the design and trying to understand the designers’ choices. I think this is a key exercise and that’s the reason why I decided to compare Pinterest’s two paths to reach a Pin.</p><blockquote>Seeing my first wireframes coming to life was a big reward: I know I still have a lot to learn, but these first achievements give me the motivation to keep on working towards my goal to become a good designer.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b3fc0d53993" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework:Greta_Challenge1]]></title>
            <link>https://medium.com/@zuninogreta/ironhacks-prework-greta-challenge1-d8f5f42f0fcb?source=rss-9ebf5c6cdb5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8f5f42f0fcb</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[travel-app]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Greta Zunino]]></dc:creator>
            <pubDate>Wed, 13 Oct 2021 08:51:53 GMT</pubDate>
            <atom:updated>2021-10-13T08:58:27.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rw7q9YEwawbAqCaoJV-uLg.jpeg" /></figure><p><em>Ironhack’s Prework:Greta_Challenge1</em></p><p>Never have people traveled as much as in the last couple of decades, and never has travel been accessible to such a large share of the population.</p><p>Such a revolution has triggered a whole <strong>set of services to make traveling easier, cheaper, </strong>and able to attract an even larger slice of the public. The realm of transportation was one of the most touched: millennials cannot believe there was a time when, landed in a foreign city, you actually had to buy a map and ask people around all the time. Today, you can simply open your smartphone and have any single road in the world at your fingertips.</p><p>Apps like CityMapper or UrbanGo not only show you how to get from point A to point B: they compare different means of transportation, guide you step-by-step until your destination, provide clear information on the time of travel and on possible delays. All of this in dozens of cities worldwide.</p><p>Still, <strong>many barriers arise when it comes to getting around in a city you don’t know</strong>. I had the chance to discuss the topic with people from different backgrounds: travel “newbies”, occasional travellers, globetrotters, people who live on a perpetual business trip. Despite the respondents’ variety, there were a few points they agreed on:</p><ul><li><em>Language</em>: directions, vending machines.. translations are often bad, or even non-existent. You feel SO lost sometimes!</li><li><em>Tickets</em>: what ticket do I need? Am I entitled to a discount? What is its validity? Can I switch from the bus to the metro with the same ticket?</li><li><em>Daily or weekly plans</em>: you often realize you could have saved a good bunch of money only at the end of your trip, if you had known THAT weekly plan existed!</li><li>…Getting stuck, lost or fined for just a ticket can ruin your long-awaited weekend escape, your crucial business trip, your first day at the university.</li></ul><blockquote>Interviewees said they would have welcomed an all-round transportation app able to guide the user not only on the journey, but also on the choice, the purchase and the payment of the ticket(s) needed to reach the final destination.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zcUtEIJ1D8FhY75Evbd4PQ.jpeg" /></figure><p>That’s what I tried to sketch in this first Design Thinking exercise: <strong>a CityMapper extension allowing the user to choose and buy the public transport ticket(s) </strong>needed for his/her trip.</p><p>Once selected the travel option of its convenience, the user can directly see the total price of the ticket(s) at the bottom of the page. By clicking on the “<strong>Ticket details</strong>”, he/she will access a page showing:</p><ul><li>A summary of the type and the number of ticket(s) needed for the whole journey;</li><li>Ticket(s)’ details for each journey leg;</li><li>The opportunity to get information on daily/weekly/other travel plans.</li></ul><p>A pain point strongly highlighted by interviewees was the language barrier. Travelers do not always speak English or the local language; translations are often unclear or inexistent.</p><blockquote>Writing the type of ticket(s) needed and the main words that may be useful in the purchase process in both the user’s language and the local language would be of great help to travelers.</blockquote><p>Once clear which and how many tickets are necessary, the next step, if the user wishes, is proceeding to the <strong>purchase, </strong>either online or at the vending machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCS68T4uVoAjIz_K90P5Ag.jpeg" /></figure><p><em>Option 1: buying online</em></p><p>If the option is available in the city selected, <strong>two choices open to the design team</strong>:</p><p>A) Redirecting the user to the <strong>local transport’s webpage</strong>;</p><p>B) Create <strong>a dedicated part of the app </strong>able to allow the user to complete the travel experience by also buying the ticket on the same platform.</p><p>This last option is surely more complex to develop, but interviewed people welcomed it warmly: if the app was easy and helpful until there, why leaving the user alone in the final, probably most difficult task?</p><p><em>Option 2: buy at the vending machines</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCLaGMaCbS5gNTN-3vO_cA.jpeg" /></figure><p>Certains users may not feel comfortable buying online, or the option may not be available in the city selected. The “Buy at the counter” option is there to assist the users in such scenarios. Once again, the <strong>objective</strong> is <strong>guiding the user step by step</strong>, reassuring him/her that the task will be quick and easy.</p><p>First goal: <strong>finding the nearest vending machine</strong>/counter; the app will show only the machines relevant to the ticket needed (you cannot buy a train ticket at a bus vending machine, for instance). It will show the different options on a map and, if wished, guide the user to the one of his/her choice.</p><p>Once there, the app will provide clear instructions on the <strong>steps</strong> to make <strong>to buy the</strong> well deserved <strong>ticket(s)</strong>.</p><p>The “Buy at the counter” option will not be possible in case the user selects a taxi, a shared scooter or a bike as means of transportation. In such cases, he/she will be informed of the situation and invited to visit the chosen means of transportation’s website to proceed with the purchase.</p><blockquote>The app extension is intended to guide the user step by step with a pedagogical approach: by repeating the name of the tickets and by giving clear instructions, the user will feel comfortable about the process, and likely to accomplish it on its own on the next purchase.</blockquote><p>Any traveler wants his/her experience to be as smooth as possible: moving around is often the most stressful part of a trip, and <strong>existing transportation apps could make a true difference, if they were able to assist users all along the journey.</strong></p><p>Brainstorming about such an app extension and coming up with a prototype made me understand <strong>how complex and fragmented is the set of actions that</strong> stretch from the definition of the route to the purchase of the ticket. It made me think that it is just the same in most of the actions we accomplish every day, and that <strong>UX/UI design try to make it easier and more pleasant</strong>.</p><p>It took me a long time to come up with a final framework: the task was so exciting that I directly started to sketch, instead of taking the time to analyse the problem and think about the answers I got during the interviews. I realized it was not just a loss of time, but also against the interest of the user, that is the main goal for us as designers.</p><p>That’s what I bring home from this first, passionate experience as a design thinker: <em>Things are complex. Users are complex. Possibilities are endless. Brainstorm, brainstorm, brainstorm, but don’t lose sight of the final objective.</em></p><p>One day we may laugh, looking at these first sketches. For now, let’s just be proud of them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8f5f42f0fcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>