<?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 Paul Heuschmidt on Medium]]></title>
        <description><![CDATA[Stories by Paul Heuschmidt on Medium]]></description>
        <link>https://medium.com/@paul-heuschmidt?source=rss-8fee13f5bc03------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_M2tiVIvhSDZLGuDnGhLzA.jpeg</url>
            <title>Stories by Paul Heuschmidt on Medium</title>
            <link>https://medium.com/@paul-heuschmidt?source=rss-8fee13f5bc03------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 09:50:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paul-heuschmidt/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[Building an AI supported search function for the supreme court’s content management system.]]></title>
            <link>https://paul-heuschmidt.medium.com/building-an-ai-supported-search-function-for-the-supreme-courts-content-management-system-9d30b6ec3e51?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d30b6ec3e51</guid>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[ai-product-design]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Sun, 12 May 2024 08:43:55 GMT</pubDate>
            <atom:updated>2024-05-12T09:46:56.205Z</atom:updated>
            <content:encoded><![CDATA[<p>The title may sound insane, and that’s because it is a design prompt, generated using <a href="https://designercize.com/">designercize.com</a>. This innovative website presents you with outlandish product ideas at the click of a button. As part of our Master’s degree in Interaction Design at the California College of the Arts, we developed design strategies around AI and machine learning technology. I was teamed up with the talented <a href="https://www.linkedin.com/in/miahe712/">Mia He</a>, and we were instructed to press the prompt-generating button and work on whatever came up. Fortunately for us, this was our prompt:</p><figure><img alt="The initial design prompt from designercize.com" src="https://cdn-images-1.medium.com/max/1024/1*33v1LquZssFUmm23Q4cATw.png" /><figcaption>The initial design prompt from designercize.com</figcaption></figure><p>At first, we were a bit overwhelmed. What do advanced search results look like? For what purposes and by whom is the Supreme Court’s content management system used? What points are important to consider when developing a design strategy around AI products? In any project, this is the moment where one could feel overwhelmed and start working in an arbitrary direction, but not us.</p><h4>Desk Research</h4><p>We began by researching the Supreme Court and discovered that in the United States, each individual state has its own Supreme Court. Consequently, we decided to design our search function for the Supreme Court in California, as this is where we currently reside.</p><p>Further research revealed that the Supreme Court primarily uses its Content Management System to organize court orders and cases. This information gave us more insight into what the search results could be sorted for.</p><p>We examined other types of content management systems and search functions, such as those used by libraries, and whatever information we could find about the content management system currently used by the Supreme Court. We also looked at how companies like Google and Open AI display AI-powered search results and the interaction design principles they use to make the experience user-friendly.</p><p>We found that AI search results are often used complementarily to existing sorting and filtering functions to uncover patterns in search results that are otherwise inaccessible to the user. Additionally, these advanced functions are not imposed on the user but rather suggested. This approach gives users a sense of control, which can foster trust, a crucial emotion in the adoption of AI-powered products.</p><figure><img alt="An example of Google’s AI powered search results" src="https://cdn-images-1.medium.com/max/1024/1*EFxrsPd8DU0oTY3RcQ8IGw.png" /><figcaption>An example of Google’s AI powered search results</figcaption></figure><h4><strong>Design Strategy</strong></h4><p>After our initial research phase, it was time to put the pieces together and develop a cohesive design strategy on how to build, test, and implement our solution. First, we decided upon a focus, a vision, and a customer value to inform our design strategy. We also came up with a name for our product — “Courtwise”.</p><p>We realized that AI could be used by the Supreme Court to better manage and access their court files, as well as help staff and researchers navigate and discover patterns in the data. Consequently, we defined a focus, a vision, and a customer value for our project.</p><figure><img alt="A slide showing focus, vision and customer value of the project" src="https://cdn-images-1.medium.com/max/1024/1*ysAuA7uo1CQI2-Bnc9mGhg.png" /><figcaption>A slide showing focus, vision and customer value of the project</figcaption></figure><p>We finally brought all these ideas together and defined in a brief statement what we would develop as part of our MVP:</p><blockquote>The AI feature offers advanced filtering options based on content and user preferences, and implements rules-based sorting options to prioritize search results based on relevance, historical significance, and other factors.</blockquote><p>We attempted to integrate our solution into the preexisting content management system, striving to keep functionality and options for personalization concise. Given the complexity of the project, simplicity is key.</p><p>The Supreme Court operates with a lot of sensitive data, and the margin for error, as is the case with any government institution, is very small. This is why, before we continued, we had to evaluate whether the use of AI even made sense for this use case. To answer this question, we made use of Google’s <a href="https://pair.withgoogle.com/guidebook/">People + AI Guidebook</a>, specifically employing the following checklist to see whether AI would be able to solve our problem in a unique way.</p><figure><img alt="A checklist published by Google’s to test weather the use of AI makes sense for your specific product." src="https://cdn-images-1.medium.com/max/966/1*_3hVt5KaD4MOueB8MADYbw.png" /><figcaption>AI Checklist</figcaption></figure><p>We found that in our case, the benefits of using AI as part of the search function would outweigh the disadvantages. It would enable a more personalized experience for our users and boost efficiency in searching for very specific content. The major reason not to use AI in this case was the high cost of errors. The Supreme Court cannot afford any privacy violations, which would be an argument against the use of AI.</p><p>At this point, we noticed that there were some serious privacy, security, and ethical considerations we would need to address in our design strategy if we really wanted to take this project to the next phase.</p><figure><img alt="Important considerations to make when using AI in the context of a public institution. Considerations are concering: safety and security, privacy an ethics." src="https://cdn-images-1.medium.com/max/1024/1*MiS4LZUbIwmjxXFVgUEflA.png" /><figcaption>Important considerations</figcaption></figure><p>In order to convince the Supreme Court to adopt our product, we needed to undergo stringent testing and fully disclose how the search engine would operate. A complete audit trail at all times would be necessary to uphold accountability and ensure the secure handling of sensitive data.</p><p>Especially, ethical considerations are a sensitive topic. We are talking about a system that accesses and represents data from the legal system, which has a real-world impact on people’s lives. There is no room for any type of bias in the model, and we have to ensure that our solution operates fairly and transparently. It was necessary for our solution to find a balance between user-side functionality and organization-side data security.</p><h4>Implementation</h4><p>To plan the implementation, we developed a step-by-step plan to ensure that we meet the necessary ethics, security, and privacy requirements for adoption by the Supreme Court. The following plan is the result of that effort. If we envision a final arrow from KPI Evaluation to Business Objectives, this process can be seen as circular, working together with the Supreme Court to optimize the product. As mentioned earlier, stringent testing and an extremely low risk of failure will be necessary before the product can be approved and shipped.</p><figure><img alt="A diagram showing the design implementation strategy." src="https://cdn-images-1.medium.com/max/1024/1*4jWbQ1d4K2j-6NEUC4KkPw.png" /><figcaption>Design implementation strategy</figcaption></figure><h4>Metrics of Success</h4><p>We made use of Google’s HEART framework to assess our desired metrics of success, as shown below. Within the framework, we are focusing on 1. Adoption and 2. Task Success, as we see the adoption of the product by the Supreme Court as the major hurdle in our design strategy. Secondary to adoption, but no less important, is task success. Will our solution uphold increased accuracy and save time?</p><figure><img alt="A Table showcasing metrics of success after Google’s HEART framework." src="https://cdn-images-1.medium.com/max/1024/1*72tDYmov_3lEdYR6H0O1Tg.png" /><figcaption>Metrics of success after the HEART framework</figcaption></figure><h4>Wireframes</h4><p>Finally, we jumped ahead and drafted our first wireframes of what this advanced search function could look like. We are aware that user research is imperative before drafting designs, but we were simply curious about what the product could potentially look like.</p><ol><li>Home screen with opened accessibility menu</li></ol><figure><img alt="A wireframe showing the homescreen with some feed and a search bar in the center. An accessibility menu is opened in an overlay via a button on the bottom-right of the screen." src="https://cdn-images-1.medium.com/max/1024/1*XH5rWjg_O11kI9nZk9Dt3Q.png" /><figcaption>Home screen with expanded accessibility menu</figcaption></figure><p>In this initial screen, we aim to showcase our plan to make the product accessible to as many people as possible. Given that we are designing a product for a public institution, our target audience is a large and diverse population. Under these circumstances, it becomes extremely important to consider factors such as vision impairments, contrast, and text size settings. To address this, we have placed a button in the lower right corner of the screen, featuring an icon that depicts a human shape. This icon remains visible throughout our user flow. When clicked, the accessibility menu opens in an overlay.</p><p>2. Results page with sorting options on the left and space for the interaction with AI on the right.</p><figure><img alt="Results page with sorting options on the left and space for the interaction with AI on the right." src="https://cdn-images-1.medium.com/max/1024/1*bM6LzLX-LXwl7RyrG8GfGg.png" /><figcaption>Search results page with suggested AI interaction</figcaption></figure><p>In this second screen we can see a search results page. To give users a sense of control and to foster trust, the AI will not output automatically but only if prompted via the click of “AI Generate” button.</p><p>3. Search results page with initial AI output</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZO3FAxkoRZVqVc4Xjf491A.png" /><figcaption>Search results page with initial AI output</figcaption></figure><p>If the user decides to move ahead and click the ‘AI Generate’ button, the output will be displayed in the panel on the right. Suggested prompts, displayed beneath the search results, provide the user with guidance on how they might want the AI to expand its output. We took this idea from Google’s Generative AI search engine add-on.</p><p>4. Search results page with expanded AI output</p><figure><img alt="The screen shows search results and side pannel on the right with an output by AI. Prompts are suggested from which the user is able to choose to converse with AI." src="https://cdn-images-1.medium.com/max/1024/1*j8W6eejlAJUynnbQt3BnOg.png" /><figcaption>Search results page with expanded AI output</figcaption></figure><p>On this last screen we can see the user has decided to click one of the suggested prompts which triggers the AI to output further information about the chosen topic.</p><h4>Main learnings</h4><p>Through this project, I have come to understand the extensive consideration required for the use of AI in public offices, where data privacy is extremely important and the cost of error is exceptionally high. Although this project was hypothetical, if more time were available, I would move forward and reach out to the Supreme Court and the Judicial Council of California Information Technology Services Office (JCCITSO) to gather more insights into whether this project is feasible. Additionally, if possible, I would like to conduct a contextual inquiry to observe how Supreme Court employees access and organize their data, and perform user interviews to further deepen these insights.</p><h4>References</h4><p>● <a href="https://www.supremecourt.gov/">https://www.supremecourt.gov/</a><br>● <a href="https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.flaticon.com%2Ffree-icon%2Fcms_2867263&amp;psig=AOvVaw1OG8ZTC8BpG5ZEyBNO2Iai&amp;ust=1697490459523000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBAQjRxqFwoTCNDDw_X6-IEDFQAAAAAdAAAAABAD">https://www.google.com/url?sa=i&amp;url=https%3A%2F%2Fwww.flaticon.com%2Ffree-icon%2Fcms_2867263&amp;psig=AOvVaw1OG8ZTC8BpG5ZEyBNO2Iai&amp;ust=1697490459523000&amp;source=images&amp;cd=vfe&amp;opi=89978449&amp;ved=0CBAQjRxqFwoTCNDDw_X6-IEDFQAAAAAdAAAAABAD</a><br>● <a href="https://www.courts.ca.gov/documents/IT-DMS-2016-01-MDS-Appendix-B3-appellate-functional-reqs.pdf">https://www.courts.ca.gov/documents/IT-DMS-2016-01-MDS-Appendix-B3-appellate-functional-reqs.pdf</a><br>● <a href="https://www.courts.ca.gov/documents/accms-factsheet.pdf">https://www.courts.ca.gov/documents/accms-factsheet.pdf</a><br>● <a href="https://www.superside.com/blog/design-strategy">https://www.superside.com/blog/design-strategy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d30b6ec3e51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reviving Circuit City]]></title>
            <link>https://paul-heuschmidt.medium.com/reviving-circuit-city-1deb3aaec432?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/1deb3aaec432</guid>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[rebranding]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 14:50:57 GMT</pubDate>
            <atom:updated>2024-01-11T14:50:57.190Z</atom:updated>
            <content:encoded><![CDATA[<h4>Championing DIY Tech and Circular Economy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7FFFvMvqX0zP-yDXdlVMQ.png" /><figcaption>New Logo and Brand Colors</figcaption></figure><h4>Introduction</h4><p>I have developed a rebranding concept for Circuit City, once a dominant force in the American electronics retail market for over thirty years. In 2008, Circuit City declared bankruptcy due to inaccurate market predictions, mismanagement, and an inability to compete with the emerging Best Buy. Circuit City’s business model was originally based on three core brand values:</p><ul><li>Extensive Product Range</li><li>Competitive Pricing</li><li>Customer Service</li></ul><p>However, the rise of the internet changed consumer expectations, leading to a preference for less interaction with in-store personnel. This shift partly explains why Best Buy’s model, which emphasized minimal employee-customer interaction, gradually took over the market. Believing that Circuit City deserves a revival, I propose a fresh new business model, customer experience, and brand identity.</p><h4>The new Concept</h4><p>My vision is to reintroduce Circuit City as a retailer and repair shop for refurbished electronics and a hub for DIY electronics workshops, aligning the brand with 21st-century values such as promoting a circular economy, local engagement, and community involvement. I found that the global market for refurbished electronics is projected to grow by 170% by 2030 (according to Maximize Market Research). This expansion is expected due to the high demand for affordable electronics and increasing awareness of sustainability issues.</p><p>I want to transform Circuit City from a large, coldly lit retail store with a warehouse ambiance into a more intimate, small, neighborhood coffee shop-style store. Circuit City should become a welcoming place that people enjoy visiting. In addition to selling refurbished devices primarily through the Circuit City website, the physical stores should offer workshops for customers to learn electronic repairs. Circuit City aims to be a hub for those interested in electronics, providing a platform for information exchange and relationship building. With these changes, Circuit City’s new core principles are:</p><ul><li>Customer Service</li><li>Community</li><li>Education</li><li>Low Cost</li><li>Sustainability</li></ul><p>To better conceptualize how the revamped Circuit City might fit into the market and to understand all the value exchanges between relevant parties, I have created the following <strong>stakeholder map</strong>. The Circuit City business, positioned at the center, primarily engages with three parties: its customers, educators, and employees. Value exchanges are categorized as either qualitative or quantitative, with an emphasis on interpersonal relationships and customer retention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1NysdQUkdmA0Kt07JzjfSA.png" /><figcaption>Stakeholder Map</figcaption></figure><h4>Competitors</h4><p>I identified three major competitors, each distinctly different from the others. On one hand, there’s Back Market, an online store specializing in selling refurbished electronics in the U.S., lacking any repair services or physical store locations. On the other hand, there are Repair Cafe and The Restart Project, both of which are non-profit, community-run organizations dedicated to teaching device repair and promoting a repair culture. I believe there is a market gap that can be effectively filled by Circuit City’s new business model. This model combines a low-contact online store offering affordable electronics with an empowering, community-focused brand. Such a brand would enable people to identify with and build relationships around it, bridging the existing market gap. I summarized my findings on these three competitors in the following document…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2u7uuI3m01rQDmVVtqxrg.png" /><figcaption>Competitor Analysis</figcaption></figure><h4>Target Audience</h4><p>As I began the project with an initial concept idea for the new Circuit City business model, the target group became apparent during the creation of the value map and competitor research. My aim is to target younger North Americans, specifically those aged 18 to 45, and their children, for whom Circuit City offers special workshops. To design the brand experience, I envisioned hypothetical users and developed customer journeys around them. These personas include Sarah, a 33-year-old single mother with limited time and money, who needs to purchase a laptop for her son’s education, and Carlos, a 20-year-old computer science student seeking to repair his phone affordably while making new connections with peers. Having recently moved to study in a different city, he is longing for social contact. I crafted extensive user personas based on these characters, imagining what their lives could be like and the challenges they might face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTQjSKsJxUhzf-EbMPcCdA.png" /><figcaption>User Personas</figcaption></figure><h4>Customer Journey Map</h4><p>To better understand how my customers interact with the brand and to identify which touchpoints I needed to design, I sketched out two customer journeys: one for Sarah, who is looking to buy a refurbished laptop for her son, and another for Carlos, who wants to get his phone fixed. Sarah’s experience with the brand is solely digital, while Carlos’s journey includes visiting the Circuit City store, interacting with employees, and even buying coffee at the in-store coffee shop.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LzVqyPyU7NYoKCrRYm7Wow.png" /><figcaption>Customer Journey Map</figcaption></figure><h4>Grid Systems</h4><p>At this point, I better understood what the brand should look and feel like. I wanted to move away from Circuit City’s original color scheme of Red, Black, and White and move towards something more grounded, friendly, and less aggressive. I tried various grid systems and styles for the website, oscillating between experimental and “fun” approaches and more stiff and corporate feels. I experimented with modular grids, which would have given the website a more editorial feel. Still, I decided to move forward with a column grid system for clarity and visibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-fzEzW5tB1uuv5v7P0iNA.png" /><figcaption>Grid System Explorations</figcaption></figure><h4>Color, Logo &amp; Typeface</h4><p>After settling on a rough initial layout for the website, I explored different color schemes that could represent Circuit City’s new image, as shown below. I experimented with pastel tones (on the far left) and blue and yellow (in the middle), which, although already used by brands like Best Buy, I still considered. I also tried more experimental approaches, like the one on the far right, but ultimately discarded it as it felt too abstract and more reminiscent of a cultural event page or a museum website.</p><p>In terms of the logo, I aimed to create something simple and easily recognizable, a design that would look good on coffee cups and t-shirts yet still reflect the store’s ethos. I decided to move forward with the example in the middle below. For the logo’s typeface, I selected “Orelega One,” a serif font that conveys playfulness while maintaining a sense of quality. For titles and paragraphs on the website, I chose the easily readable sans-serif typeface “Radio Canada,” and for quotes, I use another serif typeface called “Tiro Bangla.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2M-YQdeY9iHkDkL8PDFlMg.png" /><figcaption>Color, Typeface and Logo Explorations</figcaption></figure><p>From this point on, I iterated the design, striving for improvement. Initially, I was dissatisfied with the color combinations and the exact layout of the website, so I continued experimenting until I found the colors that pleased me. I chose a combination of blue (0C356A), yellow (FFC436) and white (FFFFFF). Although these colors are already used by Circuit City’s old competitor, Best Buy, I believe that with a new concept focused on repairing devices, education, and selling refurbished tech, Circuit City will no longer be a direct competitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ssIVMtXqqjQok5tA9ptk0A.png" /></figure><p>I received feedback that my current design, intended for an intimate and welcoming store, still appeared too corporate. In response, I experimented further and decided to break up horizontal lines and add illustrations that I created using DALL·E 3. I added micro-interactions for buttons, hover states and even added a new kids page (below, on the far right). My persona Sarah is looking to buy a laptop for her son and has limited time. I see this as an opportunity for her to engage further with Circuit City as she is also looking to expand her social network and making some time for herself on the weekends.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1RCeu5i-zj4H-qWuHryZoQ.png" /><figcaption>Final Designs</figcaption></figure><h4>Key take aways</h4><p>This passion project has taught me a great deal about shaping a brand’s experience using colors, grid systems, fonts, and language. It has also enlightened me about the process of completely redesigning a brand from scratch. If I had more time, I would love to revisit the beginning and conduct user research to validate my assumed user personas, Carlos and Sarah. Additionally, I would like to design the interior of a Circuit City repair store, as this is a crucial aspect of the user experience.</p><p>I thoroughly enjoyed researching for this project and envisioning a new concept for an old electronics retailer in the 21st century. I read that Circuit City was recently acquired, so if anyone from Circuit City is reading this and is interested, I am more than happy to collaborate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1deb3aaec432" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An editorial for aliens.]]></title>
            <link>https://paul-heuschmidt.medium.com/an-editorial-for-aliens-f762cee69bb8?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/f762cee69bb8</guid>
            <category><![CDATA[editorial-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[fashion]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[aliens]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Sun, 01 Nov 2020 16:05:24 GMT</pubDate>
            <atom:updated>2020-11-11T16:00:37.944Z</atom:updated>
            <content:encoded><![CDATA[<p>Our objective for this weeks project at the Ironhack UX/UI Bootcamp was to create an editorial website with an emphasis on visual design. We worked in teams of two and had one week to finish the project. The goal was to create a high fidelity, responsive, static interface for a website that we invent. The <strong>user personas</strong> for the project where provided by our teachers.</p><h3>User Persona</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*So7rwn_DasI9xAtjk36BvA.png" /></figure><p>We chose Paula, a 19 year-old creative that wants to connect with aliens. Or at least that was what we interpreted. So for us it was as clear as day that we had to create an editorial for aliens. By that we mean not really for interstellar visitors but rather for earthlings that love extraterrestrials just as much Paula does. All though a purely alien website could have also been fun.</p><h3>Competitor Analysis</h3><p>Since we already knew who our user was we started off with some <strong>secondary research</strong> and <strong>competitor analysis</strong> to see what others have done before us. We found three websites in particular that came close to what we had in mind.</p><p>These are <a href="https://www.kaltblut-magazine.com/">https://www.kaltblut-magazine.com/</a>, a quirky, young fashion editorial, <a href="https://www.gaia.com/">https://www.gaia.com/</a> a spiritual blog and conspiracy hub and finally <a href="https://cybrmagazine.com/">https://cybrmagazine.com/</a> a editorial about all things sci-fi and how cool they are. Accordingly we created one <strong>style guide</strong> for each of these websites to better be able to visualize their aesthetic core…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_Ly-uIGP1MrHwQ_2-Bd82w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9euXM4R87Xj6RlnZA3iWA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNwo4W3BxPoPs1WZUv6fBA.png" /><figcaption>competitor style guides</figcaption></figure><h3>Mood Board</h3><p>From here we started an gathered material from the web that could be used for our <strong>mood board</strong>. Colors, pictures, textures, impressions, ideas we collected all in a figma file. We threw everything around and iterated again and again. Each of us built a unique mood board which we would melt into one final version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*8r-Sq557fKcS6BF_UKdtXg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*aXJ0p7UcRlzNLcBVkraRbQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*ic_XzXROa-Lby8MbhD_iiw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/902/1*i1sZHfr_IyY3aPVdXdE9Qg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*cO3r0Iesgg0sUD7HoovzhQ.png" /><figcaption>mood board iterations</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wbcUNVRpinG9l6ZJmWB04w.png" /><figcaption>final mood board</figcaption></figure><h3>Brand Personality</h3><p>We conducted a survey too see which keywords people connected with our mood board to get a grasp of our <strong>brand personality</strong>. In the survey we presented our finalized mood board together with a list of forty traits that we chose our selves. The respondents where asked to choose five traits out of the list that they found most fitting for the mood board. These are the traits that where mentioned the most:</p><ul><li>Bizarre</li><li>Futuristic</li><li>Cyberpunk</li><li>Odd</li><li>Alternative</li></ul><p>We where very happy with the outcome of the survey since it approved the feeling we where trying to convey through our mood board.</p><h3>Style Tile</h3><p>With the general mood and our brand personality in mind we started developing a <strong>style tile</strong> for our product. We played around with a lot of fonts but chose <em>Press Start P2</em> as our header font because we liked the kind of 90s gaming vibe and found that it was a good fit with the brand personality. Accordingly the buttons where decorated with the same font and made to look like straight out of a video game. As for the body text we chose a font called <em>Robot Mono</em> since it looks like it was typed with an old typewriter and thereby creates this feeling of reading a classified file from area fifty one. For the logo we chose neon vibrant colors that should remind the user of such films like Blade Runner or Akira, a kind of cyberpunk neon sign vibe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EfDaEeBg3KR3ERSzduhB9g.png" /><figcaption>style tile</figcaption></figure><h3>Prototypes</h3><p>Based on our style tile we designed our hi-fi prototypes right away. I have to confess that we skipped the lo- and mid-fi stages for this project. First, because we had only two days left to finish and second, since we focused mainly on the visuals the proper UX process was lacking a bit. Non the less I we corrected some issues that showed in our user testing. Finally we prepared our presentation for the project and practiced a bit.</p><p>All in all I am proud of what we built. Especially the concept behind the product is something I can really get behind. All the sample content on the prototype was chosen by us since we both are super in to this kind of stuff. Yai is speaking to a developer that would be interested to build the hole thing so the next step for us would be to design the hole site.</p><p>For now these are the desktop and mobile prototypes that we designed…</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F8W4abKTy9ec%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D8W4abKTy9ec&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F8W4abKTy9ec%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f09081c7048d083d676d63878133f0d/href">https://medium.com/media/6f09081c7048d083d676d63878133f0d/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FVOE3CfFxZWM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DVOE3CfFxZWM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FVOE3CfFxZWM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6f4ee5149406a97cc8f7ef94b9528bd9/href">https://medium.com/media/6f4ee5149406a97cc8f7ef94b9528bd9/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*B0FXGIJ65PXOIrob5-vJgQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f762cee69bb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An app against social divide.]]></title>
            <link>https://paul-heuschmidt.medium.com/an-app-against-social-divide-6ec02de32c3f?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec02de32c3f</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Thu, 29 Oct 2020 12:54:10 GMT</pubDate>
            <atom:updated>2020-11-06T16:10:29.040Z</atom:updated>
            <content:encoded><![CDATA[<p>My colleague Mez Dumas and I built a MVP for a co-working app thought up by a client in Berlin. The Idea behind the product was to built a networking platform that would bring people closer by letting them organize events to meet peers. I personally loved the clients approach of avoiding any algorithmically personalized feed in an attempt to protect the users autonomy. She emphasized repeatedly that at the center of this project lies the community, not the individual.</p><h3>Empathize</h3><p>We kicked off this two week project with an introductory meeting during which we agreed upon a scope of work, the deadlines and our deliverables. The very first thing we did in approaching this project was bold googling to get a grasp of what was already out there and who could be our competitors. Luckily, we already received a brand positioning map from our client which made it easier for us to filter who would be worth considering.</p><h4>Research</h4><p>The next step was competitor analysis and secondary research. We found that there was at least one platform that tried to address a similar problem. It is called Vero and it advertises to be a social network without algorithms, that gives their users full control over who sees their content. Besides Vero there are a number of companies that come close but never something that was the exact same model. We also conducted primary research through the means of surveys and interviews. We got over 70 responses on our survey and it showed us several key points:</p><ul><li>about 60% of people have used apps before to connect with new people in a non romantic context</li><li>about 10% of people are more likely to make an invitation than to receive one, while 40% of people do both equally and 50% people receive more invitations that they send out</li><li>only 40% of people would be interested in meeting someone if they would not know whether they have something in common or not</li></ul><p>We learned that not a lot of people are truly interested in meeting complete strangers solely based on location. Furthermore the interviews showed us that often times people that move to a new city are looking for people with a specific purposes in mind, be it sports, work related things or to talk about specific topics/obtain information.</p><p>In addition to our surveys we also conducted 1 on 1 interviews with people that had the experience of moving to a new city, where they did not know a lot of people and tried to build a network from the ground up.</p><h4>Empathy Map</h4><p>We collected all the keywords and phrases from these interviews, wrote them down on post-it notes, using the collaboration platform<a href="https://miro.com/"> <em>Miro</em></a> and organized them by topics. From there we ordered said post-it notes on an empathy map template to narrow down what our user persona could be like. What are his/her views, hopes, goals, pain points etc. Up until this point the information from the interviews is still in a kind of cloudy state with the viewpoints of many different people displayed on one canvas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xAjb_jIQWplJsrKJYf99nA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bz81NFlePUImpxavYB__w.png" /><figcaption>affinity diagram and empathy map</figcaption></figure><p>We found that the main pain points to be solved where:</p><ul><li>safety concerns</li><li>building a network in a new city</li><li>avoiding awkwardness when meeting strangers</li></ul><h4>User Personas</h4><p>Based on our findings we decided to create two personas, male and female, that are similar in a lot of ways but differentiate in the kind of the contacts they are looking for. When building user personas we want to condense the information from our empathy map as much as possible, representing as many of our users as possible while still creating a consistent and authentic persona. For this reason we decided to create two personas: While Clarissa is looking to built her social networking on a more professional side Dennis is primarily looking for someone to do sports with after work. In our view the product should be able to accommodate both of their requests. Both of them just arrived in Berlin and are yet limited in their number of contacts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EP0rAHDD2yCDwr-bZwV_jQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q0GTMyY1S8N6UUSxVyoi-Q.png" /><figcaption>user personas</figcaption></figure><h3>Define</h3><p>After we figured out our user personas we narrowed all our information down to a problem statement and finally our<a href="https://www.designkit.org/methods/3"> “how might we”</a>.</p><p>The purpose of the problem statement and the “how might we” is to condense the information from the user personas even more and to bring it down in to one single sentence. That way it becomes clear what our objective will be and exactly what problem we are trying to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDjmcC7uezOhsx_1Q1YJsg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7xPxRMUsQCRli8rN11d9g.png" /><figcaption>problem statement and “how might we”</figcaption></figure><h3>Ideate</h3><p>From here the process becomes a bit messier. Here begins, what we call the ideation stage of the process and in my opinion it is the hardest and most fun part of UX Design. We started out with a practice called<a href="https://www.iamnotmypixels.com/how-to-use-crazy-8s-to-generate-design-ideas/"> “crazy eight”</a>. In this exercise the goal is to generate eight ideas to solve the problem in just eight minutes. These ideas do not necessarily have to be logical or make sense but they have to be illustrated and explainable. From experience I know that during the crazy eight exercise usually one or two solutions emerge that can actually be improved and worked on.</p><p>As for this project the crazy eight did not deliver us the one breakthrough design but helped us to get a first idea of what the wireframe could look like. This was the point where we hit a bit of a wall since there where so many options to move forward but none of them really felt right. We did not just wanted to do the next meet-new-friends-app and also not another LinkedIn. It took us a few days, a lot of discussing and free brainstorming to get that idea that would manifest as the center of our design. The Idea was to let the user be able to create events under any kind of topic. For example an English speaking expat who just moved to berlin and needs to get their registration done in German could use the app to team up with people that find themselves in the same position. This way they can avoid <em>awkwardness</em> since they share the same problem, interest etc. and all them can <em>grow their network</em> in a casually without to much small talk.</p><p>With this design we are already tackling two of the three main pain points that we where able to extract from our research. The one that is left is the safety concern, namely to make sure that people that post events are sincere in their intentions. This can also be worked on in a later stage for example by implementing a rating or verification system so we did not worry about it too much at this point.</p><h4>Mood board</h4><p>The next step was to make the thing visual. At first we collected adjectives that could describe our brand and tried to come up with mood boards that match set brand image. These where the options that we presented to our client:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XyGhY2MWnh4GzrHQloiLWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KleP52cOp08A-ohHyyBaOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2K8cEOgtlkxMJQaC4xccVw.png" /><figcaption>optional moodboards</figcaption></figure><p>Out of four contesters the client chose this one:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*REFJm8RoKUGtu1cc9dyuGQ.png" /><figcaption>the mood board for our product</figcaption></figure><p>The colors should convey friendliness, casualness and an inviting atmosphere. People are relaxed yet they want to achieve a collective goal and work together, learn from each other and build a network. The client chose this mood board because she wanted to avoid a corporate and stiff image. These colors are vibrant and high in contrast, thereby conveying a young and casual feeling. After we agreeing upon the colors we defined the user flow that we would design.</p><h4>User Flow</h4><p>Our deliverable is a MVP and for that reason the user flow should be including just enough to make the product work in it’s core functions. Since the events are at the center of the product, attending and creating an event are definitively part of our MVP. We want people to organize and communicate within the app so a chatroom was another must have.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFFq_Kwm8zn6aN_FJbZEHw.png" /><figcaption>user flow</figcaption></figure><p>This is what we came up with. The user will start off at her feed page. From there she will proceed to view a certain event on that feed page. She will take a look at the event creators profile before joining the event. After she becomes an attendee she will be granted access to the event’s chatroom. She checks out the event specific chatroom before deciding to create her own event, for which she chooses a description text, a location and a time. After creating and posting the event she will return to her original feed screen.</p><h3>Prototype</h3><p>Since we now knew exactly which screens to work on we started creating our first lo- to mid-fi wireframe. The process was a constant back and forth between designing and testing. At the end we added two more screens. The profile of the user and a calendar feature, where the user is able to see all events she is attending. The following picture shows a selection of our lo- to mid-fi wireframes. The little arrows between some of the screens indicate a design iteration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ksxyfbDg4ZfC80HSmRbMQ.png" /><figcaption>lo- to mid-fi wireframe</figcaption></figure><p>Before we began with our hi-fi prototype, we put together a style tile for orientation. We chose an easy-to-read sans-serif font called “Spartan” and agreed on all the icons which we would use in our final design.</p><h4>Style Guide</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSVX1KwNv49ioG1XIw8t1g.png" /><figcaption>style tile</figcaption></figure><p>On the last two days of our two week project we worked on the hi-fi version of our product and ironed out any little ambiguities in our design by testing and adjusting. And finally, after many hours of research, ideation and design, this is our final hi-fi prototype:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRR5gIjZYEFg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRR5gIjZYEFg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRR5gIjZYEFg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6273c66ec6ecf98caa69537f46886100/href">https://medium.com/media/6273c66ec6ecf98caa69537f46886100/href</a></iframe><p>I have to say it was an absolute pleasure to work on this project especially because it was an idea I was really able to get onboard with. These two weeks went by super quickly and it was an absolute pleasure to have Mez on my team.</p><p>Thanks Pri, thanks Mez:)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec02de32c3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lucid Dreaming App]]></title>
            <link>https://paul-heuschmidt.medium.com/lucid-dreaming-app-9194cfd3f897?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/9194cfd3f897</guid>
            <category><![CDATA[lucid-dreaming]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[dreams]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Tue, 22 Sep 2020 07:10:24 GMT</pubDate>
            <atom:updated>2020-11-10T15:38:05.967Z</atom:updated>
            <content:encoded><![CDATA[<h3>A dream tracking app.</h3><p>As part of the Ironhack UX/UI Bootcamp we had to design a health tracking app. It was a two-week-solo-project and we enjoyed the freedom of choosing what exactly we wanted to work on.</p><h3><strong><em>Empathize</em></strong></h3><p>At first I had to figure out what kind of health tracking app I wanted to build. For this reason I brainstormed topics that interested me and that I already knew a little about. As result of this brainstorm and for reasons of personal interest I chose to design a dream tracking app that will help you practice lucid dreaming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vAnpNeVMtHMoeWoYUc4WqA.jpeg" /><figcaption>Brainstorm</figcaption></figure><h4>Secondary Research</h4><p>After I decided to work on an app that lets you document your dreams in order to practice lucid dreaming, I continued with <strong>secondary research</strong> and collected a loose collection of keywords surrounding the topic of lucid dreaming. After I listed all these words I started organizing them in clusters to create a ordered mind map and wrap my head around the topic.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qZ4dwVEx-ch5OPFwDkerA.png" /><figcaption>Topic Cluster</figcaption></figure><h4>Primary Research</h4><p>Next I wrote a survey and asked people if they knew about lucid dreaming, if they ever had a dream journal before and if they have ever used an app to document their dreams. I received 62 responses and it turned out that a lot of people where familiar with the concept of lucid dreaming and many have even tried to document their dreams but only a small percentage have used apps for that purpose.</p><p>I wanted to know what the main <strong>pain points</strong> where that people experienced when tracking their dreams so I conducted interviews with individuals that had experience with the topic and even achieved lucid dreaming themselves.</p><p>After some interviewing I came to the conclusion that a lot of people that document their dreams had problems with the consistency of their documentation. So this is definitely something that my design has to address.</p><h4>User Persona</h4><p>I collected more key words and organized them in an <strong>affinity map</strong>. On the basis of the affinity map I built an <strong>empathy map</strong> and constructed my <strong>user persona</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q2jHnrZcYOJPKvPRa6v3kg.png" /><figcaption>User Presona</figcaption></figure><h3>Define</h3><p>After formulating a user persona and processing the many bits of information I was able to gather from the interviews I wrote down the <strong>problem statement</strong> as well as my <strong>how-might-we</strong>. These will help me stay focused on the what the application is trying to achieve and which problem it is tackling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*uNa1v5V9sRLXO0toCxw4sg.png" /><figcaption>Problem Statement and “How might we”</figcaption></figure><h3>Ideate</h3><h4>Mood Board</h4><p>Right away I had concepts and pictures rushing through my head so instead of continuing with the feature prioritization and card sorting I jumped ahead to do some work on possible <strong>mood boards</strong>. I thought of the movie inception and eternal sunshine of the spotless mind (all though this movie is not directly related to dreams). I tried to remember what kind of devices they used in the movies and what their interfaces looked like. I experiment with color and fonts for a bit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ha69og0m4PN01u9RGq0vVg.png" /><figcaption>Preliminary Mood Boards</figcaption></figure><p>From the interviews I learned that if you want to document your dreams in detail you will have to do it right after waking up while remaining in a kind of limbo between dream and reality. For that reason I chose a darker background for my application that would help the user to stay in that limbo. During the prototyping process I iterated a lot on the looks of the design. For that reason the final design varies quite a bit from the first mood board versions.</p><h4>User Flow</h4><p>I continued with the feature prioritization using the <strong>MoSCoW method</strong> to figure out which features where a must, should, could or should not have and created a <strong>user flow</strong> for my first prototype accordingly. At the center of the design lies the dream journal. Additionally, I added a search function, rating system for dreams to keep track of your mood and sleep quality as well as library containing theoretic knowledge about lucid dreaming and a stats page that corresponds to the dream ratings. I chose these features based on the information and pain points gathered from my primary research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CB88A22CTCFQ8GjMWHP3Fg.png" /></figure><h3>Prototype</h3><p>I started working on a first low- to mid-fi prototype. While designing the prototype I avoided putting any effort in aesthetics or the exact positioning of buttons and text but rather focusing fully on the user flow. I also inlcuded the option to record audio files on the add entry screen since some of the lucid dreamers from my interviews told me repeatedly that the feature could be very useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YcP3Us45pCudq_3srTTn7g.png" /></figure><p>After my first draft I proceeded with user testing followed by iteration and more user testing and more iteration and so on. After I was happy with the basic basic layout I moved to developing a concept for my mid- to hi-fi prototype. The first thing i did ways making the background darker and giving each journal a little more space. Refrencing to the word “Oneironaut “ which in greek means “Dream Traveler” and describes a person that is able to lucid dream I wanted to give the app a feel of nautical log.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6kwwvDJHKslnFO23QEcFA.png" /><figcaption>These pictures illustrate how my journal screen developed over multiple steps.</figcaption></figure><p>Finishing the mid- to hi-fi prototype I noticed some things that I was still not happy with. For example how the buttons are sometimes hard to distinguish from the background as well as some problems with the UX writing and still some more problems with the user flow. So of course I continued testing and tried to iron out any small problems and inconveniences people experienced when using the prototype. After some further iteration I ended up with the following design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YVljeFMwCgpbr0S_XgmlVA.png" /></figure><p>I changed the background color to a even darker blue as well as adding some slight shadows to buttons and inner shadows to text input fields. Finally I designed a loading screen and added some animation. At last I had to choose a name. Since the name “Oneironaut” was already taken by a competitor I went with the name “Hypnos”, the greek god of sleep, since it is a short and recognizable name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*hUum2MwS0C0PJUTkYh-56Q.png" /></figure><p><em>Sweet dreams!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9194cfd3f897" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Efficient Wanderlust]]></title>
            <link>https://paul-heuschmidt.medium.com/efficient-wanderlust-af919e223628?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/af919e223628</guid>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 15:43:09 GMT</pubDate>
            <atom:updated>2020-07-29T15:43:09.783Z</atom:updated>
            <content:encoded><![CDATA[<p>The third design challenge, as part of the UX/UI Design Bootcamp prework organised by Ironhack Berlin, was to improve a flight tracking app of our choice. For this purpose we conducted user research to identify the pain points of set app and continued with designing correspondent solutions.<br>For this challenge I chose the “Skyscanner” app not because the UI is especially better than it’s competitors but because it had the cheapest flights and did not require any registration for access, which I consider a huge plus.</p><h3><strong>Research</strong></h3><p>As a scenario for my research I chose a twenty-something backpacker, who’s dream is to see the Tajmahal in Agra, India. He has three weeks of vacation from Jan. 21 till Feb. 11. and wants to book a hostel for his first 3 nights in Agra. His top priority is low price.</p><p>One research unit was separated into three blocks:</p><ol><li>The 5 second tests</li><li>Using the app as the backpacker. (The test subject is using the app, while I record the screen)</li><li>Interview</li></ol><p>The results showed two main pain points:</p><p><em>a.)</em><strong><em> </em></strong>Users often had problems finding the filter settings on the hotel-screen and therefore simply did not use them. Instead they spent a lot of time scrolling, searching visually for the cheapest options.</p><p>b.) Users complained about the “share” button on the flight-screen because it was overlapping the price of the last search result, blocking it from view.</p><h3><strong>Solutions</strong></h3><p>Since my subjects where overall very content with their experience of the app I wanted to avoid changing the user flow too much. Instead I simply relocated two specific buttons and redesigned one of them two solve the two pain points mentioned above.</p><p>Ad a.)</p><p>The button for filter settings on the original hotel-screen is located on the very bottom of the screen. It is shaded an therefore barely visible. To solve the issue I made the search bar for the location a bit smaller and was therefore able to fit in the standard icon for filter settings on the top right side of the screen while removing the original button completely. This way the filter settings are on one line with all the other search settings and clearly visible. In addition there is more space to view the search results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*CBc1BWr9Y_gXcJ7YNu5zyw.jpeg" /><figcaption>left: original, right: improved prototype</figcaption></figure><p>Ad b.)</p><p>To solve the issue of the share button blocking the price of the last search result I moved it to some available space in the head section of the screen without changing any other part of the UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*Pr-CjnhKJD1b91qYX3TtYw.jpeg" /><figcaption>left: original, right: improved prototype</figcaption></figure><h3>Lessons Learned</h3><p>This challenge taught me that no design is perfect and that there is always room for improvement. It was a chance to put together all parts of the knowledge that we had acquired so far like: design thinking, UI design and UX research.</p><p>I found it especially interesting to see how different angles of research (interview + 5 second test + user testing) on the same person can give you a much deeper insight into a problem instead of just one angle. For example, I was able to witness the problem described in the interview first hand by watching the screen recordings later on.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af919e223628" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Bye, Ticket Machine]]></title>
            <link>https://paul-heuschmidt.medium.com/good-bye-ticket-machine-88316a7c6c3a?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/88316a7c6c3a</guid>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Tue, 21 Jul 2020 11:38:37 GMT</pubDate>
            <atom:updated>2020-07-21T11:38:37.875Z</atom:updated>
            <content:encoded><![CDATA[<p>“Citymapper” is an app that allows you to find your away around a city, showing you which options for transportation are available. But there is one thing lacking, users still have to buy the necessary tickets physically or through the local public transportation company by downloading another app.</p><p>As part of our Ironhack precourse, we were asked to come up with an additional feature for the Citymapper app that would allow users to buy the ticket on the app.</p><p><strong>Empathize and Define</strong></p><p>First, I sat down with five individuals of different age and background and asked them about the experiences with public transport abroad. How did they experience buying tickets? Was it easy? Was it not? What are the pain points? I discovered four main issues that they would want to be solved:</p><ol><li>Users do not want to register somewhere else. They do not want to share their email address with more parties than absolutely necessary.</li><li>Users want to limit physical contact to a minimum. In regards to the current pandemic limiting physical contact is a matter of reducing risk of infection, especially in high traffic public areas like train stations and around ticket machines.</li><li>Users want to save time. Buying tickets at a machine means queuing, figuring out which ticket to buy, how to operate the machine, dealing with system failure etc., which all eats up a lot of time.</li><li>Users want to bypass the language barrier of buying a ticket abroad. If you are not able to speak the language it can be very hard to acquire the ticket needed to get to your destination. Which also means that you lose a lot of time.</li></ol><p><strong>Ideate</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sZcM2UIi1jXyp2SRAZMYfQ.jpeg" /></figure><p>The next thing I did was brainstorming to solve these issues. I figured there were three possible solutions:</p><ol><li>Buy ticket in app and receive it in app.</li><li>Buy ticket in app and receive it via sms.</li><li>Buy ticket in app and receive it via email.</li></ol><p>The most elegant solution would probably be to get the ticket in your app. But since I was not exactly sure how that would work I went with a simpler approach and chose number three. The user would buy the ticket in app and receive it via email.</p><p><strong>Prototype</strong></p><p>At this stage I sketched out a very simplistic wire frame of how the interaction of buying the ticket could work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ssSwl20gkWdbHqDaI_emQ.jpeg" /></figure><p>When the user is looking for a connection from A to B he/she is given the option to buy the necessary ticket right there. If the “buy ticket” button is pressed the user is redirected to a list of possible ticket solutions. After picking the appropriate one he/she is asked to pay the ticket. The interaction ends with the system sending an email with the ticket attached and a screen informing and thanking the user pops up.</p><p><strong>Lessons Learned</strong></p><p>This exercise helped me to understand how important it is to conduct user research. The people I interviewed mentioned problems I would have never thought about on my own. Also the brainstorming helped me to identify multiple ways of solving the same issue.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88316a7c6c3a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Flow for Drunk People]]></title>
            <link>https://paul-heuschmidt.medium.com/user-flow-for-drunk-people-8fea5d3045b5?source=rss-8fee13f5bc03------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fea5d3045b5</guid>
            <category><![CDATA[ironhack-prework]]></category>
            <category><![CDATA[wireframing]]></category>
            <category><![CDATA[ironhack-berlin]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Paul Heuschmidt]]></dc:creator>
            <pubDate>Thu, 16 Jul 2020 11:26:21 GMT</pubDate>
            <atom:updated>2024-01-11T13:56:11.176Z</atom:updated>
            <content:encoded><![CDATA[<h3>User flow after a long night out</h3><p>I am attending a ux/ui bootcamp organised by Ironhack. Part of our precourse was to reverse engineer the user flow of an app of our choice. I went with Uber. Why? Because, let’s face it, a lot of people that use Uber are doing so, because they are unable to drive home safely themselves. So i asked myself, how do you interaction design for drunk people?</p><p>Well, you want the experience to be unchallenging, the screen to look underwhelming and easy to process. That means high contrast colors, large fonts, few buttons.</p><p><strong>The User Flow of Getting Your Keys Back</strong></p><p>So let us imagine someone gets home with an Uber, but shortly after the Uber has left, he notices that his keys are still in the car. So he opens the Uber app again. His goal is to get in touch with the Uber driver in order to get his keys back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYzHjhE8jofpP_gwKR_HtA.png" /></figure><p>On the first screen he will choose the options button, easily visible in the upper left corner. This button will lead him to his account screen where he presses on “previous rides” to see all the rides he did in the past. After choosing his last ride he will be brought to a forth screen. This one is larger and therefor scrollable compared to the last three. Under the header reading “Problems with the ride and refund” he will find a text saying “I lost something”. If he clicks on that he will be lead to the “help” screen where he is given the choice to contact the driver. On the last screen he is asked to provide his phone number so that he can be connected with the driver.</p><h3><strong>The Wireframing Challenge</strong></h3><p>This challenge helped me learn more about Figma and especially it’s prototyping tool. I quite enjoy building screens and this challenge gave me a chance to concentrate on the composition solely. I found that Uber did a great job at keeping the screens simple. It was not necessary to remove much from the original design to end up with a bare wireframe. With that in mind i think it is fair to say that their designs are very much drunk proof.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fea5d3045b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>