<?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 Karim Mansour on Medium]]></title>
        <description><![CDATA[Stories by Karim Mansour on Medium]]></description>
        <link>https://medium.com/@herrmansour?source=rss-152406a07589------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j6ZRKRa88pbzdapzowRJuA.png</url>
            <title>Stories by Karim Mansour on Medium</title>
            <link>https://medium.com/@herrmansour?source=rss-152406a07589------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 10:24:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@herrmansour/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: Vueling App Re-design based on Heuristics Analysis]]></title>
            <link>https://medium.com/@herrmansour/case-study-vueling-app-re-design-based-on-heuristics-analysis-3ceaf3599db0?source=rss-152406a07589------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ceaf3599db0</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[heuristics]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Karim Mansour]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 23:48:17 GMT</pubDate>
            <atom:updated>2025-01-14T08:50:19.749Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="“Vueling style guide showing colors, typography, icons, and buttons. Colors include Main Brand (yellow #FCF150, teal #54B8B9), Functional (green, blue, orange, red), and Neutral (black, grey, light grey). Typography features ‘Barlow Semi Condensed’ for headings, buttons, labels, and ‘Source Sans Pro’ for body and navigation text. Icons include arrows, a plane, home, and luggage. Buttons are yellow for primary actions and black/white for secondary options.”" src="https://cdn-images-1.medium.com/max/1024/1*C7EsBEjbt2R0N5k_A1NxLg.png" /><figcaption>A style tile I created for the Vueling app to fasten the redesign process.</figcaption></figure><p><strong>Intro</strong></p><p>The task of my third project during the Ironhack Bootcamp was to perform a heuristics analysis for an application of my choice and redesign four screens to present my solutions where the current interface does not align with usability heuristics. This solo project started on Wednesday afternoon and lasted about two days, with the presentation taking place on Friday morning.</p><p>Before I get into the heuristics analysis, let me say a few words about the process of finding an application to do the analysis with. It sounds like a trivial thing to choose an app, but for me it turned out to be more difficult than expected. One of the reasons is certainly that I use only a few apps frequently, like Telegram, Chrome and Google Maps. All of these are already pretty well optimized, and I thought that these apps were not ideal for my first attempt at heuristic analysis. I then went to have a look at open source apps on GitHub.</p><p>There are plenty of apps which are under development and their interfaces look like you will easily find some usability problems. On the other hand, a lot of the services these apps provide are things I wouldn’t normally use an app for, and I felt like it would be beneficial to make a good judgment about their usability. In hindsight, I think this is a misconception and that it can even be an advantage to have little experience in a specific area to really see if the interface is intuitive and easy to use. I tried to remember the last time I used an app where I really found the experience complicated or frustrating, and pretty quickly the app for the Spanish discount airline Vueling came to my mind. After a quick test of the interface and noticing that nothing had changed since the last time I used it, I ended up choosing this application for my analysis.</p><p><strong>Heuristics Analysis</strong></p><p>Many people, like myself before this project, may not be familiar with the term heuristics and what it means. Heuristics, originating from psychology and cognitive science, are mental shortcuts that help us solve problems and make quick decisions. These shortcuts often work on a subconscious level.</p><p>Typical real-life examples include the <em>social proof heuristic</em>, where someone believes a restaurant is higher quality because it has more visitors, or the <em>quantity heuristic</em> in media, where frequent mentions of a topic make it seem more significant, or products with more reviews appear more trustworthy.</p><p>In design, heuristics are “rules of thumb” or best practices that guide the creation of user interfaces to ensure intuitive and easy usability. Very well known are Jakob Nielsen’s ten usability heuristics, like for example the ‘error prevention’ heuristic, which encourages designers to build interfaces that minimize the probability of users making mistakes that could be prevented by better design. In the image below you can see an overview of all of the ten usability heuristics that will also be the center of my upcoming analysis:</p><figure><img alt="“Image showing Jakob Nielsen’s 10 usability heuristics with icons for each: Visibility of System Status, Match Between System &amp; Real World, User Control and Freedom, Consistency and Standards, Error Prevention, Recognition Rather Than Recall, Flexibility and Efficiency of Use, Aesthetic and Minimalist Design, Help Users With Errors, and Help and Documentation.”" src="https://cdn-images-1.medium.com/max/1024/1*SISamgGO_-1LljS03l4ndA.png" /><figcaption>Jakob Nielsen’s Ten Usability Heuristics</figcaption></figure><p>With these ten heuristics in mind, I started my analysis by getting an overview of the current process of booking a ticket in the Vueling app. As you can see in the screenshots below, the current process looks very inefficient:</p><figure><img alt="33 Screenshots taken from the Vueling app." src="https://cdn-images-1.medium.com/max/1024/1*X8puZm4R8W3_vLqb6l4E9g.png" /></figure><p>The user has to go through about 33 steps before they can even enter their payment information. Part of this is probably to make the user spend more time in the app and also to offer more optional services, which is where the airline company makes most of its money. As UX designers, however, we put the user first, and that’s what I’ve kept in mind in all of my subsequent redesigns. Some of the solutions may not be fully in line with some of the business interests, but they can be understood as a good example of how keeping heuristics in mind can improve the flow and usability of the application. I will also point out some alternatives to my solutions that might be more in line with Vueling’s business interests, where applicable.</p><h4>Searching for a flight</h4><p>The first thing a user has to do when searching for a flight is to enter key information about the origin, destination, date range, and number of passengers. To understand how inefficient this process is, I will show you again a series of screenshots, nine in all, that represent all the steps the user has to go through to enter this information:</p><figure><img alt="Ten screenshots from the vueling app, showcasing how inefficient the current search functionality of the app is." src="https://cdn-images-1.medium.com/max/1024/1*8UQdoyHrnGQImRo0AEE7BQ.png" /><figcaption>The whole process for entering the flight details takes 9 screens.</figcaption></figure><p>By using different screens for each piece of information the user has to enter, the process is not only unnecessarily tedious, but also inflexible, forcing the user to go back if he wants to change any of the information he entered, and therefore not in line with the <strong>flexibility and ease of use</strong> heuristic. In addition, the interface hides information the user has entered, forcing him to remember everything, which violates the <strong>recognize rather than recall</strong> heuristic. Information that may still be relevant to the user, or that the user may want to change, should be visible throughout the process, if possible, to reduce cognitive load and allow for more intuitive use of the interface.</p><p>When searching for the origin and destination of a flight, the user is also initially presented with an extensive list of all possible options. In the case of booking a flight, users usually already know what they are looking for and this information is rarely needed, which breaks with the <strong>Aesthetics and Minimalist Design</strong> heuristic that asks us designers to present only the important information to the user that is needed to accomplish the task.</p><p>A problem found in many interfaces is also present here, where the search button is colored in the primary color yellow, indicating that it is ready to be pressed even though some of the required information has not yet been entered by the user. This is not consistent with the <strong>visibility of system state</strong> heuristic and ultimately leads to an error message. This message could be prevented in the first place by a design that conforms to the <strong>Error Prevention</strong> heuristic.</p><p>In the image below, you can see the areas where the current interface doesn’t match the usability heuristics, as well as my solution.</p><figure><img alt="“Comparison of a Vueling app search process with usability heuristics and solutions. Left: Current multi-screen process violates heuristics like visibility of system status, error prevention, flexibility, recognition, and minimalist design. Right: Solution condenses the process into one screen, optimizing heuristics. Proposed changes include disabling the search button until all fields are complete and presenting a simplified UI for improved efficiency and clarity.”" src="https://cdn-images-1.medium.com/max/1024/1*O0pQSXIKz00R9cX8PBCzkg.png" /><figcaption>Heuristical problems in the current Vueling search function for flights and my proposed solution.</figcaption></figure><p>By condensing all the search functionality into one screen and disabling the search button until the required information has been entered, my solution solves the problems mentioned above. As you can imagine, once the user decides to use the search function, an animation takes them to the more functional search form that offers all the options, allowing the home page to remain as it is and still allowing the company to promote its offers. This solution not only makes the process more efficient, but also keeps the user informed about the information they have already entered and when the search function is available.</p><h4>Flight Fare Upgrades</h4><p>After the user decides to book a specific flight, they are offered an upgrade option. While it is understandable that the company wants to promote these optional upgrades, the process is currently very frustrating for users as they cannot proceed to the next step unless they either select one of the upgrades or scroll down and select the basic flight package — a clear break with the <strong>flexibility and ease of use</strong> heuristic. The Continue button, which was on the bottom right of the previous screens, is also hidden, which is totally confusing to the user because it makes the interface inconsistent and doesn’t fit the <strong>consistency and standards</strong> heuristic.</p><p>In the screenshot below, you can see my solution, which puts the basic flight option at the top and pre-selects it so the user can quickly move to the next step by clicking the now-active Continue button. In my solution, the upgrade options can be found by clicking on a separate upgrade button. It would also be possible to list the options below if the company prefers to make the upgrades more visible.</p><figure><img alt="“A series of app screens for selecting flight fares. The first screen highlights upgrade options like ‘Fly Grande,’ the second shows the ‘Fly Light’ basic option lower on the page, and the final screen reorganizes the interface with ‘Fly Light’ preselected at the top, an active continue button, and an option to upgrade fares.”" src="https://cdn-images-1.medium.com/max/1024/1*tTXt9bus49A4BWxTgWqg_w.png" /><figcaption>Heuristical Problems in the Flight Fare upgrade sections and my proposed solution.</figcaption></figure><h4>Seat Selection</h4><p>After deciding to continue without a seat reservation a popup appears that asks the user to take the same decision again. If the user wants to continue without a reservation instead of clicking on the CTA button he has to click on a button that is looking like a hyperlink, therefore confusing the user by breaking the <strong>consistency and standards heuristic</strong> and making the process inefficient. In my solution below I added an info text below the “Continue without selecting seats”-Button and allowing the user to progress without having to take the same decision again.</p><figure><img alt="“A series of app screens for seat reservation. The first screen shows available seat options with prices, the second displays a popup asking if the user wants to choose a seat, and the final screen removes the popup and clearly indicates that a random seat will be assigned if none is selected.”" src="https://cdn-images-1.medium.com/max/1024/1*vvWhwU0tTmxNwevknhB3qw.png" /><figcaption>Heuristical evaluation of the current seat reservation process and my proposed solution.</figcaption></figure><p>Based on feedback I got after my presentation I agree that Vueling probably will insist on forcing the user to take the decision again, giving the user the possibility to reconsider reserving a seat. The company is making a gross of their profit at this point. In this case it would still be better to stay consistent and format the “Continue without seat”-Button as a normal CTA button. This way the process is transparent for the user and feels more trustworthy.</p><h4>Contact Details Form</h4><p>The contact details form — like many other forms out there — doesn’t comply with important usability design heuristics. One of the main problems here is that the “Continue” button is again highlighted as a CTA button before the user has completed all of the required fields, and therefore doesn’t comply with the <strong>visibility of system status </strong>and <strong>consistency and standards </strong>heuristics. Users may assume that they can proceed without filling in some of the required fields (in this case, all of the fields on the form are required), but then receive feedback from the system that makes the user feel like they have made a mistake. This violates the <strong>error-prevention</strong> heuristic, since this error could not have been anticipated by the user and could have been prevented in the first place by better design. My solution below solves these problems by combining a progress bar with the Continue button. With each completed field in the form, the button fills in a little more, clearly indicating the current system status, and is only activated when all required fields have been completed, preventing errors. In addition, successfully completed fields are highlighted in green to further encourage progress and provide positive feedback to the user during the process.</p><figure><img alt="“Screens showing a passenger form process in the vueling booking app. The first screen highlights issues like a misleading active ‘Continue’ button despite mandatory fields being incomplete, and the use of error colors for empty fields. The second screen implements a solution with disabled CTA buttons until fields are filled, clear instructions on mandatory fields, and a progress bar combined with the button for better clarity and efficiency.”" src="https://cdn-images-1.medium.com/max/1024/1*ep-zAW6M1O0jNLDO0Rh77w.png" /><figcaption>The contact details form and its heuristical problems on the left and my solution including a combination of a progress bar and the continue button.</figcaption></figure><h4>Conclusion</h4><p>For the user heuristics mainly function on a subconscious level. As designers we have to become conscious about these heuristics and use them to guide our design decisions to create more intuitive and user- friendly experiences. In this project I learned that something as seemingly small as the color of a button to something as large as the entire information architecture of the application are part of the usability heuristics. While some of Vueling’s design choices were certainly aimed at increasing their profit, I am sure they would benefit greatly from many of my supposed solutions. Making the flow of the application more intuitive and communicating more transparently to the user would also increase their revenue.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ceaf3599db0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing an eCommerce Website]]></title>
            <link>https://medium.com/@herrmansour/designing-an-ecommerce-website-1017b762dd01?source=rss-152406a07589------2</link>
            <guid isPermaLink="false">https://medium.com/p/1017b762dd01</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Karim Mansour]]></dc:creator>
            <pubDate>Mon, 06 Jan 2025 07:43:35 GMT</pubDate>
            <atom:updated>2025-01-23T12:21:15.423Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>A UX/UI Design Case Study</strong></h4><figure><img alt="Illustrative thumbnail featuring jewelry items, wireframe sketches, and survey result charts, symbolizing the UX/UI design process for an eCommerce jewelry website." src="https://cdn-images-1.medium.com/max/1024/0*GRaXy2WW5RMlc_Rm" /><figcaption>Image created by OpenAI’s DALL-E</figcaption></figure><h4>Introduction to the Project</h4><p>For my second project during the Ironhack UX/UI Design Bootcamp, I teamed up with <a href="https://medium.com/@apostolbianca91">Bianca</a>, <a href="https://medium.com/@midandelion93">Gaby</a>, and <a href="https://medium.com/@mrtz.romain31">Romain</a>. Our task was to find a stakeholder from our peer group who owns a business selling products online and to design an e-commerce website for them. Using the Design Thinking method, we aimed to practice aligning our stakeholder’s business goals with solutions that addressed customer pain points while creating mutual benefits for both the business and its users.</p><p>Compared to our first project, this one pushed me to think beyond user needs by developing practical solutions that also considered business objectives. Furthermore, I learned to adapt my pace and prioritize tasks within a team with varying levels of expertise, all while enhancing my technical proficiency in Figma.</p><h4>Finding a Stakeholder and Secondary Research</h4><p>We were fortunate to find a stakeholder very quickly, thanks to Romain. A friend of his, Sirikit Harivongs, runs a handmade jewelry business in Portugal and currently relies on a basic Shopify template to sell her rings and necklaces online. Additionally, she uses Instagram to engage with her target audience. With these factors in mind, we began our initial secondary research to gather information about business practices and customer behaviors in the jewelry market. For me, it was the first time dealing with jewelry as a product since I had never purchased any before. I was surprised by the market’s size and its significant growth potential in the coming years. Below, you can see our initial findings, which focus on market analysis, competitors, customer behaviors, and the growing use of technology to enhance online jewelry shopping experiences:</p><figure><img alt="Different Post its sorted by categories, showing our findings of our initial secondary research." src="https://cdn-images-1.medium.com/max/1024/1*eBLLjxV6g5M_0xjPUzjtsw.png" /><figcaption>Our initial findings from our secondary research about the online jewelry market.</figcaption></figure><p>Some key takeaways were:</p><ul><li>The jewelry market is experiencing significant growth with a large number of competitors.</li><li>Most customers of handcrafted jewelry value the uniqueness of the pieces and rely on social media for information.</li><li>The online shopping industry is increasingly adopting advanced technologies, such as virtual showrooms and augmented reality tools, to enhance the customer experience when shopping online.</li></ul><p>With these initial insights in mind, we proceeded to create an interview guide for our stakeholder interview. We aimed to learn more about her business values, goals, target audience, how she crafts her jewelry and what makes it unique, who her competitors are, and what marketing strategies she has previously employed so that we could build upon them. Preparing for a stakeholder interview for the first time taught me that there is a distinct difference compared to user interviews. When interviewing users, it is important to create a comfortable environment first, using warm-up questions to stimulate their imagination and help them engage with the context. By contrast, stakeholder interviews are more professional in tone and focus directly on key points. Warm-up questions in this context are mainly used to gather information about the company’s background and history.</p><p>Our main insights from the stakeholder interview were:</p><ul><li>Her current target audience consists of women aged 25–40 who value the artistry of handcrafted designs and sustainability.</li><li>She has previously used popup ads but currently relies solely on Instagram to market to her audience.</li><li>She draws inspiration from sensuality, nature, and the ocean, and she aims to focus on storytelling to market her jewelry.</li><li>She is looking to expand her production to handle larger quantities in the future.</li></ul><h4>Competitor Analysis</h4><p>Afterwards we conducted a competitor analysis to understand how other jewelry businesses present themselves online and identify common practices. Using an ad hoc matrix, shown in the image below:</p><figure><img alt="A so called “Ad Hoc Matrix”: A table used for our competitor analysis to compare different jewellery online shops and their features like payment options, visual style, shop features etc." src="https://cdn-images-1.medium.com/max/1024/1*8fEKrAa2OWOfLEqHNqoGow.png" /><figcaption>Competitor Analysis in form of an Ad Hoc Matrix</figcaption></figure><p>We compared competitors across a wide price range to observe differences and similarities. While distinct visual identities set these brands apart, most online store features and product presentation methods were strikingly similar. However, it became clear that the Shopify template our stakeholder currently uses falls short in telling a consistent visual story. A more personalized presentation would significantly benefit her brand.</p><h4>Empathizing with our Customers and identifying the Problem</h4><p>Next, we needed to delve deeper into potential customers’ preferences. Without sufficient knowledge to formulate specific questions for user interviews, we decided to create an online survey to gather quantitative data. Using the Lean Survey Canvas and Google Forms, we designed a survey to explore factors influencing purchasing decisions, trust-building elements for online stores, and common challenges when buying jewelry online.</p><p>While our stakeholder had defined a clear target audience, we opted to keep the survey audience broader to uncover untapped opportunities. One surprising yet crucial finding came from our open-ended question asking respondents to share anything we hadn’t addressed: the biggest challenge customers face when purchasing rings online is uncertainty about the product’s size and fit.</p><p>As shown in the image below, 85% of our respondents were women aged 25–44, affirming the target audience identified by our stakeholder:</p><figure><img alt="“Survey results displayed as charts: Pie chart shows age groups, with 60% aged 25–34, 25% aged 35–44, and 10% aged 18–24. Gender pie chart shows 100% female respondents. Bar chart on trust in online stores highlights customer reviews (90%), reputation (80%), and testimonials (35%) as key factors. Another bar chart on jewelry shopping priorities lists product images/descriptions (95%), customer reviews (75%), and website ease of use (30%) as most important.”" src="https://cdn-images-1.medium.com/max/783/1*vvKQeOvLRJdjQHxH0ySI9Q.png" /><figcaption>A few of the key insights we gathered through our survey about our target audience and their online shopping preferences.</figcaption></figure><p>Our survey also revealed that high-quality product images are the most critical factor influencing purchasing decisions, followed closely by customer reviews and return policies. Customer testimonials were frequently cited as a key element in building trust with an online store.</p><p>While the survey provided valuable insights, patterns began emerging early in the process, allowing us to start conducting user interviews sooner. These interviews helped us uncover additional qualitative details, such as:</p><ul><li>The importance of showcasing jewelry on models to provide a better sense of quality, size, and fit.</li><li>The primary pain point for customers is ensuring accurate measurements of the product.</li></ul><p>We synthesized our research findings from the survey and interviews into an affinity diagram. Using dot-voting, our team quickly aligned on prioritizing the sizing and fit issue. While improving the visual representation of the jewelry remained a focus, it largely depended on the availability of product images from our stakeholder, which we had yet to receive. Later, we found that the provided images allowed us to create an appealing online shop.</p><p>To better understand and empathize with our customers’ experiences, we created a persona named Amélie Aubert. Amélie is a 34-year-old professional who values unique jewelry as a way to present herself confidently at work. Given her busy lifestyle, she prefers the convenience of shopping online. You can find more details about her behaviors, goals and frustrations when shopping for jewelry online in the image below.</p><figure><img alt="A Persona Card for Amélie Aubert, with a photo of a confident looking woman and her Behaviors, Goals and Frustrations listed" src="https://cdn-images-1.medium.com/max/1024/1*LYX-R3nb8S-oBZt39PLpVw.png" /><figcaption>Our Persona Amélie Aubert</figcaption></figure><p>In our User Journey Map Amélie is looking to buy a ring as a Christmas gift for her mother. One of her most challenging moments arises when she feels uncertain about the ring’s size and fit, leading her to worry about potential returns and diminishing her confidence in the purchase.</p><figure><img alt="A graph showing emotional ups and downs of Amélies journey buying a ring online, with descriptive text explainig her thoughts and potential design opportunities in form of “How might we” statements." src="https://cdn-images-1.medium.com/max/1024/1*xeRHefL6mPWZv9_V4ytfcw.png" /><figcaption>Amélies User Journey Map</figcaption></figure><p>This insight led us to articulate our stakeholder problem statement, emphasizing how the user’s challenge with sizing and fit directly translates into a broader issue for the business itself:</p><figure><img alt="Our Stakeholder Problemstatement: “[Service]Our online jewellery store was designed to achieve [Goal] an increase in revenue of our business. We have observed that [Product] currently the process of purchaing rings is not meeting [User Goal] the customers need to confidently choose the correct size which is causing [Negative effects] loss of potential customers, having us to deal with returns and therefore a decrease in revenue to our business.”" src="https://cdn-images-1.medium.com/max/660/1*aS9cuj6macxdQGjKajsFgQ.png" /></figure><h4><strong>Ideation</strong></h4><p>After gathering all the insights and defining the problem we aimed to solve, we began brainstorming solutions using techniques like Crazy 8s and Worst Idea. Among our top ideas were:</p><ul><li>An AI-based ring-sizing tool that calculates the correct ring size from an uploaded photo.</li><li>A live customer support feature to assist with finding the perfect size.</li><li>A size guide based on established sizing conventions.</li></ul><p>To determine which solutions were feasible, we employed the MoSCoW method. Considering our tight deadlines and the potential technical challenges, the AI tool was too complex to prototype effectively and would leave some questions about its reliability. Live assistance was too resource-intensive for our stakeholder’s current business stage. Ultimately, we selected the ring size guide as our solution.</p><h4><strong>Information Architecture</strong></h4><p>Next, we created a sitemap for our stakeholder’s online store, forming the foundation for designing the user flow. Below is the sitemap I developed:</p><figure><img alt="Screenshot of a sitemap displaying a hierarchical structure of a website. The diagram includes main sections such as Home, About, Search, Shop, Cart and Account, with sub-sections branching beneath each category. Arrows and lines connect the nodes, visually representing the navigation paths." src="https://cdn-images-1.medium.com/max/1024/1*8BdWhN5iWuIloZPHNNLBLw.png" /><figcaption>My sitemap for our online store showing the different templates that would have to be designed for our stakeholder final shop.</figcaption></figure><p>One key learning for me was understanding that a sitemap visualizes the templates that structure a website and their relationships, rather than listing individual pages. For instance, a site for Rings and one for Necklaces may show different content but share the same Shop template, and this template is what the sitemap references. Similarly, a Product Page, which showcases specific details about an item, is part of the Shop’s hierarchy and is placed accordingly in the sitemap.</p><p>Based on the sitemap, I designed the user flow, shown below, to map out how users navigate between these templates.</p><figure><img alt="“User flow diagram for an e-commerce site. Starts at ‘Main Page’ (yellow), moves to ‘Rings (Category)’ (blue), ‘Product Page’ (light blue), ‘Cart’ (purple), and ‘Checkout’ (diamond). At checkout, users can sign up (orange) if not logged in. Flow continues to ‘Shipping Information,’ ‘Delivery &amp; Payment,’ and ends at ‘Confirmation’ (purple). ‘PayPal Express Checkout’ bypasses steps. Bottom-left legend explains ‘Happy Path’ and ‘Alternative Path’ with arrows for decisions.”" src="https://cdn-images-1.medium.com/max/1024/1*ktXEbmYjYNr6eWyhj_x6pQ.png" /><figcaption>The User Flow for buying a ring in our stakeholder online shop. We went with the happy path with the PayPal Express Checkout.</figcaption></figure><p>Integrating an AI solution for sizing, which would require users to upload or take a photo, would have made the flow more complex and time-consuming. By contrast, incorporating the sizing guide directly into the product page kept the process streamlined and user-friendly.</p><h4><strong>Wireframing</strong></h4><p><strong>LoFi</strong></p><p>Using the user flow as a guide, I sketched a LoFi wireframe to clarify layout decisions and create a simple prototype for concept testing. With access to high-resolution images from our stakeholder, we opted for a design emphasizing large product visuals to create a more immersive shopping experience. Below is the LoFi prototype I created for our initial testing:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fpage-id%3D14%253A319%26node-id%3D3553-1668%26viewport%3D1191%252C468%252C0.12%26t%3DkKhBfV8tycpOhMjH-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26starting-point-node-id%3D3553%253A1668&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fpage-id%3D14%253A319%26node-id%3D3553-1668%26viewport%3D1191%252C468%252C0.12%26t%3DkKhBfV8tycpOhMjH-1%26scaling%3Dscale-down-width%26content-scaling%3Dfixed%26starting-point-node-id%3D3553%253A1668" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/5e86530b7234f7a152c55f2846fa7a9e/href">https://medium.com/media/5e86530b7234f7a152c55f2846fa7a9e/href</a></iframe><p>This rough prototype, while quick to create, served its purpose well. In concept testing, we confirmed the flow’s clarity and ensured no critical information was missing. Users appreciated the inclusion of the sizing guide and reviews but found the category image on the Rings Shop page visually confusing, as it wasn’t clearly distinct from product images.</p><p><strong>Mid Fi</strong></p><figure><img alt="“Brand style guide for ‘Sirikit Harivongs,’ featuring colors and typography. Primary colors include salmon and beige, with secondary colors of light blue-gray and dark blue-gray, plus neutral grays. Tints and shades are displayed alongside an approximate color distribution bar. Typography uses Roboto Serif for the logo (24px) and Roboto for headings, menu, impress, product names, and paragraphs in various weights and sizes.”" src="https://cdn-images-1.medium.com/max/1024/1*jdD3e_svERpFdaO32cA-ow.png" /><figcaption>A style tile in which primary and secondary colors as well as typeface choices have been defined.</figcaption></figure><p>By incorporating the style guide’s font definitions and addressing feedback from concept testing, I created a MidFi wireframe prototype. This iteration refined the layout further before moving to the HiFi prototype.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fpage-id%3D4058%253A1515%26node-id%3D4058-2381%26viewport%3D5210%252C-71%252C0.16%26t%3DqLo7w2CyyEJvEKhH-1%26scaling%3Dcontain%26content-scaling%3Dfixed%26starting-point-node-id%3D4058%253A2381&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fpage-id%3D4058%253A1515%26node-id%3D4058-2381%26viewport%3D5210%252C-71%252C0.16%26t%3DqLo7w2CyyEJvEKhH-1%26scaling%3Dcontain%26content-scaling%3Dfixed%26starting-point-node-id%3D4058%253A2381" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/a82e559e95899e4b86087a2acbcc6d8b/href">https://medium.com/media/a82e559e95899e4b86087a2acbcc6d8b/href</a></iframe><p>The online shop was beginning to take shape! Due to time constraints, we tested the prototype only within our team, where it performed well. However, since team members were familiar with the design concepts, usability testing with unbiased users would be a valuable step in future projects to validate the intuitiveness of interactions across menus and templates before advancing to the HiFi stage.</p><h4><strong>Hi Fi Prototype</strong></h4><p>With only one afternoon left and a significant amount of work to do, I divided tasks among team members. This allowed everyone to play to their strengths. That way the group achieved impressive results despite the limited time available. Bianca and Gaby took care of our Presentation. They wrote a beautiful script that focused on story telling and polished our slides. Thanks to them our final presentation was great! Romain worked on some UI elements like buttons and review cards that I could then use later in my HiFi Prototype, which was my task. I filled the Mid Fi Wireframes with high res images from our stakeholder, created all the interactive components and interactions between site templates. At this stage, I also implemented our size guide solution on the product page, referencing common ring size conventions based on finger diameter and circumference in the US, UK, and Europe. Customers can use this guide to ensure that the ring sizes offered in our stakeholders online shop will fit their specific finger sizes which will make them feel more confident in their purchase. Test the prototype yourself below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fnode-id%3D4048-1910%26t%3DecIswsEGsW9JfV6M-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26page-id%3D4048%253A1899%26starting-point-node-id%3D4048%253A1910&amp;type=text%2Fhtml&amp;schema=figma&amp;display_name=Figma&amp;src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FXTJJEA9NBA0O47Wj0Xg61F%2F%255B-P2-Team-3-%255D-Design-File%3Fnode-id%3D4048-1910%26t%3DecIswsEGsW9JfV6M-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26page-id%3D4048%253A1899%26starting-point-node-id%3D4048%253A1910" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/d32cf0cdf28c199df38ed4faf3590cdd/href">https://medium.com/media/d32cf0cdf28c199df38ed4faf3590cdd/href</a></iframe><p>Working on a HiFi Prototype in Figma the first time, I learned how to create interactive components that visualize different states like hover or on click, use variables to set up more complex interactions between different components and I could even use some of my motion design knowledge to add some zoom animations for the collections thumbnails on the homepage that help to put the product in the center of the user experience.</p><h4>Learnings and Future Outlook</h4><p>This project provided valuable insights and learning experiences for me. A key takeaway was understanding how to balance stakeholder goals with user needs. I realized that in real-world scenarios, simple solutions can often be the most effective, especially when aligned with the stakeholder’s practical constraints. Additionally, exploring the jewelry market, particularly the challenges users face when purchasing rings online, opened my eyes to the many usability problems you can find even in unexpected areas. The Design Thinking process proved its strength in uncovering these issues, highlighting how empathizing with users not only leads to better solutions but also deepens a designer’s understanding of various industries. Another significant learning was the importance of clear communication within a team, especially when skill levels and expertise vary. Assigning tasks based on individual strengths helped us achieve more, and I aim to implement this practice even earlier in future projects. Looking ahead, I recognize the importance of dedicating more time to usability testing to refine layouts and interactions, ensuring they are intuitive. Additionally, exploring an Instagram integration to streamline the journey from social media to product pages could be a valuable enhancement for the stakeholder’s business. Finally, with more time, I’d also like to develop a fully responsive prototype.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1017b762dd01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Sustainable Food — A Wicked Problem]]></title>
            <link>https://medium.com/@herrmansour/case-study-sustainable-food-a-wicked-problem-4ed31e7a54c5?source=rss-152406a07589------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ed31e7a54c5</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Karim Mansour]]></dc:creator>
            <pubDate>Mon, 09 Dec 2024 07:37:27 GMT</pubDate>
            <atom:updated>2024-12-17T16:46:58.654Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Case Study: Sustainable Food — A Wicked Problem</strong></h3><figure><img alt="A header image generated with Gemini’s image generator AI showing an Illustration of different fruits and vegatables stacked in a fridge." src="https://cdn-images-1.medium.com/max/1024/1*tHEwN-K_vNH2aZNv8LFfCw.jpeg" /><figcaption>Image created with <a href="https://gemini.google.com/app">Gemini’s</a> image generator</figcaption></figure><p>Entering the first week of my UX/UI Design Bootcamp at Ironhack, I was placed in a group of four with members from Germany, Portugal and Venezuela. Working remotely and collaborating with a group of people from different backgrounds for the first time would turn out to be an intense learning experience about communication, getting things done under tight time constraints, not being a perfectionist, and of course the main goal: practicing the design thinking methodology on the wicked problem of sustainable food. But what makes this problem so wicked?</p><p>As defined by Horst Rittel a few of the key characteristics that makes problems wicked are:</p><ul><li><em>they are a class of social-system problems which are ill-formulated</em></li><li><em>there are many clients and decision makers with conflicting values involved</em></li><li><em>the information out there is confusing</em></li></ul><p>Sustainable food is a social systems problem that lacks a clear problem definition (ill-formulated), involves many stakeholders with different values and interests (producers, retailers, consumers, etc.), and as we enter the first stage of the design thinking process, we will soon realize how much confusing information is out there!</p><h3><strong>Empathize</strong></h3><h4>Secondary Research</h4><p>To get a first broad overview of relevant topics in the field of sustainable food, we started with a short secondary research session. After 30 minutes of searching the web and clustering our findings, we had a lot of interesting topics to dig deeper into, and I am sure we have just scratched the iceberg:</p><figure><img alt="An image showing post its of our secondary research findings, clustered by the following catergories: Trends&amp;Markets, Affordability, Food Waste, Diet, Reaching the User, Apps, Environmental Backgorund and Technology &amp; Innovation." src="https://cdn-images-1.medium.com/max/1024/1*c1f741OMZE4t0tjUl5FAjg.png" /><figcaption>Clustered findings of our intial secondary research</figcaption></figure><p>Now we faced our first problem as a group: How could we — who had only known each other for about an hour, with all our different backgrounds and most of us not knowing much about sustainable food — agree on which topics to focus on for our user interview guide? There was simply not enough time for lengthy discussions. At this point we got introduced to a very useful tool for collaborative work: Dot-voting! By giving each team member three votes and a few minutes to vote, we were able to come to an agreement faster than I have ever seen!</p><p>We agreed to focus on affordability, food waste, and how to reach the user. The latter would be a challenge for us later in the design process because it is still too broad a topic that includes education, certification, and availability of sustainable food.</p><h4>User Research</h4><p>Creating interview questions based on our limited research was difficult for me because I thought I didn’t know enough about the topics, but there was no time to do more research. It actually turned out to be helpful to know just enough to ask questions on the topic, and not knowing “everything” helped to keep me curious and wanting to learn more about individual user experiences. As we will see later: I wasn’t even curious enough!</p><p>After conducting our user interviews, we entered our transcripts along with our interview guide into ChatGPT, which saved us an insurmountable amount of time in matching our users’ answers to our questions and quickly getting some sort of structure. Still, we were left with a lot of information and our FigJam board looked like a mess!</p><figure><img alt="A screenshot from our FigJam board showing all of our interview transcripts and keypoints extracted and organized on post its. It looks a bit messy because of the vast amount of information to process." src="https://cdn-images-1.medium.com/max/1024/1*T7C37CrC4T37S49SAXjHAg.png" /><figcaption>After our user interviews our FigJam board looked like it had too much information to process at first!</figcaption></figure><p>How could we extract useful information from all of this and structure it so that we knew which problem to focus on? By deriving short, keyword-like posts from all the responses and creating affinity diagrams, we were able to highlight the main issues of interest, and after another round of dot voting, we agreed to focus on food waste and certification as the main issues with which to create our user persona.</p><figure><img alt="A screenshot from our FigJam board showing an Affinity Diagram for our research findings. We focused on 5 groups: Food Waste, Certification, Shopping Routines, Farmers Markets and the Price Issue. In the end we dot voted for two winners to continue to focus on: Certification and Food Waste." src="https://cdn-images-1.medium.com/max/1024/1*7-bSRH2GyNeaxd9WKdrx2A.png" /><figcaption>Affinity diagram and dot-voting results</figcaption></figure><p>In retrospect, it is easy for me to see that at that point we were complicating our lives unnecessarily by choosing two problems to work on instead of one.</p><h4>User Persona</h4><p>Based on our research we created our primary user persona, Maria Lopez.</p><figure><img alt="An image showing our User Persona, her Biography, Needs, Painpoints, Personality and Brands she likes." src="https://cdn-images-1.medium.com/max/1024/1*BrsHyaBLbPKdh9mRnGHYNg.jpeg" /></figure><p>Maria is a busy freelance graphic designer from Spain in her early 30’s. She is single, lives in Paris and definitely has too many sustainable food related problems going on at once.</p><p>She struggles with:</p><ul><li>reducing her food waste,</li><li>sustainable food is too expensive,</li><li>not knowing what certificates to believe,</li><li>the next farmers market being too far away,</li><li>and she doesn’t know enough vegetarian recipes to cook!</li></ul><p>Again, with the benefit of hindsight, I realize that our problem space was too broad and we were trying to fit all of our insights into one persona. If we had focused on one problem to work with earlier, or created personas for each problem and selected one as our primary persona, the following steps could have been less difficult.</p><h4>User Journey Map</h4><p>Creating Maria’s user journey map was a challenge in itself. Imagining the steps she would take to complete her task, her thoughts and frustrations, and most importantly, the touch points where we, as designers, could intersect to potentially solve problems with our future product was a true exercise in empathy.</p><figure><img alt="An image showing our User Journey Map for our User Persona Maria for the scenario of her wanting to shop some food after a long day in the office until the next day where she has to deal with her leftovers." src="https://cdn-images-1.medium.com/max/1024/1*YVhE3UAN7DGULbuGuC8_NQ.png" /><figcaption>User Journey Map in our scneario for Maria being on her way home from office and considering her dinner options.</figcaption></figure><p>To make her journey relatable, I found it very helpful to describe a real world scenario for Maria. It would keep me from thinking about “things she might do” and instead explain what she does. While our group user journey map was based on a relatable real-world scenario for Maria, we would soon find that we had introduced some behaviors that were not based on our user research just to make her journey coherent.</p><h3>Define</h3><p>By describing the user, their needs, and what we learned from our user research in a single sentence, we create a problem statement that defines the problem our product will try to solve. We quickly found ourselves working on two different problem statements, one focused on making informed choices about organic food at the supermarket and the other focused on preventing food waste. It was particularly difficult to formulate the insight for our food waste problem statement because we focused on Maria throwing away her unused leftovers, which we couldn’t support with our user research. Reviewing our user interviews led us to review our user journey map. We saw that we should focus more on providing recipe ideas for leftover ingredients to prevent food waste, and we were able to back this up with our research. In practice, we did our first small iteration between the define and empathize phases of the design thinking method to arrive at our final problem statement:</p><figure><img alt="An Image of our Problem Statement: “Busy young individuals with limited budgets neet to find a way to know what to cook with their leftoever ingredients and how to store food to make it last longer because currently, they struggle to manage thei food inventory which causes waste of food an money.”" src="https://cdn-images-1.medium.com/max/630/1*0ss77iLjvUexNvEigu3Odw.png" /><figcaption>Our final problem statement</figcaption></figure><p>In reviewing our user interviews, I also had one of my key learnings from that first project:</p><h4><strong>You can never be too curious! Always ask follow-up questions!</strong></h4><p>One of our users reported that she</p><blockquote>“sometimes buys surprise packages, but doesn’t always know what to do with the ingredients in them, which can lead to food waste”.</blockquote><p>Asking follow-up questions at this point about other experiences with surprise packages or digging deeper into the problem of food waste would not only have helped us create more realistic personas and UJMs, but would have given us more insights for defining our problem statement!</p><h3><strong>Ideate</strong></h3><p>Now that we had narrowed down our findings to a single problem, we would again diverge to come up with possible solutions. Using “How Might We” statements helped us focus our minds on solutions that would actually help and therefore be useful to our users. After a round of Crazy 8’s, we continued with Worst Idea brainstorming, where the bad but funny idea of a “foodwasters meetup” turned into one of our favorite ideas of a “leftovers meetup with social cooking”. Using the MoSCoW method to prioritize our ideas, we arrived at our Minimum Viable Product Statement. At the very least, our mobile application should have:</p><ul><li>A scanning feature to scan your food inventory</li><li>Recommend recipes to cook from that inventory</li><li>Recommend ways to store food to make it last longer</li></ul><h3>Prototype</h3><p>With these requirements in mind, we created our first simple user flow:</p><figure><img alt="A Screenshot of my User Flow for Maria when she uses our app to take a picture of her fridge and get recipe recommendations from our AI." src="https://cdn-images-1.medium.com/max/1024/1*BWmvFti7LFOBosjjEKO3Sg.png" /><figcaption>My User Flow for accomplishing the task of scanning your food inventory and getting recipe recommendations</figcaption></figure><p>This helped us visualize what actions and decisions the user would have to make to complete the task in our app, and what screens we would need to sketch in our first Lo-Fi wireframe prototype:</p><figure><img alt="A photo of my LoFi wireframe sketch for the screens that would have to be designed in our app to complete the User Flow." src="https://cdn-images-1.medium.com/max/708/1*tRVSudrSFpfp7erEtsEHxA.png" /><figcaption>My first rough sketch for our App following the User Flow</figcaption></figure><h3>Test</h3><p>Now it was time to test our concept with potential users. We were not sure if we should create a clean Figma wireframe for this, but since time was running out, we decided to go with a prototype made from photos of our paper sketches. This is where I learned another important lesson from this project:</p><h4><strong>The amount of feedback you can get from even very simple paper prototypes is amazing!</strong></h4><p>Although some of the screens were not entirely clear to our users, they were able to navigate through the app and understand its core functionality. It may have even helped that they had to use their imagination a bit more to visualize themselves using our app in a real-life situation and how they would interact with it. The feedback on the usefulness of our product was all positive and every user said they would use such an application very often to prevent food waste and learn more about what to cook with or how to store their leftovers. We also got a lot of suggestions on what the app could do better that we hadn’t thought of in our first iteration:</p><ul><li><em>“Could there be an option to manually add food?” </em>— Addressing that some people may have security concerns with the camera</li><li><em>“What about the food outside the refrigerator? Can I view and edit that, too?”</em> — pointing out that in a real-life scenario, tracking only the leftovers in your refrigerator is not very useful.</li></ul><p>On a real project, we could now iterate our user flow and wireframes to incorporate these feature requests before creating a more refined figma wireframe for more detailed testing, saving time and money in the production cycle.</p><h3>Conclusions</h3><p>Working with an international team remotely can be challenging but also stimulating collaborative solutions.</p><p>It is amazing how much you can get done when having tight deadlines.</p><p>Not knowing everything is crucial to stay curious and keep learning more about user behaviours.</p><p>Working with imperfect solutions can already provide valuable insights for fast iterations of prototypes.</p><p>I can’t wait to apply what I’ve learned to another round of design thinking and see what my new learnings will be in this iteration of the learning cycle!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ed31e7a54c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework:Karim Mansour_Challenge2]]></title>
            <link>https://medium.com/@herrmansour/ironhacks-prework-karim-mansour-challenge2-b45975d229a1?source=rss-152406a07589------2</link>
            <guid isPermaLink="false">https://medium.com/p/b45975d229a1</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[task-analysis]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[wireframe]]></category>
            <dc:creator><![CDATA[Karim Mansour]]></dc:creator>
            <pubDate>Fri, 15 Nov 2024 13:37:58 GMT</pubDate>
            <atom:updated>2024-11-16T09:32:30.596Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*bu0jgW05VDSXfPCqeDv-Fw.jpeg" /><figcaption>Image taken from<a href="http://www.flickr.com/photos/jammind/"> Judy and Jam</a> on <a href="https://de.pinterest.com/pin/565764771949647623/">Pinterest</a></figcaption></figure><h3>Wireframing</h3><p>The goal of this challenge was to go through the process of creating a low to mid fidelity wireframe for the completion of a task in an app of my choice. I chose the Spotify app because I wanted to become more aware of all the interactions I have within the app, which I use pretty much every day. The goal of the task will be: “Create a playlist and add your first track” because this is one of the more complex interactions you can have within the app that involves multiple screens.</p><h4>Task Analysis</h4><p>To get a full understanding of what actions the user needs to perform to complete the task, I started with a simple task analysis. Verbalizing and writing down the whole process helped me become aware of all the subconscious interactions I was doing, for example, after clicking the plus button I would immediately click “Create Playlist” because I never use the second option “Create Mix”. I had to create about 10 playlists before I had a full understanding of every single interaction that takes place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*nh5U8PLLgOIopEuli8l0Hg.png" /></figure><h4>UI Elements Inventory</h4><p>Before I could start wireframing, I needed to understand all the visual elements on the screens and their functionality. Creating a simple UI inventory helped me categorize the elements into buttons, text fields, navigation components, etc. This allowed me to determine the appropriate fidelity to represent all of these within the wireframe without distracting from the user flow needed to complete the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/399/1*jlifkQgHct3CpxlE0b1_oA.png" /><figcaption>A very simple UI Inventory to gain awareness of all UI Elements on the screen</figcaption></figure><h4>Paper Lo Fi Wireframe</h4><p>Before jumping into Figma, I did a very quick Lo Fi paper wireframe to understand the structure of all the UI elements within the layout of each screen, as well as creating an initial flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohu8xnQCn3ZWC8C4DLwGiQ.jpeg" /><figcaption>A very rough paper wireframe, to visualize the UI Elements within the layout. I admit, it got pretty rough at the end.</figcaption></figure><p>In my first attempt, I forgot to draw the media player and the bottom navigation bar, which showed that I was not fully aware of the whole layout. Thanks to pen and paper, I was able to start over quickly. Although the second attempt could still be refined, I decided it was good enough to go into Figma and create a clean wireframe there.</p><h4>Figma Prototype</h4><p>In Figma, I created a Lo to Mid Fi wireframe prototype using a combination of simple shapes and components from wireframe kits. I also set up an interactive user flow to complete the task using Figma’s built-in prototyping features. I found that the process was greatly accelerated by the clarity provided by going through all the steps beforehand. I didn’t have to make any decisions about what elements were actually needed for this user flow and could just focus on creating low fidelity placeholders, layout, and interactivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6ZVDZj_RTLHyqT3wLFAmg.png" /><figcaption>Screenshot out of Figma showing the individual wireframes for all screens and the flow for completing the task</figcaption></figure><p>Interactive prototype below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Dcdn.embedly.com%26embed_origin%3Dcdn.embedly.com%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FcILV3DHqvT0nfdL43kNLqJ%2FIronhack-Prework-Challenge-2-Wireframe%3Fpage-id%3D0%253A1%26node-id%3D0-3%26node-type%3Dcanvas%26viewport%3D285%252C463%252C0.1%26t%3DkFDqEOm0irN2Em1D-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D0%253A3&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FcILV3DHqvT0nfdL43kNLqJ%2FIronhack-Prework-Challenge-2-Wireframe%3Fpage-id%3D0%253A1%26node-id%3D0-3%26node-type%3Dcanvas%26viewport%3D285%252C463%252C0.1%26t%3DkFDqEOm0irN2Em1D-1%26scaling%3Dscale-down%26content-scaling%3Dfixed%26starting-point-node-id%3D0%253A3&amp;image=https%3A%2F%2Fwww.figma.com%2Ffile%2FcILV3DHqvT0nfdL43kNLqJ%2Fthumbnail%3Fver%3Dthumbnails%252F4a2960d3-249d-4eac-a0b6-396e6474f69e%26t%3DkFDqEOm0irN2Em1D-1&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/737086d1d2401a67a5191314acd1b0b0/href">https://medium.com/media/737086d1d2401a67a5191314acd1b0b0/href</a></iframe><h4>Key Takeaways</h4><p>During this challenge, I learned that creating a wireframe is an essential tool in the UX designer’s repertoire. With wireframing, you focus on all the structural elements needed to complete individual tasks within the application, and the layout is intuitive and functional without having to spend time visually refining elements. Wireframing also allows you to quickly iterate on concepts without investing too much early on. The steps of task analysis, inventory of UI elements, and sketching on paper before starting to work within a wireframing software accelerates the whole process by deconstructing the fundamentals of the interaction.</p><p>Besides a lot of learning, I also had a lot of questions come up:</p><ul><li><em>What is the right level of wireframe fidelity for a given task (e.g., are placeholder texts or rectangles the best option?)</em></li><li><em>Should you include the visual feedback that occurs when an action is taken in the task analysis?</em></li><li><em>How detailed should a UI inventory be?</em></li></ul><p>I also had some more technical questions like:</p><ul><li><em>What is the right resolution for a wireframe?</em></li><li><em>How do I make sure all components render properly at different resolutions?</em></li></ul><p>I am really looking forward to learning about all of this and much more during the bootcamp!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b45975d229a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework:Karim Mansour_Challenge1]]></title>
            <link>https://medium.com/@herrmansour/ironhacks-prework-karim-mansour-challenge1-d2ef22bc461c?source=rss-152406a07589------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2ef22bc461c</guid>
            <category><![CDATA[paper-prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[prework]]></category>
            <dc:creator><![CDATA[Karim Mansour]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 15:58:48 GMT</pubDate>
            <atom:updated>2024-11-11T15:58:48.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="An Infographic showing the 5 steps of the Design Thinking Cycle" src="https://cdn-images-1.medium.com/max/564/1*49iUiKYkkZj5wXZA-SfvBw.jpeg" /><figcaption>Image from <a href="https://personifycorp.com/blog/design-thinking/">personifycorp.com</a> on <a href="https://de.pinterest.com/pin/578290408427185712/">Pinterest</a></figcaption></figure><h4><strong>The Challenge</strong></h4><p>The task in this challenge is to go through the first four steps of the design thinking methodology (empathize, define, ideate, prototype). For this, a new app feature for a public transportation app should be created to solve the pain of buying public transportation tickets.</p><figure><img alt="Citymapper Logo" src="https://cdn-images-1.medium.com/max/406/1*zVHahVfhxNK3s01bapCRXQ.png" /><figcaption>Image from <a href="https://en.wikipedia.org/wiki/Citymapper">Wikipedia</a></figcaption></figure><h4><strong>The Company</strong></h4><p><em>Citymapper</em> is a public transportation app and mapping service that displays transportation options, between any two locations in a supported city. It integrates data for all modes of urban transport, including walking, cycling and driving, in addition to public transport.</p><h4><strong>Empathize</strong></h4><ol><li><strong>Interview</strong></li></ol><p>To get a deeper understanding of the experiences of different users and to find out the real pain points of using public transport apps and buying tickets, I interviewed five people between the ages of 25 and 42. To do this, I created an interview guide. The goal was to gather the information I needed to create an improved app feature, but to keep the conversation open and unbiased. Here are some examples of questions I asked my users:</p><ul><li><em>“How often do you use public transport, and what is usually the main reason?”</em></li><li><em>“Can you walk me through the last time you had to buy a public transport ticket? What was the experience like?”</em></li><li><em>“What is your most memorable experience using public transport in a foreign city or country?”</em></li><li><em>“In your imagination, what would the perfect experience of acquiring and using a public transport ticket look like?”</em></li></ul><p>2. <strong>Evaluation</strong></p><figure><img alt="An overview in Goolge Sheets of all the interview answers" src="https://cdn-images-1.medium.com/max/1024/1*gknNTSA5wmKZdcnSLN5wwg.png" /><figcaption>I created a Google Sheet to get an overview of the common experiences of the group of people I was interviewing</figcaption></figure><p>All of those I interviewed use public transport quite regularly, ranging from 1–2 times a week to daily. All also use their local public transport app to buy tickets when needed (some users also use subscriptions that eliminate the need to buy local tickets) and have used public transport abroad.</p><p>In general, everyone I interviewed is pretty happy with their current transit app, as these apps have come a long way in the last few years. There are still noticeable pain points when it comes to:</p><ul><li>understanding which ticket option is the most cost-effective (<em>“Is it better to buy individual tickets or a 24-hour pass?”</em>),</li><li>having to use different apps when traveling to different cities or countries or</li><li>being able to cancel an ongoing subscription at any time (they can usually only be canceled at the end of the month, thus costing the user).</li></ul><h4>Define</h4><p>Since buying a ticket was only a minor concern for the group of people I interviewed, I decided to expand the problem space to include the pain points that came up in my research. The problems I am trying to solve can be defined as follows:</p><ul><li>Eliminate the need for other transportation apps by</li><li>providing an easy-to-use, transparent app feature that</li><li>clearly shows costs,</li><li>is flexible so users don’t have to worry about fixed ticket durations, and ultimately</li><li>provides a cost-effective way to buy public transportation tickets anywhere.</li></ul><h4>Ideate</h4><p>After analyzing the responses of the people I interviewed, I already had an idea of what a possible app feature might look like. To get as many different solutions as possible, I did a quick brainstorming session. The top three in ascending order where:</p><p><strong>Linking the local public Transport App</strong></p><p>When searching for a public transport route, the user is presented with all local public transport apps and their respective prices within the app. With a single click, the user can then open the app of their choice and buy their ticket. While this solution is probably the most realistic to implement (Citymapper already has a similar feature with car-sharing companies and taxi services like Uber and Bolt), it still leaves the user to figure out which ticket option is the best, and it doesn’t solve the problem of having to use multiple apps.</p><p><strong>Urban Transit Pass</strong></p><p>A subscription-based model with flexible pricing options for City, Country or Global Pass options and the ability to cancel weekly. This solution would be very convenient for the user, who would be able to use public transport freely and even worldwide with a global pass. Apart from the fact that it is not very easy to implement in reality, the solution also has some problems. There is no solution for users who only want to buy a single ticket, and there is also uncertainty for subscribers about when to cancel or whether they are actually getting good value compared to their public transport habits.</p><p><strong>Fare Capping</strong></p><p>With this solution, the user simply buys single ride tickets. They are aggregated in the app to create daily, weekly or monthly passes. At the end of the month, the user is guaranteed to be charged only the cheapest option based on their public transport usage. I chose this solution because it solves all the defined problems. The user doesn’t have to worry about different pricing options or monthly subscriptions, because he is guaranteed to always pay the lowest possible fare. With enough cooperation with different public transportation providers, this solution would also eliminate the need for different transportation apps and could be used anywhere.</p><h4>Prototype</h4><ol><li><strong>Creating a Paper Prototype</strong></li></ol><p>To test how a fare capping feature could look like within the Citymapper app, I created a paper prototype. The prototype consists of all the necessary screens to complete the task of buying a ticket and starting your public transport journey.</p><figure><img alt="A picture of the first 4 screens of the paper prototype" src="https://cdn-images-1.medium.com/max/960/1*Eris6qAaj9le2YX6ljy-JQ.png" /><figcaption>Screens 1–4</figcaption></figure><figure><img alt="A picture of screens 5–8 of the paper prototype" src="https://cdn-images-1.medium.com/max/960/1*iO9TGmwPCyY7jXqyQtCe6Q.png" /><figcaption>Screens 5–8</figcaption></figure><p>The Fare Capping screen shows the user how much the ticket will cost, and also shows the progress towards either a daily pass (once three individual tickets are purchased within 24 hours) or a monthly pass (once a monthly total of €50 is reached).</p><p>2. <strong>Self Testing</strong></p><p>I also did a quick self-test to get an idea of how the interaction feels. Here is a short animation showing the prototype in action:</p><figure><img alt="An animation of the paper prototype being tested" src="https://cdn-images-1.medium.com/max/718/1*H_3AX04UOGozJ0yxTYyPyA.gif" /><figcaption>GIF animation of the paper prototype</figcaption></figure><h4>Key Learnings</h4><ul><li>The empathize phase is particularly important because its results affect all subsequent steps. Reiteration is essential: For example, a second round of interviews would have allowed me to refine my questions, which were sometimes too broad in my first iteration. Another approach to empathy would have been to ask users to walk me through a ticket-buying experience with their current app. This could provide a more practical understanding of their behaviors and feelings. In addition, the diversity of respondents has a significant impact on the results. Including people who don’t regularly use public transportation could provide a fresh perspective on their experiences and challenges.</li><li>The Define phase will also be heavily influenced by the results of the Empathize phase. It is important to be able to incorporate these new insights while remaining focused on the core problem.</li><li>After the interviews, I already had an idea of what a good solution might look like, which turned out to be a challenge during the Ideate phase. It is important not to fall in love with an idea too early so that you can stay creative and come up with as many solutions as possible.It can help to incorporate different brainstorming techniques as well as mind mapping to keep an open mind.</li><li>During the prototyping phase I learned how the interaction would actually work. At first, I was surprised at how many screens were actually needed to accomplish the task. It helped to get a clearer understanding of all the interactions that are happening on screen. Ultimately, being able to prototype quickly is a crucial skill to be able to repeat this phase, and it is something I will have to work on.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2ef22bc461c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>