<?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 Caterina Canale Mayet on Medium]]></title>
        <description><![CDATA[Stories by Caterina Canale Mayet on Medium]]></description>
        <link>https://medium.com/@caterina.canale.mayet.c?source=rss-77e01e7c39c4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*i-qJ13qmJu_zfFpFRqWCXQ.jpeg</url>
            <title>Stories by Caterina Canale Mayet on Medium</title>
            <link>https://medium.com/@caterina.canale.mayet.c?source=rss-77e01e7c39c4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:24:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@caterina.canale.mayet.c/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[UX Case Study: Pets Becoming Local]]></title>
            <link>https://medium.com/@caterina.canale.mayet.c/case-study-pets-becoming-local-d0bfedfab4ba?source=rss-77e01e7c39c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0bfedfab4ba</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[pets]]></category>
            <dc:creator><![CDATA[Caterina Canale Mayet]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 20:04:06 GMT</pubDate>
            <atom:updated>2022-09-03T18:38:03.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52cR9SPKN8rHU_Eyd2_DcA.png" /></figure><p><em>Be Local, Pet</em> is an app designed <strong>for dog lovers who move to a new place</strong> or travel to unfamiliar places with their pets.</p><p>This app is <strong>community-based</strong>, where people can provide and get <strong>trustworthy information</strong>, participating actively in helping other pet lovers with different issues related to their fur children.</p><p><em>Be local, Pet</em> allows users to find and reach hospitals, veterinarians, pet shops, pet-friendly recreation parks, restaurants, and bars.</p><p><strong>Clients:</strong> Alexia Recchi (CEO) Astrid Lustig (Head of Content).</p><p><strong>Project Length:</strong> 9 days.</p><p><strong>Team members:</strong> <a href="https://www.linkedin.com/in/caterina-canale-mayet/">Caterina Canale-Mayet</a>, <a href="https://www.linkedin.com/in/pikastih/">Pika Stih</a>, <a href="https://www.linkedin.com/in/clotilde-fourrier-4a6170a6/">Clotilde Fourrier</a>.</p><p><strong>Roles:</strong> UX Researcher, UX Designer, UI Designer.</p><p><strong>Format:</strong> Native App.</p><p><strong>Tools:</strong> Figjam, Figma, Maze, Google Forms, pen and paper.</p><h3>1. Project Goals</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bJ_snoKTGmvIRc3PiuccJg.jpeg" /></figure><p>The customer intended to build a mobile application called Be Local, Pet. Her initial idea was to create <strong>an app that could help pet owners who move to a new place</strong> <strong>find all the necessary services and amenities</strong> when there is not a peer network around them. Requirements were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*bt1xfqisq2-uacGGWUvR1A.png" /></figure><h4>The challenge</h4><blockquote>“When we moved to settle in the big city with our pet, we faced the anxiety of not knowing the best places to go with our dog. We also didn’t have anyone to ask, as we hadn’t made friends yet. That was the starting point of Be local, Pet.”</blockquote><h4>Initial Limitations</h4><p>The stakeholder’s <strong>idea was only in an initial stage</strong>, which we found challenging. However, this proved to be an exciting opportunity for innovation and creativity, as <strong>we had the freedom and opportunity to create a project from the very base foundations upwards.</strong></p><p>She came to us with this app view and the requirements for this one. They <strong>lacked a clear business plan or any quantitative research about the need for this product in the market</strong>. This aspect was a challenge for us designers, as we foresaw the necessity to do an extra investigation on the product market besides the UX process. Initially, this situation was a critical point due to the <strong>absence of this crucial elementary information or KPIs</strong> from the client end to guide the outcomes.</p><p>As a first step, <strong>we integrate this concern into our initial research</strong> to prove their assumptions and define the UX strategy for this project.</p><h4>What Was Our Design Process?</h4><p>We established Stanford D.school <strong>Design Thinking Process</strong> as the ruling method to lead our project. It is essential to mention this <strong>wasn’t a waterfall process, but continuous loops</strong> coming back to each step in the process to improve our MVP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mYWQ5Uo068j53zjGVpMheg.png" /></figure><h3><strong>2. Empathizing</strong></h3><p>We performed research based on the initial requirements by asking <strong>cat and dog owners </strong>who match the user criteria: what were the <strong>things they struggled</strong> with the most when arriving in a new place or when <strong>they got their pets for the first time</strong>? In which ways did they <strong>get this information</strong>?Is there a <strong>need for this app on the market</strong>?</p><p><strong>We ran six in-depth interviews and two surveys</strong>. A first survey to find the most common pain points among our users, and a second one to go deeper into the problems encountered in the first round of research.</p><p>We identified many problems and opportunities the app could help: <strong>finding pet-friendly</strong> flats, reliable pet-sitters, pet-friendly hotels, etc. In parallel, one big problem that arose was access to <strong>reliable information</strong>.</p><h4>Don’t Reinvent the Wheel</h4><p>We analyzed <strong>six possible competitors or similar products</strong> in the market that matched our app to find common points and understand how they work:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g0vCaxVFg35xsJPZoA9LWQ.png" /></figure><p>Some of our inspirations were how they displayed features such as <strong>pet-friendly places and parks</strong>, <strong>reviews and recommendation</strong>s for veterinaries and other services, a <strong>community of pet owners</strong> who help each other, and <strong>neighborhood updates and news</strong>, among other exciting design solutions. <strong>Colors and visuals were light and vivid</strong>, using youthful aesthetics.</p><h4>What did the people say?</h4><p>We performed <strong>two surveys</strong> on which we had <strong>38 answers</strong>. Some of the main findings were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rP3L8Ze7Rivp0yWJ2qlDFg.png" /></figure><p>Two of the most important findings we discovered reading the<strong> open answers</strong> in the surveys were:</p><ul><li><strong>People care most about reliable recommendations </strong>of places, reviews, and locations.</li><li>Sometimes there are issues they would like to <strong>ask experts, experienced people, or other owners regarding their pets</strong> that are not always veterinary related.</li></ul><p>What is <strong>essential</strong> for people to find in their area?</p><ul><li>Good vet &amp; hospital</li><li>Pet-friendly accommodation</li><li>Good parks</li><li>Pet shops</li></ul><h4>What did the people think?</h4><p>We did <strong>six in-depth interviews</strong> with pet owners who shared some experiences when they first got a pet or moved to a new place. We noticed <strong>the complexity of finding new services, information about their pet</strong> health or behaviors, or <strong>dog-friendly places</strong>. Some of the most remarkable comments were:</p><blockquote>“I never know where to go for a Pet Shop. And it’s hard to know if we can bring our dog.”</blockquote><blockquote>“Where to find dog-friendly areas nearby me? That’s is still complex for me.”</blockquote><blockquote>“I joined some Facebook groups like “cats in Berlin” and other groups about cats. I just ask there as a forum.”</blockquote><blockquote>“When traveling with pets or even in a new city, it is tough to find restaurants and bars that allow dogs — especially for places where it is colder, and you need to sit inside.”</blockquote><h4>What were our Insights and Approaches?</h4><p>After compiling all the information, we executed <strong>an affinity diagram and a user empathy map</strong>. We narrowed the findings down to a list of insights to frame the problems and opportunities on where to focus:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L_8HlzZ5Gm75s-4psJo5Fw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSph9DdHCNAGFG7BsMOfoQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toXxp9uPqPeJ1lKBVm0FXw.png" /></figure><h4>From Pet Owner to Pet Lover</h4><p>In the original brief, our stakeholder targeted this app for <strong>people with pets moving to a new place</strong>, as the primary <strong>target user for this app</strong>. However, <strong>we identified other user groups </strong>as new pet owners and travelers pet owners during the research.</p><p>We built <strong>two user personas</strong> following these groups, considering all the problems and needs we found.</p><p>Notwithstanding, <strong>Later in the DEFINE, IDEATE, and PROTOTYPE phase </strong>of the project, we struggled with having many ideas/solutions for all of our users as we continued our design process. So <strong>we came back to the user definition, narrowed</strong> them down to<strong> our initial user</strong>, and let the <strong>edge cases accommodate</strong> themselves in the Minimum Viable Product (MVP).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XK8uQ-mja_LBhLHyPEY-yQ.png" /></figure><p>Following this twist, what helped us figure out our users better was framing<strong> it as a pet-lover rather than a pet owner</strong>. We understood that most of our target group is <strong>dedicated and passionate pet owners</strong> that strongly care about their furry children.</p><blockquote>“Sometimes it is challenging to find reliable services when it comes to my dog needs.”</blockquote><p>As obvious as it sounds during the course of the project, we realized this app <strong>was not thought for every pet, as stated in the beginning, but primarily for dogs</strong>. During the research, we consult many pet owners, including cat and birds owners, on what we recognize that dog owners’ needs are different from<strong> other pet owners</strong>, like socializing with other pets or going to a close park to walk.</p><p>In this way, <strong>we primarily focus our MVP on dog owners and accommodate cats </strong>as a first stage. Then we left a room open for similar needs of other animal owners.</p><h4>Vivianne’s Experience Journey</h4><p>Consecutively, we piece together all our pain points and the user needs in <strong>a journey map </strong>that helped us frame the problems better. As was mentioned above, <strong>we focus only on one user persona for our NVP</strong>; therefore, we work with Vivianne’s journey moving to Madrid.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2SEnroonDS_AD7O3iTVcA.png" /></figure><p>Through her journey, We point out the <strong>online research (Google and Facebook groups) and who to ask as the significant frustrating steps in her quest</strong> to find places, services, and information for her dog, more <strong>when something happens to her dog</strong>. She would like to have <strong>recommendations from real people</strong>, but she feels frustrated the information is not entirely reliable.</p><h3><strong>3. Defining</strong></h3><p>Later in the project, when we started the <strong>Ideation process (wireframes)</strong>, we faced <strong>the difficulty of narrowing many problems down to a global one and defining this properly. </strong>We realized we were disoriented as we tried to solve many needs simultaneously. We were also concerned about whether we were only <strong>solving the stakeholder requirements and not a real need</strong>.</p><p>Therefore, we used <strong>the help of our user stories, the jobs to be done</strong> in the app, and defined the <strong>information architecture</strong>. These let us make our problem statement, hypothesis, and HMW question to guide our outcomes. In addition, as we mentioned before, we <strong>narrowed our two users into one</strong> for this first stage of the product, and we <strong>reduced the number of design elements</strong> to the <em>must-have.</em></p><h4>The Problem…</h4><h3>Pet lovers who are new in a city need reliable ways to find pet-friendly places, services, and information for their pet based on their location, as they don’t yet have these connections in the city and want to make sure they get reliable sources.</h3><h4>The Guiding Question…</h4><blockquote>How could we create a community app based on location, recommendations, and trustworthy information to help pet lovers in a new city discover the best places for their pets?</blockquote><h4>The Hypothesis...</h4><blockquote>We are confident that by designing this app based on trustworthy recommendations by a local community, pet owners who are relocating to an unfamiliar place (or are traveling) will be more confident with the decisions they are making regarding their pets.</blockquote><h4>What are the jobs this app has to be done?</h4><p>The team defined then the jobs-to-be-done(JTBD) list this app should take into consideration to solve the problem and the user’s needs:</p><p><em>“Find reliable pet places and information in a city, based on reviews.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qNkhn27bhYHRAbkKpEV5_g.png" /></figure><p><em>“Ask for help, pet socialization, or talk to the community about any pet-specific question or issues.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aOuL6zryRRfMT-Sdue-ftw.png" /></figure><h4>The Product Values</h4><p><strong>Together with our stakeholder,</strong> we performed a session where we terminated the brand values the product should have. Based on our research and the customer ideas, <strong>we determined six central values</strong> that could help our final prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kn3vJEk83Dg0jcxghFEfGg.png" /></figure><h3><strong>4. Ideating</strong></h3><p>The <strong>Brainstorming session </strong>produced<strong> </strong>a bunch of ideas (keeping in mind what the stakeholder requested) that were grouped by concept similarity due to the large amount of them. In this way, we classify them by the <strong>MoSCoW prioritization method</strong>. We defined the ideas that should and must this new app have.</p><p>Nevertheless, as explained before in this case study, when designing the first <strong>wireframes</strong>, it wasn’t easy to <strong>prioritize which ideas and solutions should and must be in our MVP</strong>. Hence we decide to return to the previous design process steps and <strong>redefine our problem</strong> statement, choose only <strong>one user</strong>, and <strong>downsize the user needs</strong> for this first step of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zevvc3KRtfifbEKKNJJrXw.png" /></figure><h4><strong>The Information Architecture</strong></h4><p>We <strong>prioritized and grouped our <em>must-have </em>ideas</strong>, sketched a sort of navigation, to finally enclosed <strong>three main sections</strong> that would construct the <strong>primary navigation</strong> in our app.</p><p>In the same way, we gathered <strong>our conclusions and stakeholder needs</strong>. We added <strong>features and requirements </strong>to help users <strong>find trustworthy places, get information</strong>, and feel c<strong>omfortable in different use cases.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXVP3HDGRZXJtY88GuCWSg.png" /></figure><h4><strong>Making it tangible</strong></h4><p>We proceeded then to b<strong>ring these ideas to life</strong>; therefore, we gave it spirit and body like any living thing. We move onward, designing <strong>four mood boards to choose from</strong> that our stakeholder and other potential users would like based on our research and brand values. We decided to go for a <strong>pastel pallet and a playful style</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*G0WS3YlC9WOD1iOGVzNV0w.png" /></figure><h3>5. Prototyping and Testing</h3><p>In parallel, we started the first <strong>sketches</strong> that could help us create our prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BqgdLY8wQuUSkLoek2-aEA.png" /></figure><h4>Our First Try</h4><p>Based on our first wireframes, we constructed a <strong>mid-fi prototype</strong> with its <strong>main navigation through a bottom bar where</strong> we display our community, profile, and places access through a <strong>map or a list to switch</strong>. Additionally, we set <strong>secondary navigation in the upper area</strong> through filters and a search bar.</p><p>One of the <strong>obstacles we faced in this step</strong> was to question the team and ask, <strong><em>“what are we really solving? Is the problem clear?”</em></strong> the problem wasn’t apparent, and <strong>the solutions we were giving were still vague</strong>. Thus we did a draft of a site map to guide our screens that later on <strong>became straightforward navigation</strong>. In addition, as mentioned before in this case study, we <strong>reframe our problem statement and solution, narrow it down to one user persona, and diminish the ideas to solve in this first stage.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AOPZKGrxjOPBdGSadYIFag.png" /></figure><p>We tested it with potential users, on which we got <strong>25 responses</strong>. The results were:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*RK7kdzejcvDpQZzqRdlX8Q.png" /></figure><ul><li>Users couldn’t figure out completely <strong>how the navigation bar worked</strong>. That is why we redesign it in different content boxes for each section.</li><li>We found out users <strong>couldn’t understand the place profiles</strong> and their information. We made them more compressible and minimized de visual noise.</li><li>The <strong>categories of the community section</strong> were redefined and rearranged.</li></ul><h4>How Do Users Navigate?</h4><p>After seeing the performance of our previous prototype, we determined <strong>eight user flows</strong>, highlighting the <strong>three critical ones </strong>we wanted to test in the following prototype:</p><p><strong>Look for a place</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msfbVRiXfKt7S5y7Yzm9_A.png" /></figure><p><strong>Desirable flow:</strong> Map &gt; Select category &gt; Display categories &gt; Select category XX &gt; Show map with selection &gt; Select a place in the map &gt; See pop-up with information &gt; “See more” &gt; Page about the place &gt; Leave a review &gt; Leave a review.</p><p><strong>Follow Onboarding</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyYhyC27-6D_PNtpKYerJw.png" /></figure><p><strong>Desirable flow:</strong> Presentation page &gt; Presentation page (discover) &gt; Presentation page (see alerts) &gt; Presentation page (post places) &gt; Presentation page (Ask) &gt; Finish tour.</p><p><strong>Ask a Question</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u3kPtqDuMc49DlNBnM3J-Q.png" /></figure><p><strong>Desirable flow:</strong> Comunity home page &gt; Post a question &gt; Write a question &gt; Publish a question.</p><h4>Building our High-Fi Prototype</h4><p>We started drafting our high-fi prototype defining its design system, components, and screens. In the middle of the process, we <strong>had different opinions on the look &amp; feel</strong>. After not reaching a consensus, we decided to create <strong>four options and let people and our stakeholder decide</strong> on what they thought was the most apeling option.</p><p>It was a complex process, as the team had strong opinions on the app’s appearance. Finally, <strong>we refined the look &amp; feel while we were doing it until getting a final solution</strong>. For instance, we eliminated the yellow boxes designed initially and replaced them with light grey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01n9tNhYwvGgag3yRFwpjQ.png" /></figure><p>The prototype took us <strong>many screens</strong> to design and <strong>many flows</strong>.</p><p>We showed the prototype draft to the <strong>stakeholder, and she liked it</strong>. She did some <strong>observations</strong> about the product; we decided to execute. We suggested implementing more features and elements. We let her understand that <strong>we did not have enough time or capacity to achieve all these additional requirements</strong> before the deadline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yO01pOmXba5muvYywYxlNQ.png" /></figure><h4>The User&#39;s Reactions to our High-Fi</h4><p>When we finally finished our first High-fi prototype, we sent it to test. We got <strong>17 responses</strong> with the following feedback:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lo7RKQV3iByHdlvaEO3ybA.png" /></figure><p>Some crucial comments targeted how the <strong>information was displayed </strong>or how <strong>interactions were understood</strong>. For instance:</p><blockquote><em>“To expand a post, the CTA “comment” is confusing. Because maybe I just want to read more but not comment.”</em></blockquote><blockquote><em>“I did not know at first where to find the list of vets. I wanted to click on search.”</em></blockquote><blockquote><em>“I couldn’t find more information about one of the vets, and I didn’t see a back arrow or a close icon to exit the vet view.”</em></blockquote><p>We decided to re-check the <strong>user mental models. </strong>In this way, we changed to <strong>recognizable icons</strong>, redesigned the category list’s access on the map, <strong>changed the wording</strong>, and <strong>improved the generic interface.</strong></p><h4>The Design System</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ii1EqTbMMhL7fcYWUQojoQ.png" /></figure><h4>The Design Solution</h4><p>During our research, we realized the <strong>need for the original product</strong> required by our stakeholder <strong>was fulfilled in other ways</strong> such as through Facebook groups, Google, references from friends, etc. Therefore <strong>it wasn’t an urgency or a big market for this, but the importance of creating this product.</strong></p><p>However, the need to contact other pet owners to ask questions through a <strong>support forum of Q&amp;A</strong>, and a local network of <strong>pet owners giving local news</strong> regarding their pets, for instance, is<strong> the added value of this product, the concept of the <em>local community.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4L8OLdK_kRTqo90t9wJMsA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*NDSwlwMDXs2LE53VKcNVfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*Z9mGDoqUt22NsymHv4okzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*91SnrnVMZGpiKDA5eTNqDw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*cUcJ_jt6n9fwE23UgZ5MTg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*LVMmYvGoi48Jd_lQgAGDPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*ZdfU3nVlS5eR0B3g34LwnA.png" /></figure><h4>Final Prototype</h4><p>Here you can see a video of our final prototype:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F694149108%3Fh%3Da686a1ecc3%26app_id%3D122963&amp;dntp=1&amp;display_name=Vimeo&amp;url=https%3A%2F%2Fvimeo.com%2F694149108&amp;image=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F1404490895-0e515f6bf0f08a1063e0b124f95949a657fba84a70cd94f62a7b313f0efcfb90-d_1280&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/1611059ca46ff1823506d218caf437ca/href">https://medium.com/media/1611059ca46ff1823506d218caf437ca/href</a></iframe><h3><strong>6. Outcomes and Lessons</strong></h3><h4>Reframing The Main Problem</h4><p>Our ideation brought <strong>many good idea</strong>s, and we performed the MoSCoW method, where <strong>we placed many <em>must-haves </em>to implement in this stage</strong> (MVP).</p><p>When we were developing the first stage of the prototype, we realized <strong>we were disoriented</strong>, as we didn’t know <strong>how many problems to solve</strong> due to a <strong>lack of prioritization</strong>. We were concerned we were <strong>not solving a real need.</strong> We found many issues the app could fix, but the <strong>main problem wasn’t identified correctly.</strong></p><p>After looking for a <strong>third party</strong> who could give us an external point of view and guide us, she pointed out the <strong>problem statement wasn’t well defined</strong>. Therefore, the <em>must-haves</em> solutions in our MoSCoW method would be excessive if we <strong>tried to solve all problems at once.</strong></p><p>As a result, we <strong>narrowed our personas</strong> to only one (new person in the city), and we <strong>prioritized the lack of trustworthy information as our main problem.</strong> That helped us to filter the essential ideas from the secondary ones.</p><h4>What Is Next?</h4><p>What the client has in mind:</p><ul><li>Add <strong>discounts</strong> and collaborations with pet businesses.</li><li>We are organizing <strong>events</strong> to increase trust.</li><li>Implement trustworthiness <strong>badges</strong> from users to other users.</li></ul><p>What the UX team recommends for a future sprint:</p><ul><li>Improve <strong>filtering options for location</strong> — specifically, where the user wants to look for places.</li><li>Improve <strong>searching options to look for services</strong> — Work on refining categories, filters, and visual map iconography.</li><li>Improve <strong>categories management in the community section</strong> — once the community grows, will be countless questions to categorize and manage. How will users search for question-answers?</li><li>Save your favorite places and comments.</li><li>Inclusion of pet sitters recommendations.</li></ul><h4>Learnings</h4><p><strong>How to work with stakeholders:</strong> Sometimes, the stakeholder requirements come in a very early stage, as an idea that has not been tested or a niche that is not needed. How do you deliver to them?</p><p><strong>Quality over quantity:</strong> When we, as designers, want to deliver a perfect product with many user cases possible in a short period, we need, yet, to come back to our core drivers and focus on the MVP.</p><p><strong>This is a simulation of the real world:</strong> We will make mistakes, we will forget details, things will not going to be perfectly delivered, but it is ok…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0bfedfab4ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Prototype in Figma.]]></title>
            <link>https://medium.com/@caterina.canale.mayet.c/my-first-prototype-in-figma-8e31b17caacd?source=rss-77e01e7c39c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e31b17caacd</guid>
            <dc:creator><![CDATA[Caterina Canale Mayet]]></dc:creator>
            <pubDate>Wed, 04 Aug 2021 22:45:03 GMT</pubDate>
            <atom:updated>2022-03-21T14:01:13.381Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are reading this, maybe it is because you were looking for content about beginner experiences using Figma or just because this article popped up in your feeds. If you are the first case this post is for you. I would describe how my experience doing “reverse engineering” with the Spotify app was.</p><p>I decided to start a new career path in User Experience Design (UX). Therefore my limitations as a newbie and the self-learning time consuming lead me to seek help joining a Bootcamp where I could challenge myself. In this way, I signed up to start this learning pad with IronHack Berlin.</p><p>In my previous week before the Bootcamp started, I had to perform a design challenge where I could apply My basic knowledge in Figam doing “reverse engineering” from a conventional app. The app I chose was Spotify.</p><p><strong>Flows and Tasks.</strong></p><p>Why did I decide on this app? One of the tasks in this challenge was to pick a user flow that has between 5 or 7 screens to prototype in Figma. Then I asked myself which app from my phone has interesting ways to navigate? At that moment a Tash Sultana song was heard from the speaker and I decided to keep listening to the same type of music genre. I opened Spotify on my phone and I realized one can navigate in this app in an interesting way. This lets me set the task to find “Tash Sultana Radio” as my main flow.</p><p>To understand this simple flow, I did a basic scheme where I can graphically explain the task better:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*VHhwirqjp3fdrNcaom06ng.png" /></figure><p>In this image, we can observe the same task but with 2 different flows to achieve the main task, which was to listen to a similar style of music similar to Tash Sultana songs. Why does this task have 2 flows? Because Spotify has different ways to reach certain pages or information. There is not only one way to navigate through the app in order to achieve one task.</p><p><strong>Prototype.</strong></p><p>Then after delineating the main flows, I proceeded to build my lo-fi prototype in basic monochromatic wireframes to make it easy to explain, improve and not distract the attention from the main flows.</p><p>I put emphasis on the main elements in the screens that helped me to achieve the tasks. For example, buttons or texts that were necessary to find the information to get to the radio. The rest of the elements reminded plain and phony.</p><p>The final result was 6 screens that were necessary to draw in Figma to explain the Flows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhlsdeHwzLKlxcDpJkQ8xQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_3CYmz_cCmGji2sbrYU6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*50NuGrg6g1TvQar3Y0nwNg.png" /></figure><p><strong>My experience building my first prototype in Figma.</strong></p><p>With the basic knowledge I had on Figma, it was sometimes a little complicated to keep going with the prototyping. One of the biggest problems was the use of UI element kits, where most of them were nested in purple “masters” or “groups” of layers (I can’t find the proper description on the web still), making it almost impossible to edit in size/colour by a beginner without the proper knowledge. In the end, I spent more time figuring out how to work with these elements rather than designing my own.</p><p>A positive aspect of Figma is how intuitive and easy it is to use if you compare it with other edition software like Sketch or Adobe XD. All commands are super clear and effortless to understand.</p><p>Finally, I had so much fun challenging myself with this little project. I have learned how to be more structured while working, tagging numerous elements to not get confused when editing. I understood how important it is to have your virtual workspace tidy and clean, and how this can facilitate the work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e31b17caacd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Citymapper: 8 hours Design Thinking Challenge.]]></title>
            <link>https://medium.com/@caterina.canale.mayet.c/how-i-designed-4-new-app-features-in-less-than-8-hours-fee386ea30f5?source=rss-77e01e7c39c4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fee386ea30f5</guid>
            <dc:creator><![CDATA[Caterina Canale Mayet]]></dc:creator>
            <pubDate>Wed, 04 Aug 2021 00:06:16 GMT</pubDate>
            <atom:updated>2021-08-26T21:14:39.871Z</atom:updated>
            <content:encoded><![CDATA[<p>This title might sound very impressive for people who are in the business of UCD and know this kind of project can take very long even for a team. But I would like to put you in context before continuing.</p><p>I decided to start a new career pad in User Experience Design (UX). Therefore my limitations as a newbie and the self-learning time consuming lead me to seek help joining a Bootcamp where I could challenge myself. In this way, I signed up to start this learning pad with IronHack Berlin.</p><p>One of the first exercises I had to perform was a design challenge where I could apply my basic Design Thinking knowledge and practice it on the way.</p><p>One of the biggest limitations was the time to carry on the challenge. I signed up just one week before the next Bootcamp started. This gave me 3 days to work on previews-course exercises the majority of people get 1 week or more to perform. This is why I did this challenge in less than 6 hours like a proper design “jam”.</p><p><strong>About the design thinking challenge</strong></p><p>The original challenge was to create a feature in an app called UrbanGo where the user could purchase different transport tickets to get to their destination in one place. The Outcome? Using rapid prototyping through paper sketches.</p><p>UrbanGo is a public transit and mapping startup that seeks to solve the problems of urban mobility by offering the quickest and cheapest public and private transport routes to its users in different places of the world.</p><p>Unfortunately, the first problem I faced was the app was not available in my Play Store to work and analyze it for this challenge. Therefore I went for another alternative app called Citymapper to keep going with the design process.</p><p>The Citymapper app has mainly the same functions and options as UrbanGo, with the difference that this other app does not have information about the ticket cost or ticket quantity like UrbanGo. In this way, I had to rethink the main challenge based on these limitations and work with the resources I had at this time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FaCTazHBtUTME-kZJ3XVQQ.jpeg" /></figure><p><strong>Goals of the Design Thinking Challenge</strong></p><p>I was assigned a series of questions to address and prepare my design process, while also guiding me in creating the best possible solution to the assigned problem.</p><ul><li><em>What problem are you solving?</em></li></ul><p>Find a quick and easy way to buy all tickets for one trip in the Citymapper app while traveling abroad, where the knowledge of public transport is limited, or in some cases, unexisting.</p><ul><li><em>Who is your audience?</em></li></ul><p>People who travel to different parts of Europe (or the world), who go for the first time or are not familiar with the public transport system in these places.</p><ul><li><em>Who is your client’s competition?</em></li></ul><p>Local apps or websites that inform or help people to purchase their tickets while traveling. E.g. BVG FahrInfo App in Berlin, or publictransport.com.cy in Cyprus.</p><ul><li><em>What’s the tone/feeling:</em></li></ul><p>Looking to find the main pain points in the experience of taking public transport in other places of the world. How people feel frustrated or confused during this process, as well as the helpful actions or processes that enrich positive experiences.</p><p><strong>Interview guide</strong></p><p>The second task, after framing the process and goals, was to get information from real users to know what they think, feel and experiment during these instances. For this reason, I prepared a small interview script to guide me in the information pursuit, and take the data out of the people’s heads.</p><p>Two of the biggest limitations I had, were the number of people available in a short time and how more or less candid the interviewed were, hence, how talkative the person is and how to make the right questions open up to insightful answers instead of short answers. I talked by video calls with 4 people, setting an interview timeframe not longer than 30 min each.</p><p>The interview script consisted of 6 main questions that led to open following questions according to the answers given, in order to get more information from the person interviewed:</p><p><em>About the user:</em></p><ul><li>What do you do? Tell me about yourself.</li></ul><p><em>About public transport use:</em></p><ul><li>How often do you use public transport? Or how do you move around?</li><li>Which public transport apps do you use in your daily life and why?</li><li>How do you buy tickets when using public transport? Apps, office, machines?</li></ul><p><em>When using public transport abroad:</em></p><ul><li>Tell me the last time you used public transport when traveling: How did you know the way to get to your destination? How was the process to get tickets for this trip?</li><li>Tell me an anecdote in the past where it was challenging to find the way to buy your tickets. Be as candid as possible.</li></ul><p><strong>The insights and the problem definition</strong></p><p>After getting as much data as I could, I proceeded to condense the information so that the findings were more tangible and limited to work on solving the problem. For this, I wrote the main findings in Post-its and group them in a way that could make sense. This helps me to have a wide overview of the issue, and asset the main insights:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9kOplQQ-oV-2oVAXpUqL0Q.jpeg" /></figure><ul><li>People prefer to take public transport when time is tight, the weather is bad or when it is a long-distance trip. However, they are happy to have bicycle options if available.</li><li><em>Confusion on where and how to buy these tickets ruins the user experience:</em> Most people look on the web or Google Maps before their trip starts, to know what to expect. However, Google Maps does not work in many places where sometimes there are options to use local apps-websites that are not linked to the Google Maps app, but this is not always the case.</li><li>When all the above does not work, they turn to a local to ask how the drill works. Finally, as a last resource, some people never find a way to get tickets and they risk fines using public transport anyway, leaving the person in fear of being checked or even committing a crime.</li><li><em>Every place differs on how to buy and what the tickets cover:</em> In some places, it is possible to buy online tickets beforehand, in some places one needs to buy directly in the machine or the driver (sometimes with the exact amount of cash), finally in other places it is used only topped up transport cards that work with tap-on.</li><li>Moreover, people have to figure out whether the tickets work by zone-distance, by single trip-timeframe, or if it is necessary to buy weekly or monthly tickets. This confuses people giving the feeling they do not have control over this.</li><li>Finally, some people struggle with the language, the type of payment, like credit cards from other countries, and the time to buy the tickets before the vehicle comes.</li></ul><p><strong>Ideation</strong></p><p>Following the process, I forged ahead with a brainstorming session to look for the best solution. The 2 most interesting ideas were having a local buddy to help the user in the process to get a ticket and/or find the best way to get to his/her/their destination while visiting the place. The second idea was to create a community of volunteer users who could contribute with local information in the app whenever they found it.</p><p>I decided to go for the last idea as It was the best match with the current Citymapper application.</p><p><strong>Prototyping</strong></p><p>I started to put this concept on rapid paper sketches, which I divided into 4 functionality flows:</p><p><em>Changing language and adding credit cards:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPDyBjoQa_6IV1i3ISlL1w.jpeg" /></figure><p>In this flow, the user is capable of choosing the language he/she/they want. To narrow the list I went with 6 suggested languages most of the users speak. Hence, the user is capable of finding its way without getting confused by the local language. In the same way, the user can add, in settings, his/her/their credit card for future payments in the app.</p><p>It goes without saying that transport web engines, local transport apps around the world, should be linked to the Citymapper, so that the user can buy any available ticket everywhere.</p><p><em>Choosing to ride a bike instead of using public transport:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9dMagcWzHpFdWjW5UgjCLw.jpeg" /></figure><p>The main idea of this process is that the user can rent a bike without going to each renting-bike app, and so the user can pay directly with his/her/their credit card linked to Citymapper.</p><p><em>Buying public transport tickets:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WN_Mpx5167e3L2aUsDdlKw.jpeg" /></figure><p>When the user decides to take public transport, there is an option that shows the price of the entire trip. This allows the user to buy a ticket just using his credit card linked to the app whenever in the world he/she/they are.</p><p>In the same way, the user can buy connection tickets in the case there is an existing ticket for one or some of the trip sections. This allows the user to save money and have all the tickets he/she/they need in just one app to show. Finally, the app also shows the main type of tickets people use in the city.</p><p><em>When is not possible to buy a ticket through the Citymapper:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwEwPYBV8fsBodlcAIXvhA.jpeg" /></figure><p>In this last flow, the app informs the user there is no way to buy a ticket online, giving the option to find the nearest place to purchase the ticket physically, like a shop, an office, or a ticket machine. Also giving tips to make the user journey easier. E.g. to buy the ticket directly on the train or in the bus with cash or card.</p><p>In this flow, I show one of the creative solutions to the main problem, which is to find a place where to buy a paper ticket when the user does not know where he/she/they can get it. To solve this problem there is a section where users can contribute to the app data by providing information if they notice something. In this way, the user can have more options where to go in unknown places.</p><p><strong>Conclusions:</strong></p><p>To keep improving a project like this is necessary to keep going through the ideation process and many days of research, solutions, and iterations. A work team is needed that contributes different visions for each idea. For an 8 hour project made by a beginner, there are limitations that are impossible to skip.</p><p>I had so much fun challenging myself, learning new ways to solve problems, and practicing skills like visual thinking, design thinking, and prototyping. They were 8 very interesting hours to make me ready to start this 3 months party.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fee386ea30f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>