<?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 Oliver Simpson on Medium]]></title>
        <description><![CDATA[Stories by Oliver Simpson on Medium]]></description>
        <link>https://medium.com/@Alfher?source=rss-d389db375659------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vMK7vy8NEYEwvXwyFyLKrQ.jpeg</url>
            <title>Stories by Oliver Simpson on Medium</title>
            <link>https://medium.com/@Alfher?source=rss-d389db375659------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:29:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Alfher/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[UX case study: Entrelp (app) redesign]]></title>
            <link>https://medium.com/@Alfher/ux-case-study-entrelp-app-redesign-f26bf58d8855?source=rss-d389db375659------2</link>
            <guid isPermaLink="false">https://medium.com/p/f26bf58d8855</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Oliver Simpson]]></dc:creator>
            <pubDate>Wed, 07 Feb 2024 16:03:47 GMT</pubDate>
            <atom:updated>2024-02-11T14:24:01.641Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX case study: Entrelp redesign</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*65Mis_jsjFnz0t_3yFflhA.png" /></figure><h3>Platform (app) and Team</h3><p>Entrelp is an occasional jobs (online) platform based in France. For the last project of the (9 week) Ironhack UX/UI design program, I teamed up with Pauline Legros and Maddalen Miner to redesign the Freelancer experience of the Entrelp Platform. We did this in collaboration with Romain Serre, the Founder and CEO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4lS403ZHnMEyOcaNF8Ddw.png" /></figure><h3>Context</h3><p>Did you know?</p><blockquote>In the last 8 years, temporary, freelance jobs in France have risen by 1800%</blockquote><p>That’s a big rise, and you might be wondering, how did that happen? Here’s how:</p><p>The 2008 economic crisis, and more recently the COVID pandemic, caused a shift in the way companies operate. Many adopted more flexible hiring practices, which led to an increase in demand for temporary staffing. These companies now hire workers as needed, which allows them to quickly scale up or down, depending on demand.</p><p>In parallel, the gig economy has exploded. We’re talking about short-term, intermittent jobs. Temporary workers (or ‘freelancers’) take on these kinds of jobs on a flexible basis, without the need to commit to any long term contracts. This provides freelancers greater autonomy in choosing when they work, what kinds of work they do, and who they work for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0kYVvBexuata4a3IiRpq-Q.png" /></figure><p>Students in particular are keen to do these kinds of jobs as they provide a way to earn money while balancing busy schedules. According to a trusted source, 40% of students are doing occasional jobs alongside their studies. 65% of them are seeking greater financial independence, and 75% are seeking professional experience, which can help them secure a more permanent role in the future.</p><h3>Market Positioning</h3><p>There are a handful of competitor platforms that offer similar services. These include Student Pop, Extracadabra, and StaffMe. StaffMe, which provides the same service to the same target market, is Entrelp’s main competitor. However, while StaffMe operates primarily in the North of France, Entrelp, which is based in Marseille, is primarily targeting employers and freelancers living in the South.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OGHZg40JxW19tHN0gjEeQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ej2k6LeB8BnNGrmvwFRf1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ObEHUk2Z0Yj23SGo-OZDKg.png" /></figure><h3>Value Proposition</h3><p>Entrelp also seeks to distinguish itself by selecting only the most skilled, reliable, and experienced freelancers. At the same time they seek to attract high quality employers that offer a good employment experience. This encourages freelancers to stay on the platform and take on more jobs (or ‘missions’) more often.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*22Qr4QFRNL6zYge_u7iiYw.png" /></figure><h3>Entrelp before redesign</h3><p>This is what the Freelancer experience currently looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kzAOfCF0xzO87PtITvjPGQ.png" /></figure><p>As you can see it’s quite basic. The essential functionality is provided, but there are many usability issues and the visual design does not reflect the values of the company, which are: Trustworthy, Reliable, and Resilient. It didn’t take long for our team to see the UX of this app could be greatly improved.</p><h3>Stakeholder Meeting</h3><p>During the stakeholder meeting, Romain provided us with an objective. This was: to reimagine the user experience of the Entelp platform for Freelancers, Employers, and The Internal Administration. We quickly decided it was impractical to try to tackle all three aspects of the platform, given our time restriction, so we decided to focus only on the Freelancer experience. Romain agreed.</p><h3><strong>Research</strong></h3><p>Having established and validated the objectives for this project, we were ready to flex our UI, UX muscles. The first thing we did, aside from secondary research, was to gather information from real people, people who have worked these kinds of jobs in the past. We interviewed 6 people and received 35 responses from our survey.</p><p>Here are a few quotes from the interviews:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*53sBSeQohQUXbthzlVEDhw.png" /></figure><p>And here are some insights from the survey (demographics, motivations, and challenges):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1C7ozFpi3VEE6HSgQ5VCw.png" /></figure><h3><strong>Persona</strong></h3><p>Based on this information, we constructed our Persona, Sophie:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1mBj5khlo1vl7y46LN_JnQ.png" /></figure><h3>Problem Statement</h3><p>Our problem statement explains:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h1vZMQQoiPJHMJX1gVS1cw.png" /></figure><h3><strong>HMW</strong></h3><p>The problem statement prompts us to ask:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cLUVXXKMDEQS9jb5NSoy8A.png" /></figure><h3>Ideation</h3><p>With our problem statement defined, and our How Might We questions written, we began the ideation process. This involved listing the features we wanted to include and prioritizing them. We also decided to go with a mobile-first approach because most young people in France use their phones for this kind of task. After doing some hand-drawn sketches and concept testing we built the mid-fi prototype.</p><h3>Usability Testing</h3><p>The usability testing revealed some interesting insights:</p><ul><li>Some button names were not intuitive</li><li>There were too many sub-levels in the Profile section</li><li>We needed to add new tab for ‘Favorite Missions’</li></ul><p>Here’s a visual representation (with more insights):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40PIKyGTBtM0pByjVGj6gw.png" /></figure><h3>Visual Design</h3><p>Once we had established the structure, navigation, and interactions of the app, we were ready to apply a visual design treatment.</p><p>We made a Moodboard based on this 5 attributes (modern, minimalist, honest, young, and connecting):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dWtFgsmOc4a0MpIFaiAwkA.png" /></figure><p>And decided on colors, typography, and icons. We tried many color combinations; in the end we decided on Entrelp’s existing 3 colors (blue, red, and white) and added a (grey/light brown) color that can be used as a background or foreground fill.</p><p>We choose Poppins as our main Typeface because its rounded corners and balanced letter-forms suggest friendliness, accessibility, and reliability:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YRILgPidPrXfg66ppOAqUQ.png" /></figure><p>All that was left was to build the hi-fi prototype:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FJSWp7t7PDAV9Bfna0H1JFO%2F%255B-FP-%255D-%257C-Design-File---Team-6%3Fpage-id%3D16%253A322%26type%3Ddesign%26node-id%3D3052-4170%26viewport%3D-5713%252C-1450%252C0.21%26t%3DMXKcS25vPEUViLYb-1%26scaling%3Dscale-down%26starting-point-node-id%3D3052%253A4168%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FJSWp7t7PDAV9Bfna0H1JFO%2F%255B-FP-%255D-%257C-Design-File---Team-6%3Fpage-id%3D16%253A322%26type%3Ddesign%26node-id%3D3052-4170%26viewport%3D-5713%252C-1450%252C0.21%26t%3DMXKcS25vPEUViLYb-1%26scaling%3Dscale-down%26starting-point-node-id%3D3052%253A4168%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F9074e954-1305-45c7-bb3b-d410eaa1fe94%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/a7115dc4799f8f762ba8a83c18bc0231/href">https://medium.com/media/a7115dc4799f8f762ba8a83c18bc0231/href</a></iframe><h3>Next Steps</h3><p>Next steps include:</p><ul><li>Improving accessibility</li><li>More testing and refining</li><li>Developing the ‘Company’ and ‘Administrator’ experience of the platform</li><li>Launching the new design</li></ul><p>Thanks for reading!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aVnQTDOKYAPECEmKiimzYg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f26bf58d8855" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX Case Study: Stop Smoking app]]></title>
            <link>https://medium.com/@Alfher/ux-case-study-stop-smoking-app-bdcfdfb30573?source=rss-d389db375659------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdcfdfb30573</guid>
            <category><![CDATA[quit-smoking]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <category><![CDATA[stop-smoking]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <dc:creator><![CDATA[Oliver Simpson]]></dc:creator>
            <pubDate>Mon, 15 Jan 2024 16:29:09 GMT</pubDate>
            <atom:updated>2024-01-16T14:22:52.560Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX Case Study: Stop-Smoking app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apwd7jDJ-V_atMqHOYy4Nw.png" /></figure><p>There are 1.1 billion smokers on the planet. 70% are trying to quit. Only 8% will succeed.</p><p>Together with my teammates Jorge Garcia Formoso and Michel Dujardin, we set out design a digital service that could help people quit the habit. This project took 8 days. Tasks were distributed; each of us participated in UX and UI development.</p><p>We developed a unique solution based on research data, one that answered our problem statement:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gn50G2D0Xg30X77CjGq07w.png" /></figure><p>The solution is composed of three primary features: 1) <strong>A distraction device</strong> to help get through intense cravings. This is accessible from within the app or via an (external) widget. 2) <strong>A daily questionnaire</strong> that collects pertinent information about the user’s smoking-related experience for that day (urges, triggers, mood, behaviors, coping strategies, etc). This information is used to detect patterns and provide personalized feedback and recommendations for the user. 3) <strong>A chat feature</strong>, which allows the user to chat with an AI companion (i.e. a chat bot), a friend or quit buddy, or a medical professional.</p><p>All three features live in the Chat, which means all interactions happen in one place (making it easier for the user). Here they are in the prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GxJzXbAZdTAlkBfHxxWi9Q.png" /></figure><p>The other features are: an <strong>on-boarding </strong>flow (to gather initial data about the user), a <strong>dashboard</strong> (of quitting-related metrics), a <strong>calendar</strong> (to see the user-history), a <strong>journaling</strong> area, and a<strong> user-profile </strong>(and settings) section:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-CsYJ3SvhuDKogReLl-Rw.png" /></figure><h3>How did we get here?</h3><p>By following the UX Design Thinking process: <strong>Empathise, Define, Ideate, Prototype, Test</strong>. More precisely, and in the context of this project:</p><ul><li>Primary and Secondary Research</li><li>Data synthesis and Problem Definition</li><li>Persona Development</li><li>Ideation and Feature Prioritization</li><li>Mid-fi/Hi-fi Prototyping</li><li>Visual Design</li><li>Concept Testing</li></ul><p><strong>Secondary research</strong> revealed multiple factors contributing to smoking relapse: stress, emotional distress, social settings, nicotine withdrawal, weight gain concerns, alcohol consumption, hormonal fluctuations, and cultural factors.</p><p><strong>Interviews</strong> (with 9 ex-smokers) provided us with a lot of data regarding: commitment and preparation (for quitting), managing temptations, motivations (accountability and positive reinforcement), and ways to quit. Here are some of the data points that came out of the interviews:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gVJNeW-VUtYcyGSGUq5ueQ.png" /></figure><p>We identified 4 key factors for effective smoking cessation:</p><ol><li><strong>Commitment:</strong> the foundation of a successful quit journey is a person’s firm decision to quit.</li><li><strong>Coping Mechanisms:</strong> knowing how to effectively manage urges and resist temptations.</li><li><strong>Accountability:</strong> keeping track of progress and being held accountable.</li><li><strong>Positive Reinforcement:</strong> Regular updates of the progress and benefits of not smoking keeps people motivated to keep going.</li></ol><p>These factors would later inform our solutions, ensuring that we not only address the physical aspect of quitting smoking, but also the psychological and emotional aspects.</p><p>Before we dive into solutions, meet Emma, our persona:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zMRnPMhjuqo4B6iRXjH43w.png" /></figure><p>This is Emma’s journey (before she discovered our app):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wnDTlrobvu-GKIDtrvwoPw.png" /></figure><p>Having prepared our persona and user-journey, we were ready for the next phase:</p><h3>Ideation</h3><p>Each team-member wrote 8 ideas onto a virtual sticky note. Afterwards we grouped them into themes and voted on the themes (that represent features) we wanted to prioritize for development:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cuV4zGHAWaEk9I3VFSIyQ.png" /></figure><h3>Prototyping</h3><p>We took these ideas and transformed them into a coherent Mid-fi prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQSb1EV4qM3jcmLIwX4CVg.png" /></figure><h3>Testing</h3><p>We performed <strong>Concept Testing</strong> on the Mid-Fi with two target users. The feedback we got was very positive: they loved the distraction tool, the ability to chat with the AI companion, and the useful information about coping mechanisms and ways to identify craving-inducing triggers before they occur.</p><h3><strong>Visual Design</strong></h3><p>We started by creating two moodboards based on the following brand attributes:</p><ul><li>Empowering</li><li>Motivating</li><li>Inviting</li><li>Stable</li><li>Trustworthy</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXSPqCwF1HneEx6URuLl3A.jpeg" /></figure><p>… And chose the second one (on the right-hand side), which we felt best reflected the brand attributes. We also created a Style Tile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5DCmMDy9obyvhF33daE8w.png" /></figure><p>And finally, we built the Hi-fi prototype:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.figma.com%2Fembed%3Fembed_host%3Doembed%26url%3Dhttps%3A%2F%2Fwww.figma.com%2Fproto%2FNlbYl6LIfOtnU3KjmAIBf6%2FTeam-1-Design-File-%255B-P4-%255D-%25E2%2580%25A2-Jorge%252C-Oliver%252C-Michel%3Fpage-id%3D116%253A21%26type%3Ddesign%26node-id%3D2338-7299%26viewport%3D495%252C372%252C0.03%26t%3DqdvvHtJVYou7iORJ-1%26scaling%3Dscale-down%26starting-point-node-id%3D2338%253A7299%26mode%3Ddesign&amp;display_name=Figma&amp;url=https%3A%2F%2Fwww.figma.com%2Fproto%2FNlbYl6LIfOtnU3KjmAIBf6%2FTeam-1-Design-File-%255B-P4-%255D-%25E2%2580%25A2-Jorge%252C-Oliver%252C-Michel%3Fpage-id%3D116%253A21%26type%3Ddesign%26node-id%3D2338-7299%26viewport%3D495%252C372%252C0.03%26t%3DqdvvHtJVYou7iORJ-1%26scaling%3Dscale-down%26starting-point-node-id%3D2338%253A7299%26mode%3Ddesign&amp;image=https%3A%2F%2Fapi-cdn.figma.com%2Fresize%2Fthumbnails%2F9c255ce9-3639-4798-8ef0-24ef7697a42d%3Fheight%3D450%26bucket%3Dfigma-alpha&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=figma" width="800" height="450" frameborder="0" scrolling="no"><a href="https://medium.com/media/6604aef7ed276cc512829d432e6c0223/href">https://medium.com/media/6604aef7ed276cc512829d432e6c0223/href</a></iframe><h3>Next steps</h3><p>Due to the severe time-constraints we did not have time to usability (and desirability) test the prototype. This would have provided invaluable feedback that we could use to improve the experience.</p><p>I would love to develop and launch this app as I feel it has intelligent and well-designed features that respond well to the problem-statement. I also feel the research we did was solid and the problem was well defined.</p><p>A future version of this app could include an entirely new app for healthcare professionals, which would allow them to track the progress of their clients (the people on their quit-smoking journey) and interact with them seamlessly.</p><h3>Reflections</h3><p>This was a challenging project as addiction is complex, not easily solved. However I feel the product we developed was high quality: the ideas were good and based on a well-defined problem. The idea development was also important, in order to take ideas from ‘basic’, or ‘floating’ ideas to fully-developed, ‘integrated’ ideas. Again, it’s a shame we didn’t have time to perform more tests.</p><p>I enjoyed working with Michel and Jorge: they have advanced skills in Research, Storytelling and Analytic Reasoning, and Ideation and Rapid-Prototyping respectively, and they were a pleasure to work with. I learned a lot from them.</p><p>It was a great experience. I would love to take it further and see if it actually helps people quit smoking.</p><p>Thanks for reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdcfdfb30573" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Keep (app) : feature improvements]]></title>
            <link>https://medium.com/@Alfher/google-keep-app-feature-improvements-168d8ecdfdd0?source=rss-d389db375659------2</link>
            <guid isPermaLink="false">https://medium.com/p/168d8ecdfdd0</guid>
            <category><![CDATA[google-keep]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[heuristic-evaluation]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Oliver Simpson]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 16:17:10 GMT</pubDate>
            <atom:updated>2023-12-18T19:12:16.816Z</atom:updated>
            <content:encoded><![CDATA[<h3>Google Keep (app) : feature improvements</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIJC0P8I55L_izw-RDxgjw.jpeg" /></figure><p>My teammate Prateek and I set out to see if we could find areas of improvement in Google Keep. For those of you who are not aware, Google Keep is an app available on Android, iOS, and web that is made for taking (and keeping) notes. It offers relatively advanced (and useful) functionality while offering a simple, easy-to-use UI, making it an excellent app. However, despite it’s many qualities, we were able to identify several areas of improvement, as I shall now demonstrate.</p><p>First we conducted a heuristic analysis, following Jackob Neilsen’s heuristic evaluation criteria:</p><blockquote>#1: Visibility of system status<br>#2: Match between system and the real world<br>#3: User control and freedom<br>#4: Consistency and standards<br>#5: Error prevention<br>#6: Recognition rather than recall<br>#7: Flexibility and efficiency of use<br>#8: Aesthetic and minimalist design<br>#9: Help users recognize, diagnose, and recover from errors<br>#10: Help and documentation</blockquote><p>The heuristic evaluation revealed the following:</p><blockquote>#2: Match between system and the real world<br>#3: User control and freedom</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*_Ry0HNK6usHpXsU5tXk-Ig.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QwXKLENTNpSb_3MGrUFmVg.jpeg" /></figure><blockquote>#7: Flexibility and efficiency of use<br>#8: Aesthetic and minimalist design</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3oJplegPLtbIDdjIZ0jt6A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w6ndEREjlEIyWFLty8QZVQ.jpeg" /></figure><p>Having evaluated the app against these evaluation criteria, we then searched Google Keep reviews on the Play Store to see if users were talking about these features (or lack of). We found reviews that corresponded directly to our heuristic evaluation results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IhgK5veCxiMLeC5xYnWK-Q.jpeg" /></figure><p>This gave us the confidence that we were moving in the right direction. To help us define the problem, we wrote a problem statement, one for each feature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X1rWJJq9R1dShtJ6bZetLA.png" /></figure><p>Having defined the problem, the next step was to sketch solutions to these problems:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4FFu9LcfjD9j2ohQL9kvwQ.png" /></figure><p>Once we had a clear idea of how the solutions would work, we set about building hi-fidelity prototypes, using Figma. Below are three solutions to the problems we identified:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6p1fnUkeNeIvRAs3KoJ66g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S1u1ZbHioywuPuI3EeDv-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*314EwnQI6FVyJb1t2wW7gA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEp5vkmZgbjGaJ9Nx65h5g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WI6UnRYbI3ZABDc_oSAtCA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHzBsSmVz7phe-er_HeH1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jD1G1hFI-Glvp4q8fFGGDg.png" /></figure><p>In conclusion, we are happy with the solutions we developed in response to our problem-statements. We are eager to test these solutions and make appropriate modifications.</p><p>I hope you enjoyed reading this article. What do you think? Please leave comments below. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=168d8ecdfdd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[E-commerce redesign: Odradek bookshop]]></title>
            <link>https://medium.com/@Alfher/ih-p2-e-commerce-odradek-bcdc71e4e3f5?source=rss-d389db375659------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcdc71e4e3f5</guid>
            <category><![CDATA[bookshops]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <dc:creator><![CDATA[Oliver Simpson]]></dc:creator>
            <pubDate>Sun, 17 Dec 2023 14:55:01 GMT</pubDate>
            <atom:updated>2023-12-18T19:13:02.760Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX case study : <strong>Odradek (</strong>e-commerce <strong>bookshop)</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SDYnBwNo1hv4IPe3fA-Twg.jpeg" /></figure><p>Odradek is a small, independent bookshop in Schöneberg, Berlin. While the physical bookshop has a reliable customer base, their e-commerce website is basic and lacks advanced features that would make it useful and engaging. Our brief was to redesign the site and deliver an experience that keeps it’s customers coming back. Our design team was composed of myslef, <a href="https://medium.com/@alina.aleksandrovna">Alina Aleksandrovna</a>, and <a href="https://medium.com/@lara.plumbohm">Lara Plumbohm</a>.</p><p>Our Stakeholder, Pauline (who works at Odradek) says:</p><blockquote>We offer a diverse range of alternative books and a large children’s section</blockquote><blockquote>65% of our customers are women, mostly between the ages of 30 and 45</blockquote><blockquote>People like to go there because we curate books for their target audience</blockquote><blockquote>We strive to maintain quality rather than just following trends</blockquote><p>We proceeded by conducting extensive primary research (6 user-interviews, and 34 survey respondents). Here are some of our findings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oy6NfsKMVjU6u9O-pWtPzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j_NJpcfucS--WMjKHx0Spg.jpeg" /></figure><p>By synthesizing the data we discovered that the most significant <strong>problem</strong> is:</p><blockquote>Socially-conscious book enthusiasts are frustrated by the <strong>lack of human connection</strong> on bookshop websites</blockquote><p>… Our <strong>solution</strong> is:</p><blockquote>Provide quality <strong>personalized book recommendations to </strong>socially-conscious book enthusiasts <strong>on the website</strong></blockquote><p>Based on this data, we created Emma, our primary persona, who would help give our product development a clear direction:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rSsk9X7JRQO9-KRoUUWhBg.jpeg" /></figure><p>Some highlights are:</p><ul><li>Emma wants personalized book recommendations based on her reading preferences, similar to the assistance she receives from the staff in a physical bookstore</li><li>Emma would like a browsing experience on the website that allows her to discover new books and authors</li><li>Emma would like to discover new books that align with her interests and preferences</li></ul><p>We also create a user-journey map for Emma:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fkNI4W-3YIcSb216gA2jxw.jpeg" /></figure><p>This helped us define our “How Might We” questions:</p><blockquote>How might we improve the online recommendations to better fit the needs of our users?</blockquote><blockquote>How might we give digital assistance to our users looking for new books and genres?</blockquote><blockquote>How might we create an online bookshop experience similar to the experience in a physical bookstore?</blockquote><p>Based on this information we started to sketch out ideas. Here is one that stuck:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZ2Mx04ynQLZveJ_CjpkCA.jpeg" /></figure><p>It’s a digital book recommendation feature. The digital assistant will ask you a series of questions about what kind of books you are looking for, and will provide a set of three books that it thinks you will like. We would later name this feature Book Buddy.</p><p>With our special feature in mind (one that will solve Emma’s pain point), we started to build the mid-fi prototype. Here are the Book Buddy and ‘Single Book’ screens:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fPvFFu4GYLANjwYzesRH1Q.jpeg" /></figure><p>We then developed a visual language for the site. Here a some characteristics, colors, buttons, icons, and fonts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EA589Z0kpsuRYAeUTS5BiQ.jpeg" /></figure><p>After usability testing the mid-fi, making adjustments, and incorporation the new visual direction, we developed the hi-fi prototype. Here is the hi-fi version of the Single Book page displayed on Laptop and mobile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IYYzimFXI0V-6rSI4tH6RQ.jpeg" /></figure><p><a href="https://www.figma.com/proto/spQLMPWQpl7Fa42ztB9Dv0/%5B-P2-%5D-Design-File-Team-1?page-id=116%3A21&amp;type=design&amp;node-id=1276-2744&amp;viewport=-1239%2C322%2C0.24&amp;t=hSsupUQWkp06hA1T-1&amp;scaling=min-zoom&amp;starting-point-node-id=1276%3A2744&amp;mode=design">Click here to discover the full, online prototype</a>. You can see the <em>Homepage</em>, the <em>Book Buddy</em>, the <em>Staff Picks</em> page, the <em>Single Book</em> page (as seen above), as well as the <em>purchasing flow</em>.</p><p>In case you skipped the live prototype, here is a focus on the Book Buddy feature:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5ZK7EMh8EZnMxAWoy0-AA.jpeg" /></figure><p>The feedback we got from the class was generally positive. Many people liked the Book Buddy feature, and most people like the design of the site in general. However, some people had trouble understanding what the Book Buddy was before entering it, and one of the teachers pointed out how it didn’t respond to the problem we previously defined.</p><p>The next steps are to:</p><ul><li>Explore new ways of solving the problem</li><li>Add pages (User-Account, Book Categories, About, Contact) to prototype</li><li>Include more payment options in the checkout flow (G-pay, Apple Pay, etc)</li><li>Launch product and collect feedback</li></ul><p>What we learned:</p><ul><li>While our special feature (Book Buddy) was appreciated, it’s not clear that it actually solved the problem we had identified in the Define stage of the process, i.e. <em>book enthusiasts are frustrated by the lack of human connection on bookshop websites</em>. While Book Buddy simulates a book recommendation interaction that customers traditionally get in the bookshop (from a human assistant), it doesn’t provide the real human connection that people crave.</li><li>Working with a real stakeholder was great. It gave us a sense of responsibility (to create a professional-grade product), and caused us to empathize with our client: talking to her challenged some of our assumptions about the bookshop and it’s customers. This made the project significantly more rich and exciting.</li><li>Working in a group can be challenging.</li></ul><p>I hope you enjoyed reading this UX case study. Any constructive comments you write will help me develop as a UX designer. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcdc71e4e3f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX  case study: Food Sustainability]]></title>
            <link>https://medium.com/@Alfher/ux-case-study-food-sustainability-106584918226?source=rss-d389db375659------2</link>
            <guid isPermaLink="false">https://medium.com/p/106584918226</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[food-sustainability]]></category>
            <category><![CDATA[ux-case-study]]></category>
            <dc:creator><![CDATA[Oliver Simpson]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 18:58:29 GMT</pubDate>
            <atom:updated>2023-12-03T19:55:08.681Z</atom:updated>
            <content:encoded><![CDATA[<h3>UX case study: Food Sustainability</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AhBulc_9y49fdRs96Ib87Q.jpeg" /></figure><h4>The Challenge</h4><p>People are more conscious now about the food they eat and where it comes from. However, not everyone has access to, or can afford, organic, locally-sourced food. Our challenge was guided by the question:</p><blockquote>“How Might We help people access local seasonal produce, while also fostering fair and honest relationships between producers and customers?”</blockquote><h4>Problem Statement (a peek into the future)</h4><p>This statement (the product of our user-research) will help you understand the problem we identified, the user-group it affects, and the goal they seek:</p><blockquote>Environmentally-conscious urban millennials need to find a personalized way to purchase organic produce from local farms because they want to reduce their food waste.</blockquote><p>… and here’s how we got there:</p><h3>Research</h3><p>In order to learn more about this subject and what people thought about it we conducted three kinds of research:</p><ul><li>Secondary Research</li><li>Surveys</li><li>User-Interviews</li></ul><h4>Secondary Research</h4><p>By reading relevant articles on the web, this is what we discovered:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DU40WOrxJj_hZhyd7KMlOQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ls1sqqbPnpRBIsfveiAIBg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m74C0kpipq3LJzsyYxoH5A.png" /></figure><h4>User-Interviews + Surveys</h4><p>We created a survey and prepared an interview guide. Our survey got 33 respondents and we interviewed 6 people.</p><p>Our <strong>target users</strong> were Environmentally-conscious people of a higher economic bracket who shop at organic grocery stores, or buy organic fruits and vegetables at local markets and supermarkets.</p><p>Our research goal was: <strong>Trying to understand people habits around food sustainability.</strong></p><p>Here are some of our survey results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1PdbFrZXh3CQ9pxMqvtOVQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WX1MYWjns6ON5d0pzhGp8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UHuOoZPTJi4sqKapBmd_mw.png" /></figure><h4><strong>Affinity Mapping</strong></h4><p>In order to make sense of our (qualitative) interview data we performed affinity mapping. First we arranged the data points into theme groups. Then we chose three key theme groups to focus on. Then we synthesized the data of each theme group into one sentence to produce an insight.</p><p>Here are the three key insights that we identified:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZhNLjF5p2fd-zm3WoQ6g5g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jz8IUo-3CZGv6PMsnyH4zg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GpCR4HWQ79Y4w6_SiEVRLw.png" /></figure><h3>Define</h3><p>The next phase of the project was to use the insights we discovered to define the problem and bring our user-group to life. We created three artifacts:</p><ul><li>User Persona</li><li>Customer Journey Mapping</li><li>Problem Statement</li></ul><h4>User-Persona</h4><p>We crafted a primary user-persona based on the data we had collected (and insights generated) in the research/discovery phase.</p><p>Meet Pauline:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7LdX1Dv8FRgSDBiAQadIA.png" /></figure><h4><strong>Customer Journey Mapping</strong></h4><p>We created a customer journey map based on Pauline, our user-persona. The ‘map’ describes the journey Pauline takes as she receives a fresh food box on Saturday (that makes her very happy), enjoys the food for a few days, but ends up eating out with friends for several days of the week and finds at the end of the week that she has so much food left over that she can’t use. When the new fresh food box arrives the following Saturday, she feels bad because of all this wasted food.</p><p>Here’s the map:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sDav-86h5yghIOBr_swBpg.png" /></figure><h4>Problem Statement</h4><p>This is the moment when we created the Problem Statement, which I shared with you at the beginning. This statement describes the user-group, their goal/need, and the insight/problem. And this statement it what our team used in the next phase to generate solutions to this problem.</p><p>Here it is again (a more colorful version):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sbF3SY5RSR-IOmrMJNGc3A.png" /></figure><h3>Ideate</h3><p>The next phase, Ideate, is about generating ideas that aim to solve the problem we defined in the Define phase.</p><h4>Crazy 8s</h4><p>We sketched out multiple ideas in a time-boxed setting with the goal of producing many ideas (some bad, some good) in a limited amount time.</p><p>Here’s the result:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEVcATDCm2j8h45Lt620UQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGoD6xPSlc57ow6tbEBz-Q.png" /></figure><h3>Prototype</h3><p>The next phase was to create the prototype, test it, and improve it based on the feedback (from the test). This was done in four steps:</p><ul><li>User-Flow Diagram</li><li>Low-Fi Wireframes + Prototype</li><li>Test + Feedback</li></ul><h4>User-Flow Diagram</h4><p>Before sketching wireframes, we created a user-flow diagram. It describes the path Pauline might take from opening our app to ordering and tracking a fresh-food box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rq4s8l0NnQ4f-TWZh46k7Q.png" /></figure><h4>Low-fi Wireframes</h4><p>We created a series of low-fi (drawn by hand) wireframe screens that correspond to the steps in the user-flow diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EMLF8AIVlPMxLsP-UANzgQ.png" /></figure><h4>Test + Feedback</h4><p>We tested the prototype with some users and got some useful feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qGEIB_-68skJejjtAoK-Bw.png" /></figure><h3>What We Learned</h3><p>We learned that building a product is difficult. It requires asking the right questions, finding the right people (to survey, interview, and test), and working in harmony with your team. But it can also be a lot of fun, and very rewarding. I personally really enjoyed working with my team, and I loved talking with people (our potential users) about their experiences. It was a wonderful journey and I learned a lot.</p><p>Thanks for reading.</p><p>Look out for Ironhack Project 2, coming soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=106584918226" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>