<?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 Anzhelika on Medium]]></title>
        <description><![CDATA[Stories by Anzhelika on Medium]]></description>
        <link>https://medium.com/@anzhelikazuboreva?source=rss-e1e9bea48e3f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*x1qFcl83qhJz4uSraV9YPw.jpeg</url>
            <title>Stories by Anzhelika on Medium</title>
            <link>https://medium.com/@anzhelikazuboreva?source=rss-e1e9bea48e3f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:45:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anzhelikazuboreva/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: Website Redesign I Catch Your Bug]]></title>
            <link>https://medium.com/@anzhelikazuboreva/case-study-website-redesign-i-catch-your-bug-4d7a125be76e?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d7a125be76e</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Tue, 10 Oct 2023 12:25:48 GMT</pubDate>
            <atom:updated>2023-10-10T12:36:37.918Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fpeez9P7E-QY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dpeez9P7E-QY&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f811da6b175e3b799aedc349124e69b6/href">https://medium.com/media/f811da6b175e3b799aedc349124e69b6/href</a></iframe><h3>Introduction</h3><p>The last Ironhack project was an extraordinary opportunity, as it allowed us to select a <strong>real-world company</strong> and engage with a genuine stakeholder. The decision to work with <strong>Catch-your-Bug</strong> was inspired by their compelling pitch during a pitch competition event and the values of the company.</p><p>Upon attending the event, I was drawn to Catch-your-Bug’s mission and products. However, I quickly noticed that their <strong>printed materials and website design could be enhanced to better serve their customers</strong>. This observation led me to approach the stakeholder with a proposal for collaboration.</p><p>The project’s objective was clear:</p><blockquote><strong>Redesign the website in order to adjust it to the consumer needs</strong> and conduct research in order to <strong>identify the key subjects that should be covered on the website</strong> in order to inform the users regarding the novel food and enhance their readiness to try the product.</blockquote><h3>Empathise</h3><p>This project made me fall in love with the UX part of the design process. Initially, I felt kind of lost as it was my first project where I worked alone. So <strong>my first thought was: “How do I start?”</strong> I mean, of course, during my previous projects, I already got the feeling for the UX/UI process. But before I was always working in collaboration with my classmates and <strong>suddenly it was only me, my imposter syndrome, and a deadline.</strong> So well how do you face the imposter syndrome? The strategy that works best for me is to <strong>find strong and substantial arguments and make thoughtful decisions</strong>. To achieve this the order of the day was first of all to do the research. A lot of research! And I enjoyed the process a lot.</p><p><strong><em>Secondary Research</em></strong></p><p>My journey began with extensive research. The first goal was to sell the product to myself and based on the gained conviction, try to find the best way to present the product to the customers. I delved into the world of insect-based food products, a topic surrounded by mixed opinions in the Western world. My <strong>secondary research encompassed nutritional benefits, sustainability, and psychological aversion.</strong> It was an interesting process as I learned some unexpected facts. So for example the lack of interest in the Western world toward the consumption of insects can be explained historically as traditional livestock offered multifaceted benefits with which the insects couldn’t compete.</p><p>I also discovered <strong>Rogers’ Diffusion of Innovation theory, identifying five crucial factors in product adoption:</strong></p><ul><li><strong><em>Relative Advantage:</em></strong> How much better the new innovation is perceived to be compared to existing alternatives?</li><li><strong><em>Compatibility: </em></strong>How well does the innovation align with the values and experiences of the target audience?</li><li><strong><em>Complexity:</em></strong> How difficult is the innovation perceived to be in terms of understanding and using it?</li><li><strong><em>Trialability:</em></strong> The extent to which the innovation can be experimented with or tested before committing to it.</li><li><strong><em>Observability:</em></strong> How easily can the outcomes or benefits of the innovation be seen and understood by the target audience</li></ul><p>This theory offered a foundation to my further approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_MTDUqdA66bc3lQzkBZ18A.png" /><figcaption>Rogers Diffusion of innovation theory</figcaption></figure><p><strong><em>Competitive Analysis</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rK0QtTP0m1KTfYaglJCKDA.png" /><figcaption>Similar Web Analysis</figcaption></figure><p>To gain insights and assess Catch-your-Bug’s position in the market, I conducted a Competitive Analysis. <strong>Using </strong><a href="https://secure.similarweb.com/account/login"><strong>Similar Web</strong></a><strong>, I compared 12 competitors</strong> based on metrics such as website traffic, bounce rates, and page views. I <strong>filtered the companies that had a better ranking</strong> than Catch-your-Bug, or the companies that showed a particular difference from the others compared. I filtered out eight companies and did a second round of comparison, and <strong>ended up with four finalists.</strong></p><p>The results of the Similar Web gave a first impression of the competitors and highlighted some important factors. For example, it showed that the <strong>website of Catch-your-Bug has one of the highest bounce rates</strong>. Another interesting aspect of the analysis was that the visitors of <a href="https://snackinsects.com/epages/a1912e88-af41-44f3-a576-4706265b1d46.sf/de_DE/?ObjectPath=/Shops/a1912e88-af41-44f3-a576-4706265b1d46/Categories/Produkte">snackinsects.com</a> spent an average of four minutes on the website, while the visitors of other competitors stayed on average not longer than two and half minutes on the respective websites. <strong>To understand the metrics and the reason behind the result of the Similar Web Analysis, I analyzed the companies further based on their design/layout, UX, content strategy, and conversion.</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEETqEWi_Jw8%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEETqEWi_Jw8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEETqEWi_Jw8%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a9b25f17d0d6e21c96e8dbbf5412b0f3/href">https://medium.com/media/a9b25f17d0d6e21c96e8dbbf5412b0f3/href</a></iframe><p>The Competitive Analysis led to a SWOT analysis, <strong>identifying opportunities such as enhancing content quality and visual design.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tG7yv7GKVur2mBO_OQUmEQ.png" /><figcaption>SWOT analysis</figcaption></figure><p><strong><em>Survey and User Interviews</em></strong></p><p>The Secondary Research was important and interesting. Thanks to the research I was convinced at 100% about the product. But now the most important thing was to discover how could I convince the users? The great thing about collaborating with a Stakeholder was that I had help with the surveys, and almost half of the participants were actually customers of Catch-your-Bug. 50 participants took the survey, but I was able to consider only <strong>34 participants</strong> for the evaluation, as those could at least imagine trying out this kind of product.</p><p>One aspect of the survey results caught in particular my attention. <strong>Taste was one of the primary concerns</strong> for trying the insect-based food product. At the same time, <strong>one of the main motivations</strong> for trying this kind of product was <strong>for 38% of participants the taste and culinary innovation</strong>. Further 56% of the participants mentioned, that they would love to see recipes and cooking tips on the website. The <strong>focus on taste is one of the important strategies</strong> that aligned also with some of the factors mentioned in Roger&#39;s theory which I talked about above.</p><p>Through the interviews with 5 users, I gained the insight that the user would like to <strong>know more about the farming and harvesting process</strong>, in order to be sure that it aligns with their values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JyPRtmv2TT8nVqes0hnZbQ.png" /></figure><p><strong><em>Stakeholder Interview</em></strong></p><p>A deep dive into the motivations and vision of Catch-your-Bug occurred during the Stakeholder Interview with Marco Schebesta, the founder of Catch-your-Bug. This interview revealed their mission, values, and goals and the competitive landscape they operate in. Catch-your-Bug <strong>aims to normalize insect-based food and values quality, sustainability, and consumer engagement</strong>. Transforming the website into a comprehensive knowledge platform was a key objective while maintaining its signature green and black color scheme.</p><p><strong><em>User Persona</em></strong></p><p>From these insights, I crafted the User Persona of the Eco-conscious Food Explorer. This persona values <strong>sustainability</strong>, seeks <strong>transparent information</strong> about certifications, safety, and farming practices, and <strong>desires a website that addresses concerns</strong>, showcases reviews, and <strong>offers inspiration for insect-based meals</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ydMktRHSQgL6pwxhnEIAIw.png" /><figcaption>User Persona</figcaption></figure><h3>Define</h3><p>As a UX/UI designer, my role is twofold: to <strong>enhance the company’s performance and to advocate for the user.</strong> Achieving a balance between these interests is crucial, though it’s not always straightforward due to varying business goals. To navigate this, I distilled insights into a clear problem statement, addressing both business and user needs.</p><p>So from the business perspective, I defined the following problem statement:</p><blockquote>Our insect-based food products were designed to offer an environment-friendly alternative for meat and enhance acceptance in society. We have observed that the <strong>lack of engaging information is not meeting users&#39; need</strong> to make an informed decision which is <strong>causing that customers don’t see an additional value in engaging with the product</strong> and overcoming their resistance toward our product.</blockquote><p>Based on the interviews and the survey, I was able to define the problem statement from the user&#39;s perspective as follows:</p><blockquote>Environmentally conscious individuals who want to reduce their carbon footprint need to find a way to <strong>be reassured that insect-based food products are a safe, healthy, and tasty solution</strong> that enhance their sustainable decisions because they have some concerns and initial hesitation due to societal stigmas and unfamiliarity with the product.</blockquote><p>From these problem statements, I formulated How-Might-We statements to identify design opportunities:</p><ul><li>HMW <strong>reassures the customers regarding the benefits and safety of the product?</strong></li><li>HMW <strong>engage the customer on the website</strong>?</li><li>HMW<strong> enhance the acceptance</strong> of insect-based food?</li></ul><p>With a clear problem definition, I presented my findings and insights to the stakeholder to ensure that we were on the same page.</p><p><strong><em>Site Map</em></strong></p><p>Before brainstorming, I created a site map of the current website. This helped identify existing content and potential improvements to the information architecture. It served as a valuable reference while generating ideas for the new website.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M7KRBmiNDr13kjPXKhefCw.png" /></figure><h3>Ideation</h3><p>Following the stakeholder meeting and strategy approval, the next step was to brainstorm solutions for the identified problem.</p><p><strong><em>Brainstorming</em></strong></p><p>I began by brainstorming ideas and sketching them out, aiming to prioritize and organize them into a new site map. To address users’ needs for information on product safety and the farming process, I devised features to meet these requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fuI9YL3UW89njuiw1BvnNA.png" /><figcaption>Sketches from the brainstorming process</figcaption></figure><p><strong><em>Restructure of Information Architecture</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDkIt1cOVRFhhjSigqmkMg.png" /><figcaption>New sitemap</figcaption></figure><ul><li>One of the initial challenges was the navigation bar, which contained too many sections. I <strong>reevaluated the inclusion of a “Home” section in the navigation bar</strong>. After consultations and research, I concluded that this choice should cater to the diverse target audience. Younger, tech-savvy users might rely on the logo to return home, while older business owners or employees might prefer a direct “Home” option. As the target audience of Catch-your-Bug included both of these users ultimately, I based my decision on competitor analysis, which revealed that competitors did not include “Home” in their navigation bars.</li><li>I also decided to <strong>relocate the “FAQs” section</strong>, as it’s less common to place it directly in the navigation bar. With the introduction of the “Bugs’ Academy,” a knowledge base for insect-based food products, the need to highlight FAQs diminished.</li><li>Considering the importance of taste and user guidelines for product integration into diets, I <strong>separated the recipe section from the blog</strong> where it was previously located.</li><li>The “B2B” section in the navigation bar also caught my attention. After discussing this with the stakeholder, we agreed that the <strong>primary focus should be on potential product consumers</strong>. Information for business owners should have a less prominent position.</li><li>To meet user needs identified through surveys and interviews, I created a <strong>“From Farm to Table” section</strong>. This section would <strong>provide a transparent view of the product’s journey,</strong> including farming and harvesting processes, social proof, and safety certifications. Additionally, under the submenu “Events and Classes,” users could find details about upcoming events and cooking classes, expanding their product knowledge and usage ideas, which is ultimately the final stage of the product journey.</li></ul><h3>Wireframe and Prototype</h3><p>After gaining stakeholder approval for my concepts, I advanced to the wireframing and prototyping phase. I began with a Lo-Fi prototype, which I tested with users. Based on their feedback, I refined the Lo-Fi version into a Mid-Fi prototype, with a focus on two key improvements:</p><ul><li><strong><em>Recipe Visibility:</em></strong> I enhanced the visibility of recipes to capture users’ attention immediately. This aligns with Roger’s Diffusion Theory, addressing the complexity and trialability factors. <strong>By showcasing product implementation possibilities upfront, we aim to reduce the initial aversion</strong> users might have towards insect-based food products. Further, this approach follows Stephen Covey’s principle of <strong>“beginning with the end in mind”,</strong> helping users visualize the end result, and increasing this way readiness to engage with the product.</li><li><strong><em>Product Reviews</em>:</strong> To address user needs, I made product reviews more prominent. <strong>Highlighting reviews contributes to building trust and credibility</strong>, an essential aspect in encouraging user engagement with the product.</li></ul><p>These design enhancements aim to reduce bias against the product, stimulate curiosity, and increase users’ readiness to try insect-based food products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5jRZA9Vl_U9GtEAJIXtWPw.png" /><figcaption>Mid-Fi Wireframes</figcaption></figure><h3>Visual Design</h3><p>With stakeholder approval of the Mid-Fi prototype and user feedback incorporated, I proceeded to define the visual elements and the UI design.</p><p><strong><em>Mood board and brand attributes</em></strong></p><p>To find the best way to present the product, I first identified the values and defined the brand attributes:</p><ul><li><strong><em>High Quality</em></strong>: Emphasizing product quality through regular checks and microbiological analysis.</li><li><strong><em>Sustainability</em></strong>: Promoting the sustainability of insect-based food.</li><li><strong><em>Educational and Informative</em></strong>: Aiming to educate consumers about insect-based food.</li><li><strong><em>Future-Oriented</em></strong>: Positioning insect-based food as a solution to future challenges.</li><li><strong><em>Consumer-Centric</em></strong>: Focusing on addressing consumers’ concerns by providing high-quality, sensorially tested products. Further, the comany aims to create attractive and interesting insect-based food products that offer added value to customers.</li></ul><p>I created a mood board that should convey these feelings and sought feedback from five users to ensure it transmitted the intended mood aligned with these attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bnjmfk5wLBAAYzOD3GK_4g.png" /><figcaption>Mood board</figcaption></figure><p><strong><em>Colors</em></strong></p><p>From the mood board, I <strong>extracted colors and used </strong><a href="https://coolors.co/"><strong>Coolors</strong></a><strong>,</strong> a color palette generator, <strong>to refine the color palette</strong>. To define the colors I did some desk research and used ChatGPT as a brainstorming buddy. My <strong>final choice was influenced by color psychology, stakeholder preferences, and user feedback.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hn3i5UNC5unrRkAzpfFu3w.png" /><figcaption>Color palette</figcaption></figure><p><strong><em>Typography</em></strong></p><p>Catch-your-Bug’s existing typography, Raleway for headings, and Helvetica for body text were a suitable choice. The elegance of Raleway matches the value of the high-quality and the cleanliness and minimalism of Helvetica go along well with the informative and customer-centric character of the company. It’s a good combination for businesses and online stores as it transmits a modern yet clean appearance. However, <strong>considering the innovative nature of the product, I explored alternative typefaces,</strong> in order to find<strong> typography which were less mainstream as Helvetica</strong> is a quite popular and overused typeface nowadays and it seems to be quite standard choice. Alone on <a href="https://fontsinuse.com/typefaces/44/helvetica">Fonts in Use</a>, an online archive of typography, you can find 1106 recordings of websites that use Helvetica compared to 19 recordings for Raleway.</p><p>First of all, I analyzed the competitor’s typography:</p><ul><li>3 of 9 were using Nunito Sans</li><li>2 of 9 were using Helvetica</li><li>4 of 9 were using uncommon typefaces</li></ul><p>In order to stand out from the other competitors I started to look out for other <strong>typefaces that would match the brand attributes transmit the essence of the product </strong>and at the same time at least differentiate from the typefaces used by the main competitors.</p><p>I came up with six different typeface combinations and after discussing them with the stakeholder, we agreed on the combination of these three typefaces:</p><ul><li><strong><em>Caveat — as an accent typeface</em></strong><em>:</em> a handwritten font can help to <strong>evoke a sense of authenticity and naturalness</strong> and in this case enhance the feeling of sustainability and eco-friendliness. Further, it might <strong>help to stand out catch attention</strong>, and make the product feel more <strong>approachable.</strong></li><li><strong><em>Montserrat — for heading</em></strong><em>:</em> it exudes <strong>professionalism and readability</strong> and <strong>conveys a sense of high quality and modernity.</strong></li><li><strong><em>Lato — for the body</em></strong><em>: </em>is a <strong>friendly, approachable, and easy-to-read</strong> typeface, that matches the consumer-centric orientation of the brand</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*oBIgUVvv-nx_sd-WMDDS_A.png" /><figcaption>New typography</figcaption></figure><p><strong><em>Background pattern</em></strong></p><p>Incorporating Marco’s <strong>wish for a trailing element resembling the product package design</strong>, I introduced a subtle background pattern. These lines, <strong>resembling wood or leaf veins, enhance the connection to nature</strong> and sustainability while providing a <strong>less overpowering visual element</strong> than just using the color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*6p0CIoTLMMiZBm8Ao1wuiQ.png" /><figcaption>Background pattern</figcaption></figure><h3>High-Fidelity Prototype</h3><p>Below you can find a YouTube video, so you can have an impression of my final result:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FBEDsOEOIZrw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DBEDsOEOIZrw&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3ec3e9dd4e3a4cac3e68d555acb8cbf/href">https://medium.com/media/e3ec3e9dd4e3a4cac3e68d555acb8cbf/href</a></iframe><h3>Next Steps</h3><p>This project was quite challenging as this time I was working alone and I had only six weeks to finish the project (weekly amount approx. 14 hours). If I would continue working on the project, my further steps would be:</p><ul><li><strong><em>Testing, testing, testing!!!</em></strong><em> </em>Continual testing is essential. <strong>Gathering more user feedback would help identify areas for improvement </strong>and refine the design.</li><li><strong><em>Complete Website Design:</em></strong> Due to time constraints, only the primary user journey (the happy path) was designed. To enhance the overall user experience, I would extend the design to cover the entire website.</li><li><strong><em>Mobile Version Design:</em> </strong>A critical next step would be to create a mobile-responsive version of the website to ensure a seamless experience for users on various devices.</li></ul><h3>Key Take Aways</h3><ul><li><strong><em>Document everything!</em></strong><em> </em>During the case study, I realized that the website had undergone some modifications, such as changes to the navbar. Regrettably, I didn’t capture screenshots of the previous version. This highlights the <strong>importance of thorough documentation in UX/UI projects to track and preserve the evolution of design decisions.</strong> In future projects, I will prioritize comprehensive documentation to ensure a clear record of design iterations and changes over time.</li><li><strong>Time Management and flexibility: </strong>The Design Thinking Approach is invaluable for product quality, but <strong>as a junior, sometimes you might feel hesitant to deviate from the rules</strong> due to a fear of making mistakes. <strong>Balancing project time constraints and real-life challenges required flexibility</strong>. There were instances when stakeholders and interviewees were less flexible than needed, forcing me to prioritize and antedate (where possible) some further steps.</li></ul><blockquote><strong>Know the rules well, so you can break them effectively. — Dalai Lama</strong></blockquote><p>Thank you for your attention. I hope you found this project interesting and if you have any feedback, I would highly appreciate it!</p><p>If you would like to l<strong>earn more about the company</strong>, you can check their website <a href="https://www.catch-your-bug.com/"><strong>here</strong></a><strong>.</strong></p><p>If you want to learn more about me and want to connect you can check out <a href="https://www.linkedin.com/in/anzhelikazuboreva"><strong>my LinkedIn</strong></a><strong> profile</strong>. I’m looking forward to hear from you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d7a125be76e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Wellness App | Care Compass]]></title>
            <link>https://medium.com/@anzhelikazuboreva/case-study-wellness-app-care-compass-20719213bd20?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/20719213bd20</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Sun, 30 Jul 2023 22:09:02 GMT</pubDate>
            <atom:updated>2023-07-30T22:09:02.343Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-CRngT3hNXxMZuxVNYd8Xg.png" /><figcaption>Photo by <a href="https://unsplash.com/@artcoastdesign?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dmitry Mashkin</a> on <a href="https://unsplash.com/photos/BLu9Bx0nADM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>Our fourth project during the UX/UI Bootcamp at Ironhack was a <strong>five-week project</strong> focused on <strong>designing a Wellness App</strong>. Our team consisted of Genieve Crump, <a href="https://medium.com/u/4c80b1ce3c61">Sergey Milyuk</a>, <a href="https://medium.com/u/e5a9b9df67e4">Dirk Gruhne</a>. Our challenge was to create a <strong>Hi-Fi prototype</strong> that would motivate individuals to take action toward their mental, physical, and emotional well-being. To meet the project’s requirements, our must-have features included:</p><ol><li><strong>User profile and goal setup:</strong> A seamless process for users to create profiles and set personalized wellness goals tailored to their needs.</li><li><strong>Goal tracking:</strong> An intuitive system to monitor and track progress towards wellness objectives, providing motivation and accountability.</li><li><strong>Personal data control:</strong> Users had the ability to edit, share, or delete their personal data, ensuring transparency and compliance with GDPR regulations.</li><li><strong>Information about data usage (UX writing):</strong> Clear and concise communication regarding the app’s data usage, presented in a user-friendly manner through UX writing.</li><li><strong>Feedback system: </strong>Thoughtful inclusion of feedback mechanisms such as empty states and error notifications to enhance the user experience and address potential issues.</li></ol><p>While there is no shortage of health apps in the market, our team decided to <strong>tackle a less mainstream aspect of wellness such as dementia</strong>. Recognizing the growing impact of dementia on individuals and their families, we aimed to design a tool that would address this crucial aspect of personal well-being.</p><p>Throughout the project, we diligently followed a <strong>user-centric approach</strong>, conducting <strong>extensive research</strong> to gain insights into the needs, challenges, and motivations of subject matter experts and individuals whose family members or friends were affected by dementia. Our research methods encompassed user interviews, surveys, and interviews with SMEs, ensuring a comprehensive understanding of our target audience.</p><p>By leveraging design thinking, user research, and iterative methods, our <strong>aim was to anticipate user needs and create a product that significantly enhances the lives of individuals providing non-professional care to dementia patients.</strong></p><h3>Empathise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*i72wM4rffqXeuzm9-KdcgA.png" /><figcaption><strong>8 Pilars Model</strong> <a href="https://www.alzscot.org/sites/default/files/styles/uncropped_medium/public/images/0002/1753/8_Pillars_Model-01.png?itok=V1PfySZq">https://www.alzscot.org/sites/default/files/styles/uncropped_medium/public/images/0002/1753/8_Pillars_Model-01.png?itok=V1PfySZq</a></figcaption></figure><p><strong><em>Secondary Research</em></strong></p><p>Our secondary research aimed to familiarize ourselves with dementia as an illness and understand how existing digital solutions address the gaps in the market. We explored the <strong>“8 Pillars Model of Community Support”,</strong> which focuses on providing proper support to individuals with dementia and their caregivers. This model <strong>emphasizes the importance of personalized, person-centered services</strong> and recognizes the significant impact of various factors on the health and well-being of both the person with dementia and their caregiver.</p><p><strong><em>Competitive Analysis</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KrfcOkJIvp9-JJdhv-7avg.png" /><figcaption>Competitive Analysis</figcaption></figure><p>In our competitive analysis, we discovered that the <strong>market for digital solutions related to dementia is still relatively unexplored</strong>. Most existing apps primarily catered to caregivers, offering <strong>informational resources about the illness as their main function</strong>. However, we observed that <strong>90% of the apps lacked an appealing user interface (UI) and, in some cases, had poor user experience (UX)</strong>, making it difficult for users to navigate and find the right information. Additionally, <strong>none of the apps provided annotation or family communication options</strong>, which would enable users to collect and share information with other informal caregivers. Furthermore, while there were brain training apps available, they did not explicitly target dementia patients or tailor their activities to their unique needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d8B28bGAETKXwAEKyidmQA.png" /><figcaption>Feature Comparison Analysis</figcaption></figure><p><strong><em>Appropriate device choice</em></strong></p><p>Research conducted by the Good Things Foundation <strong>highlighted the benefits of tablets and smartphones for people with dementia and their caregivers</strong>. These devices can enhance the quality of life by providing practical support, social connections, and opportunities for relaxation and entertainment. <strong>Tablets offer larger screens</strong> for reading and watching videos, <strong>while smartphones are more portable for communication on the go</strong>. The <strong>choice between a tablet and a smartphone depends on individual preferences and needs</strong>, considering the specific requirements and preferences of the person with dementia and their caregivers. As our users would use the app on some occasions together with the patient, we decided that in terms of accessibility, it would be better to use the tablet as it offers a larger screen</p><p><strong><em>Survey and Interview</em></strong></p><p>To gather further insights, we conducted a <strong>survey with 70 participants</strong>. Key findings from the survey were the following:</p><ol><li><strong>62,3% of patients with dementia live alone</strong> and 21,7% with family</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sLCa4JFV231nGs3UuroDAg.png" /><figcaption>Living situation of dementia patients</figcaption></figure><p>2. <strong>Top 3 activities</strong> which were perceived to have the most positive effects on the patients are: <strong>outside activities, looking at photos, and reminiscing activities</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQPn-aqHdsFAk_auTI-iOQ.png" /><figcaption>Activities with beneficial effect</figcaption></figure><p>3. Participants expressed a <strong>desire for more information on effective communication with the patient, managing difficult behaviors, and ensuring patient safety.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nsMH92satO2J1qSRNXD8Pg.png" /><figcaption>Required information regarding dementia</figcaption></figure><p>4. 33 participants expressed a <strong>need for assistance with activities</strong>, 27 desired a <strong>community function</strong>, and 24 wanted <strong>educational content</strong> in the app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cggCZHtZ8V849LbZUj-rjA.png" /><figcaption>Required assistance while taking care of dementia patient</figcaption></figure><p>We further deepened our understanding through <strong>qualitative interviews with seven participants</strong>, all of whom had a family member diagnosed with dementia. Three of the participants also had professional experience with dementia patients. The insights from these interviews were collected and organized using an affinity diagram, which revealed the <strong>importance of patient safety, the organization of leisure time, and stimulating activities to enhance both physical and cognitive abilities</strong>.</p><p><strong><em>User Persona</em></strong></p><p>Based on our findings we then created a user persona. Our user persona’s <strong>pain points include a lack of knowledge about dementia, concerns about patient safety, and the challenge of balancing various responsibilities while providing care for the patient.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*siWJOTOCDfG60yGg4qR44w.png" /><figcaption>User Persona</figcaption></figure><h3>Define</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dnMh7enbrpceqGYjr3dtLA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/ja/@laurynasm?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Laurynas Mereckas</a> on <a href="https://unsplash.com/photos/1TL8AoEDj_c?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Our research helped us identify a problem, and we defined the problem statements as follows:</p><blockquote><strong>Friends and family</strong> who help (on some level) to <strong>care for someone with dementia </strong>need to find a way to better <strong>manage the needs of the patient while preserving their independence</strong> because they <strong>don’t feel like they have the right tools or knowledge to properly help or care for their loved ones.</strong></blockquote><p>Once our problem statement was clear, we proceeded to <strong>identify the opportunities</strong> that our solution could address. We asked ourselves the following questions:</p><ol><li>How could we <strong>stimulate the cognitive and physical exercise</strong> of dementia patients?</li><li>How could we provide our users with an <strong>efficient method to address the challenging behavior</strong> of the patient?</li><li>How can we create a tool that <strong>preserves the patient’s independence</strong> for as long as possible?</li><li>How can we enable users to <strong>access all the information</strong> <strong>they need to provide efficient care</strong> for the patient?</li></ol><h3>Ideation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rP5Td69Zn-HZ7IrYTpl87Q.png" /><figcaption>Worst idea</figcaption></figure><p>We decided to kick off our brainstorming session with the <strong>“Worst Idea” exercise</strong>, aiming to alleviate the pressure and liberate our creativity. By generating some outlandish concepts, we warmed up and prepared ourselves for the actual brainstorming phase. Subsequently, we <strong>transitioned these unusual ideas into potentially valuable ones</strong>. This practice led us to some good ideas, such as setting up a <strong>survey to identify user pain points.</strong></p><p>Next, we proceeded with the “Crazy 8&#39;s” exercise, designed to generate eight ideas within eight minutes. After a dot-voting process and discussions, we <strong>prioritized the ideas using the MoSCoW method.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EUUR98YY7mbH2XmKOOQMKg.png" /><figcaption>Crazy 8&#39;s</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KvG_vIHHFyc3hrsOFDM-XQ.png" /><figcaption>MoSCoW</figcaption></figure><p>During an extensive team discussion, we emphasized the <strong>importance of our solution providing genuine value</strong>, rather than being just another informative resource in the market. After multiple brainstorming and iteration rounds, we reached the conclusion that our solution should be an app for a tablet that offers a <strong>personalized care plan for caretakers.</strong></p><p>Often, news of an illness catches both the patient and their family off guard, leaving them <strong>feeling unprepared and lacking knowledge</strong> on the topic. Although there are plenty of helpful resources aiming to offer support, the <strong>abundance of information can be overwhelming</strong>, particularly during the early stages when emotions run high, and mental clarity is lacking. Based on the <strong>insights from the initial survey which highlight users’ needs and preferences</strong>, our plan aims to offer a <strong>step-by-step guide </strong>with recommended resources to read, to-do lists, and activities that can be performed together with the patient.</p><h3>Wireframing and Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WP2uRLItNapQeVwX4ueahw.png" /></figure><p>Once we had defined our solution, <strong>each team member proposed a Lo-Fi prototype</strong>. Subsequently, we engaged in discussions and conducted dot-voting to <strong>select the screens that best addressed the persona’s pain points and our problem statement.</strong> After achieving consensus, we proceeded to create a Mid-Fi Prototype and <strong>tested it with users</strong>. The Usability Testing provided valuable insights on how to iterate and improve our product. We <strong>implemented this feedback</strong> before advancing to the Hi-Fi prototype.</p><h3>Visual Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gSFlq2oYXP-g-T3sACRAVQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@tiago?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tiago Muraro</a> on <a href="https://unsplash.com/photos/pwMds57bapI?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Brand Attributes</strong></p><p>Before developing the Hi-Fi Prototype, our team embarked on a thoughtful journey to <strong>define the visual direction of our solution</strong>. We carefully considered the desired perception and emotions we want our users to experience. Our goal was to create <strong>a solution that exudes guidance and support</strong>, assisting users in facing the illness of their loved ones. Additionally, we <strong>aim for the app to be informative and empowering</strong>, providing users with a concrete plan and reducing fear of mistakes. Lastly, the <strong>app should be practical</strong>, offering easily implementable tips and strategies for daily routines.</p><p><strong>Mood Board</strong></p><p>To translate our brand attributes into visual elements, we created a mood board that encapsulates the feelings we wanted our users to experience. This <strong>mood board served as a foundation for defining our app’s visual design.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/787/1*lPxHBf_UknPpeMBfTGPlYg.png" /><figcaption>Moodboard</figcaption></figure><p>Based on the mood board, we <strong>extracted suitable colors</strong> and used the <strong>Coolors Tool to generate various color palettes</strong>. Through team discussions and dot-voting, we narrowed down our choices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92zaNIKZZLSZMmuRcuQU2Q.png" /><figcaption>Color choices</figcaption></figure><p>To validate our color selections, we applied them to some screens and <strong>conducted A/B testing. </strong>User feedback was instrumental in iterating and finalizing our color palette. <strong>Blue was chosen for its association with calmness, reliability, trust, and intelligence</strong>, perfectly reflecting the supportive and approachable atmosphere we wanted to create. The <strong>mix of light and dark tonalities complements each other, improving aesthetics and user experience by enhancing accessibility and readability</strong>. Additionally, <strong>yellow was used for its warmth and positivity</strong>, with potential <strong>benefits for logical thinking and learning improvement.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*GBtoVHoMD99p-WdOOEZoRA.png" /><figcaption>Color Palette</figcaption></figure><p>For the app’s typography, we opted for <strong>Roboto</strong> due to its <strong>excellent legibility,</strong> crucial for older users with age-related vision changes. Its <strong>neutral appearance</strong> makes it easy to recognize characters, particularly suited for seniors. Given the learning section with abundant text-based resources in our app, Roboto seemed like the perfect choice, <strong>balancing content density with reading comfort.</strong></p><h3>High-Fidelity Prototype</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCmJ1FT2u2KI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCmJ1FT2u2KI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCmJ1FT2u2KI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c481c816f8d6ed2a9a1d1c1b2c7d7f06/href">https://medium.com/media/c481c816f8d6ed2a9a1d1c1b2c7d7f06/href</a></iframe><h3>Next Steps</h3><p>If we were to continue working on this app, the next steps would involve <strong>conducting more usability testing</strong> to gather valuable feedback and further enhance our design. We would proceed with <strong>designing the remaining app screens and content</strong>. Additionally, we plan to <strong>adapt the design for mobile devices,</strong> focusing on the carer functionalities. Our future aspirations include <strong>incorporating community support features</strong> and the ability to <strong>set up multiple profiles</strong>, facilitating information sharing among caregivers.</p><h3>Key Take Aways</h3><ul><li>This project proved the immense <strong>value of collaboration within a diverse and versatile team</strong>. Each team member brought unique backgrounds and perspectives to the table, which greatly contributed to the effectiveness of our collaboration. Through constructive discussions, we were able to generate innovative ideas that catered to different viewpoints.</li><li>In addition, the project underscored the s<strong>ignificance of Usability Testing and user feedback</strong>. Some team members had personal experiences with relatives affected by dementia, underscoring the importance of data-driven decision-making to avoid biases.</li><li>Personally, this project taught me <strong>valuable lessons in time management and self-care.</strong> The challenging nature of the project, combined with time constraints and a less mainstream topic, demanded extensive desk research before diving into the design thinking process. This experience highlighted the need to prioritize my well-being and <strong>avoid obsessing over pixel-perfection when it isn’t essential</strong>, enabling me to distribute my energy more efficiently.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20719213bd20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: E-commerce | Bellé Cycles]]></title>
            <link>https://medium.com/@anzhelikazuboreva/case-study-e-commerce-bell%C3%A9-cycles-2fa5e3a93dbd?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fa5e3a93dbd</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[e-commerce-business]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Mon, 10 Apr 2023 16:26:34 GMT</pubDate>
            <atom:updated>2024-03-15T11:25:11.598Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EVtgBoylJ9d-8vO9VK8faQ.png" /></figure><h3>Introduction</h3><p>In today’s digital world, <strong>e-commerce</strong> has become an <strong>essential part of every business</strong>. A good e-commerce website not only <strong>increases the online presence</strong> of a brand but also <strong>enhances its credibility</strong> and customer trust.</p><p>As a Ironhack UX/UI student, together with my team of three members (<a href="https://medium.com/u/f925a821cb48">GabyTatters</a>, Gonzalo Perez and myself) we had the opportunity to <strong>design a responsive website for a local business</strong> (<strong><em>Belle Cycles</em></strong>) over a period of <strong>five weeks</strong> (weekly time amount aprox. 14 hours).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qkBOOl9CgwzBR4efw7ZGyw.png" /><figcaption><a href="https://www.instagram.com/p/Bdwo4VdHa0I/">https://www.instagram.com/p/Bdwo4VdHa0I/</a></figcaption></figure><p>Belle Cycles<strong> </strong>is<strong><em> </em></strong>a local business that produces <strong>custom-made bicycles</strong>. Enrico Belle has been building frames for 20 years and started its brand “Belle” ten years ago. Currently, the brand sells its bicycles through direct communication via email or telephone. Belle’s online presence is limited to Facebook and Instagram, which accounts for a significant part of its sales.</p><p>The objective was to <strong>increase Belle’s online presence and improve the brand’s credibility</strong> by designing an e-commerce website.</p><h3>Empathise</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ic4MdhI5VkFlaUPZZSOAcg.jpeg" /><figcaption><a href="https://www.shutterstock.com/image-photo/boy-street-ground-knee-injury-screaming-256379848">https://www.shutterstock.com/image-photo/boy-street-ground-knee-injury-screaming-256379848</a></figcaption></figure><p>The first step was to <strong>gain insights into the pain points and expectations</strong> of the users and stakeholders. We conducted S<strong>takeholder Interviews</strong> to understand the <strong>brand’s values, objectives, and target audience</strong>. We also conducted <strong>User Interviews</strong> to <strong>identify their needs and expectations</strong> from a bike seller’s website or app. In addition, we conducted a <strong>Competitive Analysis</strong> to get familiar with the market.</p><p><strong><em>Stakeholder Interview</em></strong></p><p>During our stakeholder interview with Enrico Belle, we learned that <strong>Belle’s objective is to produce completely personalized bicycles that are unique </strong>to each individual. They uphold <strong>honesty and simplicity</strong> as their core brand values and strive to <strong>provide the highest quality of service</strong> while being <strong>mindful of their impact on the planet</strong>.</p><p>Belle’s target audience is <strong>middle to upper-middle-class individuals in their 40s and 50s</strong>, whom they aim to provide with a <strong>feeling of exclusivity and personalization</strong>. Belle’s main competitors are worldwide craftsmen builders like <em>Speedvagen</em> and <em>Stelbel</em>, as well as local competitors like <em>Mattia Legor</em> and <em>Rizzo</em> in Barcelona. Belle acknowledged that each builder has its own style, and customers can choose the style that best suits their preferences.</p><p>Their <strong>strengths</strong> lie in <strong>the service and guidance</strong> they offer, as well as the <strong>variety of tubes</strong> they use. The waiting time to receive a custom-made bicycle can take almost a year, but they believe it adds extra value to the product, and their <strong>goal is to satisfy all their customer’s bicycle needs</strong>.</p><p><strong><em>User Interviews</em></strong></p><p>During our User Interviews, we identified several key aspects that are important for the success of the UX/UI design for a bike seller’s website or app. Although we had difficulty finding users within Belle’s specific target group of middle to upper-middle-class individuals in their 40s and 50s, we still <strong>interviewed bike enthusiasts</strong> in general to understand their needs and expectations.</p><p>Firstly, users expect <strong>an efficient and intuitive communication interface</strong> that allows them to <strong>contact the seller quickly and easily</strong> to discuss details about the bike.</p><p>Secondly, users want to know all the available options and features for the bike, such as frame height, technical equipment, and color options. They expect <strong>a visually engaging and informative product page that highlights key specifications</strong>.</p><p>Thirdly, users want a direct and personalized contact with the seller <strong>to feel valued and well-informed about their purchase.</strong> They expect friendly and professional customer service that guides them through the buying process and answers their questions.</p><p>Finally, customers want <strong>a sense of control and customization over their purchase</strong>. They expect <strong>a user-friendly and interactive interface</strong> that allows them to build their dream bike by selecting each component.</p><p><strong><em>Competitive Analysis</em></strong></p><p>After conducting Stakeholder and User Interviews to gain insights, we proceeded with a <strong>Competitive Analysis</strong> of Belle’s market. We compared Belle to <em>Lego, Rizzo, Sturdy</em>, and <em>Festka</em>, focusing on i<strong>dentifying Belle’s strengths and areas for improvement</strong>.</p><p>The Feature Comparison Analysis revealed that <strong>Belle offers essential features</strong> such as 100% custom geometry, different frame types, customized paint jobs, and a two-year warranty. However, it also showed that Belle <strong>lacked some key features</strong> that could enhance the company’s value proposition and provide a competitive advantage. For example, all of Belle’s competitors had a fully responsive website, whereas Belle <strong>only had a landing page</strong>. Further Sturdy offered additionally an online shop for components, and both Sturdy and Festka <strong>offered complete bikes</strong>, however those couldn’t be customized by the user.</p><p>During the Competitive Analysis, we identified an <strong>opportunity</strong> for Belle <strong>to develop a Bike Builder</strong>, which none of the considered competitors offered. A Bike Builder is a <strong>user-centered tool</strong> that allows customers to participate in the bike-building process by selecting different options and specifications.</p><p><strong><em>User Persona and User Journy Map</em></strong></p><p>With insights from the interviews and Competitive Analysis, we created a User Persona. I present you the design enthusiast Diedrik:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xV1Vhx8fhJOCvjzx0MMV3w.png" /></figure><p>Diedrik’s <strong>pain points</strong> include feeling <strong>confused and disappointed when not finding the information needed</strong>, a <strong>lack of transparency and customer care</strong> regarding an expensive product, and <strong>difficulty contacting artisans </strong>who don’t have a strong online presence.</p><p>We then created a User Journey Map (UJM) to identify <strong>How-Might-We </strong>(HMW) opportunities. The HMWs we prioritized were:</p><ul><li>How might we help Diedrik <strong>visualize his dream bike</strong>?</li><li>How might we help Diedrik <strong>get relevant information</strong> about the product?</li><li>How might we help Diedrik <strong>reach an artisan</strong>?</li><li>How might we help Diedrik <strong>feel more confident about buying this expensive product</strong>?</li></ul><h3>Define</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*iizHSdzDVBHqrQyA9sxUDA.png" /><figcaption><a href="https://www.instagram.com/p/Bl7Q7qyhjLJ/?img_index=1">https://www.instagram.com/p/Bl7Q7qyhjLJ/?img_index=1</a></figcaption></figure><p>After gaining sufficient insights, we defined <strong>two problem statements</strong>: one to analyze the business’s effect on the user, and another focused solely on the user.</p><p>For the <strong>business-focused statement</strong>, we observed that Belle Bike <strong>lacked a proper platform to display its product</strong>, which <strong>negatively impacted the trustability of the brand</strong>, leading consumers to seek other artisans.</p><p>For the <strong>user-focused statement</strong>, we defined the problem as the need for cyclist enthusiasts with purchasing power to <strong>access detailed information</strong> about customised bikes and <strong>optimise their decision</strong>, given the significant investment involved.</p><h3>Ideation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*huMZMJw7rTg-aiUAqE70eQ.png" /><figcaption><a href="https://www.instagram.com/p/BRBOP-aAicF/?img_index=1">https://www.instagram.com/p/BRBOP-aAicF/?img_index=1</a></figcaption></figure><p>To generate ideas, we used the <strong>Crazy 8’s</strong> technique. The scope of Crazy 8’s is to generate eight ideas in eight minutes. After one minute pass you should pass to the next idea and so on. It’s great way to reduce the attachment to one particular idea and enhance the objectivity, which will help to continue generating ideas.</p><p>We then prioritized the ideas using the <strong>MoSCoW technique</strong> (Must-have, Should-have, Could-have, and Won’t-have) to identify <strong>essential features</strong>. We agreed that our solution definitely <strong>must have a bike builder and an easy way to contact the seller</strong>. Further, it <strong>should have and a feature to learn more about the artisan and their work</strong>. A <strong>could have</strong> for the solution would be <strong>a blog</strong>, which would <strong>enhance brand visibility and trustworthiness </strong>and a <strong>music playlis</strong>t and a <strong>feature to listen to music</strong>, as Belle mentioned that music contributes to the essence of his workshop. Firstly we considered to make a profile for the customers where they would be able to track the state of their order, however, we decided against a personal profile or login section.</p><p><strong><em>Information Architecture</em></strong></p><p>Next step was to ensure, a well-organized and user-friendly website optimised for search engines. We <strong>created a Site Map to establish a clear structure for the website’s content</strong>. Below you can find our Site Map.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3hCaGr_vETbCL4x7oJwAnA.png" /></figure><p><strong><em>Happy Path</em></strong></p><p>Due to time constraints, the scope of the project was to focus only on the <strong>Happy Path</strong> (the primary user goal of building and customizing a bike). Therefore, our Happy Path focused on the B<strong>ike Builder.</strong></p><h3>Wireframing and Prototype</h3><p>After establishing our Happy Path, features, and information structure, we created <strong>Low-fidelity and Mid-fidelity Wireframes</strong>. An extract from our Mid-fi Wireframes can be found below, showing the <strong>Bike Builder</strong> in different steps that <strong>enable users to select various options and see their customizations come to life on the screen</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9MIhSGVFmZQ_iZtxcwQQ6Q.png" /><figcaption>Mid-Fi Wireframes</figcaption></figure><p>Finally, we <strong>prototyped the Mid-fi Wireframes</strong> and put them to the test. We asked 5 Users to <strong>test the prototype</strong> and based on the feedback we <strong>iterated on our Prototype</strong>.</p><h3>Visual Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*jTOwIs8Afs_pt_Z4OhQUJw.png" /><figcaption><a href="https://www.instagram.com/bellecycles/">https://www.instagram.com/bellecycles/</a></figcaption></figure><h4><strong><em>Brand Attributes</em></strong></h4><p>During the stakeholder interview, Belle shared the company’s core values. Belle is a custom bicycle manufacturer that has carved a niche for itself by creating personalized, high-quality bicycles that cater to the individual needs of its customers. The brand is known for its <strong>authenticity, simplicity, reliability, sophistication,</strong> and emphasis on <strong>craftsmanship</strong>.</p><p>Belle’s <strong>authenticity</strong> is reflected in its <strong>custom-made</strong> bicycles that are <strong>tailored</strong> to fit the individual needs of each customer. This authenticity is also reflected in the brand’s <strong>honesty and simplicity</strong>, as Belle is not interested excessively in marketing itself or overcharging customers. The honesty is also reflected in the mindfulness of their impact on the planet.</p><p>Belle values <strong>simplicity</strong> and aims to offer a <strong>personalized and easily accessible service</strong>. The brand also prides itself on being <strong>approachable and available</strong> to customers who are curious about the brand.</p><p>Belle’s <strong>reliability</strong> is focused on the <strong>quality</strong> and <strong>product durability</strong>. The brand is committed to delivering a <strong>high-quality, personalized service</strong> to its customers.</p><p>Belle’s <strong>sophisticated</strong> image is evident in its <strong>target audience</strong> of middle to upper-middle-class customers in their 40s and 50s who value high-quality, personalized products. This <strong>focus on exclusivity</strong> and attention to detail contributes to the brand’s sophisticated image.</p><p>Belle’s <strong>emphasis on craftsmanship</strong> is evident in the <strong>attention to detail</strong> and <strong>personalized service</strong> it offers.</p><p>Overall, Belle’s brand attributes reflect its commitment to delivering a personalized, <strong>high-quality, and authentic</strong> service that values <strong>craftsmanship, simplicity, and exclusivity</strong>.</p><h4><strong><em>Moodboard</em></strong></h4><p>After defining the brand attributes we worked on the Moodboard and tested it on our classmates and based on the feedback iterated on it and after that put it to test with our friends. Below you can see the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*CfrDHWDFiOILjpo2Nve1jg.png" /><figcaption>Moodboard</figcaption></figure><p>We <strong>extracted the colors</strong> from the Moodboard:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*O2l5bsBsSbltNNxAroArZg.png" /><figcaption>extracted colors</figcaption></figure><p>And using the tool on Coolors.co we tried to experiment and <strong>create several color palettes</strong> and in the end the whole team agreed on the following one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*oGHPweVzQzp8D-f0DgtSSQ.png" /><figcaption>Color Palette</figcaption></figure><p>For the Typography we choose <strong>Theinhardt</strong> as it has <strong>clean, geometric shapes and sharp angles</strong>, which gives a <strong>modern and minimalist look</strong> and perfectly aligns with our brand attributes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/1*cA2yVL6_DXo8dYM2YYjouw.png" /><figcaption>Typography</figcaption></figure><h4>A and B Testing</h4><p>After having our visual inspiration from the Moodboard and after experimenting with our color palette we tested two screens on our classmates. We got a lot of useful feedback regarding our progress bar and the footer. And also on the color. Almost 90% of the group agreed that the rich black from version A would suit our company more, as it has a mechanical touch and it wouldn’t interfere with colourful pictures, so we would have more freedom of choice regarding the pictures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*l8JQn3tAILwl4PStYAWfmg.png" /><figcaption>Verson A (left) and Version B (right)</figcaption></figure><h3>High-Fidelity Prototype</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuCiEc0uZHEQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuCiEc0uZHEQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuCiEc0uZHEQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dae492e21f06c8a625334d66a5453266/href">https://medium.com/media/dae492e21f06c8a625334d66a5453266/href</a></iframe><p>On the A and B testing we got the feedback that our progress bar looked more like a navbar and didn’t communicate the feeling of progress, instead conveyed a sense of separate process. So for our Hi-Fi we added the radio button which would change state, depending on with step you are at right now. We also added the title for each step step. We tried to keep the <strong>design simple and minimalistic</strong> as it’s one of the main core values of Belle and at the same time simplicity <strong>enhance the usability</strong>. In terms of usability we also created <strong>several options to highlight the state of selection</strong>. So there are five different states:</p><ol><li>Unselected state</li><li>Hovered: the title is more highlighted (the weight change from thin to medium)</li><li>Not selected: the visibility is reduced to 50%</li><li>Not selected hovered: title is highlighted as in the hovered version and the visibility is at 70%</li><li>Selected: visibility is at 100% and title size is 15px instead of 14px and weight change from light to medium.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cWjzQpXBykGIJ-PAcmN6xw.png" /><figcaption>Components</figcaption></figure><p>The same approach was used for the navbar, where additionally also the radio button was added. At this point a shout-out to the components, which also permitted us to make our color bar dynamic and a huge shout-out to Nicky and Leo, our wonderful Ironhack teachers, who totally nailed the explanation of the components.</p><p>Considering the <strong>user’s need for transparency</strong> we placed the price where it would be immediately jump into eyes and <strong>at every step the price will vary</strong>, so the user has always overview of the price.</p><p>Another <strong>pain point</strong> was to enable the user to <strong>access to the information</strong>. This was a little more tricky to handle as we also wanted to keep the website minimalistic. We resolved this problem by putting the <strong>information icon</strong> and when the user will hover it, he will get <strong>an overlay with all the relevant information</strong> regarding the component which he is choosing in that moment.</p><h3>Testing and my iteration suggestions</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Feisvxxr7O1c%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Deisvxxr7O1c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Feisvxxr7O1c%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6b809e28c99aca3093ac48adad4d76b2/href">https://medium.com/media/6b809e28c99aca3093ac48adad4d76b2/href</a></iframe><p>At the end of each project we have to make a presentation and after presenting our solution we got further feedback from our classmates. So the pain points were:</p><ol><li><strong>progress bar was still not clear</strong> enough and didn’t convey the feeling of progress</li></ol><p>2. some people mentioned that they would like <strong>more transparency regarding the price</strong></p><p>3. <strong>the information icon was confusing</strong> and didn’t convey the right message which was intended by our team</p><p>With this <strong>feedback from our last presentation</strong> and with the some <strong>objections I had in earlier stage of the project</strong>, which didn’t found approval in the team though, I kept <strong>iterating on our prototype</strong>. So following changes where made:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-BQ7k40FZ8680qfE4qF5w.png" /><figcaption>Controll Bar</figcaption></figure><ol><li><strong>A toolbar</strong> below the product picture for further navigation as: <strong>zoom-in and zoom-out, 3D view and full screen modus</strong>. This features were presented at the Low-Fi stage. But my team didn’t agreed on them as they considered important to keep the website minimalistic as it was one of the main objectives of Belle. In the User Interview which I conducted I had observation from my User on this options. Also at the first User Testing I put also this option to test with 3 different users and got a positive feedback from them. None of them raised the objection that it would reduce the minimalistic touch of the website. As I had not the necessary bike pictures for the 3D views, I had to cheat a little on this. I consider that this option should be where as they don’t damage the User Flow and <strong>instead increase the usability and give even a bigger sense of control to the user.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pD7a9Vx2aRm6LVAY87mhgA.png" /><figcaption>Price and information details</figcaption></figure><p><strong>2.</strong> Based on the feedback from our class I added the<strong> price to every item</strong> in order to <strong>enhance the transpasency</strong></p><p><strong>3.</strong> <strong>Information access</strong>: As the<strong> information button</strong> in the last version was confusing and remained mostly unperceived. I placed it now close to every item. It <strong>reduce the minimalistic touch</strong> a little, but at the same time it <strong>increase the user flow and the usability</strong> of the website, as now the user doesn’t have to select the item in order to access the information, but now he can review this information for every item even if right now he has selected a different item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*CJYvs0BVhrahHVNCZTTHPQ.png" /><figcaption>Chatbot</figcaption></figure><p><strong>4.</strong> <strong>Chatbot</strong>: at this point I would like to bring in mind two of the pain points of our user. One of them was the <strong>lack of transparency and customer care</strong> regarding an expensive product and <strong>difficulty contacting artisans.</strong> In terms of minimalism my team didn&#39;t approve on the chat bot. The argument was that the user can contact the artisan through the contact form as we have already a Contact Us section on the website. Three of five of the users who we interviewed <strong>highlighted the importance of the customer service and customer care</strong>. Also one of the HMW statements was</p><blockquote>HMW help Diedrik feel more self-assured to buy this expensive product?</blockquote><p>In terms of reacting to this observations a chatbot would be a great idea as it can provide <strong>quick and efficient customer service</strong>, assist in building a personalized bike, and <strong>create a bond with the customer</strong>. This can lead to a seamless and enjoyable user experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2o2rjOExVhTRudbgjR7nw.png" /><figcaption>Progress Bar</figcaption></figure><p><strong>5.</strong> I <strong>refined the progress bar</strong> based on the feedback in class.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2FxtWmG9LP88twS5zD_cTQ.png" /></figure><p><strong>6. </strong>In class we had a lot of positive feedback on our Bike Builder and some even compared it to a computer game. This brought me to the idea to <strong>enhance even more the game feeling for the color bar</strong>. So instead of the classical <strong>color slider</strong> I used a slider which has a bike inside and the bike change color based on the color where you currently are at. <strong>This optimisation goes also along with the values and brand attributes like craftsmanship, uniqueness, and authenticity</strong>.</p><p>7. <strong>Colors</strong>: Although it’s true that black and white are usually associated with the simplicity and minimalism, and although the class agreed on the black and white version, because it also convey a mechanical touch associated with bikes. I couldn’t get rid of the feeling that we haven’t experimented enough with the colors. <strong>Belle is not just about simplicity and bikes. Belle is also about authenticity, reliability and style! </strong>Black and white is quite predictable, it can be found anywhere. So I kept <strong>iterating on the color palette</strong> and playing around with colors. Again at this point a huge shout-out to the components otherwise I would have spent a lot of time on this… After testing different pallets with some Users in the end I mixed two color palettes together and ended up with following color palette</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8l-wXzjIUGQarvb0ZBKikQ.png" /></figure><p>The color palette consist mainly of <strong>neutral colors</strong> so it still maintain the <strong>minimalistic touch</strong> and should work well with colourful pictures. This colors also represent the brand attributes. So the <strong>green color</strong> can be <strong>assosiated with authenticity </strong>as it evoke a sense of genuineness and honesty. The <strong>white</strong> color create a sense of calmness and clarity and <strong>represent simplicity</strong>. The <strong>blue</strong> is often <strong>associated with reliability</strong>, as it is a stable and trustworthy color. Colors that are <strong>associated with sophistication include for example deep shades of purple</strong> and create a sense of elegance and refinement. Additional reason which would motivate this color palette is that Belle emphasized the <strong>importance of mindfulness towards the impact on the planet</strong> as one of the brand’s core values. The <strong>color palette reflects nature</strong>, and since cycling is an outdoor activity, these colors complement the brand well. So all in all this color palette works well for the brand, is still <strong>simple and minimalistic and convey the sense of uniqueness to the website.</strong></p><h3>Key Take Aways</h3><blockquote>Fail fast, iterate quickly — Reid Hoffman</blockquote><p><strong>Testing is a crucial aspect</strong> of design, and the more opportunities you have to test, the better. This way, you can iterate and refine your design.</p><blockquote>The key to effective UX design is communication. Whether you’re working with clients, developers, or other designers, clear communication is essential for success. — Laura Klein</blockquote><p>Once again, I had a demonstration of how important <strong>clear and structured communication</strong> is! In our team, we had some problems with communication, and this made us lose some time. Moreover, for user testing, it’s always essential to communicate clearly and structure the communication to get relevant and useful feedback quickly.</p><blockquote>UI without UX is like a car with a beautiful exterior and no engine. It may look good, but it won’t get you anywhere. — Zoe Hong</blockquote><p>I agree that the UI part is quite fun, but without proper UX, it will drastically reduce your chance of creating a successful product. As a design freshmen, it’s easy to get carried away, but the process should be done step by step. In our team, the typography and colors didn’t change from Lo-Fi to Hi-Fi, and I guess this already tells a lot. Whereas even after the Hi-Fi presentation, there was a lot of room for improvement for different elements, such as price, progress bar, and information. These things should be taken care of before it comes to the visual design. A breathtaking information icon won’t get you anywhere if it’s not placed in the right place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fa5e3a93dbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: “Wicked Problems — Immigration”]]></title>
            <link>https://medium.com/@anzhelikazuboreva/case-study-wicked-problems-immigration-748ba48dea97?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/748ba48dea97</guid>
            <category><![CDATA[immigration]]></category>
            <category><![CDATA[designthikning]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[wicked-problem]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Sun, 05 Mar 2023 16:34:30 GMT</pubDate>
            <atom:updated>2023-07-30T22:14:30.333Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Case Study: Wicked Problem </strong>| <strong>Immigration</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xgw1xNxKEMKtJIth24HxLA.png" /><figcaption>Photo by <a href="https://unsplash.com/@villxsmil?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Luis Villasmil</a> on <a href="https://unsplash.com/photos/mlVbMbxfWI4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3><strong>Introduction</strong></h3><p>Our first project at Ironhack’s UX/UI Bootcamp aimed to <strong>familiarize us with the Design Thinking</strong> process and teach us how to <strong>address</strong> <strong>wicked problems </strong>and find solutions to them. A wicked problem is a social or cultural problem with a complex and interconnected nature, making it difficult to solve.</p><p>Working in teams, we had <strong>three weeks</strong> (part-time program) to complete the project. My team consisted of <a href="https://medium.com/u/6d9e30c9d1ef">Beatriz Muriel</a>, <a href="https://medium.com/u/e5a9b9df67e4">Dirk Gruhne</a>, <a href="https://medium.com/u/39c0a89ad4a">David Acuña</a>, and myself, and we chose to work on the wicked <strong>problem of immigration</strong>. Our briefing was:</p><blockquote>“How Might We help migrants find information, complete tasks, and get their paperwork done to start their life in a new city.”</blockquote><p>The <strong>scope of the project</strong> was to deliver a <strong>Lo-fi Wireframe and a Lo-fi Prototype</strong> of our solution.</p><h3><strong>Empathize</strong></h3><p>With our briefing in hand, we began the Design Thinking process by conducting <strong>Secondary Research</strong> to clarify our ideas, dive deeper into the topic, and gain some initial insights. As we had to tackle such a vast problem, we agreed to focus our research on only two countries, Germany and Spain. We chose this two countries due to time constraints and the fact that our team members were based there.</p><p>Our Secondary Research provided initial clarification on the topic and helped us identify the <strong>top ten problems immigrants face</strong>. However, the topic was still too broad, and we needed to narrow our focus further to stay within the scope of the project. Therefore, before conducting User Interviews, we decided to exclude refugees and asylum seekers from our target group. The reason for this was practical: it would be difficult to find users from those groups to interview.</p><p>We interviewed six users, and this was probably <strong>the most insightful moment of the project for me!</strong> It was at this point that I truly realized what it means that “<em>You have to fall in love with the problem and not the solution.</em>” Since we received our briefing, my mind kept working on possible ways to solve the problem, especially since I have immigrated twice in my life and I understand the struggle. So I was thinking about how we could make the information more accessible and how we could organize it in the best way? <strong>However</strong>, nobody from the participants mentioned these struggles in particular. We even iterated our interview guide after a dry run with our classmate to make the questions clearer, in order to collect more information about the pain points concerning the bureaucratic duties. But still, it turned out that our target group had different pain points.</p><blockquote>“The thing which enhanced then my integration was friendship. Thanks to it, I started to feel like I belong to this place, and it helped me to open up and start to integrate myself.” — User 5</blockquote><p>The <strong>Affinity Diagram</strong> revealed that <strong>users’ pain points were socialization, language barriers, and cultural integration. </strong>This aspects<strong> </strong>we also encountered during our Secondary Research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WaQP0f_Se8lZMzZSumxR6A.png" /><figcaption><a href="https://ankommenapp.de/APP/EN/Startseite/startseite-node.html">https://ankommenapp.de/APP/EN/Startseite/startseite-node.html</a></figcaption></figure><p>To summarize the insights and patterns we found by then, we created a <strong>User Persona, </strong>which would reflect the user needs and later help us make product decisions based on the Persona’s goals and the frustrations.</p><blockquote>“If you design for everyone, you delight no one. That is the recipe for a mediocre product.” — Alan Cooper</blockquote><p>Allow me to introduce you Stefan, our curious newbie in Spain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x5MZkDOCy6QWQYEGgqaJCA.png" /></figure><h3>Define</h3><p>Once that our Persona took shape, we were able to proceed smoothly to the Defining stage, where we <strong>structured all the insights and defined the problem</strong>. First, we wanted to gain a deeper understanding of users’ current experience in accomplishing a particular goal/task, so we created a <strong>User Journey Map. </strong>Below you can see Stefan’s current experience:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcgDMrmfBdg3HMsnHGn7ew.png" /></figure><p>By creating the User Journey Map, we were able to frame the <strong>How-Might-We Statements </strong>and<strong> </strong>spot design opportunities.</p><p>Our User Journey Map led us to the How-Might-We Statements, which were all about <strong>helping the user connect with people and find support and orientation in a new place</strong>. We defined our final <strong>Problem Statement </strong>as following:</p><blockquote>Expats who have just moved to Spain need to find a way to create a valuable network because, at the beginning of their stay, they struggle to get support from friends and acquaintances.</blockquote><h3>Ideate</h3><p>Once that we had our Problem Statement, which was focused on the social aspect of immigration, and with the Brief in mind, which was focused more on the administrative aspect of immigration, we could start ideating and try to find a balance between these two things.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OF2h1b6OU2FVm-PJSjIHIA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@markfb?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mark Fletcher-Brown</a> on <a href="https://unsplash.com/photos/nN5L5GXKFz8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>To make the Brainstorming process more structured and less chaotic, we decided to start with the <strong>Crazy 8’s method. </strong>Every team member had eight minutes to create eight ideas, switching to the next idea after one minute has passed. This method is <strong>great for generating a lot of ideas without getting too attached</strong> to any particular idea. After each of us had our ideas, we explained them to each other and then dot-voted on the ideas we loved the most. Once this was done, we started brainstorming, discussing those ideas, and extending and mixing them.</p><p>In the end, we agreed that the best way we could help our persona create a valuable network and find support would be by creating a <strong>social network that connects expats and locals over language and skills </strong>(both intended as a service). To motivate users to engage in the long term, we decided to introduce a reward system using tokens. On this platform, <strong>users can search for specific services</strong>, such as help with tax declaration, or, like in our persona’s case, someone who would accompany him to the hospital and help with translation. Users can <strong>access the offered services by paying with tokens earned by offering services themselves or by offering their own services in return</strong>. For example, if the person who accompanied Stefan to the hospital is interested in learning German, then Stefan could offer his German skills in return.</p><h3>Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9RR6r8MgrLSaz0_Gh3aWyg.png" /><figcaption>Prototype: <a href="https://youtube.com/shorts/LpRPeiULt-Y?feature=share">https://youtube.com/shorts/LpRPeiULt-Y?feature=share</a></figcaption></figure><p>After that we had our definitive idea, we could finally create a <strong>tangible representation</strong> of it. We had to deliver <strong>a Lo-fi Figma Prototype of just one User Flow</strong>, not the whole application. With our team, we started by discussing which flow we wanted to work on and which screens we needed for this flow. We also discussed the main features that were non-negotiable. Once we agreed on these things, we decided to use the <strong>Divide and Conquer strategy</strong> again. We thought it would be the most effective way if each of us designed the screens on our own, <strong>saving time and avoiding long discussions</strong>. Afterward, we could analyze and discuss our designs.. To reduce the workload, we split the screens in two parts, with two of us working on the first part and the other two on the second part.</p><p>After we had our sketches, we compared them and discussed with our team which features we wanted to keep, where the buttons made the most sense, etc. Once we were all on the same page, we could start with the <strong>Wireframes.</strong> Here, we again split the screens into just two groups, so we could practice more with Figma and create more screens. Once everyone had their wireframe screens, we compared and discussed them to choose the design we loved the most. After that, we worked on making all the screens coherent. Once we had our final wireframes, we could <strong>prototype the screens</strong>.</p><h3>Next Steps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o3MBRr2wGclPs_AN-AkoEg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@evan__bray?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Evan Dennis</a> on <a href="https://unsplash.com/photos/i--IN3cvEjg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>After creating a Lo-fi Prototype, our work was done and we had to present our project in class. Since this project was for academic purposes, <strong>we were constrained by time limits</strong>. If we had more time, we would first <strong>test our Prototype</strong> and gather feedback from users. If necessary, we would then iterate our product. We also would also like to <strong>broaden our interview scope</strong> and <strong>include additional User Personas</strong>. Furthermore, we would expand the app’s functionalities and <strong>include other features</strong> such as short language lessons and tutorials.</p><h3>Outcomes &amp; Lessons</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dN2MUQtajPN5SWW7jldP0Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kylejglenn?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kyle Glenn</a> on <a href="https://unsplash.com/photos/-f8ssjFhD1k?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As mentioned earlier, this was an <strong>academic project</strong>, so the app was not developed or launched in the end. However, this experience was full of insights, and I learned a lot during the process.</p><p>I have always considered empathy to be my strength, and it surely is. During this project, however, I learned what empathy truly means and how to think in a user-oriented way instead of having a problem-solving mentality. During this project, we also learned about various tools such as Affinity Diagram, User Persona, Crazy 8s, etc and how to use them.</p><p>Besides the obvious things that you learn when you attend an UX/UI Bootcamp, I personally learned how to work in online teams. At the beginning, I was skeptical that it could actually work that well, but this project showed me that it is possible and can be just as enjoyable as working offline. I really enjoyed working in my team as the teamwork was full of empathy, support, and respect. Each of us had space, opportunity, and the willingness to contribute to the project, which was really precious.</p><p>Furthermore, the project was a great exercise to improve time management skills as it was quite challenging due to the time restriction and the need to balance the Bootcamp with work and the everyday life.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=748ba48dea97" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Anzhelika Zuboreva_Challenge 1 | Design Thinking]]></title>
            <link>https://medium.com/@anzhelikazuboreva/ironhacks-prework-anzhelika-zuboreva-challenge-1-design-thinking-4c7a2771780f?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c7a2771780f</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[cittymapper]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Sun, 22 Jan 2023 19:46:26 GMT</pubDate>
            <atom:updated>2023-01-22T20:09:52.494Z</atom:updated>
            <content:encoded><![CDATA[<p><em>After the theoretical introduction to the subject, the first challenge consisted in using the steps of the Design Thinking approach for creating a new feature for the app Citymapper.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqWsvqOHmPDun5OuuK8LgA.jpeg" /><figcaption>Citymapper Press Kit by Gilbert Edam</figcaption></figure><p><strong>Citymapper</strong></p><p>Citymapper is a London based company which first launched a navigation and mapping app in 2011. Citymapper aim to improve the urban mobility by offering the users an accurate route planning with real-time data to help people to navigate in a complex public transportation networks. The app has 50m+ users and is available in all major cities around the world. Beside the public transportation, Citymapper covers also private modes of transportation such as cabs, car-sharing, scooters, walking, etc. Further the app provides information on the cost, duration and carbon footprint of each trip. This information helps users to make an informed decisions about their way of locomotion.</p><p><strong>The Problem and the scope of the project</strong></p><p>Although Citymapper already solves a lot of issues which a person has to face while using the public transports to get from point A to point B and it provides more services compared to the competition. For example unlike Google it focuses on several options and compares the benefits and disadvantages of each option (like price, time and carbon footprint). Another benefit is that Citymapper offers a comprehensive step-by-step guide for the route including which entrance or exit to use and it even alert the user when they are at the current stop in order to avoid that they miss it. In spite of it all there is still one pain point for many users: the different amount of public transport tickets the users have to purchase.</p><p>The assignment for this challenge was to create a feature for the app which will solve this problem of having to purchase different public transport tickets by different channels.</p><p>The framework conditions for this task were:</p><ul><li>that users already have all their information on the app, they will neither need to log in nor enter any data when paying/checking-out;</li><li>For now, forget about security issues and other limitations. Focus on finding a quick and user-friendly solution;</li><li>Be creative!</li></ul><h3>The Design Thinking Approach</h3><p><strong>1. Empathize</strong></p><p>In order to understand better the users and to identify their priorities, I first conducted an interview with people in my environment. Before the interview I had to clarify my mind and to determine who my audience is and what problem am I solving. For the interview I chose five individuals who use public transportation regularly or occasionally. The important aspect to me were to find people who also had experience of using the public transportation abroad as often is leads to different kind of behaviour as the people who use the public transport on the everyday basis, they usually use the season tickets for the place where they are based.</p><p><strong>2. Define</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*71LmRyE-VHx2IyGlpi1lKw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lisanto_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lisanto 李奕良</a> on <a href="https://unsplash.com/photos/pT4gB7T6tog?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I was surprised to discover that each of interviewed persons preferred to buy tickets online and no one had concerns about running low on battery or similar issues. This way they could avoid queues, save time and pay cashless. Further they had another thing in common, everyone preferred to use possibly a website instead of downloading several apps (this is a resounding YES for the new Citymapper feature! ;) ) .</p><p>All of the participants also agreed on the same thing - the process of buying a ticket online/through an app should be: easy, fast (without unnecessary log-in details, etc.), comfortable (good UX/UI design) and offer several payment options.</p><p>There are few common issues which the participants encountered: the protracted process of buying a ticket and problems with internet connection. Sometimes the process of buying a ticket through an app took to much time and before the process could be completed in the meanwhile the transport already departed and in the end the ticket couldn’t be acquired anymore or during the process of purchasing a ticket there were some problem with the connection, so in the end there were some error and it wasn’t clear if the ticket was purchased or not.</p><p>So the main priority is to create something fast and simple.</p><p><strong>3. Ideate</strong></p><p>The next step was to brainstorm and to come up with as many ideas as possible which addressed and solved the problem. I was thinking about several options like simply adding an option to purchase the tickets through the app or integrating the daysaver ticket to it.</p><p>For my final solution I got the inspiration from one of my participants, who told me that in Switzerland there is an app where you simply have to log in before you start your ride and in the end you simply have to log out and the app will automatically calculate the price and charge the right amount from the payment method which you defined before. The same operating principle I already saw when I rented a bike with “Nextbike”. I think this kind of solution would be great as it would have also another benefit that it will offer flexibility to the users. Life is unpredictable: there are days that you have forgotten something in the office and you have to turn around or you are visiting a city and you are on your way to some sight, but on your way there you see from the window of a tram something what arouse your interest and you decide to get off. Wouldn’t it be amazing if you just can log out instead of letting your ticket expire and later buy a new one and pay twice?</p><p><strong>4. Prototype</strong></p><p>The last step in this project, after picking our last solution, was to create a paper prototype. Below you can see the result. I decided to highlight the button in red, when the ticket is not activated and to highlight it in green to show that the ticket has been activated. This way also during the ticket control the process will be accelerated. Further this feature recognise when the daysaver ticket would have been the cheapest option. So if on one day you have used the public transportation several times, you will be charged the amount for the daysaver ticket and not for each individual journey.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cPJgnjXmcQO46DQ5niK3A.jpeg" /></figure><p><strong>Conclusions</strong></p><p>It was quite exciting to work on this challenge as I could directly apply the theoretical knowledge. The task was challenging as I don’t live in one of the major cities so unfortunately I couldn’t discover the fullest potential of Citymapper, but could only use it in a limited way, so it made the ideation process difficult as I wasn’t sure if I might overlook something what is already integrated in the app.</p><p>In my case I had not much struggles with evaluating the interviews as all the participants had the same demands and also we had to conduct the interview with 5 participants. I can imagine though that it doesn’t really reflect the reality and in the real life this process is much more complicated. But still it was an interesting experience to put yourself in the position of the customer and try to create something new which suits their expectations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c7a2771780f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge 2 of the prework as a UX / UI student at Ironhack: Wireframing]]></title>
            <link>https://medium.com/@anzhelikazuboreva/challenge-2-of-the-prework-as-a-ux-ui-student-at-ironhack-wireframing-3829d7c223d1?source=rss-e1e9bea48e3f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3829d7c223d1</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Anzhelika]]></dc:creator>
            <pubDate>Sat, 21 Jan 2023 23:26:45 GMT</pubDate>
            <atom:updated>2023-01-21T23:26:45.778Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P7JTbBaSLQ6xLKCEWLa7zA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/fr/@odiin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Erik Odiin</a> on <a href="https://unsplash.com/photos/jbQvJx2EWnU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>For my Bootcamp in UI/UX design at Ironhack, I have some prework to submit and the second challenge was to “reverse engineer” on a popular app and to create a wireframe. We could chose any app and we had to identify the user flow on which we wanted to work.</p><p>For this challenge I chose the app “Booking.com” as I come from a hospitality bakground and used to work a lot with this website in the past. Further I’m a travel junkie myself, so often I’m faced with the situation to find an appropriate accommodation. For the next week, me and my friends, have planed a trip to Colmar and we struggled a little, while checking several websites to find an accommodation, as we are a lot of people and also have a dog with us. Further the problem was the price, as we had a limited budget. So the path which I chose to work on is to find the cheapest accommodation for a selected destination (in this case Colmar).</p><p><strong>Screenshots of the user flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkovOCm3tHUJfdhPJJfs2Q.png" /></figure><p><strong>UI elements</strong></p><p>When I was analysing the chosen flow, the most important UI elements, which I came across, were:</p><ul><li>Searching field</li><li>Input field</li><li>Buttons</li><li>Icons</li><li>Picker</li><li>Radio button</li><li>Stepper</li></ul><p><strong>Wireframing</strong></p><p>Once I have identified the important elements and that I was clear about the structure of the screens, the work could begin! To create a wireframe sounds like an easy task at first. I mean isn’t it about creating something simple? And to create something simple is simple, right? Wrong! Actually it was quite challenging for me to put aside my inner perfectionist and to concentrate on the main details. You can’t imagine the struggle to let the corners angular, when in the app they were round! But I made it! ;) Further it’s quite challenging to simplify the structure in order that anyone would intuitively understand and be able to accomplish the task without further instructions. And here is the outcome:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3o9h12tfFibOrYe5dM0TA.png" /></figure><p>As it is my first wireframe, I would appreciate if you have any feedback or advice, what I could have done better/differently.</p><p><strong>Prototype</strong></p><p>After having my wireframe screens, the next task was to put together a prototype using Figma. Below you find the link for the result and you can see the flow on Booking.com to have the result of the cheapest accommodation.</p><p><a href="https://youtube.com/shorts/gCJJVVQ3-JU">Ironhack UX/UI Bootcamp: Exercise - Wireframe</a></p><p><strong>Conclusion</strong></p><p>It was very interesting to interact with the app, which I have already used many times and to try to look at the things from another perspective. It was quite inspiring to try to take a step back and go beyond the habit and instead to analyse what could have been done to improve the user flow. For example I came to the conclusion that the option of sorting the results might have been integrated earlier in the process as it’s an extra step which the user has to take, which seems quite superfluous. I haven’t came up yet with the solution though and I hope that after completing the bootcamp, I will be able to do so :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3829d7c223d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>