<?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 Alexander Assmann on Medium]]></title>
        <description><![CDATA[Stories by Alexander Assmann on Medium]]></description>
        <link>https://medium.com/@alexander.assmann91?source=rss-b89851071367------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*LQecry7q7i06ugt_.jpg</url>
            <title>Stories by Alexander Assmann on Medium</title>
            <link>https://medium.com/@alexander.assmann91?source=rss-b89851071367------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:50:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexander.assmann91/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[Wellness App — A Case Study]]></title>
            <link>https://medium.com/@alexander.assmann91/wellness-app-a-case-study-bf4355bfaa43?source=rss-b89851071367------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf4355bfaa43</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[food-allergies]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[food-intolerance]]></category>
            <dc:creator><![CDATA[Alexander Assmann]]></dc:creator>
            <pubDate>Sun, 26 Jan 2020 21:14:42 GMT</pubDate>
            <atom:updated>2020-01-26T21:14:42.767Z</atom:updated>
            <content:encoded><![CDATA[<h3>Wellness App — A Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p29pRqt9Owm8bdb2NpsE0A.jpeg" /></figure><p><strong>BRIEF</strong></p><p>The goal of the project was to create an application, starting from a broad topic in the realm of wellness and generating ideas through user research.</p><p>I chose physical wellness and more specifically allergies and intolerances as a subtopic of physical wellness.</p><p><strong>SUMMARY</strong></p><p>On this project, I worked on gathering insights by conducting user interviews. Compressing all of these insights into realistic personas, helped me to find solutions based on my insights of real people’s problems. After creating personas I designed prototypes and tested them and refined them based on feedback by potential users.</p><h3>Find Struggles by Interviewing</h3><p>As a person who doesn’t have any allergies or intolerances, the first thing I wanted to do was to find out as much as I could about situations in people’s lives where intolerances or allergies impacted them negatively in any way.</p><p>For this purpose, I conducted generative user interviews with the main focus on getting stories from people. This is one of the most effective ways of being able to empathise and understand not only problems but also the context around them.</p><p>In a total of 14 interviews, spread over two rounds I collected the most important problems that people with allergies had. I focussed on food allergies and intolerances, as these seemed to be the most concrete and tangible issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAqPkavdlrZNSiDPd5re_Q.png" /></figure><h3>Create Personas by Condensing Insights</h3><p>Personas are a great tool for compressing research information in a way that makes it easier to understand and empathise with the people and their problems. They can be created by taking into account and filtering all the data gathered during the interviewing phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*Ug_2KBCDdJRmdIbD9p542A.png" /></figure><p><strong>Ulrike, 48 — The Guest</strong></p><p><em>“I love eating at restaurants, but I’m always worried about whether there is something in the food that I’m allergic to.” — Ulrike</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/314/1*z30H-gTnTf0Z-2SjkYrCww.png" /></figure><p><strong>Jordi, 37 — The Waiter</strong></p><p><em>“I want to give each customer the attention they deserve, but I also don’t want to keep other customers waiting for too long.” — Jord</em>i</p><h3>Formulate a Problem Statement</h3><p>Keeping the personas and all the previous insights in mind, a problem definition can be created in order to have a clear statement in mind against which possible solutions can be tested.</p><blockquote>As a restaurant guest abroad, I want to be sure that my food is free of allergens, so that I don’t have any allergic reactions to it.</blockquote><h3>Ideate and Create Prototype</h3><p>When coming up with new designs, the most important thing to keep in mind are the insights gathered in the initial user research stage. These insights directly represent problems that people have and that could be addressed in a new product.</p><p>Since people complained about ingredients, that they might be allergic to not being listed, the idea of creating a communication interface with the waiter came up.</p><p>Since waiters often feel stressed and do not have a lot of time, one screen contained all the information they needed.</p><p>Since people felt like they could not always communicate well with waiters, the information in the waiter’s language was automatically generated from the allergy information provided and three simple options<strong> </strong>were given for the waiter to communicate back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQ65yfJXgr3Quf3IzjASuw.png" /><figcaption>First prototype</figcaption></figure><h3>Test &amp; Iterate with Personas In Mind</h3><p>One of the reasons for creating the personas was that they can easily be reused to give a realistic scenario in user testing with prototypes. This scenario can be given to testers in order to immerse them more into a vivid situation, in order to spot problems that might occur earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jqeTs7kR1eUWjhO-k1uiw.png" /><figcaption>The scene of the scenario</figcaption></figure><blockquote>You are Ulrike, 42 from Germany on a holiday trip to Spain, you’re travelling alone and you’re currently in a small village close to Barcelona looking for food.</blockquote><blockquote>You found a restaurant and went inside, you realise nobody speaks English or German, you sit down and pick Paella from the menu (Since it’s one of the dishes you actually know).</blockquote><blockquote>Unfortunately, you are allergic to Gluten and Milk and you want to communicate that to the waiter to make sure you’re not eating anything that’s bad for you.</blockquote><blockquote>The waiter is coming up to you.</blockquote><p>After giving this scenario and the paper prototype to 6 people in order to see where problems would occur, some changes were made, informed by the feedback given by the testers.</p><p><strong>Improvements</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*edvb0JKoeo5xxzPDVsA0-w.png" /><figcaption>Improvements on Allergy Info Screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2fNEh1MA20G102oX0RkYw.png" /><figcaption>Improvements on Waiter Info Screen</figcaption></figure><p><strong>Check out the </strong><a href="https://sketch.cloud/s/jDRma/a/dn9oQb/play"><strong>Final Prototype</strong></a><strong>.</strong></p><h3>Outlook</h3><p>As the time scope of this project was limited, a mid-fi prototype was the final deliverable. In case more time was given I would have created tested with more different user flows, such as a waiter having to ask in the kitchen and then needing to communicate possible other options afterwards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf4355bfaa43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good & Bad User Experiences]]></title>
            <link>https://medium.com/@alexander.assmann91/good-bad-user-experiences-a441271abcd7?source=rss-b89851071367------2</link>
            <guid isPermaLink="false">https://medium.com/p/a441271abcd7</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[nielsen-heuristics]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Alexander Assmann]]></dc:creator>
            <pubDate>Sun, 12 Jan 2020 23:22:43 GMT</pubDate>
            <atom:updated>2020-01-12T23:22:43.834Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone has these moments, where using something just feels effortless, sometimes we don’t even notice when a user experience is good, because it feels natural.</p><p>On the other hand bad experiences can frustrate us, and when thinking about it, I bet you could come up with a few in just a couple of minutes.</p><p>I will tell you about some good and bad user experience that I had and I’ll relate them to the Nielsen Heuristics in order to try to understand what makes good and bad design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z2GVCQQazQXU30FXYmGWTw.png" /><figcaption>Nielsen Heuristics</figcaption></figure><h3>Good Experiences</h3><h4>Bunq — Registration Process</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBteFwevf0xQQh2ymC1yOQ.jpeg" /><figcaption>Nielsen Heuristic: Flexibility &amp; Efficiency Of Use</figcaption></figure><p>Bunq is an online bank founded in 2012 in the Netherlands. Designers seem to be at the heart of the company as every experience I have had with their application has been a joy. I was especially delighted by the registration flow, when I opened my account. I expected having to send proof of ID via post and waiting multiple weeks until my account would be available, as it has happened to me in the past.</p><p>Instead I had my international bank account open in just over 5 minutes. I had to provide my data, show proof of ID and fingerprints and go through a video face recognition process and that was it. There’s no comparing this to any of the more traditional banks.</p><h4>Google Flights — Map Exploration Feature</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BARN3dfyTsGFQSCku7akjg.png" /><figcaption>Nielsen Heuristic: User Control &amp; Freedom</figcaption></figure><p>When I first found out about the Google Flights Map Exploration feature it completely changed the way I was travelling. Instead of deciding for a place I wanted to go ahead of time and then picking out flights and checking the prices, I just looked at a map of Europe and saw possibilities that I didn’t even think about in the first place.</p><h4>Apple — Wifi Sharing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Z5os5WFpIiYRodTQoPT2w.jpeg" /><figcaption>Nielsen Heuristic: Flexibility &amp; Efficiency Of Use</figcaption></figure><p>Everyone knows the experience of going to a friend’s place and asking for Wifi, going to the router, typing in a long password only to realise that you must have misspelled something, since you can’t connect. With Mac and iOS users can just easily share passwords by holding phones together and tapping a button.</p><h3>Bad Experiences</h3><h4>Peugeot 206 — Adjusting a seat’s position</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*AH_Il7T5vJ6kOKKmiwv9XQ.jpeg" /><figcaption>Nielsen Heuristic Violated: Consistency &amp; Standards</figcaption></figure><p>I drive an old Peugeot 206, I’m not the biggest car fanatic, but I like my car. Apart from one thing. Everybody who uses my car gets the direction in which they have to push or pull the lever that adjusts the passenger’s seat position wrong. This was very interesting to me, since the lever itself has writing on it, which actually tries to explicitly tell you how to use it. However since most cars work differently, people just assume they already know what’s write and immediately pull the lever instead of pushing it.</p><h4>Bins with small openings</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*y4gNLLSWLJD0jIOqm7T8ZA.jpeg" /><figcaption>Nielsen Heuristic Violated: Flexibility &amp; Efficiency Of Use</figcaption></figure><p>At my parents’ house there’s a bin that frustrates me every time I use it, the opening isn’t big enough to empty food remains from a large plate in it and on top of that you can’t open it with your foot, so you have to awkwardly balance whatever you have in your hand while opening the lid with your other hand, which is less than sanitary.</p><h4>Bosch — Dishwasher Silence Plus</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*9kfJRwku5g2ZjUPdSWp3TA.jpeg" /><figcaption>Nielsen Heuristic Violated: Help &amp; Documentation</figcaption></figure><p>I recently got a new dish washer, which is great in almost every aspect. I would be really happy if it wasn’t for the fact that the first time I tried to turn it on in Silence mode, it took me more than half an hour to figure out what to do. I read through the instructions manual, which was cryptic, I tried to make a connection between the buttons I was seeing and what I was reading. It turns out the instruction manual wasn’t only specifically for this kind of machine and the dish washer doesn’t have a Silence mode, but runs quiet by default.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a441271abcd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge: Creating Wireframes for the Duolingo Stories Feature]]></title>
            <link>https://medium.com/@alexander.assmann91/challenge-creating-wireframes-for-the-duolingo-stories-feature-c055fa87f32f?source=rss-b89851071367------2</link>
            <guid isPermaLink="false">https://medium.com/p/c055fa87f32f</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[sketch]]></category>
            <category><![CDATA[duolingo]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alexander Assmann]]></dc:creator>
            <pubDate>Sun, 12 Jan 2020 21:29:07 GMT</pubDate>
            <atom:updated>2020-01-12T21:37:44.987Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNrcIkqQZrCTidkwUDKoRw.png" /></figure><p>I really enjoy language learning, I think it’s a great way to connect with people from all around the world and learn about different cultures. There are many apps and websites dedicated to helping people on their language learning journeys, and one of the most famous ones is Duolingo.</p><p>Duolingo added, in my opinion, one of their best features yet with the Stories feature. A user can read a story in their target language while always having the option to look up words and being regularly quizzed on whether they actually understand what they are reading, thus making the whole experience very engaging and efficient.</p><h3>Wireframing</h3><p>As a challenge for the Ironhack UX/UI bootcamp I’m attending, I created wireframes for this flow. When wireframing an already existing app, one of the main concerns is to filter out which information is useful and which isn’t visually.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GCMgoAzZ7uRZN2KB66QdnA.png" /><figcaption>The “Stories” flow, mostly consisting of icons, buttons, checkboxes and text</figcaption></figure><p>In this particular user flow, as well as with the Duolingo app in general, I noticed, that the creators are relying heavily on icons, which made the wireframing experience interesting, as I had to always decide whether to include an icon in higher fidelity or just add it as an abstract shape.</p><p>Finally, I created a prototype from these wireframes, which you can try <a href="https://sketch.cloud/s/r0pDP/a/Jdomz5/play">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E1PYUpQf9_Rm2ktD6jZEUQ.png" /></figure><h3>Learnings</h3><p>Instead of using Invision to create the prototypes, I used the Sketch prototyping functionality that was added in version 49. While I like the integrated experience in Sketch, which reminds me of my Figma workflow, I also noticed the shortcomings of this approach. One thing I wasn’t able to implement without the use of Plugins was a hovering state, which would have been necessary to highlight the possibility of users to look up words as they read the story.</p><p>Therefore the next time I will create a similar prototype, I’ll give Invision a go.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c055fa87f32f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge: Redesign a Trip Booking Site]]></title>
            <link>https://medium.com/@alexander.assmann91/challenge-redesign-a-trip-booking-site-aebcd28605aa?source=rss-b89851071367------2</link>
            <guid isPermaLink="false">https://medium.com/p/aebcd28605aa</guid>
            <category><![CDATA[kayak]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Alexander Assmann]]></dc:creator>
            <pubDate>Thu, 09 Jan 2020 17:24:10 GMT</pubDate>
            <atom:updated>2020-01-09T17:24:10.816Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>The third challenge I faced as part of my Ironhack UX/UI design course was to find and fix pain points in a popular trip booking site.</p><h3>Process</h3><p>The challenge consisted in picking a user type among various groups of people who would use various trip booking sites and to then find and have an interviewing and mobile web site testing session with three different users.<br>In these testing sessions users had 5-seconds to look at the screen and subsequently had to recollect as much information as possible from it.</p><p>After selecting a mobile site suitable for the user type (Kayak) for in-depth analysis, the users were given a task, in this case to travel to South America, and a budget. I asked the users to think out loud, so that it would be easier for me to take notes on what they were doing and how they were processing the information they were seeing.</p><p>As a result of observing the users while they were trying to finish the task, I was able to find the main pain point, that made it harder for people to finish their tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7-XVNSa9Bg5P1vWCvXyjZA.png" /><figcaption>Before changes</figcaption></figure><p>All users tried to first type in South America into the flight search field, which didn’t help them, because there was no option to see all flights in a specific region. Then all users resorted to picking a random location in South America, which led to a big variety of prices users would have had to pay for a flight.</p><p>Since I had used Kayak before, I was aware that the site has an Explore feature, which shows users the cheapest prices for many cities at once on a map.<br>I therefore decided to help users who didn’t know exactly where they were going by making the Explore feature more easily accessible.</p><p>After thinking about different options how I could do that, like making the button to reach the feature more prominent, I decided to include it into the Destination Search flow, since there was still a lot of space unused. Instead of adding a link, I opted for showing the map immediately, in order to communicate the concept visually to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cnbxacckWFHpHjkjVseSRQ.jpeg" /><figcaption><a href="https://sketch.cloud/s/wjPow/a/nnZvdg/play">Click here to try the prototype</a></figcaption></figure><p>After creating my solution by creating a wireframe prototype in sketch, I gave it to two of the users who had previously tested the site before, and worked in their feedback, which was mainly about removing parts of the prototype, which didn’t have to do with the added feature.</p><h3>Learnings</h3><p>To conclude, I took a lot away from this challenge about how to conduct testing sessions and how to create wireframes and especially prototypes with Sketch. The most interesting part of the task for me was to conduct the 5-second tests with people, I tried this out with many different apps, since I’ve finished this challenge and found it surprising, how many apps out there could be completely misinterpreted, if you just have 5-seconds to look at them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aebcd28605aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Challenge: Designing a Ticker Buying Feature for Citymapper]]></title>
            <link>https://medium.com/@alexander.assmann91/challenge-designing-a-ticker-buying-feature-for-citymapper-bc911eb03eb5?source=rss-b89851071367------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc911eb03eb5</guid>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[citymapper]]></category>
            <dc:creator><![CDATA[Alexander Assmann]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 18:26:00 GMT</pubDate>
            <atom:updated>2020-01-07T18:26:00.480Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of a challenge for my upcoming Ironhack bootcamp I started designing a ticket buying feature for the Citymapper app.</p><p>Citymapper is an app that helps people to find the best connection to where they want to go. It shows different options, how long each takes and how many changes you need to do while you travel, allowing users to have a stress-free trip.</p><p>The first thing that I did was making sure to get input from people who would be potential users of Citymapper to find out the pain-points and what people want in an app like this. After designing an interview guide and interviewing a few of my friends a few main problems crystallised regarding transport tickets:</p><ul><li>People aren’t sure about what kind of tickets they need to buy</li><li>People want to feel sure, that they did everything right in the process (i.e. validating)</li><li>People don’t like waiting in line or using machines with bad interfaces</li></ul><p>After consolidating these pain points from all the interviews, I started creating a problem statement to identify which main problem I am trying to solve.</p><p><strong>As a traveller using public transport abroad, I am often unsure about which tickets I need to buy in order to take my trip.</strong></p><p>After writing down the problem statement I started ideating about different solutions, focussing on what I learnt from the interviews I held. One of the ideas was to have a button to buy tickets for each individual trip, another one was that users could buy a long-term subscription “All-in-one pass” in order to never have to worry about anything related to ticketing.</p><p>In the end I decided to pick the solution in which users could pay for the tickets necessary for individual trips, as most interviewees described experiences about these situations to be most frustrating.</p><p>After that I took about an hour to start sketching on a paper prototype, which I then tried out with two people in order to see how understandable and intuitive my solution was.</p><figure><img alt="A paper-prototype for a new pricing feature for the Citymapper app" src="https://cdn-images-1.medium.com/max/1024/1*Zk0IiGSl95hZ1u0NOqcIwQ.jpeg" /><figcaption>Paper prototype</figcaption></figure><p>All in all the experience was very helpful to make help me understand various aspects about the design process.</p><p>I learnt for instance, that it is better to ask open-ended questions and to have a conversation in a user interview rather than having a catalogue of questions to ask robotically. I had an especially hard time not interrupting people when there were longer pauses, but as I got better with each interview, I noticed how much more information people would be able to share, if I just didn’t interrupt them.</p><p>It was also hard to focus on just one problem statement instead of trying to fix all problems at once.</p><p>And finally, writing this blog post was also very helpful, as I hadn’t written any essays in a while.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc911eb03eb5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>