<?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 Vivienne Popp on Medium]]></title>
        <description><![CDATA[Stories by Vivienne Popp on Medium]]></description>
        <link>https://medium.com/@vfpopp?source=rss-e2f39d11d62e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1kmIF4DXrrnu0XfRFuHBZQ.jpeg</url>
            <title>Stories by Vivienne Popp on Medium</title>
            <link>https://medium.com/@vfpopp?source=rss-e2f39d11d62e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:17:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vfpopp/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[Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Editorial Project]]></title>
            <link>https://medium.com/design-bootcamp/case-study-every-project-needs-a-james-ironhack-ux-ui-bootcamp-editorial-project-bd73f4718a6d?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd73f4718a6d</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Sun, 14 Nov 2021 20:57:27 GMT</pubDate>
            <atom:updated>2021-11-21T11:24:49.861Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Editorial Project</h3><p>You know what’s a great tool to use when giving a Design Thinking presentation to engage your audience right away? Start with a persona that the audience can completely empathize with. Better yet, give them a persona that matches their prey schema and they won’t forget the presentation — and hopefully one or two other content points you told them afterwards.</p><p>This week we spent project week, which was all about editorial design, with our persona James Holmes. And since the presentation, James seems to have become a regular part of our student group. He even participated in our weekly <a href="https://kahoot.com/">kahoot</a> last Friday. In the following, I would like to introduce you to James and the project in which we designed a digital magazine for visual learners.</p><h3>1. Overview</h3><p>In the fourth week of the UX UI Bootcamp we focused on UI design and editorial design. The task was to design a digital newspaper or magazine in a duo team work, based on a persona that was roughly given to us as a proto persona. In this briefing we also named four media providers that the persona consumes. The output was to be an interactive hi-fidelity prototype of a desktop or app variant. We decided on the app variant.</p><h3>2. <strong>Problem Statement</strong></h3><p>The problem statement changed during the course of the project, as we were able to understand and thus formulate the problem more and more precisely as the work progressed. At the beginning, we formulated the problem statement as follows:</p><blockquote>“The user does not find an easy fast way to get qualitative content for further self education.”</blockquote><p>As well as the following hypothesis statement to match:</p><blockquote>“We believe that our users want the best quality of content information in an easy/fast/quick/effective way, to enable personal and professional growth.”</blockquote><p>By further analyzing the competition and describing our user persona, we ultimately formulated the problem statement like this:</p><blockquote>“Users with visual learning strengths don’t have a great range of editorials and tools to further learn and grow to stay informed about current business &amp; economic matters.”</blockquote><p>And to this we added the hypothesis statement:</p><blockquote>“We believe that the visual learning users want the best visually processed information to enable faster, and better learning of information.”</blockquote><p>We worked out both statements together by formulating each of them individually and then presenting and discussing them with each other. This enabled us to arrive at a common formulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B5GohjJOgAWe7rhn_DJHzw.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Problem &amp; Hypothesis Statement</figcaption></figure><h3>3. Users &amp; Audience</h3><p>And now about James.</p><p>At the beginning of the project, there was already a roughly described user persona. This persona is called James, 32 years old, belongs to the archetype “ambitious businessman”, reads business magazines like Bloomberg or TechCrunch and is interested in tools and techniques for better retention of the readings.</p><p>In the course of the project, we realized quite early on that we needed a more in-depth persona in order to come up with an appropriate result. So we expanded the persona further and James Holmes was born.<br>James moved from London to Berlin to expand his company. He has long working days and has little spare time. He wakes up everyday following the same routine, where he drinks his cup of coffee and reads his favorite magazines about the business world and economics. He is passionate about his work and always wants to be on top of new developments to stay ahead of his competitors. When he manages to find the spare free time, James spends it going on a bike road trip with his friends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GQjCI4KqRUiLL7uwMBP4nQ.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: User Persona James Holmes</figcaption></figure><p>Since he has so little free time, he needs well-prepared information. He can’t read whole articles and it frustrates him when information is not well organized. In addition, he is a visual learner and wants information prepared specifically for that. His goal is to grow steadily, personally and professionally.</p><p>Since the focus in this project was on UI design, we didn’t do any further research to back up the persona with facts.</p><h3><strong>4. Roles &amp; Responsibilities</strong></h3><p>The project was developed by my dear colleague and fellow student <a href="https://medium.com/@benjaminpeterhartmann">Benjamin Hartmann</a> and me in equal parts within four days. We worked together completely remotely and mainly used <a href="https://www.figma.com/">figma</a>, <a href="https://slack.com/">slack</a> and occasionally <a href="https://zoom.us/">Zoom</a> for collaboration. We broke the tasks down into smaller subtasks and distributed them evenly. As a result, we both contributed to almost all of the results presented below. Only the user journey map and the user flow were created by me, while Benjamin worked on the sitemap alone.</p><h3><strong>5. Scope &amp; Constraints</strong></h3><p>This project was also developed within four days, in addition to the lectures. It was developed within the Ironhack UX/UI Bootcamp. The narrow time frame was therefore a limiting factor.<br>Since the rough user persona already existed at the beginning of the project, this had a great influence on the final result including the competitive analysis. Since competitor magazines were already contained in the initial description of the User Persona.<br>Furthermore, it was clear that this project should focus on UI design. This influenced the scope in such a way that we did not delve deeper into UX research and did not further substantiate the user persona through interviews, gorilla research or surveys, for example. Rather, it should be assumed that this work had already been done in advance and could now serve as a basis.</p><h3><strong>6. Process</strong></h3><p><strong>Project management.</strong> In a first step we started with the project setup. We thought about the logical sequence of the individual steps and created a Kanban board with the help of the tool <a href="https://app.asana.com/">asana</a>.</p><p><strong>Competitive Analysis.</strong> After that we performed a competitive analysis. We analyzed eight different magazines and newspapers. We focused on the visual analysis, but also considered factors of the business analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DQyqqtEx7wtcsf-iTIPlng.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Visual Competitive Analysis (Forbes)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2ZiMYlbwjYJZzWgcP_4XQ.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Competitive Analysis</figcaption></figure><p>For example, we looked at the colors, typeface, layout, price, use of images. Three competitors, which we considered to be particularly relevant for our persona, we analyzed in more detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UoKcshg96m8iNCetbpkcuw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9kplXfT_LT_uaRpyIwG1KQ.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Visual Competitive Analysis (The Economist and Bloomberg)</figcaption></figure><p><strong>Brand Placement.</strong>We used the results of the competitive analysis to make a brand placement. For this purpose, we created a diagram with an x-axis and a y-axis. The x-axis describes the price range, while the y-axis represents the range of presentation between conservative to modern. After ranking the competitors, we placed “our magazine.” We decided to place our brand, which we called The Vibe, in the higher-priced, modern sector.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i8yKWm7IJjI-eO22ySHABg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Brand Placement</figcaption></figure><p><strong>Problem Statement + Hypothesis Statement. </strong>At this point in the process, we formulated a first draft of both statements. After formulating the user persona and the user journey, we returned to the problem statement to refine it as described above.</p><p><strong>Moodboards. </strong>We started the ideation phase by creating mood boards.Each of us created a mood board within one hour. Beforehand, we formulated the brand values of our magazine <br>THE VIBE which we wanted to represent: reliable, professional, progressive and innovative. The mood board results differed primarily in terms of the type of image inspiration, but the subsequent joint analysis revealed many commonalities. For example, the color palette.</p><p>To test that the intended perception of the mood boards corresponds to reality, we then conducted a survey. In this survey we showed the mood boards to the respondents and offered them different adjectives to choose from. They could select 3 to 5 adjectives that they associated with the mood board. The survey revealed that the adjectives professional and reliable were particularly hit. However, the adjectives progressive and innovative were hardly seen or not seen at all. We take these findings into account when creating the hi-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TkNTPYf9bjF9oT1DjIiN0w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lHcDvw4WHXm1bkSIjLiAnA.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Moodboards</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nX1eMM5ve_NMON_X188eWw.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Moodboard Survey</figcaption></figure><p><strong>Style Tile. </strong>Based on the findings of the User Persona, the Competitive Analysis and the Moodboard, we created a first version of the Style Tile. Initially, this version only contained the color palette as well as the type face and font. Later in the project, while working on the hi-fi wireframes, we revised and extended the style tile. For example, we added specifications for primary and secondary buttons and icons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ee0SYUFXJxuh-PuSrBTjKg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Style Tile (Final Version)</figcaption></figure><p><strong>User Persona + User Journey Map. </strong>While working on the mood board, we realized that the persona needed to get a bit richer, so that we can work with it. Therefore, we took another step back in the design cycle — or rather iterate the empathize phase. <br>We expanded the user persona to create the James Holmes described above, and then added more context by creating a user journey map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zx5oHuHQ1zBog6_t0DiBJw.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: User Journey Map</figcaption></figure><p>The User Journey can be described as follows: <br>James gets up as he does every morning, following his routine, and with his first morning coffee, reads various magazines to stay up to date. While looking through them, he gets annoyed, as he has done several times before. This is because the information is not well prepared for him as a visual learner. He can’t remember it quickly and it’s too much text for him. Out of frustration, he decides to search for an alternative. He finds The Vibe magazine and decides to download the app to try it out. He finds a special feature in the app: visual mode. He activates it and has finally found a magazine that is exactly tailored to his needs.</p><p>This already indicated the idea for a solution to the defined problem.</p><p>In the next step, we created the sitemap in parallel to the user flow.</p><p><strong>Sitemap.</strong> Starting from the home site, the sitemap shows all categories and subcategories and thus provided us with the necessary structure or setup for the first sketches of the prototype. After creating the hi-fi prototype, we revised it again as changes occurred during the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Sx5BqQK5OJQzmIa60b48eg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Sitemap</figcaption></figure><p><strong>User Flow.</strong> We sketched the user flow to define which flow we wanted to focus on. This selection was necessary due to limited time. Even though we had more far-reaching ideas, we were ultimately only able to make the prototype clickable for this one user flow. The User Flow describes the user’s journey from opening the app to consuming the item through the registration/purchase process and switching to visual mode.<br>In the process, we also modified the User Flow with regard to the registration/purchase process. This is because while creating the mid-fi wireframes, we realized that this process is a purchase that is handled in the AppStore and thus is not similar to purchasing through a web store. Therefore, the user is not redirected to a page where he first enters his user data and then his payment data. Instead, they can confirm the purchase with a few clicks and Face ID. All data is already stored. Accordingly, the user flow also changed with this realization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7wx31P41KIIKRLP5D4Uvgg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: User Flow</figcaption></figure><p><strong>Lo-fi wireframe.</strong> In the next step, we created lo-fi wireframes for the previously defined user flow, which we then presented to each other, discussed and assembled. The lo-fi wireframes already contained two different views for the home screen (visual and text mode) as well as a representation of the visual article screen, a subscribe screen and screens of the checkout. Furthermore, the toggle button feature for switching between a visual and a text mode was already included.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WvB3wGIaXN9GC7cGSBbhpg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Lo- &amp; Mid-Fi Wireframe</figcaption></figure><p><strong>Mid-fi wireframe.</strong> We proceeded to create mid-fi wireframes from the templates of the lo-fi wireframes. The home and article screens were very similar to the lo-fi wireframes, while the checkout process, as described above, was rethought and adapted to the iOS App Store. For the mid-fi wireframe, we also added a summary of the article content with short bullet point sentences on the article page, so that even less text is needed and more space is left for visual elements.<br>We subsequently tested the mid-fi wireframe with one user. While testing was not primarily in our scope, at the same time we wanted to avoid having major logical errors in our hi-fi prototype.<br>The test showed that the user flow we devised and presented worked well. However, the toggle button for switching between the two modes was not at all self-explanatory. This is a weakness that we have not yet completely solved even in the hi-fi prototype. However, it became clear that this button needed an explanation. We therefore added the label “Pictures”. Since not only pictures but also graphics or other visual elements could be shown, this designation is still not precise enough and probably unclear anyway. This would have to be examined in a continuing project work and I go into it again at the end of this article, under next steps.</p><p><strong>Hi-fi wireframes.</strong> Based on the lo- and mid-fi wireframes, we created the individual screens of the hi-fi wireframes, which we then linked together as an interactive prototype. To achieve a consistent result, we reverted to the previously created style tile, which at this point contained colors, typefaces and icons, and a first version of a button (mid-fi quality).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_CcthJW9fA9MH-R1bYPNbQ.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Hi-fi Wireframe Icon + Home Screens (Visual + Text View)</figcaption></figure><p>During the work we made some design decisions, which also led to the final extension of the style. To develop the hi-fi prototype, we created several components with different variations. For example, we created a “Header” component with six different variants, each reflecting different states: with and without a back arrow, with and without a theme category, and with Picture mode enabled or disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AI6MpIb3nmp33eJMleXZbg.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Hi-fi Wireframe Article Screens (Visual + Text View)</figcaption></figure><p>In addition, we created components with primary and secondary button variants, defined the color scheme for icons and the appearance of icons in different states — selected or unselected. Also at this stage we created the logo in font and icon form. Besides, we created components for article displays, categories with images, the subscribe and buy screen with different variants representing the states. Since we needed a lot of images for the fictitious magazine — especially in visual mode — we used the <a href="https://www.figma.com/community/plugin/738454987945972471/Unsplash">unsplash plugin</a> for figma. If you like to test the protoype, please click <a href="https://www.figma.com/proto/1z2yKS5n1x3hy2TLqDuiXk/Project-4-%7C-Group-5%3A-Benjamin-%7C-Vivienne?page-id=1790%3A389&amp;node-id=1969%3A7321&amp;viewport=241%2C48%2C0.14&amp;scaling=min-zoom&amp;starting-point-node-id=1969%3A7321&amp;show-proto-sidebar=1">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rUEGDAIs-DHH1G7cA4Xpew.png" /><figcaption>Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Project: Hi-fi Wireframe Subscribe + Payment Screens</figcaption></figure><h3><strong>7. Outcomes &amp; Lessons</strong></h3><p>In conclusion, I can say that with The Vibes, James has finally found a magazine that is specifically geared towards visual learners. So for now, this fictional project has been successful. <br>Nevertheless, there is no question that the next step would be testing and iterating. As already mentioned above, the toggle button should be discussed again in particular. First, a suitable name (Visual View, Visual Mode or else) must be found which does not exceed the limited space available at this point. Secondly, it remains to be worked out in which other and/or additional ways this function can be explained to the user (pop-up window that explains the button?).<br>Moreover, it would be important to further expand the style tile in the UI area and to develop a style guide.<br>In addition, the texts and the padding would have to be analyzed again in detail and adapted.<br>Furthermore, it would be interesting to apply the design to the desktop version. This would probably result in further changes for the design and possibly also for the structure.</p><p>During this project I learned to work with grids and how to create style tiles, which are very helpful for collaboration. I also learned how powerful mood boards can be as an inspiration.</p><p>If you do not want to miss my next article, follow <a href="https://medium.com/@vfpopp">me</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd73f4718a6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-every-project-needs-a-james-ironhack-ux-ui-bootcamp-editorial-project-bd73f4718a6d">Case study “Every project needs a James” — Ironhack UX/UI Bootcamp Editorial Project</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study —“Fresh from the field directly into the Ironhack Bootcamp” — Ironhack Bootcamp Project]]></title>
            <link>https://medium.com/design-bootcamp/case-study-fresh-from-the-field-directly-into-the-ironhack-bootcamp-ironhack-bootcamp-project-962e53c555fd?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/962e53c555fd</guid>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Sun, 07 Nov 2021 22:38:34 GMT</pubDate>
            <atom:updated>2021-11-21T11:25:10.352Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study —“Fresh from the field directly into the Ironhack Bootcamp” — Ironhack Bootcamp Project</h3><p>Do you remember a moment in your life when you bit into what at first glance seemed like an ordinary food and thought,</p><blockquote>“Gee, I thought every egg tasted the same. Just like egg.”</blockquote><p>At that moment, you realized that potato doesn’t taste like potato per se. Rather, there is a whole cosmos of potato flavors and intensities out there.</p><p>In this case, you will get along very well with Ines Martin. The user persona who walked me through week 3 of the Ironhack UX UI Bootcamp, in which we focused on the area of e-commerce.</p><p>In the following article I would like to tell you more about the project to create a hi-fi prototype for <a href="https://www.foodhi.de/">Foodhi</a>. Let’s take Ines shopping.</p><h3>1. Overview</h3><p>As mentioned this project was about the area of “e-commerce”. For this we worked in groups and had to find a local business that either already has online sales or has potential for online sales.<br>The task was to either improve the existing online presence or, if not yet available, to redesign it.<br>Outcome was to be an interactive, hi-fi prototype for desktop.<br>The goal was to create a great online shopping experience for the end user.<br>For this we created a user persona that belongs to the archetype “conscious food consumer”.</p><p>Our group had chosen Foodhi, which is a regional e-commerce that follows the principle of “from farm to fork”. In doing so, Foodhi follows an educational approach by offering only what nature or agriculture provides on that particular day. This turns the conventional system on its head. Because agriculture thus does not produce on time for the consumer. Instead, the consumer gets involved in the natural cycle and “eats what comes to the table” — or what can be offered in the Foodhi webshop after selecting the delivery date.</p><p>Foodhi goes even further and assigns a central role in the system to the farmers. Thus, potato is not potato in this context. Behind every product there is a producer with a face, a story, his own ideals and approaches. This makes each individual product a brand in its own right. In the store there will therefore be no potatoes of the variety “Linda” and “Laura”, but the potato of farmer Maria will be offered next to the potato of farmer Bernd. The potential buyer will thus choose a potato from one producer.<br>Foodhi is a Berlin-based startup that has already completed the beta phase and plans to launch in early 2022.</p><h3>2. Problem Statement</h3><p>At first, it was not easy to clearly formulate the problem statement, because the focus was missing and it could not be completely understood how Foodhi should work. Therefore, it changed several times during the course of the project.<br>At the beginning we formulated:</p><blockquote>“Users do not know when to order for getting what they like”.</blockquote><p>Then,</p><blockquote>“Users don’t understand why they might not get what they want on a specific delivery date.”</blockquote><p>In the meantime, it was difficult to stay focused on the user and not formulate the problem from the company’s point of view. Already when phrasing the two versions mentioned above, it became clear that the essential problem lies in communicating or making the specific business approach understandable. This is because it limits the consumer’s choice at first glance.<br>Ultimately, we expressed the problem statement as follows:</p><blockquote>“Users struggle to understand delivery times or product stock according to their wishes.”</blockquote><h3>3. Users &amp; Audience</h3><p>In order to better empathize with the user, we created a user persona. To do this, we used data from a survey that the company Foodhi had conducted in its beta phase and made available to us. In addition, we used clues from the interview with the CEO to develop our user persona, which we named Ines Martin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xvEHlqfH9SZBCF0PEQTe0Q.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — User Persona</figcaption></figure><p>Ines Martin is 29 years old and works as a project manager. She is successful, busy and well off. In her limited free time, she likes to invite friends over to her house to cook for them. On these occasions, she would like to serve something special. The products she chooses for this should preferably be local, fresh and of high quality.</p><h3><strong>4. Roles &amp; Responsibilities</strong></h3><p>This project was a group effort. The group consisted of four UX UI Bootcamp students randomly assembled by the Teacher Assistants. The project was worked on completely remotely with the help of various tools such as figma, miro, and Zoom. <br>While we kept getting together for voting sessions and discussions, we divided the work to be able to complete the project within the time frame.</p><p>In the process, I took on the following tasks:</p><ul><li>competitive analysis,</li><li>first characteristics user persona,</li><li>first draft information architecture,</li><li>low-fi wireframe</li><li>low-fi prototype testing,</li><li>main user flow + structure/systematic of the user flow,</li><li>value proposition,</li><li>design assets partly,</li><li>hi-fi wireframe + prototype partly</li><li>prototype recording</li></ul><h3><strong>5. Scope &amp; Constraints</strong></h3><p><strong>Time.</strong> Also this bootcamp project was worked out within 4 days (Monday-Thursday) besides the lectures and presented Friday morning. The briefing was already given to us in the afternoon of the Friday before. This allowed us to contact and select a local company over the weekend and arrange an interview for Monday evening. Due to the limiting time factor it was necessary to work in parallel and sometimes to do the second step before the first. This would be different in a perfect working world. However, it probably often corresponds to reality.</p><p><strong>Stakeholder.</strong> Since we were designing for a real company this time, we were dependent on the information and time the stakeholders could spare for us.</p><p><strong>Corporate Design.</strong> The already existing corporate design assets influenced our work, namely: colors, shapes, font. Moreover we got a first hi-fi wireframe of one app screen. The app is under development.</p><h3><strong>6. Process</strong></h3><p>We followed the Design Thinking Principle: Empathize — Define — Ideate — Prototype — Test.</p><p>After defining the project goals and approach, we first wanted to better understand the company, the business environment and the users.<br>For this purpose, we conducted an interview with the CEO of Foodhi, made a competitive analysis, which later we extended to other competitors according to the CEO’s information.</p><p><strong>Interview.</strong> The goal of the interview was to get as much information as possible. We were particularly interested in the company’s values, business idea, processes (flow), products and producers, as well as any materials that already exist for corporate design. For the latter, we were given logos, color codes to four colors, and a font.<br>The values of the company later influenced the values for the website design and are reflected in the design principles.</p><p><strong>Competitive Analysis. </strong>Within the Competitive Analysis we examined 8 competitors for the following criteria:</p><ul><li>Order</li><li>Offer</li><li>Delivery</li><li>Packaging</li><li>Communication</li></ul><p>There were sub-criteria for each criterion, such as “Order Deadline”, “Minimum Order Value” and many more of the main criterion “Order”.</p><p>The Competitive Analysis helped us to understand differences and similarities between Foodhi and the competitors. It also helped us develop elements of the website in the ideation phase. For example, we got inspiration for the checkout process. But also while we were thinking about information architecture, the insights were helpful to make a meaningful taxonomy i.e. grouping/categorization.</p><p>In order to redirect the focus to the user we wanted to design the site for, we created the User Persona mentioned above and described a User Journey.</p><p><strong>User Journey. </strong>The User Journey describes how Ines Martin wants to host one of her dinners with friends and sets out to shop for all the products. She ponders back and forth trying to figure out where to shop. In the end, she decides on a market a little further away that sells local produce. She takes the drive, picks up all the individual products, stands in various lines, and arrives back home after another nerve-wracking drive. Completely exhausted, she starts cooking. Meanwhile, she thinks to herself that it’s time to find a better alternative for the next shopping trip. At dinner, a friend tells her about Foodhi. Ines is thrilled and decides to use the platform for her next invitation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BikndwHioRqzhGzMjWfcMQ.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Customer Journey Map</figcaption></figure><p><strong>Jobs To Be Done.</strong> On the second day, we used the Jobs To Be Done method to better understand the need or pain relief of the user with the use of Foodhi. We formulated a main and a related JTBD:</p><p>Main JTBD:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*bmhqVSSBLzMYiwFsmYSqKA.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Main Job To Be Done</figcaption></figure><p>Related JTBD:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*bnpZj7EWgtuykXEnhXKAzA.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Related Job To Be Done</figcaption></figure><p><strong>Value Proposition. </strong>Later, we created a value proposition with the same goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*3WwU5R_tK-sO_gRmovSwmg.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Value Proposition</figcaption></figure><p><strong>How Might We.</strong> Once we had better empathized with the user, we wanted to define the problem more precisely, using the technique of How might we questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*oB9xNkzLcSNXLxUv1MkAOg.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Problem Statement and How might we questions</figcaption></figure><p><strong>Information Architecture. </strong>We then slowly moved on to the next phase: Ideation <br>We brainstormed and created a first draft of the information architecture. My colleague concentrated mainly on the product part and I on the entire website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XINe4GvpIeACvfGmFNn8ng.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Information Architecture Draft</figcaption></figure><p><strong>Sitemap. </strong>From this, we developed a sitemap in the next step. In this context we had long discussions and consulted the results of the competitive analysis to create the taxonomy. In order to stick to the rule of offering a maximum of 6 categories, we kept it simple and grouped the products into four categories. This makes sense, since the store will only have a manageable number of products at the beginning. In addition, the 4 categories allow that more categories are added. So it remains scalable if the store grows. At this point, we would have liked to test the taxonomy with users and with stakeholders. For example, the card sorting method would have been a good way to do this. Unfortunately, we were not able to realize this due to the time frame.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZHAIkgc1IehC7_1Esy4eg.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Sitemap</figcaption></figure><p><strong>User Flow. </strong>We then brainstormed on possible user flows and decided on four user flows that we considered valuable to put on paper. We distributed the development of the four user flows among the four team members, so that each team member sketched a flow. In the end, we found out which flows did not work and which flowed better or worse. Based on these findings, we decided which two user flows — a happy path and a not-so-happy path — we wanted to implement and later also reproduce in the prototype. We decided for:</p><ol><li>Happy Path: Location — Date — Food — Checkout</li><li>Not So Happy Path: Location— Food — Date— Checkout</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B4Vxy-TSC251K1u8KGxxQQ.jpeg" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — User Flow</figcaption></figure><p><strong>Design Guidelines. </strong>Before we started creating the first wireframes, the next step was to define design guidelines based on the company’s values. Accordingly, the design of the website should be simple, scalable, relevant and transparent.</p><p><strong>Low-fi Wireframes and Paper Prototype Test.</strong> Then I created the first low-fi wireframes on paper and created a paper prototype, which I tested with a user. The user was given a “shopping list” and was asked to shop for three products on Foodhi. He was thus supposed to go through the Happy Path user flow outlined earlier. <br>Overall, it was found that the user flow already worked quite smoothly on the whole. For example, the user did not question the multiple offers of an apparently identical product (potatoes from farmer A, potatoes from farmer B, potatoes from farmer C, etc.). The thesis that some instructions in text form (e.g. choose delivery date &amp; we will show you, which food will be available) as well as additional labeling to icons and schematic representations are necessary to guide the user through the process could also be supported. <br>Furthermore, it was found that the position of one of the “order” buttons was not optimally chosen. It was in the upper right corner, instead of in the lower right area, where the user would have expected it. The position was then corrected in the next prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-xPcDiiDgcxD4EfyVpwiqg.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Low-fi Wireframes/Paper-Prototype</figcaption></figure><p>In the paper prototype, the user was given the equivalent choice of entering a delivery date first or pressing a button directly to search for specific products. This resulted in one of the key findings of the test: the user immediately pressed the search selection to purchase the requested three products. Since this path should be possible but is not the favored path of this business model, this insight had a significant impact on the design. In the next prototype, therefore, we decided to let the Delivery Date selection stand on its own and move the search to the navigation bar at the top. This is where the magnifying glass icon is located. Clicking on the icon opens a search box in the nav bar, where the user can search for products and producers. This creates a hierarchy and yet leaves the users with a choice of ways to get to their destination.</p><p><strong>Mid-fi Wireframe. </strong>Due to the tight timeframe, we worked on low- and mid-fi wireframes in parallel. While I created the low-fi wireframes and tested the paper prototype, mid-fi wireframes were to be created in parallel. Unfortunately, due to the misunderstanding of mid-fi wireframe, none existed on the morning of the fourth day. Since we had to finish the hi-fi prototype and a presentation on the same day, we made the decision not to make a mid-fi wireframe anymore. Otherwise we would have risked the completion of the hi-fi prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*JYAyrHaV8vWUNeRFtYGeeg.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Design Assets</figcaption></figure><p><strong>Hi-fi prototype. </strong>On the fourth day, we developed the interactive hi-fi prototype to map the essential user flow. This was developed on the basis of the low-fi wireframes and the analysis of these. For this purpose we created design assets from different components and variants and oriented ourselves on the already existing brand / UI guidelines of Foodhi.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrElxHd9wB3ScJM3NyYmug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jfDHMZhGlC8E4RtDfMSqSQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vBiclZVS1noM9UvQTBRUnQ.png" /><figcaption>“Fresh from the field directly into the Ironhack Bootcamp” — Hi-fi Prototype</figcaption></figure><p>The zip code input field was positioned as the first central element on the website. Since this should directly prompt the user to enter his location and thus filter whether he lives in the delivery area. <br>Second essential element is the progress bar, which offers the user orientation within the ordering process and accompanies him from the first to the last step. <br>The third element is a schematic representation of how Foodhi works. This illustration clarifies the ordering process for the user through the Foodhi website. <br>Next to it, the user will find an explanation of Foodhi’s business idea. <br>In addition, the various producers are represented by individual cards. <br>In the navigation bar, next to the profile and the shopping cart, there is also a magnifying glass icon, which opens a search bar for the user when clicked. Through this search he can find products and producers in a direct way.<br>Since the direct search of a specific product should be only the secondary purchase process, this search option is shown smaller.<br>This supports Foodhi’s business plan, which is to make the customer buy what is currently available on the field.</p><p>After entering his zip code, he is prompted to select the delivery date. After selecting the delivery date, the products available at that time are displayed to him. The products are always shown in combination with the respective producer. Once the selection is complete, the user can start the checkout process by clicking on the shopping cart icon.</p><p><a href="https://www.figma.com/proto/1OMIaMPp3tOaEEHbVcFjCl/Project-3-%7C-Group-2-%3A--Mar%C3%ADa-%7C-Amos-%7C-Vivienne-%7C-Ildiko-(Copy)?node-id=1191%3A3710&amp;scaling=min-zoom&amp;page-id=1136%3A20&amp;starting-point-node-id=1202%3A1418&amp;show-proto-sidebar=1">Here</a> you can try out the prototype.</p><h3>6. Outcomes &amp; Lessons</h3><p>In <strong>conclusion</strong>, it can be said, that the intended result of an interactive hi-fi prototype could be achieved. Even if this only applies to the essential user flow. This user flow works well in the first test with the low-fi prototype. Whether this is also true for the hi-fi prototype would have to be found out in the next step. In the following, we should test and iterate. In doing so, a significant focus should also be placed on the color scheme caused by the corporate brand (red and green: low vision) as well as on the size of the individual elements.<br>Furthermore, it would be advisable to create and test the other functions and pages as a mid-fi prototype in order to save unnecessary time and budget resources.</p><p>Subsequently, a comprehensive hi-fi prototype should be created, which should again be tested. Moreover, the launch would take place in January 2022. From that point on, feedback should be collected from real users. For example, with NPS, CSAT or CES.<br>In addition, it would be recommended to conduct a card sorting with stakeholders and, if applicable, potential customers to confirm the categorization.</p><p>What I learned in this project:<br>It is important to have or establish a common understanding of the task and of concepts. Otherwise, the process becomes very time-consuming, which of course also affects project costs. In addition, it is important to agree on organizational framework conditions, such as uniform filing, working hours and the like. For the next project, I would like to agree on the following points in advance with the team:</p><ul><li>When is something ready? Establish definition of done</li><li>When should something be finished? Time frame</li><li>Where and how should documents be stored?</li></ul><p>If you want to know if I will succeed in the above points in the next project, click <a href="https://medium.com/@vfpopp">here</a> and follow me to stay up to date.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=962e53c555fd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-fresh-from-the-field-directly-into-the-ironhack-bootcamp-ironhack-bootcamp-project-962e53c555fd">Case Study —“Fresh from the field directly into the Ironhack Bootcamp” — Ironhack Bootcamp Project</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study “How to separate private and professional on WhatsApp?” —  Ironhack Bootcamp Project]]></title>
            <link>https://medium.com/design-bootcamp/case-study-how-to-separate-private-and-professional-on-whatsapp-ironhack-bootcamp-project-260b5777654?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/260b5777654</guid>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[features]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 16:01:54 GMT</pubDate>
            <atom:updated>2021-11-21T11:25:05.904Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study “How to separate private and professional on WhatsApp?” — Ironhack Bootcamp Project</h3><p>Do you recognize the following situation?</p><p>It is Saturday. You wake up in the morning after a way too busy time. Maybe it’s been a tough week, or more likely a month of overtime. You are thinking to yourself, that you will not spend any thought on the work this weekend.</p><p>But then it happens: You receive a professional WhatsApp message. You are annoyed, exhausted, and you really need these two days off.</p><p>If this situation sounds familiar, you might feel like Ronja Braun.</p><p>She’s the persona who walked me through my second Ironhack UX UI Bootcamp project. Unlike the first project, this one was a solo project, that I worked on within four days, alongside the lectures.</p><h3>1. Overview</h3><p>The goal of my solo project was to integrate a feature into the messenger application WhatsApp, taking into account both UX and especially UI design. The feature should allow to have two parallel accounts on a mobile phone. The required result should be a high-fidelity prototype.</p><p>In the following article, I will describe the project and the single process steps in more detail.</p><h3>2. Problem Statement</h3><p>In the course of the project, my focus changed and the problem statement became more concrete. Thus, at the beginning, I formulated the problem statement as follows:</p><blockquote>“Persons having more than one WhatsApp account need a way to log into upteen accounts on one phone simultaneously.”</blockquote><p>In retrospect, I have to note, that this was primarily not a problem statement at all. It was rather a description of a need.</p><p>Later I formulated the following problem statement, as a basis:</p><blockquote><strong>“Business people are not able to separate their business and private communications on WhatsApp.”</strong></blockquote><p>The reason behind this, of course, is that it is not possible to have two WhatsApp accounts on one phone at the same time. So this is the identified problem in terms of the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zflCTiho2a2aiBMQEhiEVA.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Problem Statement</figcaption></figure><h3><strong>3. Users &amp; Audience</strong></h3><p>From the results of the guerrilla research, I could conclude that this feature would be used primarily for business people, who use WhatsApp in a professional as well as private context. Therefore, I decided to focus on this group.<br>I already mentioned the persona Ronja Braun at the beginning of this article. At the start of the project, she did not yet exist. Also other personas were not available. <br>Ronja Braun belongs to the archetype “young communicator”. She has been living in Berlin for several years and worked as a brand manager for a beverage brand. For professional reasons, she travels a lot, has many international contacts and is more or less constantly communicating with customers, partners and colleagues. WhatsApp is the standard tool for this, as it is fast, free and freely available. On the one hand Ronja loves her work, on the other hand she therefore always works way too much and has only few private breaks. She needs two separate WhatsApp accounts, because she wants to separate her private and professional communication without carrying two phones around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kWQQYxoDshLeQKPUvfmSZA.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Persona Ronja Braun</figcaption></figure><h3>4. Scope &amp; Constraints</h3><p>Time. As expected for a bootcamp project, this project was developed within a very tight time frame of four days, in addition to the lectures. This therefore represents a significant limitation.</p><p>Procedure. Furthermore, the deliverables, which were expected, were mentioned by the teachers. This certainly had an influence on the process of the project.</p><p>Even if a margin remained, since not all deliverables were absolutely necessary. Rather, they were used as orientation points. An own and above all logical procedure was thus indispensable.</p><h3>5. Process</h3><h3>DAY 1 — Getting started</h3><p>The ideas for the features came from our group of UX UI students. So on day 1, the very first thing I did, was to talk to my colleague, who had come up with the feature. Since my briefing on the feature was only two short sentences, I wanted to get a deeper understanding of what she meant.</p><p><strong>Project Setup.</strong> After that, it was necessary to sort out my thoughts. So I used brainstorming and mind mapping to get an overview of the project, the problem, the goal and the approach as well as the methods and tools.</p><p><strong>Guerilla Research.</strong> In order to get a solid insight into the thoughts of potential users within a very short time, I first used the method of Guerilla Research. I asked 5 people five questions. I found out that 60% of the people I asked, would like to have such a feature. 100% of this group of people would like to have this feature to separate their private and professional communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9O2yknCQcykXow099eTdA.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Guerilla Research &amp; First Low-fi Wireframes</figcaption></figure><p><strong>UI.</strong> In addition, I dealt with the UI design, with the colors, shapes and elements of WhatsApp, in order to be able to understand their “language”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2lD72bPl1XVdiFHqeXm_Pw.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Color Study</figcaption></figure><h3>DAY 2</h3><p><strong>Low-fi wireframes and first test.</strong> On the second day, I created the first low-fi wireframes with pen and paper, as this seemed to be the fastest and easiest method. On the one hand, I wanted to better understand the architecture and structure of the app. On the other hand, I went straight on and already developed the first ideas on how I could implement the feature in the app. My first idea was to work with two tabs within each page. I showed my first drafts to one person and asked them to interact with it. This revealed some problems — especially display problems — as many elements would have had to be listed twice. This would have led to confusion. At the same time, the analysis of the UI and also the guerrilla survey showed that it is precisely the simplicity, which is a key characteristic of WhatsApp. So after this step it was clear, that I needed to develop my ideas and designs further.</p><p><strong>Competitive Analysis.</strong> First, however, I took a step back and undertook a competitive analysis. In doing so, I wanted to learn how others solve this problem and get possible ideas. I examined three direct competitors: Signal, Telegram, and Facebook Messenger. The latter two offer multiple account usage. In addition, I looked at 10 supporting programs, which allow multiple accounts to be used on one phone. Some of these programs simply duplicate WhatsApp for this purpose. So you have to switch back and forth between two WhatsApp applications. Telegram and Facebook Messenger solve it within the app. However, you can only switch from one account to the other with several clicks. In both cases, you have to go into the settings for switching. <br>Summing up the analysis, I can say, that none of the offered solutions convinced me. This is mainly because they are bulky and involve several steps for the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xWWvk-LQfdhOFpzRoFD3Aw.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Competitors</figcaption></figure><p><strong>First Problem Statement. </strong>After the analysis, I wanted to focus more on the problem again, so as not to lose sight of it. So at the end of the second day, I held the first problem statement, which you could ready above already.</p><h3>Day 3</h3><p><strong>User Persona and Journey Map.</strong> To further sharpen the problem and then find the appropriate solution, I next engaged with the user and created the User Persona Ronja Braun already described above. <br>Afterwards, I drew up a user journey map in order to put myself in her shoes. The User Journey is roughly already mentioned in the intro of this article. Ronja, after long days at work, finally has a free weekend where she doesn’t want to be disturbed by work. Nevertheless, she promptly receives a professional WhatsApp message. She thinks about what to do and finds the new feature on the Internet, which she eventually installs. At the end of her user journey, she has two separate WhatsApp accounts on one mobile. She can mute her work account and finally enjoy her free, private weekend.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UdNZ9F2P7UgJoFrwhhWEXw.jpeg" /><figcaption>Case Study “How to separate communications on WhatApp” — User Journey Map: Ronja Braun</figcaption></figure><p>The User Journey made it clear to me, that it will be important to really separate the accounts. So this would have to be reflected in the design as well.</p><p><strong>Sitemap. </strong>The next step was to create a sitemap of the app. Because this showed me the points, where I could target the feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-9VNQNTJAycKsRh-CHVkw.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Sitemap Cutout</figcaption></figure><p><strong>Low-fi Wireframes and paper prototype test.</strong> With all this information, I created further, quite detailed low-fi wireframes, which already contained labels of the individual windows. This was necessary, because I wanted to do a paper prototype test in the next step. For this, I thought of three tasks that my test person should solve:</p><ol><li>Add a new account</li><li>Switch accounts</li><li>Open new message in other account</li></ol><p>The test showed me some links between pages, that I had missed or linked incorrectly, as well as some click paths that my test person wanted to go and I had forgotten. Also, the test subject did not recognize the added “create another account” button, which led me to rework the icon, I had developed up to that point. I recorded the test with a camera for subsequent analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpzn_q7NqsqNtkljiQ6nBQ.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Low-fi Wireframes 2nd Edition</figcaption></figure><p><strong>Mid-fi Wireframes. </strong>I then created mid-fi wireframes in figma, focusing mainly on the layout and structure. This also incorporated the findings from the paper prototype test. I first integrated the reworked icon for adding account, which you can see on the top right of the mid-fi wireframe “Settings”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*03n_xm8cf2mqP9lBYxQxbw.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Mid-fi Wireframes</figcaption></figure><p>As a last task on this day, I specified two user flows that I wanted to map with the high-fi prototype:</p><ol><li>User adds a second account</li><li>User switches between 2 accounts</li></ol><h3>DAY 4</h3><p><strong>High-fi prototype. </strong>On day 4, I recalled everything I had learned and analyzed about the design. Before I started creating the hi-fi prototype in figma. For this, I found a UI kit, that had been created by another <a href="https://www.figma.com/community/file/874576344344319149">figma user</a>. I was able to use this as a base so I didn’t have to rebuild everything from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSaLTnIt6ZUrZB4_jUcs1w.jpeg" /><figcaption>Case Study “How to separate communications on WhatApp” — High-fi Prototype</figcaption></figure><p>I integrated the new icon as well as a switch button that allows to switch between the two created accounts. This switch button is superordinate to the individual windows, so that not everything must appear twice in the app. Because this would lead to confusion (as already mentioned above). The switch button is once used elsewhere in the WhatsApp application (Calls — All/Missed Calls). Thus, it is a very own UI element of WhatsApp, which is used here in a different context.<br>I also integrated an icon that allows adding a new account under Settings. However, the user can just as easily create an additional account via the Settings menu item. He then goes through the usual process for creating a new account, just as he did when creating his first account. Here you can find my <a href="https://www.canva.com/design/DAEt0VGJrKc/2AohFcd5_Or8Rt7FcVvElQ/view?utm_content=DAEt0VGJrKc&amp;utm_campaign=designshare&amp;utm_medium=link&amp;utm_source=sharebutton">presentation</a>, including a video of the prototype. Or if you rather prefer to try it yourself click <a href="https://www.figma.com/proto/popzHdoCMf8AHucBx6Fbmf/Project-2-%7C-Add-a-Feature%3A-Vivienne?node-id=1603%3A1880&amp;scaling=scale-down&amp;page-id=1265%3A347&amp;starting-point-node-id=1595%3A1201">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpFpfv96RAJQdZfSqx7V1A.png" /><figcaption>Case Study “How to separate communications on WhatApp” — Account Switch &amp; Add Account Button</figcaption></figure><h3><strong>6. Outcomes &amp; Lessons / Conclusion</strong></h3><p>In summary, I can say, that Ronja now finally has the possibility to separate her WhatsApp communication into professional and private matters. Even if this is only represented in a hi-fi prototype so far and thus only looks as if it were real. Just a facade to dream for an imaginary person.</p><p>Next steps. In a next step it would be important to test the hi-fi prototype and iterate the whole process. Also it would have to be considered if the representation would still work when adding a third or fourth account.<br>It would probably also be appropriate in a real project to exchange ideas on technical feasibility at the latest. It is not unlikely that changes would result from this as well.</p><p><strong>Looking back. </strong>What fascinated me in this project was how powerful, effective and efficient the guerrilla research method is. With only a few questions, a small amount of interview partners and above all within a very short time, it is possible to gain essential insights. Here I would also like to refer to the following <a href="https://www.youtube.com/watch?v=0YL0xoSmyZI">video</a>.<br>In addition, I have learned to mirror as early as possible the first ideas and drafts with a potential, unbiased user. Every time, I’m surprised anew by the insights that emerge and how those insights catapult you to a completely unexpected place. Once you get into it, this approach is really extremely enjoyable. For this, it was very helpful for me to work with low-fi wireframes, which I could produce in a relatively short time. This way it is not so hard to throw the less good ideas overboard and continue working with a better idea.<br>Ultimately, within this project I was able to realize, how much I enjoy working with prototypes. For me it is a great pleasure to develop ideas on the basis of an analysis. Then to bring them into reality in a certain way with the help of prototypes, before testing them. Only to continue spinning out ideas and testing them again. What I also find great about it, is that in the end, even if you work alone on a project, it’s the result of many. Because the knowledge that you get from each test or interview person flows into the further development until the product is ready.<br>And so I hope that I will be able to experience many more of these project journeys. Here on Medium, I will report on them. Feel free to follow <a href="https://medium.com/@vfpopp">me</a>, so you don’t miss anything.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=260b5777654" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-how-to-separate-private-and-professional-on-whatsapp-ironhack-bootcamp-project-260b5777654">Case Study “How to separate private and professional on WhatsApp?” —  Ironhack Bootcamp Project</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study “How to get Sebastian to visit Museums” — Ironhack Bootcamp Project]]></title>
            <link>https://medium.com/design-bootcamp/case-study-how-to-get-sebastian-to-visit-museums-ironhack-bootcamp-project-22288c040e6a?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/22288c040e6a</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[prototyping]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Mon, 25 Oct 2021 05:49:26 GMT</pubDate>
            <atom:updated>2021-11-21T11:24:59.048Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study “How to get Sebastian to visit museums” — Ironhack Bootcamp Project</h3><h3>1. Overview</h3><p>In this article I like to introduce you to Sebastian Schulz, by telling you about my first project within the Ironhack Bootcamp, Week 1. This project was worked out in a team of four UX UI students, mostly remotely, besides the lectures, in 4 days.</p><p>The theme of “Culture &amp; Heritage” was a given one. The project brief described the ongoing crisis of visitor decline, that has plagued institutions since the 1970s. This decline has resulted in the basic problem, that heritage institutions are failing their mission to preserve and pass on the cultural heritage.</p><p>So the question, which came out of that was:</p><p><em>How can we help these institutions attract more people again, so that they can fulfill their mission in the 21st century?</em></p><p>The answer was to come in the form of an app. The goal of this project was to create a low-fi prototype. However, the goal of the project was also to go through the stages of the design thinking process and apply different methods, which are explained in more detail below.</p><p>Due to the wide field of Culture Heritage institutions, we decided to focus on museums. Museums were chosen, because we assumed that museums are an essential part of preserving and transmitting cultural heritage.</p><h3>2. Problem Statement</h3><p>For helping to bring more people back to museums, first we needed to understand the reasons for these circumstances. Through our research, we found various problems, which prevent people from visiting museums. For example, ticket prices that are perceived to be too high are a factor. But so are poorly presented exhibitions, unclear information or opening hours, that do not coincide with people’s free times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3LD-2N7i3PiRxjudA5wrWA.png" /><figcaption>Pain Points – Why not to visit Museums – Outcome Affinity Diagram</figcaption></figure><p>In the course of the project, we were able to organize the pain points and thus form categories. According to our research, problems that prevent visits can be divided into the following categories:</p><ul><li>Ticket</li><li>Purchase</li><li>Cost</li><li>Availability</li><li>Time</li><li>Planning</li><li>Better options</li><li>Museum experience</li></ul><p>The problem changed as the project progressed, as we tried to focus it more and more narrowly.</p><p>We eventually formulated the following <strong>problem statement</strong>:</p><blockquote><strong>“Spontaneous museum visitors need a way to get a clear overview on available exhibitions according to their needs, because it is hard for them to access the information about what is on offer.”</strong></blockquote><h3>3. Users</h3><p>For this kind of fictional project we created a user persona. And yes, you have red his name before: Let me introduce you to Sebastian Schulz. Sebastian is a user persona of the archetype: spontaneous museum goer. <br>He is 32 years old, single, lives in Berlin and works in customer service in a cooperation. He wants to go to a museum with his friends and needs clear and concise information about current exhibitions. He is frustrated, that it is time consuming to find the right information. Sebastian has irregular shifts and can therefore usually only plan his free time at short notice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RrnmqVlDQYrIjcHj" /><figcaption>User Persona Profile Sebastian Schulz</figcaption></figure><p>With regard to his museum visit, it is also important to him, that the ticket price is not too high and the museum is not too far away. If he decides to visit, he fears that the exhibition will be disappointing. Or he is afraid, that the place will be too crowded. Besides, it makes him sad when he can’t get any more available tickets.</p><h3>4. Scope &amp; Constraints</h3><p>Since the project was created within the Ironhack Bootcamp, there were some external constraints and specifications that influenced the development:</p><ol><li><strong>Time Frame</strong>: the project was started and finished within four days. This also meant, that we had to continue to work on some points within the process. Although in-depth research would have led to more profound results and probably would have changed the problem definition and solution approaches.</li><li><strong>Lectures</strong>: Lectures, which mostly took up the morning and early afternoon, accompanied the project and provided us with methods and also a structure of elaboration. That means, that the approach was more or less predefined.</li><li><strong>Research Results</strong>: Due to the time frame described above, the research results were also limited. We could conduct two interviews and got back 14 responses from the survey.</li></ol><h3>5. The process in 8 steps</h3><p>Basically my team and I tried to follow the steps of the design thinking process, using different methods. I would like to give you an insight in eight steps:</p><p><strong>1.Research:</strong> First, we tried to put ourselves in the user’s shoes. To do this, we conducted research and used both a quantitative and qualitative method. This resulted in a questionnaire with eight questions, which we shared with our environment and the Ironhack network. We also conducted two interviews with people we knew. To prepare the interviews, we used among others the Lean Survey Canvas.</p><p>The research allowed us to better understand, who the users are, what their needs are, and what their relationship is with museums. This was also to keep us from not satisfying our own needs, but to focus on the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oO3gTO4jBE74CDeWVhxfFw.png" /><figcaption>Survey Museums — Responses</figcaption></figure><p>2. <strong>Synthesizing:</strong> After the research, we analyzed these results and created an affinity diagram. Each group member wrote down all insights from the research on post-its. In a further step, we grouped these post-its and voted for a key problem, which we wanted to address more deeply. We focused on the essential pain point of planning a museum visit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BPxXKifbJGBwWrWpq_CDng.jpeg" /><figcaption>Affinity Diagram — Insights from Reasearch</figcaption></figure><p><strong>3. Focus the problem</strong>: To get a better grip on this obstacle of planning, we worked with the technique of asking “How might we” questions in the next step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eSG4Jv8LxduN4x75qwWPWA.png" /><figcaption>Results of the “How might we-Technique”</figcaption></figure><p><strong>4. More focus, more empathy:</strong> To focus even more on the user’s problem and emphasize even deeper, we then used the research results to create an empathy map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KfsEONGzCTYK6VvkXaj5Uw.png" /><figcaption>Empathy Map — Visiting Museums</figcaption></figure><p><strong>5. Define the problem:</strong> With all this information and outputs from the various methods, described above, we moved on to defining the problem.</p><p>The problem statement (see also 2. problem statement) was to provide the basis for us to develop a precise solution. Our problem statement referred to the spontaneous museum visitor, who has difficulty finding the right information for him.</p><p><strong>6.Ideate: </strong>To solve the problem, we needed as many ideas as possible in the next step. For this we used the Crazy 8 technique. This resulted in some very absurd ideas. Mine, for example, because I wanted to think as absurdly as possible in order to break out of the usual thought patterns. So I imagined a hot air balloon hovering over the city and presenting the information to short-tempered museum visitors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yaqeOgCXg4WZZm0LybP7Q.png" /><figcaption>Four results of my Crazy 8 pictures</figcaption></figure><p>This was fun, but less useful for coming up with an idea for the prototype, which would be created in the next step. Fortunately, some of my team members had more realistic ideas, that we could then use to further elaborate the prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-0vKAWXzpzAR9RXrJBHzw.png" /><figcaption>Chosen ideas resulted from the Crazy 8</figcaption></figure><p>So again, we voted on the ideas. Everyone had three votes to distribute. The result led us to decide, to work out a prototype from the three ideas:</p><ol><li>A map function, that shows the museums in the vicinity,</li><li>A needs filter and</li><li>A random button.</li></ol><p>From this step, the conversations and discussions also crystallized, how the app would work and, which flow the user would go through with the app.</p><p><strong>7. User journey map:</strong> To outline this interaction process between user and app in more detail, we created a user journey map of our persona Sebastian Schulz.</p><p>We described how Sebastian has the spontaneous idea to experience a cultural event, how he doesn’t know what exactly this could be. Then he uses the app, chooses from the options, sets the filters, specifies how much he can spend and how far he wants to go. Sebastian is happy. He gets the result, he is overwhelmed by, because of the abundance. He is a little hesitant. Then he discovers and clicks the random button and is absolutely happy and excited. But the answers don’t really satisfy him, so he clicks the random button again. This time he likes the suggestion. He decides to try it and is satisfied.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D3L8vuapZQnrcMFK31rTEQ.jpeg" /><figcaption>User Journey Map of Persona Sebastian Schulz — Planning for a museum visit</figcaption></figure><p><strong>8. Prototype:</strong> As a last step in the project, we created a prototype of the app, which we have given the working title “Easy Museum”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x66DJFpdti3HsYLtTmO9eQ.png" /><figcaption>Easy Museum low-fi Prototype</figcaption></figure><p>To begin with, the prototype of the “Easy Museum” app shows various museum offerings in the app. It is possible to filter according to today or tomorrow. Here, the user can either click directly on one of the offers or use the filter button.</p><p>Clicking on the filter button takes the user to the page, where various options can be selected and parameters can be chosen.</p><p>By clicking the “Find my Museum” button, he can initiate the search. A results page appears.</p><p>Here he can click the map button and gets to a map view, that shows the filtered museums in the vicinity.</p><p>If the user does not like the result, he always has the possibility to get a randomly selected museum by clicking on the random button. The principle is similar to chat roulette. App user and museum are randomly assigned to each other.</p><p>Finally, the user can also buy the ticket for the museum visit directly in the app.</p><h3>6. Lessons &amp; Next steps</h3><p>Since this was a bootcamp project, it ended with the creation of the prototype and the associated presentation. The prototype was not tested further.<br><strong>In conclusion</strong>, I would like to note a few points:</p><p><strong>Lessons, I learned</strong></p><ul><li>The problem statement has a really big impact on the solution outcome. This could be formulated more precisely next time.</li><li>It is easy to loose the focus on the user‘s problem. Our focus got blurred during the ideation phase. Like this, it was possible, to develop a random button, which actually does not help the user, who wants to quickly get accurate information. Even though we had considered this feature as an add-on. It just seemed too beautiful to us for not creating it.</li><li>Time management is key. Therefore it is important to take decision and stick to it and stay focused on the process.</li><li>Group work might be challenging in the beginning, because it needs some time and effort, getting everyone and everything under one hat. It is important to find away of gaining consensus.</li><li>Doing is better than thinking about the perfect solution, so just get started. Even more, if there is a tight schedule.</li></ul><p><strong>Next Steps</strong> might be:</p><ul><li>Although there was a tight time limit, we got quite a good insight and understanding of the user. Nevertheless, for a real project, it would probably be negligent to work with so little data. Therefore, it would be advisable to do more research. On the one hand to confirm, that the spontaneous museum visitor archetype exists and on the other hand to create more personas. Moreover to get more insights of the user‘s problem.</li><li>Furthermore, it would be appropriate to test the prototype and iterate the processes with additional research.</li><li>It would also be interesting to find stakeholders and organizations to collaborate with in this project.</li></ul><p>I am happy, that I could introduce Sebastian to you today. I will be happy about any comment or thought and hope you have enjoyed reading about my experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22288c040e6a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/case-study-how-to-get-sebastian-to-visit-museums-ironhack-bootcamp-project-22288c040e6a">Case Study “How to get Sebastian to visit Museums” — Ironhack Bootcamp Project</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework — Challenge 2: Wireframing]]></title>
            <link>https://medium.com/design-bootcamp/ironhacks-prework-challenge-2-wireframing-4e1b148973af?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e1b148973af</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Sat, 09 Oct 2021 11:10:35 GMT</pubDate>
            <atom:updated>2021-11-21T11:25:07.621Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack’s Prework — Challenge 2: Wireframing</h3><p>In the following article I would like to report about my second challenge within the Ironhack Prework course. <a href="https://medium.com/@vfpopp/ironhacks-prework-challenge-1-design-thinking-963d7313397b">Here</a> you can read more about my experiences during the first challenge.</p><p>Wireframing. In the second challenge I dealt with the topic of <a href="https://www.experienceux.co.uk/faqs/what-is-wireframing/">wireframing</a>. The goal of the task was to rebuild an existing, designed app to the low fidelity level of wireframes in order to understand and present the structure and functionality behind it.</p><p>Flow. In a first step, I chose an app to work with. In a second, I decided on a flow of the app that I wanted to look at in more detail. I chose the app <a href="https://www.paypal.com/de/home">PayPal</a> and the flow “Send money”. I chose this flow, because I use the app frequently and therefore know it well. In addition, it allows a clear differentiation from other flows of the app and thus facilitates the description of the process. In addition, a flow should be selected that covers a maximum of between 5 and 7 screens.</p><p>Screens. Next I created screenshots of the screens that the user goes through when he follows the user flow “Send money”. At first I created 7 screenshots, which I then rebuilt as wireframes in the <a href="https://www.figma.com/">figma</a> program. Later it became clear, that I had to reduce the number. Because I needed a screen twice, in different states, for the logical representation of the sequence. One with an unfilled input field, the other with a filled input field. Otherwise I would have had to exceed the maximum number of 7 screens. Therefore I excluded the optional task of the user “write message” within the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*mH7BsTxbCaFaixfvr_7wbA.png" /><figcaption>Ironhack’s Prework Challenge 2: Wireframing — Additional Screen “Write Message”</figcaption></figure><p>UI Inventory. Next, I analyzed the different elements I needed to create the wireframes. I found that there were fewer elements than I expected. Besides primary and secondary buttons, I would like to mention links, arrows, menu items, and search and input fields as examples. This resulted in the UI Inventory, which ensures the uniformity of the elements. I made use of an already existing Ironhack wireframe kit.</p><p>User Flow. After that, I arranged the completed wireframes in a row based on the user flow and numbered the screens from 1 to 6 according to their position in the flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BMrW96SHQjb2PwG3XLJk-A.png" /><figcaption>Ironhack’s Prework Challenge 2: Wireframing — Wireframes 1–3</figcaption></figure><p>Task Analysis. In preparation for creating the prototype, I then performed a task analysis. This describes which tasks a user has to perform to get to his goal. In this case, to send money (goal).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y322Lz_vMzEy-3VGgNP8Mg.png" /><figcaption>Ironhack’s Prework Challenge 2: Wireframing — Wireframes 4–6</figcaption></figure><p>The result of the analysis shows that <strong>5 tasks</strong> are necessary for the user to achieve the goal:</p><ol><li>Being on screen 1: <strong><em>The user clicks on one of the send money buttons</em></strong> → She will get to Screen 2.</li><li>On Screen 2: <strong><em>She clicks on one of the contacts</em></strong> → She will get to Screen 3.</li><li>On Screen 3: The currency is predefined and there is no need to tap into the money field, the cursor is already there: <strong><em>The user types in the amount of money</em> </strong>→ She will get to screen 4.</li><li>On Screen 4: The money amount is displayed. <strong><em>She clicks on next</em></strong><em>.</em> → She will get to screen 5.</li><li>On screen 5: All details of the transaction are displayed: Payee, Money Amount, Currency, PayPal Fee, Sum of Transaction, Kind of Transaction, Time of Transaction. <strong><em>She clicks on the send button</em></strong> to verify and trigger the transaction. → She will get to screen 6.</li><li>On screen 6: The transaction confirmation will be displayed. The aim of sending money is reached. Next tasks, after finishing the flow can be described as follows: <em>She clicks “Done”</em> to finish the action and get back to the start screen 1 <em>or she clicks “back to send”</em> to get to the pay screen (screen 2) to repeat the process.</li></ol><p>Prototypes. In a final step of the challenge, I created a <a href="https://www.figma.com/proto/SncjSwuebWQmEhaGN7E52a/Challenge-2:-Wireframing?node-id=6%3A11&amp;starting-point-node-id=6%3A11">clickable prototype</a> in figma. This allows to play through the flow “Send money”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*YygZeCuumog_Pda7KI9t2g.png" /><figcaption>Ironhack’s Prework Challenge 2: Wireframing — Prototype</figcaption></figure><p>For this purpose, I connected the relevant buttons, links and input fields following the logic. Also the forward and backward arrows as well as the cross to close are clickable. At the end of the process, both buttons can also be clicked. This takes the user to the start page or Screen 2, from where the action can be played through again from the beginning. The result is an endlessly clickable prototype. <a href="https://www.figma.com/proto/SncjSwuebWQmEhaGN7E52a/Challenge-2:-Wireframing?node-id=6%3A11&amp;starting-point-node-id=6%3A11">Here</a> you can try it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e1b148973af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhacks-prework-challenge-2-wireframing-4e1b148973af">Ironhack’s Prework — Challenge 2: Wireframing</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework — Challenge 1: Design Thinking]]></title>
            <link>https://medium.com/@vfpopp/ironhacks-prework-challenge-1-design-thinking-963d7313397b?source=rss-e2f39d11d62e------2</link>
            <guid isPermaLink="false">https://medium.com/p/963d7313397b</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <dc:creator><![CDATA[Vivienne Popp]]></dc:creator>
            <pubDate>Sat, 09 Oct 2021 10:55:19 GMT</pubDate>
            <atom:updated>2021-10-09T10:55:19.768Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack’s Prework — Challenge 1: Design Thinking</h3><p>This article reports on my experience taking my 1st challenge of the Ironhack Prework Course UX/UI Design. The Ironhack Prework Course covers the basics that will be deepened in the bootcamp, and includes several tasks and challenges. These need to be worked on and submitted before the start of the actual bootcamp.</p><p>Design Thinking was to be exemplified in Challenge 1. The app Citymapper served as an example here, which supports the mobility of users by offering various routes and mobility options after entering the starting point and destination. The problem is that the app does not offer the possibility to directly handle the booking process (e.g. ticket purchase). The resulting task was to develop a feature for the app, that prevents the user from having to switch to other channels for the transaction process. It was assumed that the user had already entered all his data (including payment data) into the app and that security problems (e.g. data protection) or other limitations could be disregarded.</p><p>Empathize. Following the design thinking process, the first step of the task was to empathize with the user. After an introspection, I prepared an interview guide, which I used to interview 5 people. The aim of the interviews was to find out the main weaknesses in the use of public transport, especially abroad. Essentially, 5 main weaknesses crystallized:</p><p>1. <strong>Orientation</strong>: it is difficult to find a possible or even the fastest connection when you are in an unknown place.</p><p><strong>2. Ticket:</strong> It is difficult to understand the ticket system (zones, time cards, etc.) and to choose the right ticket for the selected connection.</p><p><strong>3. Currency</strong>: It may be necessary to first exchange money into local currency before ticket purchase becomes possible. If it is possible to pay cashless, it may be more expensive due to transaction costs (e.g. VISA).</p><p><strong>4. Time</strong>: Both orientation and ticket purchase are time consuming.</p><p><strong>5. No Internet</strong>: The few, which wanted to use a digital app for purchasing a ticket abroad, couldn’t, because they had no internet connection.</p><p>Define. After I was able to put myself in the users’ shoes, the next step was to define the main problem to be solved: understanding which ticket is the right one and acquiring it, is complicated, confusing and time-consuming.</p><p>Ideate. To solve this problem, I proceeded in two steps:<br>Brainstorming to generate as many ideas as possible.<br>Selecting the most promising ideas to work on in the next step.</p><p>Prototype. From the three previously selected ideas, I created paper prototypes that mapped the user flow. As mentioned above, there were no limiting factors such as legal regulations. In the following section I present the prototypes, which are based on the UI of Citymapper. Here I assume that a search has already been triggered in the app and the corresponding possible connections are displayed. In each of the three prototypes shown below, the connection of the fictitious M4 is selected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*8wIGrrSOt8qNaA52" /><figcaption>Ironhack Prework — Challenge 1: Design Thinking — Paper Prototypes: Search Screens</figcaption></figure><p><strong>Prototype 1: Scan&amp;Go</strong><br>In the “Scan&amp;Go” prototype, a QR code icon appears on the search result screen. If this is clicked, a QR code scanner opens. This scanner can be used to scan the QR code that is displayed at the local station. This way, the app understands that the user is at the respective station and is now starting his transport. With location transmission enabled, the app knows where the user is. As soon as the location matches the previously entered destination, the ride is automatically ended and the user is logged out. Billing is also automated at the end of the trip, according to the distance traveled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*r5g1EpfV9JbNCWoK" /><figcaption>Ironhack Prework — Challenge 1: Design Thinking — Prototype 1 “Scan&amp;Go”</figcaption></figure><p><strong>Prototype 2: Toggle&amp;Consume</strong><br>In the “Toggle&amp;Cosume” prototype, a toggle appears in the search results interface. As soon as the user taps on it, a new screen opens, in which a toggle button is located. Here the user can switch the button to “On” as soon as he starts his ride. After the ride, the button switches back to “Off” and thus ends the ride. The user is billed according to the time spent. The payment unit per minute is communicated in advance, as are the approximate total costs. To prevent the user from forgetting to switch the slider to “Off,” the app reminds the user with a push message when the pre-calculated time for the selected ride has expired. This prevents the customer from incurring avoidable extra costs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*lyyv87o0XY6S4Zr4" /><figcaption>Ironhack Prework — Challenge 1: Design Thinking — Prototype 2 “Toggle&amp;Consume”</figcaption></figure><p><strong>Prototype 3: Shop Local&amp;Import</strong><br>Unlike the two prototypes before, this prototype does not avoid switching to another channel (another application), but it facilitates or harmonizes this process.<br>A Local App button is displayed on the search results screen. When clicked, the user is directed to the interface of the local public transport provider. Here, the possible tickets are already preselected. Another click confirms the purchase. The user data stored in the Citymapper app is used to process the payment. After the user has made the purchase, a purchase confirmation of the ticket is displayed. An arrow icon also allows him to return to the Citymapper app. The ticket is automatically imported into the Citymapper app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*_wOP9y1klVEAP2sP" /><figcaption>Ironhack Prework — Challenge 1: Design Thinking — Prototype 3 “Shop Local&amp;Import”</figcaption></figure><p>Test? At this point, I stopped following the path of the Design Thinking process, as testing was not part of the challenge. <br>Instead, I want to share three <strong>key learnings</strong>, I have experienced during the Challenge:</p><ol><li><strong>Empathize</strong>: It is incredibly important to start with the first step, empathize, to understand the problems and users. This is because it opens up perspectives and aspects that would otherwise remain completely closed. Because it is impossible to even remotely imagine them.</li><li><strong>Define</strong>: The exact definition was crucial in order to find an appropriate solution. It was important to formulate the definition as precisely as possible and to limit it, in order to be able to develop an equally precise solution.</li><li><strong>Paper Prototype</strong>: At first, it felt unusual to just sketch away — especially since it was the first time. However, once I started doing it, I understood the product and the processes better and better. Because I had to think through the individual process steps, the benefits and the goals of the product in detail, before it was possible to sketch something.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=963d7313397b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>