<?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 Luís Perdigão on Medium]]></title>
        <description><![CDATA[Stories by Luís Perdigão on Medium]]></description>
        <link>https://medium.com/@luismperdigao?source=rss-2b0bd98d4b57------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2ysO2fd11xrJT5aDkrCZxQ.jpeg</url>
            <title>Stories by Luís Perdigão on Medium</title>
            <link>https://medium.com/@luismperdigao?source=rss-2b0bd98d4b57------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:33:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@luismperdigao/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[imotion — How are you really doing?]]></title>
            <link>https://medium.com/@luismperdigao/imotion-how-are-you-really-doing-7f472cde1d12?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f472cde1d12</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Sun, 28 Nov 2021 20:37:49 GMT</pubDate>
            <atom:updated>2021-11-28T20:37:49.982Z</atom:updated>
            <content:encoded><![CDATA[<h3>imotion — How are you really doing?</h3><h4>Designing a mood tracking app</h4><p>Hello dear Medium community,</p><p>I would like to present you the case study of one my latest projects during my UX/UI Design Bootcamp at Ironhack Berlin. The current project was individual and developed within the course of 2 weeks.</p><p>Our task for this project was to apply design thinking methodologies to design a mobile app for <a href="https://nationalwellness.org/">The National Wellness Institute</a>.</p><p>The purpose of this app was to help people adopt and maintain a routine that enhances their well-being, driving them to action.</p><p>The tool could be focused in any category related to personal wellbeing. The only requirement was that it should tracks the user’s progress and push them to commit to a healthier lifestyle.</p><p>Since the wellness sphere is so complex and diverse, my first step was to research potential problems wellness which could be tackled.</p><p>Analysing data from several sources, it became obvious to me that mental health is a huge problem which affects a big part of the world population. The most found disorders are anxiety and depression. The data I found is from 2017 but the ongoing pandemic crisis just aggravated the situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*vi1uQlYultCLIzSbrbHmTA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wyEy9Wm9WVeIODujcviuXg.png" /><figcaption>Data concerning mental health problems — Our World in Data, 2017</figcaption></figure><p>There are several strategies to tackle this problem which affects so many of us: relax and meditate regularly, eat a healthy, balanced diet, practice mindfullness, exercise regularly, get enough sleep, avoid alcohol and drugs, find therapy…</p><p>One of the methods which came to my attention was journaling. But what do we mean when we talk about journaling? Journaling can be described as a written account of our thoughts and feelings as we navigate everyday life.</p><p>Several studies have shown repeatedly how tracking our emotions can have a positive impact in our mental health. Journaling can help manage anxiety, reduce stress and cope with depression. It lets people recognise triggers and patterns and learn how to better control their emotions.</p><p>My idea for this project was then to create <strong>imotion</strong> — an emotion tracker which allows users to identify and register their emotions in a visual, intuitive manner, associate activities to those emotions and get insights and statistics based on their data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lq8QEHvJ5nzYNiXfLjtUrw.png" /></figure><p>We ask others all the time “how are you doing?”, but how often do we ask ourselves: “how am I doing?”</p><p>It’s difficult to identify exactly what we are feeling. It takes too much time and energy. Users need a simple, digital medium to track how they feel to learn about themselves.</p><p>I started off my design process by researching other competitors. There is a large amount of apps focusing on this problem, such as Daylio, Moodflow, Pixels, Bearable… Some of them offer a multitude of features and premium features, others are free, some are more visual and minimalistic, others combine all health tracking in one place.</p><p>My next step was then to go talk to the users, in order to understand their problems and needs. For this project, the research tools I used were user interviews with users who journal and online surveys.</p><p>The research I conducted led me to create a user persona: Frederik Sorensen. Frederik is a 25 year old civil engineer, having his first job after university. He suffers from anxiety and stress, mostly induced by his demanding job. , Despite of his mental problems and lack of time and energy, Frederik needs a digital medium to journal and track his emotions, where he can connect with himself and find triggers and patterns.</p><p>The journey map below describes the journey for users like Frederik.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SJTityOJFCrOINTCEwP6jQ.png" /><figcaption>Journey map for the user persona I created</figcaption></figure><p>The main user flow starts with the selection of a time slot, the entry of an emotion — which can be combined with text, labels, photos and voice recordings — , the selection of the activities the user was up to during that period of time. From that, the user can get a statistic overview in several time frames and insights based on his activities and emotional states.</p><p>There are many methods to classify emotional states. The primary emotions I defined were 7: disgusted, bad, angry, fearful, surprised, happy and sad. From there, each emotion has a multitude of emotions associated to it, to help the users select exactly what they are feeling.</p><p>There are also many activities which can impact our emotional states positively and negatively. For this project, I focused on a few of them, for demonstration purposes, while still giving the user the possibility to add their own activities.</p><p>At this stage, I started working on lo-fi prototypes with a pen and a paper. After testing the paper prototype with users, I further refined them to mid-fi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6HUFKP8omR_jvPt4cDhz0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAd6pQXZzdHGZgg4heQ4DA.png" /><figcaption>Images of the lo and mid fidelity prototypes for imotion</figcaption></figure><p>Once the next usability testing was performed with the user and certain features were adjusted, I started working on a mood board and subsequently on a style guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7HxlqAhTzmN1SMDaK2rcUQ.png" /><figcaption>Some elements which were part of the style guide</figcaption></figure><p>The next stage was to design the high-fi prototype. You can take a look at some of the screens down below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/424/1*fU0T4DYRGxEii8oFQwYSxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*F4xOo9ZohRZElX1vcxOr4g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*ZZ9wUHM7h8sz7kHag_sYsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/1*WBGyDXVpzzdIXj8NdRN4cA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*w2qvvp7VQWqKvgTscjq-mg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*MoxB0CG7HnazOJ3AUlFW1g.png" /><figcaption>Some screenshots from the app, displaying the 5 main sections of the app — Home, Emotion, Calendar, Statistics and Insights</figcaption></figure><p>Some potential next steps could be: correlate emotions to specific life stages, design more ways of visualising data, develop the branding and more content and keeping on testing and iterating.</p><p>This project reminded me not to get too attached to one idea, since everything can be improved upon. A simple solution is not always easy to achieve but practice is key.</p><p><em>Thank you for your time!</em></p><p><em>I hope you enjoyed reading about the case study as much as I enjoyed working on it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f472cde1d12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Patchwork: your Daily Dose of Inspiration]]></title>
            <link>https://medium.com/@luismperdigao/patchwork-your-daily-dose-of-inspiration-f2fbacb143c1?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2fbacb143c1</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Sun, 14 Nov 2021 22:24:09 GMT</pubDate>
            <atom:updated>2021-11-14T22:24:09.738Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing a responsive editorial magazine for young creatives</h4><p>Hello, dear Medium readers.</p><p>I’m back again. Like I’ve been doing lately, I’m bringing you a case study from one of the projects I’ve completed during my UX/UI Design Bootcamp at Ironhack Berlin.</p><p>This time, we had to “<em>design a responsive online platform for a magazine, newspaper or blog directed to meet the needs and goals of one of the presented User Personas</em>.” The final result had to be a consistent, branded and engaging experience for readers. This project, more than any during the course, was very focused on the visual component of the interface.</p><p>For this project, I was joined by my colleague <a href="https://medium.com/u/a356da45c5ca">Adriana Liotta</a>, with whom I had the great pleasure of working during the 4 days.</p><p>In a design thinking approach, users are in the centre of the whole process. As such, I suggest we first take a look at our User Persona, which was randomly assigned to us. Let me introduce you to Paula.</p><p>Our first step was to analyse the User Persona and try to reflect on it to design an appropriate experience and interface.</p><p>Paula is a Laid-Back Creative. She is a 19 year old student. She reads Vice, Rolling Stone, Le Catch and other webzines. She wants to be an artist and connect with people. Paula read anywhere and everywhere.</p><p>Her goals are to be cool and achieve her dreams. Read the most influential authors from her time to show off on Instagram. Have her first expo soon to start being “someone” in the art scene.</p><p>Analysing the User Persona, we were able to deduce Paula is passionate about art in every form and needs to get inspirations daily and keep up with trends.</p><p>The next step in our design process was to analyse the competitors above listed — Vice, Rolling Stone-, both in content and visual terms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p5FnVtl0g-P7yzgmGe8uDA.png" /><figcaption>Some visual elements we collected from the competition</figcaption></figure><p>We deduced that such competitors overloaded users like our persona with too much content which is not relevant. We could also find a lot of promotional content, focused on converting the user. <br><br>From that, we concluded that young creatives need an efficient way to find their “daily dose of inspiration” because the existing webzines display content which is not relevant.</p><p>With Patchwork, we then wanted to design a creativity hub, a platform where people like Paula can draw inspiration from selected stories from the creativity industries. Paula’s daily dose of inspiration to inspire her in her artistic work.</p><p>The name “patchwork” came to us because our goal to incorporate many distinctive and seemingly disconnected visual elements. Patchwork also serves as a representation of the diversity and broad range of the creative industries.</p><p>We started thinking about what we wanted to create with Patchwork. We pictured Patchwork as an inspiring, unconventional, contemporary and quirky magazine.</p><p>With that in mind, we set to create a mood board which represented those values and tone of voice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dp0rRihPD7T92uSbc6d7gg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WXrh5IWoLSi5OfAw7DU06Q.png" /><figcaption>On the left — Some screenshots from the mood board we created for Patchwork. All image credits goes to the creators. On the right, the style tile for Patchwork.</figcaption></figure><p>For the Patchwork’s image, we handpicked pastel colors, which we associated to different categories of the creative industries. The colours are both soothing and accessible but also make the whole design more playful and lively.</p><p>In terms of typography , we chose a very functional and readable sans-serif font, <a href="https://fonts.google.com/specimen/Karla">Karl</a>. For the headlines, we chose <a href="https://fonts.google.com/specimen/Lora#glyphs">Lora</a>.</p><p>Our next step was to create a user flow to represent the journey of the user on Patchwork. This helped us visualise the screens we had to design for the project. We also produced a sitemap to represent all the categories within the Patchwork.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g52CJOiKugm8z_iTemKhZg.png" /><figcaption>The user flow which describes the usual process a user goes through with a webzine such as Patchwork.</figcaption></figure><p>Once that step was done, we grabbed the paper and the pen and started sketching the screens we had in mind: the main page, the category page and the article page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ku7ARHd1193psV9Ir3i6hQ.png" /><figcaption>Some screenshots of the low-fi and mid-fi prototypes of Patchwork.</figcaption></figure><p>We followed the usual methodology in a design thinking approach: low-fi to mid-fi to high-fi prototypes.</p><p>You can take a look at some of the high fidelity screens of the final product down below, on both desktop and mobile versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYA7ruKyo0hTqqhZ5yDIRw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_Mhj0OmXGTMDFEngy-SOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hYzcj1gttUkZhXkwBjugkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VkOHIHHOlnQqP6FZ8Dxujg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WzR_FJcnZz-vrTK92xWLag.png" /><figcaption>Some screenshots from the desktop version of Patchwork. All image credits goes to the creators.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*QcBPYU9GD0s6kW8I7F0VPg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*VKg8r_wh5o-K9jq223fuSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/352/1*pBBrmFFXb834_kP-0tSwPg.png" /><figcaption>Some screenshots from the mobile version of Patchwork. All image credits goes to the creators.</figcaption></figure><p>If we had more time than the four days which were assigned, we would have liked to perform more user testing, develop the branding, design for other devices resolution, such as tablet. <br>Finally, we also would like to design a social community aspect to Patchwork, enabling interaction between users.</p><p>Good teamwork is fundamental in each project.</p><p>This project reminded me of how great it is to work with someone who is visually oriented and aligned with your aesthetical sense. It’s very rewarding when you can inspire each other and generate ideas together— no matter how daring and out of the box — to design a great experience and interface for the user.</p><p><em>That’s it. I hope you enjoyed reading about this case study as much as I enjoyed working on it.</em></p><p><em>Thank you for taking the time to read it!</em></p><p><em>See you next time! :)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2fbacb143c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Shopping Experience for Tinta nos Nervos]]></title>
            <link>https://medium.com/@luismperdigao/a-new-shopping-experience-for-tinta-nos-nervos-331a34e471c5?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/331a34e471c5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Sun, 07 Nov 2021 21:13:50 GMT</pubDate>
            <atom:updated>2021-11-07T21:13:50.730Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing a e-commerce experience for a local business</h4><p>Hello Medium!</p><p>I’m back again with another case study from one of my UX/UI Design bootcamp projects at Ironhack Berlin.</p><p>This time, we were requested to apply design thinking methodologies to design an e-commerce website for an existing small business. The first step was to select and approach the business ourselves for this cooperation.</p><p>The group I was working with consisted of 4 members — me included — . The time frame we had to complete this project was 4 days.</p><p>Let’s first take a look at the client we were working with for this project.</p><p>We decided to go a bit further than Berlin. We went all the way to Lisbon, Portugal and contacted a bookstore: <a href="https://tintanosnervos.com/"><strong>Tinta nos Nervos</strong></a>.</p><p>I first stumbled upon Tinta nos Nervos randomly, while strolling through my hometown, Lisbon, a few months ago. The façade is as inviting as the owners of the shop. The beautiful interior and unique selection of illustrated books makes it very hard to leave their shop. Tinta nos Nervos also serves as a platform to promote the work of illustrators and organises all kinds of the events for the community — workshops, book launches, exhibitions…</p><p>In their words: “Tinta dos Nervos is not only a bookshop, a gallery, an author’s object shop, a café. We are all that and more. The place for Drawing, Illustration, Comics and Graphic Arts.”</p><p>However, the user interface and user experience of their website could be greatly improved. So we approached them with our proposal of redesiging their e-commerce experience and they accepted the collaboration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bcWaZBrB5e6AnbmZ5Fuyog.jpeg" /><figcaption>Interior of Tinta nos Nervos — <a href="http://www.domephotography.com/"><em>All images © Diana Cotovan / Dome Photography 2015–2021</em></a></figcaption></figure><p>The first step in our whole design process was to have an interview with one of the stakeholders.</p><p>The interview enabled us to understand a lot about the business: their values, their goals, their vision, the kinds of products they sell, their types of customers, the competitors…</p><p>After that, we spoke directly to the user — the customer who buys this kind of books to understand his wants and needs.</p><p>We asked the user to navigate through the website and understood that the user experience online could be significantly improved. The current website lacks hierarchy, displays duplicated content and is difficult to identify as an e-commerce website.</p><p>In the empathise stage of our design process, we also led several online surveys and questionnaires with the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pJ-oRco8klkVFkZFhqM0Bw.png" /><figcaption>Let me introduce you to Inês, our user persona</figcaption></figure><p>The information gathered led us to create a user persona: Inês. She is a Software Engineer and devoted mother of two young children. She lives in Porto, Portugal. Inês loves graphic books, comics and other unique books from all over the world. Reading is also an important part in the upbringing of her children. Because of her busy schedule, she needs an online shop to purchase the books she likes for her and her children, while still supporting local commerce.</p><p>Both the data we gathered from the user along with the information from the stakeholder completely guided our design.</p><p>We were then able to define that Tinta nos Nervos customers needs a better structured e-commerce website because they need to easily find and purchase products they want.</p><p>One of our main challenges throughout this project was to reorganise the existing information. Most of it, could be either merged or removed. The point was to simplify the digital experience and diminish the cognitive load for the user.</p><p>For that purpose, we created site maps — of the current website and of our design- and task flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnM-xrZRAyqOblcieJim1w.png" /><figcaption>Task flow demonstrating the process of the user searching for a product and adding it to the basket</figcaption></figure><p>After that, each of us started sketching individually, remotely. We then presented to each other our lo-fi prototypes. The team then combined the best elements of each lo-fi prototype in one.</p><p>The stage that followed that was the creation of mid-fi protoypes, created digitally. On this stage, we led several usability tests, in order to understand if the user could achieve is main goal: to find a book and purchase it.</p><p>After a few tweaks, we were able to find the right mid-fi prototype and we advanced to the high-fi prototyping.</p><p>We designed a website that represented the essence of Tinta nos Nervos, where illustration took the central stage. Illustrations are all scattered throughout the website, promoting the artists beautiful work.</p><p>In terms of typography, we chose a more classy, serif font for the headlines, contrasting with a sans-serif, modern and readable for body copy.</p><p>We strived for a clean, functional design, with neutral colors that let the books shine to catch the users attention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eFAGvVc8bsHHeCDKkSKImw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9T0PcsX9YHN3zCShfpKLwQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/976/1*u_FIYI4u_UxrQ9DyjXJHfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*yvwGLk4meSB7qiqUNJW4DA.png" /><figcaption>Some screenshots of our high-fi protoypes. The information is fictional and user for demonstration purposes only.</figcaption></figure><p>Once again, team collaboration and proper task delegation was fundamental in this process.</p><p>At every stage, research both with the stakeholder and the user should be done and inform the design for the next stages.</p><p>In our extremely digitalized world, it is also important for businesses to offer customers the best online shopping experience possible. That’s where design can make the whole difference. It is the image of a business and can set it apart, no matter the size.</p><p><em>Thank you for your time!</em></p><p><em>I hope you enjoyed reading this case study.</em></p><p><em>See you next time!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=331a34e471c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing Regular Trips for Blablacar]]></title>
            <link>https://medium.com/@luismperdigao/hey-39bcc9d08aaf?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/39bcc9d08aaf</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 21:27:18 GMT</pubDate>
            <atom:updated>2021-11-01T07:14:40.804Z</atom:updated>
            <content:encoded><![CDATA[<h4>Book trips that are made on a regular basis</h4><p>Hello Medium!</p><p>It’s me again with another case study from my ongoing UX/UI Design Bootcamp at Ironhack Berlin. This was an individual project for which executed in four days.</p><p>This time, we had to apply design thinking methodologies to design a non-existing feature for an existing app. Each feature was randomly assigned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kJHKET7woq4XbbRhUzwziw.jpeg" /></figure><p>I had to work on a feature that would enable Blablacar users to book regular trips. By regular trips I mean trips that are often made between different locations.</p><p>Let’s first take a look at <a href="https://www.blablacar.co.uk/">Blablacar</a>.</p><h3>Blablacar</h3><p>BlaBlaCar is a carpooling marketplace. Founded in 2006 in France, the app and website connects drivers and passengers willing to travel together between cities and share the costs of the journey.</p><p>Blablacar simply acts as a broker, a bridge between drivers and riders. For every booking, it receives a commission.</p><p>In terms of competition, every type of transport service that could take the user from one point to another could be considered a competitor.</p><p>For the following project, the research methods I applied were guerrilla research techniques, online surveys and questionnaires to several users.</p><p>From my research, I was able to learn a lot about the needs and wants of carpooling users.</p><p>The main reasons why people use carpooling like Blablacar are the economical cost and the velocity in comparison with public transport. In certain cases, carpooling is even the only way for some users to get to their destination.</p><p>Indeed, carpooling users travel to the same destinations rather often. This leads me to believe the feature I was designing could be useful to users and should be considered being implemented by Blablacar.</p><p>Riders who often travel between the same destinations can’t book regular tickets. I believe that regular trips will make it easier and faster to the places they travel often. We could measure the success of the feature by analysing the value generated by regular trip bookings through the app.</p><p>The feature could benefit users like Ducas Dubois. <br>Who’s Lucas Dubois? The persona I was able to create based on my user research.</p><p>Lucas is a 23 years old French student. He studies Finance at the University of Montpellier. Lucas lives with his parents in a rural area.</p><p>Lucas needs to commute a few times a week to attend his classes in the city. He has no drivers and is extremely limited by public transport. Therefore, carpooling is his best option to get where he needs to. However, Lucas has to book a trip each time, which costs him time and energy.</p><p>The user journey for someone like Lucas would look something like this:</p><ul><li>User needs to get to a certain destination on a regular basis.</li><li>Doesn’t use private or public transport for its’ duration, unavailability and cost.</li><li>User finds out online about carpooling. Downloads an app and proceeds to book trip to selected destination.</li><li>User notices the unnecessary need to repeat a booking each time per trip.</li><li>The user finds about Blablacar and the possibility to book a regular trip. Books several trips in a single click.</li><li>The user saves energy and time while booking his regular trips, which results in an overall better travel experience.</li></ul><p>The sitemap would be based on the current flow existing in the Blablacar app. The main difference would occur in the initial stage, in which the user could chose between a single trip or a regular trip. Each of the following steps would accommodate the initial users choice — location selection, dates selection, time selection, driver selection, trip information and trip confirmation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r9KLd8DySE_tYsVL-zRQYQ.png" /><figcaption>The sitemap illustrates the flow for Blablacar’s regular trips feature.</figcaption></figure><p>When designing in different fidelities, I tried to replicate common user interface elements found on other transportation apps.</p><p>After analysing Blablacar, I stuck as much as I could to the current interface design of the app. I reused and replicated everything I could. My goal was to deliver a design which would be consistent and easy to implement.</p><p>In my design process , I also considered the very likely scenario in which a driver did not drive in one of the selected dates by the user. <br>In that case, the user could book certain rides with a driver and keep on searching for another driver for the missing dates.</p><p>I started with the lo-fi wireframes — a pen, a paper and a marker. I then jumped to my laptop’s screen and started designing the mid-fi wireframes. The next and last step were the high-fi wireframes.</p><p>You can take a look at some of the most important screens below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nOE_Aak8vJp8r2uAoE7NVw.png" /><figcaption>The mid-fi wireframes which led to the final design.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qo5LTi_Rtyvzz7Y7pmWFRA.png" /><figcaption>The high-fi prototypes I designed for Blablacar regular trips feature.</figcaption></figure><h3>Conclusion</h3><p>If I had more time, I would have designed solutions for larger and more complex ranges of dates. I would also like to keep on testing the flow with users. And, like always, iterate — gather feedback, learn from it and keep on improving.</p><p>The following exercise reminded me of a lot of things I already learned on my journey as a UX/UI designer.</p><p>The lo-fi and mid-fi wireframes are the building blocks of every design. If you need to refine your design, leave the high-fi wireframe and go back to them.</p><p>Is it also vital to approach several users stages of the design process to try your product. Every stage is ideal to do research and learn more about your user.</p><p>I never used Blablacar or any carpooling service. It was definitely a very compelling challenge to step out of my comfort zone and to learn and design for a feature I never considered before.</p><p><em>I hope you enjoyed reading about this project study as much as I enjoyed working on it.</em></p><p><em>Enough blabla now! :)</em></p><p><em>Thank you so much for your time! Bye!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39bcc9d08aaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Case Study: immi App]]></title>
            <link>https://medium.com/@luismperdigao/a-case-study-immi-app-7d7c627648c5?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d7c627648c5</guid>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Sun, 24 Oct 2021 19:01:58 GMT</pubDate>
            <atom:updated>2021-10-24T19:08:13.007Z</atom:updated>
            <content:encoded><![CDATA[<h4>How might we help immigrants start their life in a new city?</h4><p>Hello, dear Medium community.</p><p>I’m back. This time, I’m here to present you a case study for one of my first projects as a student of the UX/UI Design Bootcamp at Ironhack Berlin.</p><p>My team was faced with a wicked problem — a problem that is difficult or impossible to solve because of its complexity and interconnectedness. It was all about immigration:</p><blockquote>How might we help migrant people find the information, complete the tasks and successfully get their paperwork done to start their life in a new city?</blockquote><p>Our task was then to combine design thinking, systems thinking and agile methodologies to define and tackle the problem. At the end, the outcome should be a mobile app prototype that could solve this wicked problem for immigrants across the world.</p><p>Our goal then was to create an app that would somehow make it easier and faster for immigrants to go through the immigration process without any obstacles.</p><p>Working with three other members over a period of only four days, my team the design thinking process with the empathise stage.</p><p>We started by researching our user: immigrants. The methods we chose to gather and analyse quantitative and qualitative data were a questionnaire and a survey.</p><p>The interviews, in specific, were directed to immigrants from our social circle, who live in Germany. The interviewees all had different backgrounds and experiences in the country they migrated to, based mainly on their nationality and occupation.</p><p>The surveys were shared in several social media communities where immigrants are present and we manage to gather dozens of answers.</p><p>The data just confirmed: immigration is, indeed, a wicked problem. <br>There can be many obstacles in the way of an immigrant. The process can be even more daunting if you have no relatives or friends in the country you are immigrating to, are not able to communicate in the native language or come from developing countries.</p><p>The data gathered helped us get to our <strong>problem statement:</strong></p><blockquote>“Newly arrived immigrants need a way to file in the correct paperwork at the right time and place because the current process is too confusing and frustrating.”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cK78coqtXq1q8XZSc20NOg.png" /><figcaption>Our <strong>empathy map</strong> helped us visualise and articulate what we knew about our user</figcaption></figure><p>During this stage, we were also able to create <strong>a user persona. </strong><br>Ismael, a Turkish citizen who just graduated, has decided to move to Germany for professional and economical reasons. Ismael already found a job in a german company and needs to complete the immigration process.</p><p>He can’t rely on any friends or family and seeks information digitally. The information he finds is confusing, contradictory and complex, stemming from Turkish social media groups and digital specialised media — blogs, governmental websites…</p><p>Ismael ends up going to the incorrect governmental institution with incorrectly filled up paperwork. The worst: he is not even able to communicate with the worker because he can’t speak german. Ismael then gets lost in the whole immigration process and even doesn’t know what to do next.</p><p>Another of the methods we used was an <strong>affinity diagram</strong> — a tool in which we gathered our data and organised it into groupings, based on relationships.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZI-kEhalmnH020EeXNmqdw.png" /><figcaption>The affinity diagram organised in different categories of “How might we’s”</figcaption></figure><p>The affinity diagram allowed us to come up with several “How might we’s”, group them and realise that most of the problems focus on the way information is presented to immigrants.</p><blockquote>How might we, then, deliver clear and personalised information in a digital, sequential and actionable way?</blockquote><p>In the ideation stage, we used several techniques to generate ideas, such as The Crazy 8 and storyboarding.</p><p>Some of the ideas we came up at this stage were then implemented in the prototype we presented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xplGGUwWsaXJEigqWNTQYA.png" /><figcaption>An example of the Crazy 8 exercise — some of the ideas were implemented in the app</figcaption></figure><p>Each of the previous stages led us to our final prototype of immi.</p><p>immi presents several features that aim to tackle the problems we identified:</p><ul><li><strong>Sequential To-do list — </strong>the app presents a logical and sequential list of steps, with clear and precise information; the user can only progress to one step once he/she has completed the previous one;</li><li><strong>Personalised checklist for documents — </strong>the checklist allows for an easy and intuitive way to progress through each of the steps for a specific task;</li><li><strong>Digitalisation of the interaction with migration institutions —</strong> immi completely digitalises the process, serving as a bridge between the government and the immigrant; this way we are, eliminating the need to schedule meetings and the problems that may arise from human interactions;</li><li><strong>Feedback for each steps —</strong> the user is constantly aware of the status of his immigration process, through updates/notifications and knows the average time each task will take for completion;</li><li><strong>Translation of documents — </strong>within a single click, immi can translate all the required paperwork for a task to the user’s desired language;</li><li><strong>Constant assistance — </strong>immi provides support from governmental authorities in the user’s selected language, through a call or a message;</li></ul><p>You can take a look at some of this features in the screenshots below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCNSQzIDanMDStZxnVtaRA.png" /><figcaption>A prototype of flow of <strong>immi </strong>— the flow includes the log-in, the customisation of the user profile, the language selection, the sequential display of steps, the translation of documents, the assistance request…</figcaption></figure><p>We will know we have achieved our goal by comparing the duration of the immigration processes of our users with the current average duration and by interviewing users about their immigration experience.</p><p>This was just the start of immi.</p><p>If we had more time, the next steps would include further interface design refinements, internal testing within the team and then gradual testing with the user. And then, like always, constant iteration and research.</p><h3><strong>Conclusion</strong></h3><p>As an immigrant for 4 years, I know how difficult the immigration process can be. immi is the kind of app I wish I had when I moved to Berlin, Germany.</p><p>It was not always easy to let go of my own biases and assume I knew what the problem and solution was. Although I could identify with many of the problems, I often had to remind myself that I’m not my user. That data comes from research.</p><p>This was also a valuable teamwork practice. Working under such time pressure and in a remote, agile setting, it was fundamental to distribute the work and collaborate and communicate adequately.</p><p>Most importantly, we could apply a lot of the methodologies taught in class. Every exercise allowed us to get a better understanding of the problem and brought us forward, closer to our prototype.</p><p>In the end, we hope our ideas may contribute in any way to improve the immigration process. It may be a “wicked problem” but design can make it less “wicked”, step by step.</p><p><em>I hope you enjoyed reading this case study as much as I did writing it.</em></p><p><em>Thank you for your time!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d7c627648c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wireframing Uber Eats]]></title>
            <link>https://medium.com/@luismperdigao/wireframing-uber-eats-14061d5aaf9b?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/14061d5aaf9b</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 10:11:19 GMT</pubDate>
            <atom:updated>2021-10-08T10:14:53.438Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reverse engineering a food delivery app</h4><p>Hey there. It’s me again. 👋</p><p>My journey as a UX/UI student at Ironhack Berlin is about to begin. <br>I could not be more looking forward to it.</p><p>In this next chapter of my story, I want to share with you one of my recent exercises at Ironhack. This time, I had to chose an app and to reverse engineer it — analyse a user flow and produce wireframes of it in different fidelities.</p><h3>The app: Uber Eats</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EmsNkyak9rJ4cjuq9NCi9Q.jpeg" /></figure><p>The app I’ve chosen to work with is<a href="http://www.ubereats.com/"> Uber Eats</a>. <strong>Why?</strong></p><p>COVID-19 changed how we perceive and consume food. Locked inside, we relied on our devices to eat whatever we felt like. Instead of going to our food, our food came to us.</p><p>Since then, food delivery apps have thrived like never before — the numbers speak for themselves. This tendency of growth is expected to remain, even in a post-pandemic world.</p><p>Yes, I know: there are plenty of food apps out there. The reason why I chose Uber Eats in particular is because they hold one of the highest revenue and share in the food delivery apps market. Uber Eats is also one of the most widespread food delivery apps, available in 45 countries and 6,000 cities worldwide.</p><p>My goal then is to better understand Uber Eats design choices and the process a user goes through while selecting food.</p><h3><strong>The User Flow</strong></h3><p>The flow I chose to work on is the the “<em>happy path</em>” most users go through while using Uber Eats: the process of finding a restaurant, choosing food from the menu and ordering it - for delivery or pickup.</p><p><strong>Here it is:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSuy8qDXhr1jGMPSz2EYKw.png" /><figcaption>Uber Eats’ user flow in 7 screens</figcaption></figure><p>The user flow is split into 7 steps. Let’s break them down and analyse each one of them:</p><ol><li><strong>The home screen:</strong> it allows the user to choose how to get the food - delivery or pickup -, choose a time and place for delivery, filter and sort through different factors. The user can browse through food categories by clicking in one of the icons - horizontally scrollable - or just scroll down and explore Uber Eats’ featured offers.</li><li><strong>The browse screen:</strong> the user can search for a specific restaurant, cuisine or dish or scroll through several food types until finding the right one.</li><li><strong>The restaurant screen:</strong> upon choosing a category, Uber Eats displays all the results. The top of the screen provides controls to filter and sort according to various parameters. Each restaurant has a picture, name, delivery fees, delivery time, a user score or any promotions that may apply. Users can also add a certain establishment to their favourites.</li><li><strong>The food screen:</strong> once the restaurant is chosen, users will find the whole menu. On top of the screen, they may add the place to their favourites or expand a menu. Below, there’s additional information about the establishment. Two buttons let the users decide between food pickup or delivery. If you scroll down, you’ll find the whole food menu - each dish includes a price, the ingredients and a label about trendiness or dietary. In alternative, the search button lets users search for a specific product.</li><li><strong>The dish screen:</strong> the dish screen includes the name, description and picture of the chosen dish. It allows users to select specific ingredients, add extras, adjust the quantity and write special instructions. The button underneath adds the item to the cart.</li><li><strong>The order review modal: </strong>a modal pops out reminding the customer of the items ordered and their price. Users can once again add utensils. The button proceeds to checkout.</li><li><strong>The order and payment screen:</strong> the last and most complex step in the journey. The user may choose the method for getting the food - delivery or pickup. A map displays the path separating the consumer from the order. The address can be changed along with instructions regarding the order. User can also schedule a specific time. There is another overview of the order, as well as buttons to add more items. Checkboxes enable the user to add utensils or other items. It is possible to add a promo through a button. Finally, after consulting the final price, users can chose their payment method. Once the consumer taps the order button, will get a confirmation of the order. And… that’s it! Food should be arriving soon!</li></ol><h3>The UI Element Inventory</h3><p>First things first. Let’s take a look at the Uber Eats user interface and understand which elements compose it.</p><p>UI elements can be grouped into different categories: input controls, navigational components, informational components and containers.</p><p>In the case of the user flower we selected, we can find:</p><p><strong>Input Controls:</strong> buttons, radio buttons, checkboxes, text fields.</p><p><strong>Navigational Components:</strong> icons, search fields.</p><p><strong>Informational Components:</strong> icons, modal windows.</p><h3><strong>Wireframing Uber Eats</strong></h3><p>Once I listed Uber Eats’ interface, it was time to grab a paper and a pen and start drawing lo-fi wireframes.</p><p>But wait… <em>what are wireframes, after all?</em></p><p>Wireframes are the skeleton, the blueprint of the design. They let us focus on the structure, user flow, functionality, layout and information architecture of an interface. The visual elements and content are kept to a minimum. Wireframing takes place in the early stages of the design process.</p><p>The main advantages of a wireframe is its low cost, speed, and ease to collaborate and gather early feedback.</p><p>Lo-fi wireframes, specifically, are the initial, simplest type of wireframes, usually drawn by hand.</p><p><strong>This is what I came up with:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o-RbxsGCKhH5TvBLxzgqug.png" /><figcaption>The 7 lo-fi wireframes I’ve drawn for each of the screens</figcaption></figure><p>The lo-fi wireframe was just the starting point. Once the lo-fi wireframe was complete, it was time to work a higher fidelity wireframe, using a wireframe kit. At this stage of wireframing, design softwares tools are usually the choice — Figma, in my case.</p><p>The following wireframe were more specific and detailed — more identical to the original Uber Eats design.</p><p><strong>This is the result of my work:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QnXdxeWMTzNCD8Js_gtatw.png" /><figcaption>The 7 wireframes I’ve designed for each of the screens</figcaption></figure><h3><strong>Conclusion</strong></h3><p>In this exercise, I was forced to take a few steps back and think backwards — to analyse and deconstruct an interface.</p><p>The final result is supposed to represent the most basic, essential elements of Uber Eats.</p><p>This was an exercise of reduction. The challenge was to keep it as simple as possible, to create a prototype which is just enough to communicate, gather feedback and collaborate.</p><p>I had to consider each element and think about its role and importance in the functionality of the interface — whether it should be included in the wireframe or not. Distinguishing between functional or aesthetical, not spending too much time on the visual part or on details was challenging at times.</p><p>All in all, it was a valuable learning experience.</p><p><em>I sincerely hope you enjoyed reading about this exercise as much as I enjoyed working on it.</em></p><p><em>Truth be told: writing all this made me a bit hungry. Now if you excuse me, I have to go. My Uber Eats food is getting cold.</em></p><p><em>See you next time! </em>🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14061d5aaf9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making buying public transport tickets easier]]></title>
            <link>https://medium.com/@luismperdigao/making-public-transport-tickets-easier-f0dd6c7991df?source=rss-2b0bd98d4b57------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0dd6c7991df</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Luís Perdigão]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 10:00:57 GMT</pubDate>
            <atom:updated>2021-10-08T11:53:54.977Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing a solution for Citymapper</h4><p>Hello everyone! <br>Allow me to introduce myself, first of all. I’m Luís Perdigão.</p><p>In a couple of days, I will be attending Ironhack’s UX/UI Design Bootcamp in Berlin. For the next couple of months, I will be sharing with you my journey as a UX/ UI Designer: the lessons, the challenges and everything in between.</p><p>Well, this is the first chapter of that story.</p><p>As one of our initial challenges at Ironhack, we had to implement Design Thinking methodologies to come up with a solution for <a href="https://citymapper.com/">Citymapper</a>. <br>Let’s first talk about the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G_q7UDwBkgncz3Hz977lrA.jpeg" /><figcaption>Mobility at your fingertips with Citymapper.</figcaption></figure><h3>Citymapper: Making Cities Usable</h3><p>Citymapper calls itself “<em>the ultimate transport app and technology for mobility in cities.</em>” It is a public transit app and mapping service which displays transport options between two locations by integrating data from all urban modes of transport.</p><p>Mobility in cities is a need. Public transport, in particular, is the most used form of mobility in many cities in the world.</p><p>Citymapper’s mission is to make cities usable: make going from point A to point as easy as it can be.</p><p>A major part of the experience of using public transport is… <strong>purchasing tickets.</strong></p><p>This particular task can be very complex and lengthy, for several reasons, which we will analyse in further detail later. You might have experienced some of those problems yourself — I know I did and will.</p><p>To add to the complexity, transport is getting more fragmented. There are more and more transport services and each has very different ways of purchasing the tickets.</p><p>If you are in a city you don’t know, then buying a ticket can be even more daunting, as you know less about moving around in the city.</p><p>It was for this problem that we had to devise a solution, which would be integrated with Citymapper.</p><p>For this challenge, I adopted the Design Thinking methodology, a user-centered approach which goes through several steps: <strong>empathise, define, ideate, prototype.</strong></p><p>Alright, let’s get to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAwr15dANicApFX6ZwJSHw.png" /></figure><h3><strong>Empathize</strong></h3><p>In this stage, we were first asked to take a moment and reflect on several questions to build our own a point of view.</p><ul><li><strong>What problem are you solving?</strong></li></ul><p>The problem we are trying to solve is the difficulty of purchasing public transport tickets.</p><ul><li><strong>Who is your audience?</strong></li></ul><p>The audience is anyone who uses public transport, with a focus on digital natives — people who rely on technology to help them on their daily tasks, such as moving around in a city.</p><ul><li><strong>Who is your client’s competition?</strong></li></ul><p>Citymapper’s competition includes digital navigation products like Google Maps, local transport apps or any private or public mobility service.</p><ul><li><strong>What’s the tone/feeling?</strong></li></ul><p>The tone / feeling should be trustful, friendly, modern, approachable.</p><p>After this reflection exercise, it was time to hear from the people who use public transport everyday and discover which problems they face when buying public transport tickets.</p><p>I interviewed five people: Maja, Maddalena, Sofia, Nuno and Francisco.<br><em>(If you are reading this, thank you for your time!)</em></p><p>The users range between 25–30 years old. They all use public transport on a daily basis and a range of modes: bus, metro, train, tram and e-scooter. They rely on it to get home, to work or to go out at night. They regularly use transport apps to find out how to travel within the city and to buy tickets.</p><p>They all live in European capitals: Lisbon, Portugal and Berlin, Germany, except for one of them — who lives in Coimbra, Portugal. Several times a year, they travel to other medium and large cities, most of the times in Europe, sometimes in other continents.</p><p>I prepared a script and asked them the following questions:</p><ul><li>Do you use public transport in the place where you live? What about abroad?</li><li>How often do you use public transport? Which types of public transport?</li><li>Why do you use public transport? What do you value the most in it?</li><li>You are at a certain place and you want to find out to get to another and you don’t know how to do it. What would you do?</li><li>How do you usually buy your tickets? How do you prefer to buy them?</li><li>How would you describe your experience purchasing tickets abroad?</li><li>Could you point out some problems you’ve experienced while using public transport? And purchasing tickets?</li><li>How would you improve / what would you change in the purchase of tickets for public transport?</li></ul><p>Each interview lasted around 30 minutes and was adapted according to the flow of the conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xbtpXIy54TPbsLoNFuqiLg.png" /></figure><h3>Define</h3><p>Once I collected the qualitative data I needed with the interviews, the next step was to analyse it and define the problem.</p><p>Our users relied on public transport everyday. Therefore, they could list many problems concerning their general usage: lack of hygiene, safety concerns, unpredictability, unreliability, lack of comfort, delays, temperature and air conditioning, public transport being overcrowded, fear of being on the wrong public transport, fear of missing the stop, amount of strikes or maintenance work, accessibility issues…</p><p>The main problem we are trying to solve is <strong>how difficult it can be to purchase a public transport ticket.</strong> For this specific matter, the number of problems was no less: not knowing where to buy tickets, fear of losing the ticket, waiting time in queues, physical problems with machines, payment limitations — only cash or only card, need of several tickets to get to one point, waste of resources (paper or plastic), not being able to buy the ticket online if there is no data or battery, not knowing which would be the right ticket to buy, not knowing the price in advance…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BesZ4lm-rO0Nx0m7suXrfw.png" /></figure><h3>Ideate</h3><p>I put my brain to work to come up with as many ideas as I could to improve the quality of public transport. Some of them came from brainstorming sessions.</p><p>Here they are:</p><ul><li>provide statistics regarding the user’s usage of public transport — how much money and time you spent on average on each mode of transport; optimisation of based on the analysis of the data;</li><li>send personalised real time notifications regarding any constraints in the most used routes or your current route — construction, traffic, strikes and so on;</li><li>send a notification before the user is approaching the final destination to avoid constantly checking the device to know when to step out;</li><li>provide ideas for touristic routes based on the location main attractions — the cheapest, fastest way by using public transport;</li><li>provide regular information about current capacity of the transport, about the accessibility of each, about the sustainability of each mode and your carbon footprint;</li></ul><p>Maybe some of these ideas could be incorporated in the solution.</p><p>The main problem we are working on, though, is the purchase of tickets. The idea I had was to <strong>create “<em>one ticket to rule them all</em>”</strong>! This would be a digital ticket, a generated QR-code which users scan to move around the city. For one route, there is only one previously generated QR-Code — no matter how many times you need to swap.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bddzMAjHysIgmR750f9Hbw.png" /><figcaption>Sketching a solution for the problems I discovered.</figcaption></figure><p><strong>The app is associated to an eco-friendly, sustainable card.</strong> This card can be topped up online or through the app and also be scanned everywhere, in case the user does not have any battery or data — which happens quite often when you are traveling abroad.</p><p>I believe this digital, centralised ticket could solve some of the problems above mentioned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9N5EPf3yylvMwDti7PL7Rw.png" /></figure><h3>Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PgorSIJw-6Nff6Sfu2xaQ.png" /><figcaption>My prototype design for making buying tickets a bit easier.</figcaption></figure><p>The above lo-fi prototype describes how I envision the user flow of purchasing a ticket through Citymapper. Allow me to walk you through it:</p><ol><li>First, the user types his/her location and destination. The user can chose to go home, to work or to one of the favourite places.</li><li>Based on the input, several routes are displayed, ranked according to speed, price, number of transfers, sustainability and other factors.</li><li>The user chooses the desired route. The route will be broken down into steps. Upon click, each mode is also broken down into stops. The total price of the trip is displayed underneath. The user buys the ticket.</li><li>In case the user doesn’t have enough credit for the purchase of the route, he/she has to charge the app. This will also top up the physical card.</li><li>A live map displays where the user currently is and where to go next to get to get to his /her destination.</li><li>This screen displays the QR-code that has to be scanned. This is the ticket for the route. In alternative, the user can just use his physical card — they are connected. <br>If there are any changes along the way that would cause a constraint, the user would get a notification. This would enable him to recalculate the trip.</li><li>In this screen, an alternative route is suggested. It will allow the user to get faster and easier to the destination. If the user wishes to, it is then possible to reschedule the trip.</li><li>The user has arrived to the destination. The final screen displays some information about the journey — price, distance, length, carbon footprint, for instance. Ready for another trip?</li></ol><p>And there you go! Hopefully, this solution will let us arrive easier and faster wherever we need to go — <strong>with just one ticket!</strong></p><h3>Conclusion</h3><p>This Design Thinking exercise reminded me of many lessons regarding UX/UI design. These are some of those reminders:</p><ul><li>There is no user-centered design without research. You are not your users. Don’t assume.</li><li>A good question is half of the answer. You have to ask the right questions to get the right answers.</li><li>Ask yourself the questions you will ask your users. What are you trying to get from this question?</li><li>A script is a reference, don’t stick too much to it. While interviewing, keep the flow conversational and natural.</li><li>Explore unclear paths. Some of the best ideas arrived from places which I least expected.</li></ul><p><em>Thank you for your time.</em></p><p><em>This was my first post on Medium but It won’t be the last.</em></p><p><em>I hope you enjoyed reading about this exercise.</em></p><p><em>You will definitely be reading more from me soon. Stay tuned!</em></p><p><em>See you soon!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0dd6c7991df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>