<?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 Hannah Parent on Medium]]></title>
        <description><![CDATA[Stories by Hannah Parent on Medium]]></description>
        <link>https://medium.com/@hannparent?source=rss-34d4ccbe8ab1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0m-qz8c5NlSUdA15PpWkww.png</url>
            <title>Stories by Hannah Parent on Medium</title>
            <link>https://medium.com/@hannparent?source=rss-34d4ccbe8ab1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:11:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hannparent/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[Project 1: Wicked Problem ‍♂️]]></title>
            <link>https://medium.com/@hannparent/project-1-wicked-problem-%EF%B8%8F-dbce39ca67eb?source=rss-34d4ccbe8ab1------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbce39ca67eb</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[surveys]]></category>
            <dc:creator><![CDATA[Hannah Parent]]></dc:creator>
            <pubDate>Mon, 17 Jan 2022 02:06:28 GMT</pubDate>
            <atom:updated>2022-01-17T07:54:18.176Z</atom:updated>
            <content:encoded><![CDATA[<p>During my first week of the UX/UI design course at <a href="https://medium.com/ironhack">IronHack</a>, I was given a “Wicked Problem” and asked to solve it.</p><p>What is a wicked problem you might ask? Well simply put…</p><blockquote><a href="https://www.interaction-design.org/literature/topics/wicked-problems">Wicked problems are problems with many interdependent factors making them <em>seem </em>impossible to solve. Because the factors are often incomplete, in flux, and difficult to define, solving wicked problems requires a deep understanding of the stakeholders involved, and an innovative approach provided by design thinking. Complex issues such as healthcare and education are examples of wicked problems.</a></blockquote><p>After realizing the complexity of the assignment handed to us, I was placed into a group with my two peers (Patrick Haack and Dave Alcantara).</p><h3>Day 1) Empathize, The True Challenge 🌠</h3><p>After our selected design brief was given to us, it was made very clear what lay ahead for our group….</p><p>It was only the beginning, but each of us quickly realized how truly<em> wicked</em> this challenge was going to be.😅</p><h3>THE CHALLENGE:</h3><blockquote>Our Design Challenge tackled the end-to-end user experience in public hospitals. <br>From appointments with the doctor, to engaging in community initiative and volunteering.</blockquote><p>Now we began to <em>define our given problem</em> using the <a href="https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process">Design Thinking Process</a>.</p><h4>Brainstorming 💡</h4><p>We took a good 45 mins and put our heads together —jotting down every idea that came to us into our notebooks. From there, we looked into existing applications that fit our design brief, creating a <em>detailed competitive analysis</em> that <em>helped narrow our scope</em>, helping us<em> realize what we want to achieve</em>.</p><p>After taking a look at our competitors we began to draft up several questions to our potential users in the form of a survey. The final results were what drove our product decisions and were incredibly vital to our process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*skyLC_l4Ti3EAhiAhlLtQg.png" /></figure><p><strong>🔑 Key Insights of our survey were:</strong></p><ul><li>User base consists of mid-age range and upwards</li><li>International, mixed user group</li><li>80% of respondents recognize <a href="https://www.doctolib.de/">Doctolib</a>. Other options were unknown. Doctolib is <em>therefore the only well-known competitor in the field</em>.</li><li>Volunteers won’t travel more than 10km/45min to a project.</li><li>Users were comfortable showing information on their health as long as it was<strong> encrypted and only sharable with trusted doctors</strong>. <strong>Control over their privacy was important.</strong></li></ul><p>The results we had from our survey weren’t shocking or much of a surprise but incredibly informative and insightful — overall it made the next steps we should make more clear.</p><h3>Affinity Map🗒📌</h3><p>With the clear results of our survey, we synthesized the data collected through the creation of an affinity map. This was a process that helped us <strong>make sense of all of the mixed data found in our survey results</strong>. We rephrased any known challenges as a question beginning with <strong>“How Might We”</strong> and grouped them into categories accordingly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZbGfXL_Dw_xg0Dkyzivgjw.png" /></figure><p><strong>🔑 Key Takeaways from our Affinity Map were:</strong></p><ol><li>Based on our surveys our users need to book appointments<strong> quickly and efficiently.</strong></li><li>Our health experts should be <strong>approved and rated</strong> to establish a level of trust.</li><li>Medical history should be <strong>accessible with a click of a button </strong>— but only <strong>shared with trusted doctors and the user themselves</strong>. (Privacy = 😃 happy users)</li><li>Users should be able to choose doctors that are covered by their insurance and speak their native language</li><li>Going to a public hospital can be confusing and stressful, it is vital to provide a form of relief/reward to the user so their experience is much more pleasant.</li><li>Expert qualifications, reviews, and location is the most vital information to our users while booking an appointment.</li></ol><h4>INTERVIEW 🎙</h4><p>We were lucky to have two health experts participate in an interview</p><p>I interviewed <a href="https://www.linkedin.com/in/alexandergorny/?originalSubdomain=de">Alexander Gorny </a>a digital health expert whose primary focus is <strong>Innovating Health Care with Heart and Brain</strong></p><p>and <a href="https://medium.com/u/d57bfddc9483">Patrick Haak</a> (one of the members of my group) interviewed <strong>Dr. Joerg Reichert, </strong>a doctor of internal medicine. His specialization is primarily in hematology and oncology.</p><p>Each of our interviews allowed us a small glimpse of the future of digital health and telemedicine and helped define what steps we need to take to compete with the 350,000+ digital health apps that are currently available to consumers. <em>Intimidating right?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dv0TMRo7gPvGZezklLgy3g.png" /></figure><p>The information each from each of our experts was not only insightful it was incredibly inspiring. We were truly motivated to find a solution to our <em>wicked problem.</em></p><h3>Day 2. LET&#39;S DEFINE! 📍</h3><p>After some rest &amp; reflection, we got back to work on the previous insights gathered the day before and channeled them into a problem and hypothesis statement.</p><h3>Problem Statement</h3><blockquote><em>Our </em><strong><em>digital public hospital app</em></strong><em> was designed to achieve a </em><strong><em>better end-to-end user experience in patient care.</em></strong><em> We have observed that the process of making an appointment is not meeting the user’s goals of </em><strong><em>booking appointment quickly, clear insurance coverage, and treatment applicability</em></strong><em>, which is causing frustration for the </em><strong><em>user and health providers.</em></strong></blockquote><h3>Hypothesis Statement</h3><blockquote><em>We believe creating a digital health platform for our users (patients) will </em><strong><em>achieve a better end-to-end experience</em></strong><em> when booking an appointment with a public hospital</em><strong><em>. We will know we are right based on appointment efficiency/quality and user (both physician/patient) feedback/ratings</em></strong></blockquote><h3>User Personas👤</h3><p>Based on the generative user research gathered, we created a user persona that captured the true essence of our target users. Introducing…..Esther Sharpio 👋</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9BfZOKPUEo36Xudcy3tLQ.png" /></figure><p>By creating Esther, we found the answer to one of the most important questions we had at the beginning of our process,</p><p><strong>“Who are we designing for?”</strong></p><p>Esther gave us helpful insights into the very core of our users and what their needs are, what features we need to include, and this was built on the previous user research (in-depth user interviews and observation data).</p><h3>Day 3) A Closer Look 🔬</h3><h3>User Journey’s🚀</h3><p>By illustrating the process of how Esther behaves, feels, and thinks while accomplishing their goals, we detected points —or moments of happiness, this is shown in our user journey map.</p><p>Here we defined the user&#39;s goals, actions, feelings, and opportunities: this shed some light on the question: <strong><em>‘How do people actually use our product?’</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsFWyIPan8NZ_ZOsNgcZbQ.png" /><figcaption>We can see from Esther’s journey the defined solutions and features we need to provide. Our team’s most important assumptions were proven correct.</figcaption></figure><h3>Day 4)</h3><h3>Almost there….Time to IDEATE &amp; PROTOTYPE 🎨</h3><p>After much reflection (and a final brainstorming session), our users’ <strong>wants, needs, and expectations from a product</strong> were<strong> made clear</strong> <strong>to us.</strong></p><p>Having some previous design background used I took initiative in my group and began the quickest form (wireframing) and developed a lo-fi prototype in Figma.</p><p>I am proud to present to you….</p><h3>HealthHack, the solution to finding trustworthy practitioners at your local hospital!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wg3UC4xI8Hy6DfGbNeoMOQ.png" /></figure><h3><strong>How does it work? 🛠</strong></h3><ol><li>The<strong> user signs up/in</strong></li><li>The user creates <strong>a HealthHack profile </strong>and enters their information and <strong>medical records</strong></li><li>The user is then taken to a map and they are able to <strong>enter their location offering them a list of public hospitals near them</strong></li><li>Once the <strong>hospital closest to them </strong>is chosen they can select from<strong> a variety of medical specializations</strong> and can select the option between an <strong>urgent or follow-up appointment</strong></li><li>From there only the<strong> top medical professionals are shown </strong>and the user can <strong>select the best option for their personal needs </strong>and <strong>view the ratings</strong> for each professional</li><li>The selected <strong>doctor’s availability/insurance coverage</strong> details are then shown with an option to book.</li><li>The appointment is booked and a confirmation is sent! There is always the <strong>option to speak with a specialist</strong> during the whole process in case of confusion/stressful experience.</li></ol><h3>DONE….But Not Quite!</h3><p>After moving from our lo-fi prototype I created our logo and finalized the design by adding color and icons suiting our brand guidelines/aesthetics.</p><p>This was probably the most exciting and rewarding part for me as we saw all of our hard work spent during the interview/research process finalized in a practical design!</p><p>Below you can see the final result or you can also<a href="https://www.figma.com/proto/sO6BFlieFGsenwf033uU0I/Final-Screens-Healthhack?page-id=0%3A1&amp;node-id=0%3A543&amp;viewport=242%2C48%2C0.38&amp;scaling=scale-down"> click this link</a></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FsO6BFlieFGsenwf033uU0I%2FFinal-Screens-Healthhack%3Fpage-id%3D0%253A1%26node-id%3D0%253A602%26viewport%3D242%252C48%252C0.38%26scaling%3Dscale-down&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FsO6BFlieFGsenwf033uU0I%2FFinal-Screens-Healthhack%3Fpage-id%3D0%253A1%26node-id%3D0%253A602%26viewport%3D242%252C48%252C0.38%26scaling%3Dscale-down&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F0ab88f80-5ca3-4752-bec5-714193b41ef3%3Fheight%3D227%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/108cc90969effc7a87443137af3f781e/href">https://medium.com/media/108cc90969effc7a87443137af3f781e/href</a></iframe><h3>What did learn?</h3><p>To be honest, I think the biggest challenge was working in a group with complete strangers and getting to know each other and what our skills were in such a short time. <em>The decision-making process</em> had to be <em>quick and timely</em> to meet the deadlines. But also I felt that I grew a lot as a designer, and the topic of digital health became incredibly touching and inspiring to me… something I might be interested in focusing on in my future.</p><p>The second biggest challenge was to <strong>narrow our scope.</strong> The initial project brief itself was much much too broad for us to know where to start…. and it took <strong>a lot of generative user research to get our desired result.</strong></p><p>That was truly the wicked part for us as a team and we all mutually agreed that it was a learning experience that will benefit us in the future!</p><h3>NEXT STEPS?🦶🏻</h3><p>I would like to go back and design my own icons and illustrations instead of using <a href="https://www.flaticon.com/">flaticon</a> and other resources.</p><p>-There are also several other screens to be designed such as medical history, settings, doctor profiles, and more!</p><p>TEST, TEST, TEST!!!! Placing our concept <strong>in front of real users to see how well they can work with them!</strong></p><h3>Conclusion ✨</h3><p>Though this challenge had its ups and downs, I feel proud of what we accomplished as a team, and also what I accomplished individually as a designer. This was my first wicked problem and I hope to be faced with many more as I learned a lot about myself (strengths and weaknesses).</p><p>I do enjoy a good challenge 😅</p><p>I hope you enjoyed learning about our design process!</p><p>THANK YOU! 🙏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbce39ca67eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack`s Prework Challenge 2: Wireframing]]></title>
            <link>https://medium.com/@hannparent/challenge-2-wireframing-40ce1e76a016?source=rss-34d4ccbe8ab1------2</link>
            <guid isPermaLink="false">https://medium.com/p/40ce1e76a016</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hannah Parent]]></dc:creator>
            <pubDate>Sat, 08 Jan 2022 23:26:06 GMT</pubDate>
            <atom:updated>2022-01-08T23:30:39.030Z</atom:updated>
            <content:encoded><![CDATA[<p>For the second challenge during the UX/UI Prework at Ironhack, I was asked to create a wireframe from an app of my choice and prototype it in Figma.</p><blockquote><a href="https://balsamiq.com/learn/articles/what-are-wireframes/"><em>A wireframe is a schematic or blueprint that is useful for helping you, your programmers and designers think and communicate about the structure of the software or website you’re building.</em></a></blockquote><p>Consider a wireframe as the blueprint to any app or webpage, they are often simplistic in nature due to the fact that they are focused on functionality and user flow. Wireframes are an essential step into turning any digital product into reality. The goal of a wireframe is to build a basic skeleton for each screen in your design, that way you can review the overall layout before colors, imagery, and branding get added into the mix. Wireframes convey the overall direction and description of the user interface.</p><p>For the assignment, I chose the app Headspace.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBnaokEblcA5XGzt7o8aw.png" /><figcaption>Headspace is an app that teaches you how to meditate.</figcaption></figure><p>Headspace is an app I frequently use to get a goodnight&#39;s sleep and relieve my stress. Even though I am using the app for daily relief, I also find myself drawn to it aesthetically as it features cute and cheerful illustrations that simply brighten your mood. I was deeply curious to understand the basic structure of it, and took several screenshots of the onboarding process to help me discover their interface structure.</p><p>Below are the seven screenshots of my choice:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FLMs240yshUUPENVjIJZKCk%2FHeadspace-Screenshots%3Fpage-id%3D0%253A1%26node-id%3D0%253A1%26viewport%3D242%252C48%252C0.1%26scaling%3Dscale-down&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FLMs240yshUUPENVjIJZKCk%2FHeadspace-Screenshots%3Fpage-id%3D0%253A1%26node-id%3D0%253A1%26viewport%3D242%252C48%252C0.1%26scaling%3Dscale-down&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F8ba5223e-1f27-459a-8f18-64fd408145a1%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/bbf56fa5b73e134edf6184ba1efc4155/href">https://medium.com/media/bbf56fa5b73e134edf6184ba1efc4155/href</a></iframe><h3>BENEATH THE SURFACE</h3><p>After examining the screenshots I drew a lo-fi version wireframe on paper. I chose the onboarding process of headspace captured in 7 screens because I was interested in how Headspace gets users to sign up and begin their mediation courses. By creating a lo-fi wireframe I was able to dive deep into the basic functions of the app and realized how the displayed information all had importance and hierarchy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2txJ3e7qilVbZ2HzMvLZw.jpeg" /></figure><p>Within the flow of the several wireframes, you can identify the <em>Task analysis.</em></p><h4>Task analysis is a process used to achieve user-centric designs</h4><p>Through this process, you can use to see a user&#39;s goals and behaviors to see how they can achieve a certain goal. By understanding the users and how they previously achieved their goals, you identify and create a product that improves their overall user experience. I discovered that <em>the main goal of headspace’s onboarding process</em> was to get the user to purchase one of their mediation plans. The user feels special and catered to by answering several questions throughout the onboarding about their meditation and stress relief needs and gives just enough information about what will be included without being too overwhelming and too many options. A strategically placed “continue” button creates a sense of direction that moves the user forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F00QqYXsKh2bh1SEnyUIMA.png" /></figure><p>After reflecting on the user flow and task analysis, it was time for me to build my digital wireframes. By referencing the lo-fi wireframes I created on paper I created a digital version in Figma. I used some elements from free wireframing kits including <a href="https://www.figma.com/community/file/844859338327309730">Ironhack’s own Wireframe Kit</a>. Having a previous background as a graphic designer, my biggest challenge was to focus on the pure skeleton of the app and pay less attention to the fun illustrations and cheerful branding. I enjoy using Figma and by far this was my favorite challenge out of Ironhack’s Prework challenges so far.</p><p>Below you can see my final wireframes and prototype.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2F235aaCJ4L2P1TItN0TNIpz%2FHANNAHPARENT---Exercise-2%253A-Design-Practice%2522%3Fpage-id%3D0%253A1%26node-id%3D23%253A1143%26viewport%3D241%252C48%252C0.19%26scaling%3Dscale-down%26starting-point-node-id%3D23%253A1236&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2F235aaCJ4L2P1TItN0TNIpz%2FHANNAHPARENT---Exercise-2%253A-Design-Practice%2522%3Fpage-id%3D0%253A1%26node-id%3D23%253A1143%26viewport%3D241%252C48%252C0.19%26scaling%3Dscale-down%26starting-point-node-id%3D23%253A1236&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F05689527-91da-4e5f-a95e-0e830716ff88%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d99d9ccc12e16af09a6246274683617/href">https://medium.com/media/9d99d9ccc12e16af09a6246274683617/href</a></iframe><p>I hope you enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40ce1e76a016" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Thinking — The Citymapper Case Study]]></title>
            <link>https://medium.com/@hannparent/design-thinking-the-citymapper-case-study-be408d1cd830?source=rss-34d4ccbe8ab1------2</link>
            <guid isPermaLink="false">https://medium.com/p/be408d1cd830</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Hannah Parent]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 19:16:02 GMT</pubDate>
            <atom:updated>2022-01-08T00:33:01.728Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design Thinking — The Citymapper Case Study</h3><p>As part of Ironhack’s Prework challenge, I was asked to participate in a case study, the goal of which was — to analyze and transform the Citymapper using the design thinking process. The end goal of the case study is to remove purchases through third-party apps, using the most user-friendly design approach.</p><h3>The Backstory</h3><blockquote>Citymapper was founded in 2011 by Azmat Yusuf. Citymapper is a public transit app and mapping service which displays multiple transport options, usually with live timing, between any two locations in a supported city. On the app, there are multiple urban modes of transport available to the user, including walking, cycling, and driving, in addition to public transport. It is currently available free of charge to users, and is supported by a mobile app on devices such as mobile phones, and on web browsers.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_9NooyMKjA5ujqH-OY0Xyw.jpeg" /></figure><p>I had never used the Citymapper app before (I am usually a Google Maps user). Testing out the app and diving into its features and content was a new and enjoyable experience for me. As someone who frequently uses public transport, I know the importance of having a mapping service that is user-friendly and gets me to my final destination without any confusion or complications. After testing the app myself, I was soon ready to begin the first steps in my design thinking process.</p><blockquote>Let The Design Thinking Process Begin</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*gWN6uK3u7pWPEM7gu_xmbQ.png" /></figure><h3><strong>EMPATHIZE</strong></h3><p>Before starting to design, I asked myself a series of questions:</p><p><em>- What is the main problem to be solved?</em><br>To deliver a user-friendly ticket purchase function within the app that allows buying tickets for multiple forms of public transport. (avoiding purchases through third-party apps)</p><p>- <em>Who is the audience for this application aimed at?</em><br>Anyone in need of a public transit and mapping service with a smartphone device</p><p>- <em>What is the client&#39;s competition?</em><br>Google Maps, Apple Maps, Moovit, Transit.</p><p>- <em>What tone/feeling does this app offer?</em><br>Fun, urban, relatively easy to use.</p><p>After answering these questions myself, I moved forward with the interview process. I interviewed 5 different people, all of them varying in age (between 20–55 years old), and asked them multiple questions concerning this case study.</p><p><strong>Some of the questions I asked were:</strong></p><p><em>What is your preferred transit/mapping application?</em></p><p><em>What are your current struggles with ticket purchases while using public transportation?</em></p><p><em>Do you often purchase a transportation ticket online?</em></p><p><em>What is your preferred payment method for ticket purchases?</em></p><p><em>What part of purchasing tickets online do you find the most difficult and what changes would you like to see in the future?</em></p><p>Based on my user research, I was able to conclude from the interviews that:</p><ul><li>Many of the participants were in fact, using Google Maps or Apple Maps and only one of the persons interviewed was using Citymapper</li><li>The user research was taken place primarily in Berlin so it was centered around people who made Deutsche Bahn and BVG ticket purchases.</li><li>They primarily preferred to buy transit tickets online as physical tickets tend to get lost, the queues for the ticket vending machines are often long, and the ticket vending machines themselves are confusing and a bit outdated.</li><li>Participants noted that they struggle with app features being unavailable offline and mentioned that features such as QR codes and having their tickets stored in Apple Wallet would be beneficial to their needs.</li><li>Many felt overwhelmed by all of the many ticket options and wished that all types of tickets were available for digital use and completely accessible on their smartphones.</li><li>The majority of the users have been in a situation where they missed their trains due to the ticket purchasing process taking too long, many of them desired to have an option for a fast check out, that way they could even buy a ticket while boarding the actual train.</li><li>Some of the participants suffer from learning disabilities and noted that learning new platforms and processes is challenging and they need the application to be self-explanatory without too many options and unnecessary information and find some current apps limit their daily needs and cause additional stress in their lives.</li></ul><h3>DEFINE</h3><p>After collecting and reviewing the participant&#39;s data, I was able to begin brainstorming solutions. I created a very rough mindmap to help me visualize and began narrowing down all of the multiple design solutions I had. I tried my best to keep my ideas centered around everyone&#39;s main needs, keeping them functional and clear to all users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ZJ288neaM5NbXWRmv70eA.jpeg" /></figure><p>The responses I got from my interview process to find my finalized idea</p><p>THE CITYMAPPER TICKET WALLET</p><p>Starting with the main issue all third-party apps will be removed and you can purchase transportation tickets directly on the Citymapper app. While analyzing the best possible route for you, it will offer you an option to purchase your correct ticket without any confusion.</p><p>If the user happens to have any additional fares such as a bike ticket, or any additional passengers such as children or dogs you can add the extra cost with a simple click. This ticket will then be downloaded directly into the app in the form of a QR.</p><p>For those using an iPhone, it will have the option to be stored in your apple wallet for quick and simple accessibility. Both the ticket and the route will be available offline. All payment methods are accepted even digital currencies such as Bitcoin.</p><p>Monthly and yearly ticket holders can always add additional fares and change zones directly in the app.</p><h3>PROTOTYPE</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dN-gH6fIMeHQs3hxBNojmA.jpeg" /></figure><ol><li>The user adds their desired route.</li><li><em>Route Planner </em>automatically detects the best type of transit and route for the user and offers them ticket choices</li><li>The user is shown their ticket option with the correct fare zone. It offers additional tickets for passengers. There is a <em>fast checkout</em> method (Paypal and Apple Pay) or the option to proceed with payment.</li><li>Their wallet balance is shown =a form of credit, as well as all other payment forms.</li><li>After clicking desired payment the user can go over all details including fare costs and credit balances before making the final decision to purchase.</li><li>The ticket is successfully purchased and a QR code is shown and downloaded into the app. There is an option to add to Apple Wallet. The time remaining on the ticket is shown as well as an option to add an alert when the ticket is expiring.</li></ol><h3>FINAL THOUGHTS</h3><p>I absolutely enjoyed this project, especially the interview process and gathering user data. I found it challenging to not overwhelm the app with too many options and information and spent a lot of time narrowing down what should and shouldn&#39;t be shown throughout the user&#39;s journey. I also realized at first I focused a lot on the wireframe instead of the core — <em>improving the experience of the user</em>. I am not completely satisfied with my result and in the future, I want to challenge myself to redesign it a couple more times and interview a different group of people for more opinions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be408d1cd830" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>