<?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 Vendi Clarberg on Medium]]></title>
        <description><![CDATA[Stories by Vendi Clarberg on Medium]]></description>
        <link>https://medium.com/@vendiclarberg?source=rss-44b2a38b815b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TGv4AjFdBIXMTA-xr5w9_Q.jpeg</url>
            <title>Stories by Vendi Clarberg on Medium</title>
            <link>https://medium.com/@vendiclarberg?source=rss-44b2a38b815b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 16:56:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vendiclarberg/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[A Wicked Problem and an attempt at a solution!]]></title>
            <link>https://vendiclarberg.medium.com/a-wicked-problem-and-an-attempt-at-a-solution-993e91892eb9?source=rss-44b2a38b815b------2</link>
            <guid isPermaLink="false">https://medium.com/p/993e91892eb9</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[first-project]]></category>
            <category><![CDATA[wicked-problem]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[prototype]]></category>
            <dc:creator><![CDATA[Vendi Clarberg]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 22:12:13 GMT</pubDate>
            <atom:updated>2023-01-31T06:41:37.410Z</atom:updated>
            <content:encoded><![CDATA[<p>A Case Study of my first group project at IronHack’s UX/UI Bootcamp</p><p>Our first project at Ironhack has come to an end and it is time to present it to the world! The focus for this project was on learning about the <strong>Design Thinking process</strong> and the <strong>Wicked Problem</strong> that my group chose, which was <strong>Immigration</strong>. It is called a Wicked Problem because it is complex and tricky with many possible solutions. I had the pleasure of working with a lovely team (see image below!) and in the end we created something we are proud of, as well as learnt a lot! Keep reading to find out about our process, the story of Laura and what other discoveries we made!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLloQmbO0cZa36pYlhzomg.png" /></figure><p><strong>The brief for this project was the following:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tp92wChLmWynoWmyiuqRSA.png" /></figure><p><strong>The concept of Design Thinking &amp; an introduction to UX research and User Centred Design</strong></p><p>Here is a brief summary of the different stages of the Design Thinking process, and what each stage means. We started off our project in the <strong>Empathise</strong> <strong>stage </strong>of<strong> </strong>the Design Thinking Process. We researched our users through various methods to learn about their <strong>needs, feelings and pain points</strong>. With that information we moved on to the <strong>Define stage </strong>to try and narrow down the problems to work on, and through <strong>Ideation</strong> we came up with solutions that would help our users reach their goals. In the <strong>Prototype stage </strong>we sketched out possible solutions and created a lo-fi prototype in Figma. I will now take you through the different stages more in-depth and explain how we reached our solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pX4ctVkKruJ3E60FclosCw.png" /><figcaption>Image from CareerFoundry</figcaption></figure><p><strong>Stage 1: Empathise!</strong></p><p><strong>Who are our users? Who do we design for?</strong></p><p>To start learning about our users we created a <strong>survey </strong>with 8 question aimed at people who have moved country at some point over the age of 18. <strong>“Lean Survey Canvas”</strong> helped us figure out which questions to ask in our survey, and who we would like to ask.</p><p>We wanted to find out:</p><ul><li>Reasons for moving country</li><li>Their age, gender and education level</li><li>If they experienced any difficulties in the immigration process</li><li>If they spoke the language of the country they moved to</li></ul><p>The survey helped us understand the demographics of people going through the immigration process, what their needs are, their motivations, their problems and how they feel. We posted the survey on different social media channels and 76 people filled it out. The purpose of the survey was to gather <strong>quantitative</strong> <strong>measurable data</strong>, meaning statistics and demographics. In the slides below we have presented some of the data we collected in the survey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53KJ9K-qU2u034DHCpggEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JSN9nwabU7qiYBAIU5GC7A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*If2IJ_32WEmvXfmf-K58jw.png" /></figure><p>To sum up the statistics, the majority of people moving to a new country were women, ages 25–34, the moved mainly for educational purposes and had beginner knowledge of the language in the country they moved to. The majority felt that not speaking the language was the main barrier, but the long administrative procedure as well as the difficult bureaucratic language came close behind. We also did <strong>5 user interviews</strong> with people who have migrated to a different country. The interviews gave us <strong>qualitative</strong> <strong>data</strong> where we learned more about the feelings, pain points and thoughts of our users.</p><p><strong>Stage 2: Define!</strong></p><p><strong>What does all this data mean for us, and what do we do with it?</strong></p><p>To start analyzing the data we first created an <strong>Affinity Diagram. </strong>This meant going through our interview transcripts to find important insights from the interviews and add them to little sticky notes in random order. We then grouped the insights that had a similar topic together and labelled the groups/categories. We had a lot of sticky notes to organise but we quickly saw patterns in our data. The main categories of information and pain points we labelled:</p><ul><li>Communication - The bureaucratic language is overwhelming</li><li>Process - Paperwork takes a long time to collect and get approved</li><li>Resources - Accurate information can be hard to find</li></ul><p>We also and filled out an <strong>Empathy Map template</strong> with the information from our surveys and interviews which helped us identify further who our users are, how they feel, what they see and do, what they hear as well as what their motivations and pain points are.</p><p>After this we could validate our assumptions around the immigration process and we could phrase a few “How might we?” questions to ask ourselves. “How might we..” statements are another way of rephrasing insights into actionable opportunities for our design solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QxY6W8Hr2kZZeEF19XQuzA.png" /></figure><p>The next step in defining the problems in the immigration process even further was to create a <strong>User Persona</strong> and a <strong>User Journey Map.</strong> We called our persona Laura Gonzales, and her story goes something like this:</p><p><em>“Laura recently moved to Berlin from Argentina because of a job offer in a tech startup. She is excited about living in a new city but also a little lonely because she doesn’t have any friends yet. Laura is a 26 year old front-end engineer but her workplace were sadly unable to help her through the process of applying for a work permit, which has left her feeling lost and stressed. She has heard it takes a long time to book and attend the necessary and multiple appointments required and she is unsure of where to start. The task of navigating through the German bureaucracy without speaking German makes her feel confused and intimidated.”</em></p><p>Since we don’t have a solution yet for our problem we created Laura’s User Journey in a “Current State”. This means it shows the process of applying for a Work Permit as it is now. The journey shows the different stages, the up and downs and the emotions that Laura is going through, and the little red stars are “touchpoints” that mark where we as a team had an opportunity to work on a design solution for this project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4_8GNQ_sCj1DeS2Y5nbIaw.png" /></figure><p>Before we cracked on with trying to come up with solutions for Laura and the rest of the immigrants in the world, we created a final <strong>Problem Statement </strong>to<strong> </strong>narrow our focus even further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uk5Id4c_-Th1fHu_YY_JFw.png" /></figure><p><strong>Step 3: Ideate!</strong></p><p><strong>Crazy 8 - What the heck is that?!</strong></p><p>To get creative and come up with ideas and concept sketches we did a round of <strong>Crazy 8</strong>. It is a pretty simple method where we all draw one sketch a minute, for 8 minutes. It can be a feature, a screen, any idea really!</p><p>The pressure of creating 8 screens/sketches/features in 8 minutes was actually really fun and helpful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d3hEe8AKQWwar9t86w5Yqw.png" /></figure><p>We discussed and explained out sketches to each other and agreed on a few ideas and features we wanted to include and develop further for our app. They were the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rdTdxbMVy2mDTOMD3Yzzaw.png" /></figure><p>After more sketches and discussions we decided to continue to develop the user flow from Laura’s user journey of needing to apply for a Work Permit in Berlin. We chose this flow because of the insights from our interviews, and the fact that is it a lot more difficult to emigrate to Germany from a country outside of the EU. We moved on to creating some simple Low-Fidelity Wireframes in Figma and proceeded to testing them with a couple of friends that fit the “early adopters” profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hQo2gk50VUPGgTpwlmPfiQ.png" /></figure><p>The main things we learnt from the testing were that we needed to adjust a few details. For example to change the position of the “Goal” and “Start” on our screen that is showing the progress of the application (screen on the right). With this feedback we went back to the Figma file to iterate a new updated version of our wireframes..and then another one, and…</p><p><strong>YouMigrate was born!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JtEZJHpJV1x1WvhcmW8Rqw.png" /></figure><p><strong>YouMigrate</strong> would be an app for people like Laura, who are moving to a new country or city, to help them through the various tasks that are involved in this often stressful process. The user first registers an account and based on the entered information a personalised list of tasks and paperwork is created for them. The flow starts with a login screen where you can choose which language you would like to have the information in. This would solve one of the main problems that immigrants face, the difficult bureaucratic language of government websites and forms. Once your account is set up you choose what you want help with. As I mentioned before, we focused our User Journey as well as our prototype on the task of applying for a <strong>Work Permit</strong> in Berlin. After choosing this option the different tasks appear, in this case it is 8 steps — submit fingerprint, submit photo, fill out a form etc, and you can also track your process on the screen that looks like a ski slope! The user gets taken through the process, step by step, and always with an option to reach out to support for help.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cmRuF1_MQ5pdxA6hK-Oz1Q.png" /></figure><p><strong>Conclusion and ideas for the future:</strong></p><p>The idea of this app builds on the cooperation of the German Government, and with over 1 million people migrating to Germany every year, it might be something that they eventually will try and develop to save resources. When brainstorming we of course had more ideas than we could fit into this project. Something we discussed and liked the idea of was a “<strong>Buddy feature</strong>” where the user can easily connect to other people in similar situation as themselves to find support and build a community, or just to find friends in the city to meet up with. We also discussed that the privacy of the users of course need to be focused on, as well as the possibility to attend appointments virtually and have the whole process done online. Ideally this app would also be available worldwide in the future.</p><p><strong>What we learnt?</strong></p><p>We have definitely learnt a lot!!</p><p>We learnt that the Immigration Process is a Wicked Problem indeed, and it can be approached in many different ways. This being my first project as a UX/UI student, I have found it very interesting to learn how to approach a problem with Design Thinking and understand how we step by step came to a conclusion. It was of course a lot of new information and methods to process, as well as getting to know each other and how we work as a team, and of course Figma and wireframing. We did have some struggles along the way, and personally I am not used to working online which I found hard to adjust to.</p><p>Overall, it was a fun process and I am looking forward to applying the knowledge to future projects!</p><p>Please also check out my team-mates for more articles and case studies.</p><p><a href="https://medium.com/@maria.martinezubierna">Maria Martinez Ubierna</a></p><p><a href="https://medium.com/@oliver.houtwerk">Oliver Voûte</a></p><p><a href="https://medium.com/@plummer.ksenia">Ksenia Plummer</a></p><p>Ricardo Baquero</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=993e91892eb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 2: Wireframing ClassPass]]></title>
            <link>https://vendiclarberg.medium.com/challenge-2-wireframing-classpass-9bf211be112a?source=rss-44b2a38b815b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bf211be112a</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[challenge-2]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Vendi Clarberg]]></dc:creator>
            <pubDate>Tue, 22 Nov 2022 21:53:38 GMT</pubDate>
            <atom:updated>2022-11-22T21:53:38.051Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to book a lovely wellness treatment!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*nJIamcHzYwzGxWXnWba_Jg.png" /></figure><p>For this final challenge of Ironhack’s prework we were asked to reverse engineer the task flow in an app of our choice, draw lo-fi wireframes, analyse the content and create five or more wireframes in Figma and finally turn it into an interactive prototype.</p><p>I chose to pick apart the app <strong>ClassPass</strong>. It is quite a simple app where you receive a certain number of credits depending on which monthly payment plan you have chosen, and with the credits you can book different exercise classes or wellness treatments. I think my subconscious is telling me I need a massage since I chose the user flow <strong>how to book an Aroma massage. </strong>I also chose this app because of the layout of the screens and the different UI elements. It felt like it would be good practice for me, and being a beginner with Figma I wanted something that seemed straight forward.</p><p><strong>Step 1: Analyse screenshots and make an inventory of UI elements</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaNfCKqzZx9oPHHECp_2GQ.png" /><figcaption>The click-flow for booking a wellness treatment</figcaption></figure><p>Inventory of UI elements:</p><ul><li>images/photos</li><li>vector icons</li><li>text boxes</li><li>navigation bar icons</li><li>action buttons</li><li>cards</li><li>links</li></ul><p><strong>Step 2: Draw lo-fi wireframes of the task I had chose and describe the flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnADU_7tqgglA7ziTWMdbQ.jpeg" /></figure><p>The flow starts on the <strong>Home screen</strong> where the user is presented with different fitness and wellness studios to choose from. The user can pick where they want to go and on the next screen they get further information about that studio. From there the user can click on <strong>View schedule</strong> to see what activities are on offer and how many credits they cost. They then choose a <strong>treatment</strong> or <strong>activity</strong>, and get forwarded to the next screen where they can pick a <strong>time slot</strong>. After that the user comes to a screen with more in-depth information on that treatment, as well as a <strong>Reserve </strong>button. After tapping on reserve, a modal window pops up where they have to <strong>confirm</strong> their choice to finalise the booking.</p><p><strong>Step 3: Wireframes and prototype in Figma</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QyPuf9P7L8b7snDSjzPR3A.png" /><figcaption>Wireframes and prototype arrows, and the screenshots again for comparison!</figcaption></figure><p><strong>Some thoughts on the task and the experience</strong></p><p>I definitely learned a lot from this challenge and it was also harder than I initially thought it would be, and it took longer to complete. Deciding which information to put in the wireframe and what to leave out takes practice, and at times I felt that maybe I left too much out and that my lo-fi wireframes got a bit too messy and unclear.</p><p>I also found that working with a phone that doesn’t have a standard screen size left me with a lot of question marks. Figma has a big selection of pre-set frames to choose from but mine is not one of them. My Pocophone F1 screen has a resolution of 1060x2246 pixels and it took me a while, some confusion and googling to figure out how to deal with this in Figma. But hey, now I’ve learnt about that as well.</p><p>We were given a kit with wireframe elements to copy in Figma to make the process easier, but I found that ClassPass uses a lot of reoccurring elements and it was faster and easier for me to create them myself instead of copying and scaling from the kit. I am very new to Figma and I thought I had figured out a good system for efficiently creating my wireframes and keeping my groups organised, turns out I hadn’t. I ended up going back and forth a lot to correct lines, boxes and alignment. I ended up feeling very frustrated at times, but I definitely also feel like I am learning more and more and that’s a very good feeling!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bf211be112a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Design Thinking_ challenge1]]></title>
            <link>https://vendiclarberg.medium.com/ironhacks-prework-design-thinking-challenge1-4246c8d5c02?source=rss-44b2a38b815b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4246c8d5c02</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[citymapper]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Vendi Clarberg]]></dc:creator>
            <pubDate>Tue, 08 Nov 2022 15:14:15 GMT</pubDate>
            <atom:updated>2022-11-08T15:29:59.708Z</atom:updated>
            <content:encoded><![CDATA[<h4>A challenge in Design Thinking with the CityMapper app</h4><p>Hi everyone!</p><p>My name is Vendela and I have recently started the prework for Ironhack’s UX/UI course. As a first challenge in Design Thinking we have been asked to look at the apps UrbanGo or CityMapper. With the methodology of Design Thinking I am to find pain points for users and possible solutions, but first, an introduction to the CityMapper app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*8qwBCfBDeJoJ-pzR3hNEDA.png" /></figure><p><strong>CityMapper</strong> is a well-developed public transit app that shows transport options, maps, live connection updates as well as walking, driving and cycling routes in over 80 cities around the globe. The app and website have been available for over 10 years now and it is constantly growing in order to cover more cities and means of transport. I have taken a closer look at the app which is packed with very useful information and various functions, but as the instructions for our challenge have pointed out, the possibility to purchase tickets directly in the app is missing and this is one of the issues I will be focusing on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rW8VNNvW1V8joSJr6D4OIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TBJ6GVMno9PyMhsOMvxn0w.png" /><figcaption>Image: Ironhack’s course-work article</figcaption></figure><ol><li><strong>Empathize</strong></li></ol><p>Prepared with a the list of questions and a user-centered approach I chose 5 individuals from within my focus group of 25–45 year-olds to interview. I chose them on the basis that they are used to travelling abroad as well as using transport apps. The conversations flowed and my interviewees had many both positive and negative public transport stories to share with me.</p><p><strong>2. Define</strong></p><p>After the interviews I analysed the information to get a clear overview. This step made it quite easy to define some of the pain points people experience when travelling. I have listed a few of them below:</p><ul><li>Difficult to know which tickets to buy, and where to buy them</li><li>Language barriers</li><li>Missing the last connection due to lack of information</li><li>Wasting time in ticket queues, and machines that are out of order</li></ul><p>From this list of issues I have chosen the following problem statement to focus on.</p><blockquote><strong>How can the users buy tickets in an easy, fast and convenient way?</strong></blockquote><p>During the interviews I found out that the users are happy to pay for tickets in an app, preferably with a credit card, google pay/apple pay or Paypal, and that they rather pay a little extra for the convenience of getting the correct ticket in a fast and simple way. After brainstorming I created a simple mind-map to collect my thoughts and to get a better understanding of what could be included in my prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LTvmYnwdtVQjdMOqG8Vdww.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*8MqMByWXmxxIM6K9XtLRyQ.png" /></figure><p><strong>3. Ideate</strong></p><p>The next step of the process was to ideate possible solutions to the pain points that had been highlighted in my interviews. I had a few different solutions in mind but in order to solve the problem with buying tickets I decided to add a button to the home screen. If you click on “Tickets” you get to see alternatives for different kinds of tickets, choose who is travelling as well as the options to choose a different city if needed. After you have purchased your ticket it will be kept in a ticket wallet of the app in the shape of a QR-code, and you also have the option to receive the ticket via email. You can choose to activate your ticket straight away or at a later time, and you can also buy tickets for additional people as long as they are travelling with you. <strong>When your ticket is active it will be displayed at the top, on the home screen!</strong></p><p>For this ticket function to actually work CityMapper would need to partner up with local and national transport companies all over the world.</p><p><strong>4. Prototype</strong></p><p>Having understood that it is not worth spending too much time on the initial prototype, it turned out quite messy. Hope you will get the flow!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VLNZRcHu0eJtBKYGvk1zw.jpeg" /></figure><p><strong>A few things I have learned from this challenge</strong></p><p>I think the challenge has been very interesting and I have learned a lot! It was a lot of fun interviewing people and I realised that my own opinions and solutions are at times quite different from others. This made me understand how important it is to interview and talk to real users. I found it quite difficult to draw a prototype without trying to make it too informative and pretty, and that there are so many things/buttons/screens to think about. I also found it interesting to learn more about the Design Thinking process and the different steps, and trying to figure out how to best move forward with the challenge. The process makes a lot of sense and I am looking forward to getting better at it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4246c8d5c02" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>