<?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 Claudia R. on Medium]]></title>
        <description><![CDATA[Stories by Claudia R. on Medium]]></description>
        <link>https://medium.com/@claudia.rewinkel?source=rss-4bd8cffb0edb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*I19hEzXUvPrXGOlB0_W2pA.jpeg</url>
            <title>Stories by Claudia R. on Medium</title>
            <link>https://medium.com/@claudia.rewinkel?source=rss-4bd8cffb0edb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:48:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@claudia.rewinkel/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[Wellness app Flo&Go]]></title>
            <link>https://medium.com/@claudia.rewinkel/wellness-app-flo-go-f1f37f00206b?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/f1f37f00206b</guid>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 22:25:16 GMT</pubDate>
            <atom:updated>2023-04-24T22:25:16.985Z</atom:updated>
            <content:encoded><![CDATA[<h4>A menstrual cycle tracking app, empowering women by helping them connect with their body</h4><p><em>Ironhack project 4: Wellness app</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DNkHvOfS9qT3yWMzb0fx2w.png" /></figure><p>Dear UX enthousiasts, welcome to my 4th case study project in the Ironhack bootcamp.</p><h3>Overview</h3><p><strong>Challenge</strong></p><p>This time the brief was a little different. We were tasked to <strong>create a wellness app</strong> from scratch to present on the <strong>Daily health conference</strong> day. On this make believe conference day it was up to us to wow and <strong>convince</strong> the stakeholders to develop and integrate our app into their arsenal of health applications available to their members.</p><p><strong>Problem: </strong>The Daily health conference has seen a significant drop in memberships and want to offer more value to their members and keep their image up to date. They organised a MPV competition among designers to rethink how people can adopt and commit to a health-improving routine.</p><p><strong>The app</strong></p><ul><li>can address any aspect of personal wellbeing</li><li>should track the user’s progress and encourage them to implement a healthier lifestyle</li><li>Users must retain control over their private data (GDR Compliance)</li><li>The UI must exude a fresh and modern feel, and should be aligned with the Daily Health Conference’s values.</li></ul><p><strong>The prototype should include</strong></p><ul><li>User profile and goals</li><li>The <strong>main user flow</strong> presenting the app’s main feature(s)</li></ul><p><strong>Must-Have</strong></p><ul><li>Users need to be able to set up their profile to include important information relevant to their goals</li><li>Users need to be able to set goals and track their progress</li><li>Users need to be able to edit, share or delete their personal data</li><li>Users need to be informed about the usage of their personal data (This is an opportunity to practice UX writing)</li><li>Users need to receive feedback from the system (empty states, errors…)</li></ul><p><strong>Nice to Have</strong></p><ul><li><strong>Educational component:</strong> find a way for users to stay informed throughout the process and understand how a health routine can benefit their well-being</li><li>A “Privacy” page should be included in the design, but there is no need to create it or its content.</li></ul><p><strong>To conclude</strong> this project we’re presenting our MVP through a 10 minute presentation on the Daily Health conference in front of the stakeholders and boardmembers.</p><p><strong>Chosen topic: </strong>Menstrual tracking app</p><p><strong>Duration:</strong> 10 days</p><p><strong>Team</strong>: Claudia Rewinkel and <a href="https://medium.com/u/be3c98b730a2">Amadeja Plankl</a></p><p><strong>Deliverables: </strong>App including all facets of UX design process, Research, Market analysis, Subject research, Affinity Diagram, Empathy map insights, User persona and UJM, Ideation results, low, mid and hi fidelity wireframes, User flows, Concept and desirability testing results, moodboard, Style tile and style guide, Hi fi interactive prototype, key insights and next steps, and final presentation slides on UX and UI process.</p><p><strong>Role: </strong>UX UI designer (<em>sidenote:</em> I might have spent an excessive amount of time on the UI as it was incredibly fun to create the illustrations from scratch and style our app, can’t wait to take you through the process!)</p><h3>Menstrual tracking to empower the modern woman</h3><p>For our topic it became clear that me and my teammate were passionate about giving women a tool to not only track their menstrual cycles, but to also empower them with knowledge on the effects their hormones have on their body allowing them to work with their cycle. Through desk research our research we found that over 90 percent of women struggle with pms symptoms but often end up gaslighting themselves not taking their symptoms seriously and wonder whether they are the only ones experiencing these feelings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loQlzW3daQstFj6W_QiFjg.png" /></figure><p>Through our research we wanted to validate our hypothesis that women would feel more in control and confident if they could both track their cycles and gain an understanding on what their body goes through and that breaking the stigma surrounding periods is important to make space to nurture the body without judgements.</p><h3>What is already out there?</h3><p>There are already a myriad of period tracking apps on the market, we believed that there was still room to add value and resources to our prospective users. We went ahead conducting both a competitive and feature analysis to understand our position in the market a bit better and to get an understanding of areas of improvement through updating our knowledge to what is already tried and true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tsea8BGVTvMoKOMQNmCUlg.png" /><figcaption>Competitive and Feature analysis</figcaption></figure><p>After our thorough analyses we concluded that some apps were already providing a vast amount of resources but that the community aspect deserves more attention.</p><h3><strong>Surveys</strong></h3><p>We created our surveys to understand the relationship women have with their periods better and to find out how people feel about sharing their personal data online. If you’re curious to see our 10 question survey take a look <a href="https://docs.google.com/forms/d/161b26VR6Ikhh4Jgp4-_VMElbix-lSs3X_5k6gVicpz0/edit">here</a>!</p><p><strong>Summary</strong></p><p>We comprised a survey of 10 questions and got a total of 75 responses, and found out our most of our users were women between 26–35 (57,3 %)</p><p>Below are two of our keyfindings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NpMk6OhQDBXqhuRgjaaK9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fJM0y1zpjK3_0PGShvRGA.png" /></figure><p>These findings revealed to us that women find it important to understand their bodies better and are willing to share with community if it is available.</p><h3>User interviews</h3><p>With the context of our quantitative data in mind, we created a user interview guide focussing on the needs of our prospective users. Particularly what the relationship is between women and their periods, what they feel they need from tracking apps and how they would feel supported during their cycle. We concluded that women feel there is still a lot of stigma surrounding periods and would love to have ways to access resources and community to feel less isolated and to understand their bodies better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TmH-vyttGiHbOTctX2WgRg.png" /></figure><p>From here we clustered our findings into an affinity diagram and dotvoted on what the main themes were to then fill out an empathy map that would help us in creating our user persona.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vWA8QSRaElHtf8Bv_QASiQ.png" /></figure><h3><strong>Defining our problem</strong></h3><h3>User persona</h3><p>Let me introduce you to our vivacious and bubbly Meg! A loyal member of the Daily health conference apps and in tune with her body for the most part as she likes to stay fit through exercise, meditation and nutrition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgyFQbb-m7tM-guV99DNmw.png" /></figure><p>Let me walk you through a day in the life of Meg through our User Journey map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yrYwWkV-qEoe8NlM9oVDew.png" /></figure><p>Meg experiences quite the emotional rollercoaster and plummets from being excited to plan for her events to feeling defeated and ashamed cancelling her event due to period symptoms that stress her out.</p><p>Meg’s frustrations highlighted the following <strong>how might we’s</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NZ82v-pfHLuJJ8GLjnq-Pg.png" /></figure><h4>Problem statement</h4><p>Our ‘how might we’ questions shaped our problem statement as follows:</p><blockquote>Women with active menstrual cycles need to find a way to understand their bodies better during their cycles because a lack of helpful resources and communities exacerbates their symptoms and confidence.</blockquote><h3>Ideation</h3><p>On to the ideation! Where we came up with a lot of ideas and general concepts through crazy 8s while also bearing in mind the must haves ,should haves and nice to haves the Daily Health Conference provided us with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xk69_4qxg8tPG5TPI_29aA.png" /></figure><p>As we already had our list of must haves we knew to focus on these specifically:</p><ul><li>Users need to be able to set up their profile to include important information relevant to their goals</li><li>Users need to be able to set goals and track their progress</li><li>Users need to be able to edit, share or delete their personal data</li><li>Users need to be informed about the usage of their personal data (This is an opportunity to practice UX writing)</li><li>Users need to recive feedback from the system (empty states, errors…)</li></ul><h4>MVP Statement</h4><p>After compiling all the essential features we created the following MVP statement:</p><blockquote>Our period tracker app aims to help users efficiently track their menstrual cycle every month.</blockquote><blockquote>Women can create their profiles, set goals, add symptoms, check daily insights and share their thoughts and feelings with the app community. They can participate in live sessions within community to build on their resilience and confidence, or chat with other women. They can also consult medical advice and a myriad of reliable resources to understand their body better and plan accordingly.</blockquote><blockquote>By ensuring that these features are available, users will be able to see cycle trends and symptoms patterns, while feeling assured their personal data is safe and confidential. The users will feel their best while on their period and be more confident navigating their menstrual cycle.</blockquote><h4>Sitemap</h4><p>At this stage of the process both Amadeja and me were extremely excited about our concept but soon felt overwhelmed with the scope of what we wanted to accomplish. This made us turn to making a sitemap before we did anything else. Our sitemap allowed us to have a visual overview of what we wanted to incorporate in our app and conveyed the general idea for the information architecture as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42iaYboqsnudAKax7zgTyQ.png" /></figure><p>Using our sitemap we created our two User Flows. The first one portraying the most efficient way to use the app when users find themselves in a stressful period of time and the latter one accommodating users who have plenty of time to browse and consult resources and perhaps partake in activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kg0dzFsRqfie-ow2d-84JA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdNflcRgmOyh_n5P8sjHLg.png" /></figure><h3>Design</h3><h4>Lofi Wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uJI_gmj0abCs34wxnT87kg.png" /></figure><p>This is where our concept started to come to life! After a concept testing we discovered:</p><ul><li>People were confused about the headphones icon that showed users that they could integrate third party streaming apps. Having that visible while on mediaplayer screens made it confusing as to whether it hinted at the mediaplayer audio or something else;</li><li>The organisation of topics could be better;</li><li>The navigation bar icons were a little unclear;</li><li>People wanted a separate screen for logging more in depth symptoms and notes.</li></ul><h4>Mid-fi wireframes</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQ-axfrhZRvnGDJDcJtj_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KxARSGbh4xpoOkLnIZSOmw.png" /></figure><p>In our midfi wireframes we iterated on the icons in the navbar adding text for clarity. We removed the headphone icon to prevent confusion, created a seperate page for symptom logging and organised our topics differently in the Resources section.</p><h3>Branding</h3><p>Now before we jumped into HI FI’s we spent a good chunk of time preparing our design system and style guide.</p><h4>Visual competative analysis</h4><p>We started off doing a visual competative analysis and realised most period tracker app have an overall feminine character and realised we wanted to pay attention to our colour scheme to make our app more inclusive to people who identify as non-binary or trans. We find it important that everyone who has an active menstrual cycle feels seen, no matter what gender they identify with. This led to us having ideas to have a more gender neutral colour scheme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUs_uij6dzMD18rTPE1UwQ.png" /></figure><h4>Moodboard and Brand attributes</h4><p>We then set of to define our period tracker app Flo&amp;Go visually. We did this by making a visual moodboard using brand attributes. Through desirability testing we were able to validate our attributes and finish our moodboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QwOUowwREE7alyOlPCN58w.png" /></figure><p>We went ahead and created our style tile, and meanwhile had lots of fun designing our avatars and illustrations!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mapdiponK3_j-tnREH09PA.png" /></figure><p>We were able to streamline our main elements like</p><ul><li>Typography</li><li>Category cards</li><li>Icons for in app use and navbar icons</li><li>Colour pallete</li><li>Illustrations</li><li>Buttons</li></ul><p>To work efficiently we invested time in making components to ensure coherency, flexibility and speed in our designing process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXFRB9gM2f8FpSgHybpi9g.png" /></figure><h4>Check out our video of our High fidelity prototype here:</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-WS4Grv20_w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-WS4Grv20_w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-WS4Grv20_w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1995b0afe48615811870a11f7657bfe7/href">https://medium.com/media/1995b0afe48615811870a11f7657bfe7/href</a></iframe><p>Our video on</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1f37f00206b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UI redesign of Headspace mobile]]></title>
            <link>https://medium.com/@claudia.rewinkel/case-study-3-ui-redesign-of-headspace-b78004d682c7?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b78004d682c7</guid>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Mon, 21 Nov 2022 08:04:31 GMT</pubDate>
            <atom:updated>2023-09-25T09:08:52.565Z</atom:updated>
            <content:encoded><![CDATA[<p>As I’m typing this I realise that this project marks the halfway point of this bootcamp. It feels crazy to think that just 5 weeks ago the Ironhack UX cohort started. For the ones who have been following my bootcamp journey: Hi there! Today I’m sharing a project that is slightly different from the ones before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tpD_W5BCTqmqEKxJ9oMmwg.png" /></figure><h3>Overview</h3><p>Our challenge for the following three days was to redesign the UI of an app of our own choice and this time UX research fell outside of the scope. Our only constraint was to pick an app that was well-known. Eventually we’d have a design critique with our teachers, guest teacher and peers where we’d be expected to defend our design decisions.</p><p><strong>Team</strong>: Solo</p><p><strong>Role</strong>: UI designer, UX designer</p><p><strong>Duration</strong>: Three days</p><p><strong>Deliverables: </strong>3–7 screens and include at least one micro interaction in Figma</p><p><strong>Methods: </strong>Heuristic analysis, Information architecture, Visual competitive analysis, moodboard and brand attributes, prototyping</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/1*UHSKFETp0la4ncxYi7XROA.png" /></figure><h3>Redesigning Headspace in darkmode</h3><p>I was definitely looking forward to this UI project, as I was eager to deepdive into figma and put the all my fresh figma skills to the test. After some deliberation I chose to redesign Headspace. I had several moments where I wondered what on earth possessed me to pick Headspace since it might not per se scream to be redesigned since it has established itself as rather intuitive and pleasant to use but its users. In the end I’m glad I stuck to it as I learned so incredibly much and pushed myself to come up with ideas I was quite pleased with.</p><p><strong>So, why Headspace?</strong> Besides the appeal of the challenge I actually use Headspace on a daily basis. The guided meditation app has grown into an incredible source of mindful activities over the years. The reason why I favour Headspace over other apps is that they offer so much more than guided meditations, they invite you to connect to your breath and body through activities such as dance, sports, yoga and offer a range of wind down sleep talks to help wrap up the day.</p><p>Even though it is such a delight to have access to so much content that is so widely varied, I noticed while using the app that it brings up several challenges in presenting information architecture in a clear and coherent way.</p><p>Now before I specify things I sought to tackle through a Heuristics analysis, I thought it fit to mention that I opted to approach this challenge in darkmode as this is most realistic for me. My phone is perpetually in darkmode, I wonder what that says about me.</p><h3>Heuristics</h3><p>Now let me guide through some of the little hiccups I came across in using the app on a daily basis through guiding you through some heuristic analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1aUUFD2abNooY_GmIsJ41g.png" /></figure><p><strong>Consistency and standards </strong>My main struggle with the app was that so much content offered in different visual elements became overwhelming at times. Especially for an app designed to combat overwhelm. For example having so many different cards to present content through.</p><p>Small things but noticable were in the V<strong>isibilty of system status</strong> where it remained unclear when clicked something cause the buttons would hardly change state.</p><p>One pet peeve I had was something I allocated to Flexibility and efficiency of use. As it felt so inefficient checking on content on your homescreen. It was hard to get a quick idea of what the content consisted of. To play the audio you had to navigate multiple screens making it hard to decide whether or not I like the content suggested to me when on the go (and I’m usually on the go)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*uIA4FR2WbkDwwnVVkdLfFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*IrMy7U5QBp6_0Td8ZANRvg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*ZKG5rPxdrrd1ZIxA5TaT9w.png" /></figure><h3>I mostly got positive feedback which was great to stay encouraged and motivated after long hours pushing the tiniest details around. Though I did have some minor details to incorporate.Inventory atomic design and cloning</h3><p>After evaluating what kind of elements were home to the app, I set out to clone 6 screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19XtTHKbXKFici4pjRx0rA.png" /></figure><h3>Visual competitor analysis</h3><p>Before diving into a redesign I analysed 3 of Headspace’s competitors. Apps I had used before included Calm, insight timer and Le petit bamboo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XsxBxMl54I3Jq5V6wiIwJw.png" /></figure><p>My <strong>main take aways</strong> were:</p><ul><li>Calm, Coherent in expressing varied content. Intuitive to use and name sounds true to the experience.</li><li>Insight timer, too chaotic. I love the content offered, but visually it felt cluttered since there was no rhyme nor reason in consistency of elements and cards.</li><li>Le petit bamboo, has a clean minimalistic aesthetaic and feel. Though lacked a bit of playfulness.</li></ul><p>I wondered if I could marry the calm and playfulness in my redesign.</p><h3>Moodboard and Brand attributes</h3><p>Now to establish the look and feel of my redesign I jumped into collecting brand attributes and making a moodboard. I did a desirebility testing to validate my brand attributes and improved upon my final moodboard.</p><p>From my moodboard I was able to extract colours and make a style to have make my new design consistent and clean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ezdx1Xi7zBRUHbDJHnXQA.png" /></figure><h3>Style tile</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cw2mI44CTmqGrhgaMZjrKQ.png" /></figure><p>After making a custom icons and deciding upon the font and elements I took a deep dive into Figma and made sure to build the design from the ground up taking sweet time on crafting components. (Yeah probably could have been a tad more efficient with time but, it was a great practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hsMNShwJwwb8sjyW_s4Bow.png" /></figure><h3>Design critique</h3><p>I presented the following screens and respective prototype in the design critique below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UnQuSy73ULVIkD-3p_hkNQ.png" /></figure><p>I mostly got positive feedback which was great to stay encouraged and motivated after long hours pushing the tiniest details around. Though I did have some minor details to incorporate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuW6U0N1znErO4nI13QCRw.png" /></figure><p><strong>Take aways</strong></p><p>In just three days I was able to completely redesign a wellknown interface (4 screens), this amazed me quite a bit. Especially since I was able to fix the minor painpoints in the original design, where I streamlined the visual clutter and made a preview for the landing screen to save time. The user testing was incredibly insightful and helped zoom in on the minor details that get lost when you get sucked into a project like this.</p><p>If I were to have more time, my next steps would be a more rigorous accessibility test, cause I realise the yellow I chose could be looked at a little more closely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSdWU5hkum3THQTBRbtSWQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KqvCeTicCIeXwU2g4qY9HA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b78004d682c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bohmy: Ecommerce, Improving UX on mobile and web]]></title>
            <link>https://medium.com/@claudia.rewinkel/responsive-webdesign-case-study-2-ironhack-4ea2f357f804?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ea2f357f804</guid>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[casestudy-2]]></category>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Mon, 14 Nov 2022 06:58:04 GMT</pubDate>
            <atom:updated>2023-01-14T10:42:20.965Z</atom:updated>
            <content:encoded><![CDATA[<p>Dear UX enthousiasts, I’m back! This time with a juicy new case study on my second project of my Ironhack bootcamp experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dmdxTw4qNAGNOlf4aMWnjw.gif" /></figure><h3>Overview</h3><p><strong>Challenge</strong></p><p>Me and my incredible team <a href="https://medium.com/u/5db3060b3d2">Adam Q</a>, and <a href="https://medium.com/u/d92e75140f6e">Mahnoush Nekoufar</a> were tasked contact a stakeholder, secure an interview and research how UX could potentially improve the online presence of our stakeholder’s company.</p><p><strong>Deliverables</strong></p><p>Completing this project involved creating a high fidelity prototype on a main device and responive pages on a secondary and tertiary device. Our main focus was redesigning a webpage. And making mobile and tablet responsive pages.</p><p><strong>Team:</strong> <a href="https://medium.com/u/5db3060b3d2">Adam Q</a>, <a href="https://medium.com/u/d92e75140f6e">Mahnoush Nekoufar</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVA5bKoTD4BtTZasoUvhMg.png" /></figure><p><strong>Roles</strong>: UX UI designer, researcher,</p><p><strong>Duration:</strong> 7<strong> </strong>days</p><p><strong>Methods &amp; Materials: </strong>User research: quantitative and qualitative research, Swot analysis, Affinity mapping, Moscow Method, Moodboard, Wireframes, Low fidelity prototyping, High Fidelity prototyping, Figma, Figjam, Zoom.</p><p>Throughout this whole process we adhered to the designprocess</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vOp24SNRa973yImeELogrQ.png" /></figure><blockquote>Empathize</blockquote><p><strong>Secondary research &amp; Stakeholder interview</strong></p><p>Through out amazing fellow peers at Ironhack we got a lead for a potential company to contact. We were able to schedule an interview with Laure, stakeholder of a Frenchbased company called Bohmy, specialising in baby clip on carriers. Before we jumped into this zoomcall we made sure to do some secondary research on Bohmy and get familiar with Bohmy’s products and online presence. Upon our new insights we were able to craft an interview guide that we were able to send ahead to Laure. If you’re curious to what we asked Laure, you can find our interview questions here</p><p><strong>Follow the data</strong></p><ul><li>More detailed information on the product, Laure illuminated us on how the company got founded. After Laure became a mum she realised she neither wanted to give up her active lifestyle nor her love for fashion. She thought of a product that is durable and aligns with her values of sustainability and durability. To ensure parents can be active whatever the weather, and in their preferred outfit, these baby carriers are of timeless designs and are attachable without damaging clothing and rain and weatherproof.</li><li>Laure conducted her own market analysis, since her product is so niche there are not many competitors aside from 2 indirect competitors.</li><li>It was important to Laure that her designs are fashionable and of quality. Her main target audience are upmarket metropolitan fashion conscious parents in colder climates.</li><li>Laure wishes to expand her business to outside of Europe trying to appeal to the international market.</li><li>The main problems with her website, was that the website was incredibly slow. Laure was looking for a way to solve this and to possibly find ways to appeal to her target audience better.</li><li>Surprisingly enough most of her sales were through the mobile app with 88% of the sales. Because of this insight we decided to <strong>follow our data</strong> and make the mobile app format our priority instead of the desktop website. We also learned that most purchases were bought as a gift.</li></ul><p><strong>User Interviews</strong></p><p>With the data above we were able to design new interview guides for users interacting with the Bohmy webshop with the task to purchase an item. Soon enough we had gained a thorough understanding of people’s experience interacting with the site. We extracted themes from our data through Affinity mapping and learned that people struggled mostly with confusing layout as people weren’t able to determine it was a webshop at first glance. Another theme slow loading of content, and issues with inconsistencies of language throughout the site and having long scrollable content and confusing information architecture making it hard for people to find what they’re looking for; in most cases company values or how to shop for items.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CgfIZyS6SRBX4BTZooQz5w.png" /></figure><p>From the Affinity diagram we extracted the following themes and key focus points for our redesign:</p><ul><li>Language inconsistencies</li><li>First impression of the site</li><li>Ease of purchase</li><li>Focus on company values: sustainability</li></ul><p><strong>SWOT</strong></p><p>Our next step was to conduct a competitor analysis, though since we knew there were only two indirect competitors since Bohmy specialises in such a niche product. It made more sense to make a SWOT analysis of the current situation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*05WmHkemeorkZ-5pFlg-cg.png" /></figure><blockquote>Define</blockquote><h3><strong>Meet Marianne</strong></h3><p>After gathering our data after our user interviews, we were able to identify our targeted users through our user persona Marianne. Don’t be shy, it’s time to get aquainted:’).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f27GzgMNgXR1b-yZYzIlTQ.png" /></figure><p>For a deeper understanding of Marianne’s daily struggles and wishes we synthesised a User Journey Map. Let’s follow Marianne through a normal day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9gcgtOQlCwjTEHIuTjLaRA.png" /></figure><p>Our User Journey Map presented us with how might we’s that informed our next step, namely the making of:</p><p><strong>THE PROBLEM STATEMENT</strong></p><blockquote>Working parents interested in upmarket fashion need to find a way to browse and purchase the right niche products for their baby because they lose time with complicated navigations and their attention is often required elsewhere.</blockquote><p>Cue the Ideation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/1*dTG6LdJYovlbABup1mpvSA.gif" /></figure><blockquote>Ideation</blockquote><h3>Crazy 8s and Moscow Method</h3><p>We had a quick round of crazy 8s to get the creative juices flowing and made used the Moscow Method to prioritize features and get a clear picture on what to focus on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4rc8bkWsgA2XXshMUHFiZA.png" /></figure><h4>Sitemap &amp; Userflow</h4><p>We then analyzed the current information architecture of the website and decided to make a sitemap to help us get an overview of the information presented on the website and how the user accesses all the information that is available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Txw7zAthoVLF36lk-7355w.png" /></figure><p>Through our sitemap we were able to design a User flow with the goal of purhasing a specific item in mind. This userflow served as the blueprint for our concept testing and creating our low fidelity wireframes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zqiVtVlW11MRqtc7w8Mdg.png" /><figcaption>Userflow</figcaption></figure><p><strong>Low fidelity</strong></p><p>Our low fidelity wireframes served as a more comprehensive ideation of how our we felt the content would best be displayed. We wireframed the screens necessary to perform the userflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FWEQzge9En6i41bE_ma06A.png" /><figcaption>Low Fidelity wireframes</figcaption></figure><p>We prototyped our Low fidelity wireframes and went ahead to conduct concept testing which led to the following iterations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0A01l1PTh8av97ENCRsKw.png" /></figure><p>We then were able to iterate on the low fidelity by making our mid fidelity include these refinements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yUiTMADCXbGGqfMjV3aQCg.png" /></figure><p>Our usability testing validated our designs. Good news to get ready for our high fidelity!</p><h3>UI preparations</h3><p><strong>Brand attributes, Moodboard and Style tile</strong></p><p>Before jumping straight into including colours and styles, we had a systematic approach by firstly coming up with brand attributes that sum up the essence of Bohmy that led us to making a moodboard</p><ul><li>Fashionable</li><li>Sustainable</li><li>Reliable</li><li>Cosy</li><li>Caring</li></ul><p>After a desirebility testing where people commented on our moodboard we learned that we were able to successfuly translate our brand attributes through our moodboard which paved the way to extracting colours and creating our style tile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Icff58TrzKVYohu8wWwFyw.png" /><figcaption>Moodboard</figcaption></figure><p>We extracted the following colours from our Moodboard as we wanted to go for a calm, cozy and reliable aesthetic. Also we wanted to evoke the connotation to sustainablity with our shade of green, and add a little playfulness with our orange accent colour. We chose Poppins for our font as it welcoming and friendly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7sebXusc5qqXHM0UcCFTnw.png" /><figcaption>Style</figcaption></figure><p>From the style tile we were able to manage our UI and design elements in a consistent fashion. Try out our prototype here:</p><p><a href="https://www.figma.com/proto/kUukT4ZtCEwROp6EbdQfbk/G6-Business-Name-%7C-Design-File?page-id=116%3A21&amp;node-id=705%3A3391&amp;viewport=638%2C-561%2C0.22&amp;scaling=scale-down&amp;starting-point-node-id=705%3A3391">Figma</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OpiymYJpixYum4CW715sBA.png" /></figure><h3>Conclusion</h3><p>I had such an amazing time with my team, and feel lucky to have learned so much in the past week.</p><p>It was especially an incredible project as we were able to work for an actual company and build a connection with our stakeholder Laure.</p><p>It was an amazing and challenging project as we followed through the entire UX design process from start to finish and learned so incredibly much in a matter of 7 days. Presenting the entire project in 8 minutes proved to be tricky since last time we needed only present the UX part, this time we had to consolidate our process and carve out sufficient time to highlight our UI part.</p><p>It was incredible to learn so much about the UI part of the process, from figma labs and micro interactions to creating beautiful designs validated through methods like desirability testing.</p><p>I feel confident to face the following challenge! Though at times the amount of new information can seem daunting, the endresults astound me and make me all the more excited to see what we can accomplish if we keep on learning and applying ourselves.</p><p>Thank you so much for reading!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*gFNLR4tRnzFSMNfRyZOjJg.gif" /></figure><p>See you for the next project:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ea2f357f804" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Track & Go: Simplifying your move abroad]]></title>
            <link>https://medium.com/@claudia.rewinkel/case-study-track-go-4242aeeb2d65?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4242aeeb2d65</guid>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Mon, 31 Oct 2022 07:56:10 GMT</pubDate>
            <atom:updated>2023-01-14T10:40:44.688Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Wicked problem: Immigration</em></p><p>Hi there fellow UX enthousiast!</p><p>It’s been a minute since the start of the Ironhack bootcamp, and many things have transgressed. For one, I was able to work on a ‘wicked problem’ on the topic of immigration, kick — start the design process with my team and present our low -fidelity prototype the very next week. No idea how we were able to learn and apply so much in so little time, but let’s take you through the process and find out how we tackled our first challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*xCbGjySr9YW4E9NBNZJcdg.png" /></figure><h3>Overview</h3><p><strong>Assignmen</strong>t: Wicked problem, Immigration</p><p><strong>Project overview</strong>: Track &amp; Go is a mobile application that helps international students organise their tasks and documents for the immigration process to get settled into their new lives efficiently and confidently.</p><p><strong>Roles</strong>: UX researcher, UX writer, UX designer</p><p><strong>Duration: </strong>5 days</p><p><strong>Team</strong>: Claudia Rewinkel, Kim Vo</p><p><strong>Methods &amp; Materials: </strong>User research: quantitative and qualitative research,Affinity mapping, Wireframes, Low fidelity prototyping, Figma, Figjam, Zoom, Canva</p><h3>Wicked Problem</h3><p>At the start of our first week we were introduced with our topic. Our wicked problem to tackle was:</p><blockquote>Along with the experience of migrating to a new country — like having to adapt to a different culture or language — comes a number of bureaucratic duties that must be completed within a particular time frame to validate the journey in the host country <strong>How Might We Help migrants find information, complete tasks, and get their paperwork done to start their life in a new city?</strong></blockquote><p>My team and I had experience with the topic as we all lived abroad at one point in our lives and firsthand experienced the many bureaucratic difficulties that come with settling in a new country. This made us determined to find the best solutions for people in the same boat. Though as we approach this project with our users in mind we tackled the problem with a User centred design thinking and dove into secondary research to define the scope of context in which we would draft our interview questions.</p><p><em>Empathize</em></p><h3>Quantitative and Qualitative reseach</h3><p>Through our <strong>secondary research</strong> we found out that most people settling in a new country feel anxiety, and are more prone to depression due to a lack of support system and struggling to organise themselves and navigate a strange language.</p><p>As for our qualitative data, we were able to <strong>interview </strong>6 people, of which 5 of them were students having moved abroad for academic purposes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v1TyUcZyS-GHDq7c7EyNvg.png" /></figure><h3>Key findings</h3><p>Through Affinity mapping we were able to make sense of the data by clustering recurring themes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-0zlHo_JNt0I5kyFP5bwA.png" /></figure><p>By getting an overview of the gathered data we found that the feeling of overwhelm was prevalent due to a number of different things:</p><ul><li>Incomplete resources and unreliable information on official websites</li><li>Lack of overview of process</li><li>Difficulty tracking to do’s and determining order of steps</li><li>Language barrier</li><li>Lack of community</li></ul><h3>Define</h3><p>After having conducted our interviews it became quite clear what our user archetype would be. Thus we narrowed down the scope of our brief from migrants to students. This is when we brought Studious Sia to life through writing up a <strong>user persona,</strong> to identify our user and give our design process a direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mkmjhcso_PZ1U5H8DPdc-w.png" /></figure><p>We crafted a <strong>user journey map</strong> to gain a deeper understanding of Sia’s context to reveal the opportunities for design solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vStHUPGMc9gQQDiDUrrPbA.png" /></figure><p>Through the user journey map we were able to reveal our opportunities as we continued asking ourselves How might we questions.</p><ul><li>How might we help Sia keep track of her progress in completing important tasks?</li><li>How might we help Sia get easy access to reliable and accurate information?</li><li>How might we help Sia organise her documents?</li><li>How might we help Sia store the documents for the next appointments?</li><li>How might we help Sia overcome confusion related to language barriers?</li></ul><h3>Problem statement</h3><p>We finally arrived at defining the problem statement, where we were tasked to write down individual problem statements to consolidate our different main statement which resulted in the following:</p><blockquote>Working International students need a way to keep track of different application <br>processes for settling in their new country because the overwhelmingly incomplete and inaccurate resources prevent them from finishing their applications on time.</blockquote><h3>Ideation</h3><p>Moving forward to the ideation phase, it was time to get our pencils out and get our brainstorming going through ideation exercise of our choice.</p><p>We choose to each come up with 8 ideas through the crazy 8’s exercise giving ourselves 8 x 1 minute to draw an idea for features/concepts or even screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l_SAIY7RXpD-5m_7_ndt6g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rPS5QJhZBTnSpb1KpuJxXQ.png" /></figure><p>This exercise allowed us to come up with multiple ideas in a matter of 8 minutes. Which we then scanned to see which concepts we could combine and sort out, by voting what viable options were.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w34pksmJ36faQgzi6wdSWg.png" /></figure><p>Afterwards we turned prioritized the features through the Moscow Method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*oHevGA5zfRG32dxoivH7Ig.png" /></figure><p>The Moscow Method was a great way to get a better understanding of what features to prioritize in building the app.</p><h3>MVP Statement</h3><p>Based on Sia’s goals and needs we were able to create an MVP statement:</p><blockquote>The goal of our checklist app at the bare minimum is to enable international working students to complete tasks when they’re settling in a new country. It also allows users to navigate categories of information with integrated to-do lists to make sure no steps are missed. It will consolidate information and documents in a straightforward way, boosting the confidence of users.</blockquote><h3>How would Sia go about opening a bank account?</h3><p>This is when the User Flow comes in, a handy tool to come up with a ‘Happy Path’ as our goal would be to enable Sia to navigate the app with the least amount of clicks while opening a bank account.</p><p>As our app functions as a hub of reliable information and offers at its core the feature of a progress tracker and to do list app, Sia would browse general information, create a new to do and store documents needed in her document wallet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QotSWjtj4mcLWseCADL7AA.png" /></figure><p>We drew low fi sketches that I turned into a low fidelity prototype to help us get through our concept testing. Through these sketches it became clear that we wanted to include a ‘suggested roadmap’ for the adventurer abroad. Having the options to customize this roadmap by moving items around, deleting them or adding tasks to the page, in the same way you’d arrange a playlist.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vL8-XDKAAhg6MVkZGIJj4g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsRInrQhQRfjsrhC_A9Fdw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*01UOreXNk3vgneA5UAch7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eIjk-ChIQVhwLKYRmKr7Pw.png" /></figure><p>After taking the screens to Figma and making minor adjustments (have the to ‘do roadmap’ at the ready and creating categories for the document wallet, we were able to prototype this user flow and invite our interviewees for a concept testing.</p><h3>Concept Test</h3><p>Through our concept test we got an overwhelming positive response, and were only really set on changing one thing in the user flow (this is also due to time constraints) We decided to make the path a little more intuitive and have the User navigate from the ‘To do roadmap’ to the ‘Scanning page through the drop down menu, instead of through the navigation bar. Like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q8qZc4F8QsSKYg8l203rkg.png" /></figure><p>We implemented the above iteration in the final prototype you can watch below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fs91czb_vDDw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ds91czb_vDDw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fs91czb_vDDw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6e995a33d83f0d7e6efae9e2ae0a4c5c/href">https://medium.com/media/6e995a33d83f0d7e6efae9e2ae0a4c5c/href</a></iframe><h3>Next steps</h3><p>Though we were only supposed to be focused on the initial steps of the design process, it became tempting to imagine what the following steps would include. If we were to have more time, we would have definitely implemented more of the feedback we got back through concept testing as some people suggested to include:</p><ul><li>A search bar to navigate to anything from the same place</li><li>Focus on how we could help ease the frustration of language barriers (as of now, we only were able to include a category for language offering language classes)</li><li>Test and iterate on a feature that includes a personal cheerleader for completing tasks (Duo lingo concept), in the hopes gamification would help the student abroad be more motivated</li></ul><h3>What I learned</h3><p>I’m so pleasantly surprised at how much ground me and my team were able to cover in the first week.</p><p>Safe to say I was overwhelmed at first but believing in the process and in my team, paved the way to completing the first project.</p><p><strong>Teamwork </strong>Due to unforseeable group dynamics at the start of the project, we fell far behind on schedule, making it seem like an uphill battle at times. Though I am so grateful for my teammate and the support from the TA’s who were always encouraging.</p><p><strong>Interviews with actual users </strong>I was impressed with the data we could gather from interviewees, and even though drafting that first interview guide was daunting, the interviews themselves were so much fun to conduct and offered so many more insights than I could have imagined.</p><p><strong>Fun is an important key ingredient in brainstorming </strong>I was so impressed with how many ideas we were able to come up with by use of exercises like crazy 8s. It nearly felt silly as me and my teammate felt slightly skeptical about the expected outcome. 8 ideas in 8 minutes?! But we surprised ourselves and had so much fun doing it.</p><p><strong>Iteration </strong>Even though I got used to this quite fast, it was notibly a pivoting point in our process when we realised that whatever ideas we’d come up with were temporary and even silly ones, good enough to consider since we are not the judges but the users. Somehow this gave us space to play and be more confident with introducing our ideas since we knew the first draft does not have to be perfect. And that the final result can only exist through validation by the user and constant iteration.</p><p>All and all it was a rollercoaster ride full of beautiful insights and methods to collect, create and align ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4242aeeb2d65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 2: Spotify Wireframes]]></title>
            <link>https://medium.com/@claudia.rewinkel/challenge-2-spotify-wireframes-4fb853d98db0?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb853d98db0</guid>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[challenge-2]]></category>
            <category><![CDATA[claudia]]></category>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Sun, 02 Oct 2022 14:04:38 GMT</pubDate>
            <atom:updated>2023-01-14T10:39:17.172Z</atom:updated>
            <content:encoded><![CDATA[<h3>Reverse engineering Spotify</h3><h4>Ironhack’s Pre-work: Claudia Rewinkel_Wireframing Challenge #2</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7HtBZ7d3OFzmMpmR" /><figcaption>Photo by <a href="https://unsplash.com/@visualbyfath?utm_source=medium&amp;utm_medium=referral">Fath</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Dear readers, welcome back to another post of the Ironhack Pre work chronicles!</p><p>For challenge 2 we were tasked with creating a wireframe prototype, based on a user flow of our chosen app. I chose the app Spotify since it’s among the apps I use most frequently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*MVChSP5F8M-E2t6C-rvdew.gif" /></figure><h3>The importance of wireframes</h3><p>Wireframes are a blueprint for your digital product and usually come in a lo fidelity (e.g. simple black and white) representation of the user flows. Creating wireframes allows you to critically review how a user will navigate through the app or website and helps communicate ideation clearly to developers and stakeholders. The purpose is to focus on the functionality, and not get distracted by the UI elements and aesthetics such as branding and animations. The benefits of using wireframes are endless, but include saving on costs and time in the longrun of the designproces and ensures coherence and functionality.</p><h3>Reverse engineering: Spotify</h3><p>Spotify has transformed the way we listen to music.</p><p>The streaming service was launched in 2008 and now lets you discover, manage and share over 80 million tracks, including more than 4 million podcast titles. You can listen for free or upgrade to Spotify Premium to access exclusive features for music including improved sound quality and an on-demand, offline, and ad-free music listening experience. Today, Spotify is the world’s most popular audio streaming subscription service with 433m users, including 188m subscribers, across 183 markets.</p><h3>Userflow: Creating a new playlist and adding a song</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ry5N06Gkb04AyMlPjHhQlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T6bVDLErwnBtVfOWZ0scNg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/244/1*0XhhA732ybq0Wn4D5biyhQ.gif" /><figcaption>Screens</figcaption></figure><h3>Wireframes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RS3FGzb-aUAd1nlBlAZEA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/234/1*3hOmg5nejTS38ShFszYFqw.gif" /></figure><h3>Take aways</h3><p>This was a great exercise as it forces you to mind the details and pay attention to all the little steps the user takes in order to complete a task.</p><p>I did not expect to struggle so much with determining what elements were most important and what elements would be distracting. I can’t shake the feeling I omitted too many elements.</p><p>I found myself resisting the urge to make the flow more aesthetically pleasing and focus on the necessary elements that were crucial to complete the task.</p><p>Next time around I’ll be putting in a little more thought about the wireframing elements to keep them as coherent as possible. I suppose it’s also a matter of process since I’ll be growing my UI wireframing kit as I go and train my eye for detail.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb853d98db0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Casestudy: Citymapper]]></title>
            <link>https://medium.com/@claudia.rewinkel/casestudy-citymapper-dcb8f5796a5d?source=rss-4bd8cffb0edb------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcb8f5796a5d</guid>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[citymapper]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Claudia R.]]></dc:creator>
            <pubDate>Sat, 24 Sep 2022 14:45:23 GMT</pubDate>
            <atom:updated>2023-01-14T10:38:09.688Z</atom:updated>
            <content:encoded><![CDATA[<h3>Design thinking with Citymapper</h3><p>Ironhack’s Pre-work: Claudia Rewinkel_Design Thinking Challenge #1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*g6zj4IeoQggCMuyEJmM1RA.gif" /></figure><p>Hi fellow design lovers and aspiring UX UI designers! Welcome to my humble ventures into my new career: the multifaceted realm of UX. I’m <strong>beyond excited </strong>to be a part of the Ironhack community, to learn and develop myself as prospective UX professional and human being. Here you’ll find how I took a stab at the 1st challenge of the Ironhack pre work module. The challenge consisted of adding a feature to the app <strong>Citymapper</strong> navigating through the first four stages of the design thinking process: Empathize, Define, Ideate and Prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGplQReTws8l2DXIzLCBiw.png" /></figure><p>Join me on my journey in the pursuit of making commutes even more pleasant for urban explorers!</p><p>How?🕵🏽‍♀️</p><p>Let me introduce you to our client.</p><blockquote><strong>Client</strong></blockquote><p><strong>Citymapper </strong>is a multimodal public transit app and mapping service. A reliable travel companion as the app displays transport options as well as live updates on your commute between any two locations in a supported city, for a seamless travel experience. Sounds like a great addition to any traveller’s digital toolbox, though there is one issue that stands out among modern travellers.</p><blockquote><strong>Problem</strong></blockquote><p>The different amount of public transport tickets the users have to purchase. Public transport tickets come in different formats (paper or plastic cards) Buying different public transport tickets is often necessary to go from point A to B. This process results in undesirable situations (queues, vending machines that don’t work, etc). Finally, things like pricing or purchasing the correct ticket can become a real pain when you are abroad.</p><blockquote><strong>The challenge</strong></blockquote><p>To create a feature for this app that solves the pain of having to purchase different public transport tickets by different channels. Ready? Set. <em>Go!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*xvatNlpwYqflere7fcoF3w.gif" /><figcaption>Me, unaware of design methods and frameworks, sprinting towards solutions</figcaption></figure><p>Though, before we jump to conclusions..</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*KXgRVEHlL0K1EKxAO7HIZw.jpeg" /></figure><p>I used the <strong>Design Thinking Method </strong>to ensure that the users were kept at the core of this project helping me navigate different stages of the process in ideating solutions.</p><blockquote><strong>Step 1. Empathize</strong></blockquote><p>The Empathize stage in the design thinking process provides opportunity to research existing experience, frustrations with modal travel apps and the experience of modal travel in general providing an overview of what problems can be solved. At this stage user interviews, surveys and competitor analysis can be used to create context.</p><p><strong>Target audience:</strong></p><p>Users who commute and travel by means of transport who have experience using modal public transport digital services.</p><p>I interviewed 5 people with the goal of gaining a better understanding of their experience using public transportation in their home cities and abroad and assessing how their travel could potentially be improved by apps like Citymapper. I also wanted to know about their experience using modal public transport apps to understand what they value and would change.</p><p>My interviewees are young professionals between the ages of 21–37 who would be prospective users of the Citymapper app and are familiar with similar apps like 9292, NRW and Googlemaps.</p><p>All 5 interviewees have easy access to public transport as they all live in big cities and often commute for work or travel. Surprisingly despite the differences in location and purpose for travelling the users had similar wishes and frustrations when it came to purchasing tickets and navigating the ticketing jungle and subscriptions.</p><p>I conducted the interviews over videocall using an interview script that ensured the interviews to be around 30–40 minutes long. Check out my interview questions <a href="https://docs.google.com/document/d/1iC1b_yyoe_J4MwpTycjw7Y3C-xNb3LhFycy6ayJ3wvM/edit">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aIxHwsO1nGEMeTrz" /><figcaption>Photo by <a href="https://unsplash.com/@kwan_fvng?utm_source=medium&amp;utm_medium=referral">kwan fung</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote><strong>Step 2. Define</strong></blockquote><p>After collecting insights from the interviews I found that generally all users were after the same: clarity, efficiency and simplicity.</p><p>Clarity in having a clear overview of their itineraries of transfers with options and possibilities for payment to choose the most efficient route in price and duration in the easiest and fastest way possible.</p><p>The main frustrations I came across were:</p><ul><li>Apps that didn’t update for realtime updates on trips.</li><li>Not being able to access tickets offline or purchase tickets in case of poor connection underground.</li><li>Unclear or incomplete information on apps, on price of tickets and options for purchase.</li><li>A general lack of integrating existing travel subscriptions in pricing offered.</li><li>Confusion about how and where to purchase tickets for different modes of transport. Often through a myriad of other parties resulting into a poor overview and:</li><li>Confusion on how and where to get refunds when trips are cancelled or modes of transport delayed.</li><li>Absence of customer service when users need assistance when getting tickets through other parties</li><li>phones can be unreliable, as users have ran out of battery or lost connection and were unable to access their ticket</li></ul><p>A commonality across all users was that abroad, the digital experience would sometimes become so confusing they would resort to getting paper tickets on the spot. Language barriers and limited language options played a role in confusion as well as it increased the chance to encounter hidden fees.</p><p>Which brought a couple of frustrations when users prepared a trip online but are unable to purchase for reasons mentioned above and have to spent more time finding out where to get paper tickets and run a higher risk of losing these paper items.</p><p><strong>Defining the <em>main</em> problem: </strong>As most problems relate to purchasing tickets through different parties, having scattered formats of tickets and having no primary access point for user assistance the following question surfaced: How might we create a seamless all-encompassing purchasing experience for travel tickets?</p><p>As the goals would be to include features like</p><p>customer support and</p><p>offline access and preferably a way to</p><p>select your language.</p><blockquote><strong>Step 3. Ideate</strong></blockquote><p><strong>Possible solution</strong>s</p><p>Solution 1. To have an option to input the travel cards you already have that serve as a discount for buying a ticket for the whole trip through the citymapper app. This would allow for the app itself to serve as a ticket with a QR code. Integrating third parties into the Citymapper app.</p><p>Solution 2. Having immediate access to third party public transport provider tickets and downloading them into the Citymapper app having clarity on what customer service to connect with.</p><p>Important to add to the above solutions is a feature that allows tickets to be shared with fellow travellers or email to access it from another device for printing in advance or accessing tickets offline.</p><p>A feature that was requested was making it clear how to access customer service and the option to select several languages providing relevant information on travel itineraries and refunds.</p><p>Several sketches</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*9GcLhI2c2k4jGXPKpXDO8w.jpeg" /><figcaption>This was solution 1. Integrating third party tickets into one app and being able to share your tickets for easy access.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnyA7-nFj9YHIJtafw7bqg.jpeg" /><figcaption>I’ve included a way for the user to access customer support at all times, as they can navigate to it quickly through the bottom navigation. In this instance the tickets are purchased at the primary vendor and can be imported into the app for safekeeping and having everything in one place. I’ve also included the option of switching languages in the top section.</figcaption></figure><blockquote><strong>Step 4. Prototype</strong></blockquote><p>I chose to keep both flows I used above in tact, since some people might want to purchase tickets separate tickets for more flexibility when travelling from a to b. I did organise the information differently to make the process a little shorter and more efficient. This was achieved by omitting one screen in the purchasing flow and placing the options for purchasing on the review itinerary screen. Furthermore, I included the prices in the itinerary to give the user a quick overview of options with all the relevant information such as mode of transport, destinations, duration and departure times.</p><p>I also added the notifications button where users can decide whether they would like to receive updates on their trip.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3rwa0-AFt5rV7IrfxMXBOQ.jpeg" /></figure><p>Takeaways</p><blockquote>‘You know how it goes now’ - <em>Peter Bjorn</em></blockquote><p>It’s tempting to go with your gut. But let go of what you think you know about the subject. I was surprised at the wealth of knowledge you can obtain through interviews!</p><p>Beyond this assignment, design is about marrying business needs and user needs, the useful outcomes are the ones that are validated by actual users keeping constraints in mind. This reminded me to keep an open mind during my research interviews. Helping me suppress the temptation to ask leading questions in interviews and listen actively to painpoints and push beyond my own initial ideas in the research phase.</p><blockquote>‘Keep it light and keep it moving’ <em>— Thom Yorke</em></blockquote><p>It’s useful to document your progress and organise notes and insights as much as you can. Good organisation is key to keep a clear mind moving through the steps.</p><p>Also I’ve learned that constraints are incredibly useful in the design process as they provide a clear context in which to operate in. For example keeping a firmer grip on the time limit for interviews and giving myself time boxes for certain stages of the process. Next time I would operate more strictly within a time period to avoid zooming in too much resulting into feeling stuck in the process.</p><p>I immensely enjoyed this challenge as it allowed me to crawl into the skin of the everyday commuter and learn about people’s experiences and wishes. I have a lot more to learn and am excited to tackle the next assignment!</p><p>Thank you for reading, and if you’re working on your assignments good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcb8f5796a5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>