<?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 Laura Frantz on Medium]]></title>
        <description><![CDATA[Stories by Laura Frantz on Medium]]></description>
        <link>https://medium.com/@lpsfrantz?source=rss-fe48be95801a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*c4W5EWszLouM5l2D1ltY5g.png</url>
            <title>Stories by Laura Frantz on Medium</title>
            <link>https://medium.com/@lpsfrantz?source=rss-fe48be95801a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:44:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lpsfrantz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[| Case study #5 | Stolperstein App.]]></title>
            <link>https://medium.com/@lpsfrantz/case-study-5-stolperstein-app-b3f5e7fc9ad5?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3f5e7fc9ad5</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[uxui-design]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Tue, 27 Sep 2022 16:24:28 GMT</pubDate>
            <atom:updated>2022-09-27T16:34:10.974Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to commemorate persecuted people by the nazi regime during WW2 while transmitting knowledge to younger generations using tech ?</h4><p>Couldn’t wait to tell you about this fabulous project ! Why ? Because it’s about all that I prefer the most : contributing to general interest, with projects highly connected to human.</p><p>On this 2-weeks-project, I worked with a teammate I’m used to and I appreciate a lot : <a href="https://medium.com/u/e9d134fcb926">Jana</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzzavGdR0bLJVK7JPEm_aQ.png" /><figcaption>Stolpersteine App.</figcaption></figure><h3>Background.</h3><p>Nicola Andersson, a passionate art historian and tech lover, would like to develop an App which provides information about persecuted persons by the nazi regime in times of WorldWar II, such as jews and other targeted groups (disabled persons, homosexuals, …).</p><p>Stolpersteine, (EN. stumbling stones) are brass tiles in the ground with the victim’s name and dates such as birth, deportation and death.</p><p>For persecuted people, there is a Stolperstein in every city in Europe, in the place where they lived at the time. A huge amount of archival and research work is needed to complete this gigantic project, a duty of commemoration and memory for future generations.</p><h3>Stakeholder’s interview.</h3><p>We conducted a 2h30 interview with Nicola, in order to get as much information as we could on the project and understand what has been done already, what are the constraints, what problems did she encountered before… and much more.</p><p>As expected, we learned a lot of valuable information. What is essential for Nicola is :</p><ul><li>To point out the singularity of this project : a collaboration with schools from the neighborhood and children do the research ;</li><li>To stop with the scanning function with the camera (VR is not possible anymore, because of too many technical issues + financial constraints) and find a different way to make the information only accessible at place ;</li><li>That the app’s main purpose are Stolperstein walking tours.</li></ul><p>That being said, we moved on to the global organization of this 2-weeks project : 2/3rd of the time is going to be dedicated to the UX part and 1/3rd to the UI design.</p><h3>Quantitative Research : survey &amp; results.</h3><p>We approached the 100 of respondents to our survey. The strategy was to post our survey in targeted groups and to send it more personnally to people identified as our target.</p><p>Here are the <strong>main insights</strong> :</p><blockquote>Target group: 30–40 years old <strong>(57,1%) ;</strong></blockquote><blockquote>People want to learn history at the place where it happened <strong>(26,5%) ;</strong></blockquote><blockquote>Almost 100% need an emotional connection to learn easily and remember ;</blockquote><blockquote>People want to be flexible in pace, movement &amp; times <strong>(71,5%)</strong></blockquote><blockquote>The way of perceiving information should be innovative, and not boring <strong>(36,7%)</strong>.</blockquote><h3>Qualitative Research : interviews with users &amp; analysis.</h3><p>Thanks to our 5 qualitative interviews from users, we had <strong>many valuable insights and quotes :</strong></p><blockquote>“ I would like to have more personal or intimate facts, for example, a description of the person we’re speaking of, who was she etc. “</blockquote><blockquote>“ Memorising dates is not fun in my opinion. Events are much more interesting with an exciting or innovative presentation which would keep me more engaged “</blockquote><p>At this stage, the affinity diagram helped us cluster and then supergroup the recurring statements, or what we call « <strong>themes</strong> ». We discovered <strong>8 themes</strong> : <strong>Need for personal connexion, Playfulness, Universality &amp; Easy Usability, Features, Flexibility &amp; Independence, Expertise/Knowledge/Ressources, Authenticity, Lack of communication</strong>.</p><blockquote>As the current version of our app is already answering to the 2 final themes, and the last one was not in our scope of possibilities, we decided not to keep them and work on the 5 first.</blockquote><p>Then, to further empathize with our user, we moved on to an <strong>empathy map</strong> <strong>to detail what our users were doing, seeing, feeling</strong>… and much more. Here is what it’s looked like :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*lRzKA-6uU7pf0sd3Rd_YeA.png" /><figcaption>Our Empathy Map.</figcaption></figure><p>This being done, we moved on to our persona. In fact, based on our interview with Nicola (the stakeholder) and our users, and thanks to some reasoning and other secondary data, we decided to create <strong>a primary, a secondary and a terciary persona</strong> : Exploring Emma, Historical Helena &amp; Learning Lisa.</p><p>We had al the reasons, based on research, to chose Exploring Emma as our primary persona. Previously, there was no persona or target defined by the stakeholder as she wants everybody to use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ShJNZ7Loc9WGXsXoaAwkEw.png" /><figcaption>Our primary persona : Exploring Emma.</figcaption></figure><p>Now that our personas are clearly defined, we moved on to our <strong>User Journey Map (UJM) for our primary persona</strong>. We decided on a scenario our user could face and here is what we came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rIrExE19k2_JPsDUd1XcmQ.png" /><figcaption>Our User Journey Map for our primary persona.</figcaption></figure><p><strong>The lowest points or « <em>red zones </em>» are showing us the painpoints of our primary persona</strong>. The HMW are giving us <strong>our design opportunities</strong>, as shown below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qHvYbVpG_FVoRaLWlPnT9w.png" /><figcaption>Design Opportunities using UJM.</figcaption></figure><p>Now that the previous steps were done, we were able to move on to the <strong>problem statement</strong> and defined it very clearly. This is the problem we’re solving :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g5GT5ymckF-lbC3VJnuVFg.png" /><figcaption>Stolpersteine’s App Problem Statement.</figcaption></figure><p>We worked on the user flow then, in order to<strong> define our user’s happy path</strong>. The idea here is <strong>to show how our product/concept is going to solve our primary user’s painpoints</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PqxFPEpBztmxv-x781TAPQ.png" /><figcaption>User Flow &amp; Happy Path.</figcaption></figure><p>Based on our UX Research <em>(see previous) </em>and thanks to a UX critique we asked, we were conforted in our way and started to Sketch &amp; Wireframe in Lo-Fi. <strong>The objective here is to make the concept be “real” and test it as soon as possible with our users</strong>. We concept-tested it with 4 users and received feedbacks. Once the concept test validated, we moved on to the Mid-Fi wireframing and Prototyping.</p><p>Then, we ran <strong>more tests</strong> : it is the crucial “u<strong>sability-testing”</strong> phase. The idea here is to test, iterate and improve as much as the data and users tell us. In order to do so, we used Useberry to analyze all the metrics and heatmaps available. As a result, we did more <strong>iterations</strong>, taking into account all the feedbacks and data we had to improve our product design before next stage : the Hi-Fi Wireframe &amp; Prototype.</p><p>Here are some of the changes we made based on the users + design critique’s feedbacks :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gtl3oYXn1Wyiv3d4TbB7_A.png" /><figcaption>Changes in our product design based on users feedbacks.</figcaption></figure><h3>Moving to UI.</h3><p>In parallel to the previous work we did until mid-fi (and before moving to Hi-Fi), we ran a<strong> visual competitive analysis</strong> to know what our competitors are doing from a visual point of view (colors, typography, buttons, style, logo, etc.). The aim is to <strong>complete our approach with a good knowldege of what’s made out there by competitors (or interesting brands)</strong> and <strong>to detach from the competitors in the brand identity we’re going to design</strong>.</p><p>Our analysis included leaders of the same sector, interesting local actors and some inspiring projects. At this stage <strong>we gained knowledge and accuracy for the brand design we are starting</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PF2soCAlh0T_W3n9NK3urg.png" /><figcaption>New pages created from users feedbacks.</figcaption></figure><p>Then, to complete this work, we defined the <strong>brand attributes</strong><em> (the 4/5 words defining our brand : educational, empathetic, inquiring, sharing, commemorative)</em> and declined it into a<strong> moodboard</strong>, as shown below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VGy93l_8amfSt3LSX1Ubw.png" /></figure><p>Right after the brand attributes &amp; moodbard we worked on our <strong>color palette &amp; typography</strong>, or differently said, our <strong>style tile</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ev4_6eFYh_Ug3ivf6azPEg.png" /></figure><p>As we’re talking of <strong>an historical &amp; educational topic with a strong public interest dimension</strong>, we paid a very particular attention to the <strong>accessibility (WCAG/W3C)</strong> to be scored as <strong>AAA</strong>. We thought of our design upstream this way and tested all the screens of the app downstream to check that we have met our specifications. It had to be <strong>part of the DNA of our product’s design</strong>, in a continuous search for improvement.</p><p>Combining all the different steps of our work together, iterating and testing again with our users, validating with our client, we ended up with this <a href="https://youtu.be/hVpzQEYz-Fs">Hi-Fi Protoype</a>.</p><h3>Next steps &amp; key learnings.</h3><p>I was very happy to work on such a beautiful and useful project and product. I am passionate with contributing to the common good and easing the transmission between generations. Leaving a positive impact in our societies, in one way or another, is a red thread for me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IWCJw5MYs3JfkY5LwgEZvQ.png" /></figure><p>I hope you enjoyed my article and this fabulous project,</p><p>Don’t hesitate to support me with a like #thumbup and follow my account no to miss any of my future UX/UI designs ;-)</p><p>Take care and see you !</p><p>Laura</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3f5e7fc9ad5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[| Case Study #4 | Wellness App.]]></title>
            <link>https://medium.com/@lpsfrantz/case-study-4-wellness-app-c36916437235?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36916437235</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Tue, 12 Jul 2022 14:13:46 GMT</pubDate>
            <atom:updated>2022-07-12T14:13:46.452Z</atom:updated>
            <content:encoded><![CDATA[<p>For this new project, I’ve been pleased to pair with my colleague Senani Mitra. Our entire design process from research to hi-fi full prototype lasted a bit less than 2-weeks. At the end of our project, we had the pleasure to pitch our ideas in front of a jury and the opportunity to capture the attention of our stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JJxl0Nv347f_fvg6A34lTw.png" /><figcaption>Our Fertility Support App : Lotus.</figcaption></figure><h3>Background.</h3><p>Technology is causing <strong>massive disruption in the health and wellness industry</strong>. The smartphone’s omnipresence has created a <strong>massive market for mobile health apps</strong>, wearables, and biometric trackers. Healthcare digital products are gaining popularity, as shown by the latest Gallup survey revealing that nearly half (45%) of Americans have at least tried digital health products such as fitness trackers or mobile health apps.</p><p>As a result, our client —<em> the National Wellness Institute</em> — wants designers to rethink how people can adopt and commit to a health-improving routine.</p><p>With Senani, we decided to work around the pregnancy/PMS/period/fertility topics without knowing yet what will precisely be our perimeter. We wanted to work on a feminine health/wellness topic where there still are many uncovered needs. At this stage, we needed to dig more to figure it out clearly.</p><p>That being said, let’s start with the begining.</p><h3>UX Strategy.</h3><p>First, let’s define what is it : User Experience (UX) Strategy lies at <strong>the intersection of UX design and business strategy</strong>.</p><p>UX strategy is the “big picture”: it is a<strong> </strong>high-level plan to achieve one or more business goals under conditions of uncertainty.<strong> </strong>In simple terms, <strong>UX Strategy is a plan-of-action on how to make sure that the User Experience of a product is aligned with the business’s objectives</strong>.</p><blockquote>“[UX Srategy]… is a practice that, when done empirically, provides a much better chance of creating a successful digital product than just crossing your fingers, designing some wireframes, and then writing a bunch of code”, Jamie Levy.</blockquote><p>In order to do so, we worked with both UX Strategy Blueprint and Lean UX Canvas as they can be seen as complementary tools.</p><p>Not to be too heavy, I’ll show below our Lean UX Canvas only. Here is what we came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8j0b-s6wMcMgcC9E7b8yg.png" /><figcaption>Our Lean UX Canvas.</figcaption></figure><p>Why doing this now ? Because <strong>this step allows us to formalize our project in a simple way</strong> — in a few words — <strong>and to come back to it as many times as necessary to adjust it, enrich it, rotate it</strong>… Which we’ll be doing during the project as you’re going to see soon.</p><p>Indeed, we quickly realized that we had to focus on a specific topic and narrow down our scope <em>(which means or to work on fertility, or pregnancy, or post-partum)</em>, based on our knowledge of the market and the <em>[presumed, at this stage]</em> needs of our users.</p><p>Consequently, not to stay on assumptions — <em>as strong UX Research is key</em> — our next step was to complete our knowledge of the market with secondary research (already existing figures regarding our topic, recent data, etc.) and to uncover our users real needs thanks to primary research.</p><p>So, let’s move on to the (very) important research phase of our design thinking process.</p><h3>Research phase.</h3><p>We split our research phase into 2 complementary parts :</p><ul><li><strong>Market Research</strong> (about competition &amp; industry) ;</li><li><strong>User Research</strong> (both primary &amp; secondary, qualitative &amp; quantitative).</li></ul><p>In order to have a clear understanding of our competitors and the market we’re in, we conducted both <strong>Market positioning chart &amp; Features analysis</strong>. Those tools help us understand what are the <strong>compulsory features </strong>and which ones could <strong>help us stand out in the market </strong>as well as who are our competitors, what are their positionings and if there is any space with no competitor in it but with (high) demand for it.</p><p>Let’s have a quick look at our Market Positioning Chart :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DsGQZ8N-POT91Y6zWuO_cw.png" /><figcaption>Market Positioning Chart.</figcaption></figure><p>If we summarize what we see, there are <strong>2 clear market positioning opporunities</strong> :</p><ul><li>An app with the possibility for the partner to login/a <strong>couple access </strong>;</li><li>An app with a <strong>semi-global approach regarding features</strong>, less complex than the existing apps, but keeping<strong> a community prism</strong>.</li></ul><blockquote>Note : we also figured out that the market for individual approach apps was already crowded, and that the market for specific approach apps was already well adressed and/or too specific to be largely adopted (which questions the profitability).</blockquote><p>In parallel, we conducted both <strong>qualitative and quantitative primary research</strong>. The aim ? To have more knowledge based on User Research with first-hand and accurate data.</p><p>In order to do so, we performed <strong>5 user interviews</strong> (qualitative) with people from our target population (women/couples currently trying to have a baby, or recently done with their Trying To Conceive (TTC) period as the woman got pregnant) <strong>and a quantitative survey</strong> widely shared among groups related to our topic (mostly on social networks). As our topic is highly specific in terms of population and period of time, it was difficult to receive as many answer as we would have liked in the short amount of time dedicated (&lt;24h). We received around 20+ qualified answers with very valuable data in it.</p><p>Here is a sneak peak of the kind of trends we received in the answers of our quantitative survey :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_HV_R0tiU4MLfLRCfOHyuw.png" /><figcaption>Most wanted features regarding a fertility app.</figcaption></figure><p>We also learned that :</p><ul><li>Clue &amp; Flo are used by more than 55% of our sample, among the 15 most-used apps. This is an important fact for us to take into account (and potentially get inspired to improve) ;</li><li>Fertility calendar is the most interesting feature for 57,9% of our sample ;</li><li>For around 32% of our sample, the biggest challenge our users faced when trying to conceive a baby was the uncertainty about the fertility period. Then comes the lack of fertility information or reproductive information for 21% of our sample. The lack of communication in the couple comes after, with around 16% of the answers.</li></ul><p>In parallel, we conducted <strong>5 different user interviews to have direct insights from users and to gather qualitative data</strong>. Conducting 3 interviews with our target users help us be sure of covering at least &lt;80% of the possible spectrum of answers. With 5, it is even better and not so far from 100%.</p><p>Now that we have many valuable information, we need to cluster and group them by theme/category. We use the Affinity diagram to do so.</p><p>Here is an overview of it :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D5QDwPZluNs_XraezzlXvg.png" /><figcaption>Our Affinity Diagram.</figcaption></figure><p>We can clearly see that the tracking accuracy, the mental health topic, the need for multiple support (partner, community, specialist, etc.) and the need for information about the topic (community/professional) clearly detached.</p><p>Here are some of the quotes we received :</p><blockquote>“ I would have like to have guidance on why I didn’t get pregnant/to know more about what were the responsible factors”</blockquote><blockquote>“ These Apps just assume your body to be like everyone else’s body, I mean I need customised information that suits my body !! All bodies are different you know...”</blockquote><blockquote>“ I think if someone could just give me the right information at the right time like it’s quite challenging when there is so much of social pressure you really feel very depressed sometimes and mentally very down”</blockquote><p>Our qualitative interviews helped us put more color to our topic and what we will build.</p><p>Once this is done, we’ve been able to move to our persona (Pressured Elsa) and her User Journey Map.</p><h3>Pressured Elsa.</h3><p>Based on all our previous researches, we’ve been able to build our persona : Pressured Elsa. She’s 29, married, living in a city, trying to have a baby for 6-months now and feeling particularly pressured by her social environment about this situation.</p><p>Below is who she is in details, with her <strong>personnality</strong>, her <strong>motivations</strong>,<strong> goals</strong> and <strong>painpoints</strong> :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jwL2vBp-pUxT8xtpZQbsUg.png" /><figcaption>Our persona : Pressured Elsa.</figcaption></figure><p>Now, let’s put a plausible scenario around our persona —<em> the User Journey Map (UJM)</em> — <strong>to identify different friction points and unmet needs of our user</strong>, which also means identify opportunities from a product/design thinking perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynTQ_UvkANYLN-Q3F4dUAQ.png" /><figcaption>Our User Journey Map.</figcaption></figure><p><strong>The stars represent the touchpoints, and the red emotions lines (below the average line) are our opportunities</strong>. Here, we’re going to adress the HMWs of the “annoyed” and “disappointed” parts, and in fact our product can solve both of the painpoints at once.</p><p>To go further in our understanding of our persona, and so our users, we completed our process with a useful tool.</p><h3>Empathy Map.</h3><p>As for any new tool in our design thinking process, let’s start with a definition :</p><blockquote>“ An <strong>empathy map</strong> is a collaborative visualization used to articulate what we know about a particular type of user. It externalizes knowledge about users in order to create a shared understanding of user needs, and aid in decision making” , NNGroup.</blockquote><p>As UX professionals, it is our job to advocate on behalf of the user. However, in order to do it, not only must we deeply <strong>understand our users</strong>, but we must also <strong>help our colleagues understand</strong> them and prioritize their needs. <a href="https://medium.com/the-xplane-collection/updated-empathy-map-canvas-46df22df3c8a">Empathy maps</a>, widely used throughout agile and design communities, are a powerful, fundamental tool for accomplishing both.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2uuz0ZDhtCEhwRl45wGi_g.png" /><figcaption>Empathy Map.</figcaption></figure><p>Now that we worked even more on our empathy and comprehension of our users, we can now work on the Problem Statement and <strong>clearly define the exact problem we’ll be trying to solve </strong>through our solution.</p><h3>Problem Statement.</h3><p>Based on all the previous steps, we came up with the following problem statement :</p><blockquote><strong>“ Women who want to track their fertility i</strong>n order to conceive need to find a way to have <strong>less stressful and more confident TTC journey</strong> because the process is intense and <strong>affects their mental and physical health in a negative way t</strong>hat is counter productive with their goal.”</blockquote><p>Now that the problem is clearly defined (user description, goal and insight), let’s move on to the ideation phase in order to come up with innovatives solutions to solve the issue.</p><h3>Ideation phase.</h3><p>For this project, and because the topic is particularly sensitive, we decided to focus our efforts on the Crazy 8s (and to avoid the worst case method) : 8 minutes to brainstorm and imagine 8 different ideas that are solving our problem.</p><p>Here is what I came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUegs-QXYat6bsXCwv8Btg.png" /><figcaption>My ideas / Crazy 8s method.</figcaption></figure><blockquote>Note : Senani worked on her side too. Then, we gathered our ideas and dot-voted for the best ones.</blockquote><p>We came up with various nice solutions and needed then to take a while to think about <strong>which features are fundamentally essential and which ones are a plus</strong>. The perfect tool to do so is called “the MoSCoW method”.</p><h3>Feature Prioritization : MoSCoW Method.</h3><p>Every project has <strong>resource limitations</strong>: Time, Money and People. So if we are planning on developing an MVP, we will need to <strong>select and prioritize what we want to include</strong>.</p><p>Also, we want to avoid <a href="https://www.interaction-design.org/literature/book/the-glossary-of-human-computer-interaction/featuritis-or-creeping-featurism">featuritis</a>. So we need to plan a gradual roll-out of our solution. The more features we have at launch, the harder it is to tell what works and what doesn’t. But, how to choose and prioritize these features ?</p><p>One of the possible way to do so is to use the <strong>MoSCoW matrix</strong> and split the features into <strong>4 categories : the must-have, the could have, the should have and the won’t have</strong>. Here is the matrx based on our example :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynnYFW1UwZdtn2Ai1BH3ZA.png" /><figcaption>MoSCoW Matrix for our Fertility Support App.</figcaption></figure><h3>Minimum Viable Product.</h3><p>Now that we clearly defined which features are compulsory and which ones are not (with different degrees), we were able to work on our <strong>Minimum Viable Product (MVP)</strong>. After some iterations, here is what we came up with :</p><blockquote>“ Our <strong>fertility support app aims to help women to efficiently track their ovulation cycle</strong> every month by <strong>keeping track of their physical symptoms</strong>. Since the Trying To Conceive (TTC) period is very intense and sometimes stressful, the app also <strong>connects user/women with expert content </strong>(articles and expert advice are accessible through a simple search bar and can be saved as a favorite)<strong> and support from other people </strong>facing the same situation via a community forum.<br>Our complementary features are designed to <strong>support every women in her TTC period on both fertility and mental health fields. </strong>Users will find<strong> f</strong>resh highlights and a quick overview of the main categories (ovulation, symptoms, nutrition, watering, expert advice, information, etc.) on the homepage. Then, <strong>our app assistant will ask our user to fill in all the needed information about symptoms everyday</strong>. Since symptom data is key, users can also easily find the dedicated dashboard page in the nav tab so that they can consult her progress over time and add more data whenever they need to. ”</blockquote><p>The contours of our application are now very clear, and strongly based on our users needs.</p><h3>User Flow — Happy Path.</h3><p>In relation with our persona, Pressured Elsa, we needed to figure out her “Happy Path” in our app to display how the app can solve her problem. Based on her journey and her main painpoints, our userflow is the following one :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rp9ypZSWmsDId8yHNRO-5w.png" /><figcaption>Pressured Elsa’s Happy Path in UserFlow.</figcaption></figure><p>This being done, let’s move on to our low-fidelity wireframes.</p><h3>Lofi wireframes &amp; Concept testing.</h3><p>As previously said in most of my previous case studies, <strong>the earlier we test the better it is</strong> : we aim to face the market quickly to avoid “dragging” heavy mistakes or a flawed concept that would cost us a lot of time and/or money.</p><p>We <strong>need to know if the concept is clear and appealing to our users</strong>. The goal is to gather feedback and to find out how the typical customer will respond to the concept, along with identifying any areas that need improvement.</p><p>Here is a sneak peak of how our Lo-Fi wireframe looked like :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KLAgPBoS-itxzzRcxJe5Qw.png" /><figcaption>Lo-Fi Wireframe (v1) of Lotus.</figcaption></figure><p>Based on this digital version (most of the time, lo-fis are made from pen and paper), we immediatly concept-tested on 5 users and received many valuable feedbacks.</p><p>I’ll not go in detail to all the feedbacks received but concept test <strong>helped us confirm the value of our app and even more clarify it and make it stronger</strong>.</p><p>Conforted with all our users feedbacks, we moved on to our Mid-Fi wireframes. We kept in mind the different improvement points identified to apply them directly in our mid-fidelity wireframes, knowing that we were going to test more and iterate again to perfectly match our users needs.</p><h3>Midfi Wireframes &amp; Prototype.</h3><p>A this stage, I have to say that <strong>we iterated many (many) times</strong>. We tested a lot <em>(directly on figma with our prototype + our user but also thanks to Useberry)</em>, we changed many things inbetween 2 user tests based on their feedbacks, pivoted, and finally perservered in the good direction, guided by what we were learning.</p><p>This phase was very intense as we ran 3 rounds of 3 to 5 usability tests everytime. We improved a lot from 1st iteration to the last one, tayloring the app on our users. We had to rethink the pop-up (too heavy in v1), work more on the dashboard (too difficult to understand for our user), to adapt our fertility meter and made it clearer… and a lot more !</p><p>Here is a quick overview of some of our midfi iterations :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ccr_Zf3EJOGNJIekRLfzA.png" /><figcaption>Low-fidelity Wireframes.</figcaption></figure><p>Our objective ? To make Lotus <strong>perfectly match our users’ expectations </strong>and become a <strong>must-have application in the digital wellness apps market</strong> where the Wellness National Institute would like to expand.</p><p>Now that our MidFi is optimized and reached its most upgraded form, we can move on to the more UI part, preceding our HiFi Wireframes and Prototype.</p><h3>Brand Attributes.</h3><p>Before brainstorming on our Brand Attributes for our App (Lotus), we started with a <strong>Visual Competitive Analysis</strong>. The goal here is to know what our competitors are doing from a visual point of view, to analyze it and to get inspired (or not) when we’ll be working on our product then.</p><p>We performed this analysis with both <strong>direct</strong> (Clue, Flo, etc.) <strong>and indirect competitors</strong> (Jam, FB Messenger, nutrition/sport apps, etc.) to get as many information and inspirations from brands as possible.</p><p>Once we were done, <strong>we moved on to Lotus Brand Attributes</strong>. What are our Brand attributes ? Or said differently : what should our users spontaneously think of when seeing Lotus ?</p><p>We brainstormed separetly with Senani, and then gather our ideas : we were agreed on all the attributes. Here there are :</p><blockquote>Inspirational ;</blockquote><blockquote>Informative ;</blockquote><blockquote>Supportive/Women Empowerment ;</blockquote><blockquote>Trustworthy ;</blockquote><blockquote>Positive.</blockquote><p>Based on our Brand Attributes, we created a <strong>Moodboard </strong>with images and feelings all related to them :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CKKAPztcsNyLJVAADtPe8Q.png" /></figure><p>Obvisously, <strong>we then tested our Moodboard on users to be sure that it was perfectly matching our Brand Attributes</strong>. We received many feedbacks, pretty positive and, most of all, confirming our choices. Consequently, we didn’t need to change it.</p><p>Now that this is done, let’s move on further into the UI, choosing the correct Typography and Color palette for Lotus.</p><h3>Style Tile : Colors &amp; Typography.</h3><p>At this stage, we made our best to find the color palette which relates the most to our brand attributes and to the feeling we want Lotus to give. <strong>We were looking for a positive, feminine color which also makes women feel confident and empowered. </strong>The perfect color for this mission is purple !</p><p>So, we started with the <strong>plum as primary color </strong>(solid &amp; gradient) and completed the primary color palette with colors matching both our brand attributes and the plum first-selected color of our palette. We ended with the <strong>plum, dark violet, a lighter tint of plum similar to old-pink and champagne for our palette</strong>. We declined them in both solid &amp; gradient fills.</p><p>Then, <strong>we looked for the perfect font to match our needs </strong>(which are the users needs in fact). As if it were a diary/journal containing all the strenghts of a woman, we were looking for an easy-to-scan handwritten-like font. We tested many and finally found the one we were looking for : <strong>Architects Daughter</strong>. It is a feminine, handwritten-like, scannable font. We then tried to find perfect complementary fonts for the body and headings. After many researches, we found the perfect match for Architects Daughter : <strong>Quicksand (headings) and Chivo (body)</strong>.</p><p>Finally, we ended with our icons/bars/buttons. <strong>We wanted our buttons to have rounded corners (smooth &amp; feminine) and our icons to be consistent and matching our expectations in terms of design</strong>. Same for our Nav Tab. Thanks to all the previous feedbacks we received, we already knew what to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JBUzAsell2UmNy0Lvh8WBA.png" /></figure><h3>Hifi Wireframes &amp; Prototype.</h3><p>Thanks to all the previous steps we worked on (+ feedbacks), we can now confidently move on to our Hi-Fi wireframes &amp; prototype.</p><p>We went further in the in the path we were on when we worked on the mid-fi versions and apply it to hi-fidelity wireframes. We polished our Hi-Fi Wireframes and conducted a<strong> design critique</strong> with members of our cohort. We received feedbacks and apply changes in our Hi-Fi. Then, we ran new tests (desirability tests) and iterated again on our wireframes/prototype.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*17U2aOs78-Dz0FeY23HItA.png" /><figcaption>Overview of some pages of our Hi-Fi.</figcaption></figure><p>I didn’t mentioned it earlier but in fact, in order to gain time for hi-fi prototyping, we created a Style Guide (a document more developped than the Style Tile), and create a strong base for our Design System (a whole Figma page fullfilled with components, variants (states), buttons, bars… and even all our animations).</p><p>Now comes the long awaited moment: the finalized hi-fi prototype ! Let’s click on <a href="https://youtu.be/yVw2WK6okbI">this video link</a> to see it in action :-)</p><h3>| Bonus | Presentation tips.</h3><p>In our presentation, we had a special attention for our stakeholders, dedicated them slides showing our app specificities and ways to monetize it.</p><p>It is important to reassure Stakeholders and Investors when presenting our product, as these people are investing a lot of money in it. As UX/UI Designers are inbetween users and business, it is our role to do so.</p><p>That’s why I really wanted to show you the 2 slides we dedicated to them. The first slide shows how Lotus stands out among all the other fertility apps :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWNdaVCGqZE_IaCHBsPINQ.png" /><figcaption>Why Lotus is different from its competitors.</figcaption></figure><p>And the second slide addresses the nerve of the war: money. What are the possible ways to monetize Lotus ? Below is what we imagine :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGnW_K_68k1inbclOHs5-g.png" /><figcaption>Monetization possibilities in Lotus.</figcaption></figure><blockquote>Note : thoses slides were particularly appreciated during our presentation.</blockquote><h3>Next steps</h3><p>As our stakeholders presentation was pretty clear about our next steps on this project, I’m directly sharing the slide with you here :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GfYZwXCvPS3Zk0rqLVFoGQ.png" /></figure><h3>Key learnings</h3><p>Same for our key learnings which I’ll be sharing right here :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mfalfrpUDZk48kumQbjS2A.png" /></figure><p>That’s it! I hope that you enjoyed reading my Lotus Case Study :-)</p><p>Please feel free to comment/clap/share and of course ask me your questions directly (if any), I’ll be pleased to answer to you !</p><p>See you on my next project ;-)</p><p>Take care,</p><p>Laura</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36916437235" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[| Case Study #3 | Redesign an App.]]></title>
            <link>https://medium.com/@lpsfrantz/case-study-3-redesign-an-app-21549700910c?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/21549700910c</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[redesign-challenge]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Sun, 03 Jul 2022 22:02:19 GMT</pubDate>
            <atom:updated>2022-07-03T23:14:40.649Z</atom:updated>
            <content:encoded><![CDATA[<p>I am very happy to share with you my entire design process in this 3-days UI Challenge.</p><p>In this project, <strong>this aim was to practice my UI skills at a rapid pace without the constraints of conducting user research</strong>. The app already has content and users. Therefor, I could dedicate all of my time and energy to improving my Information Architecture and visual skills (UI).</p><blockquote>Improving UI skills through UI challenges is a common practice in the design community.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*g1VHAmhx9LWceArb994Qaw.png" /><figcaption>Spotify Original Logo.</figcaption></figure><h3>The Challenge</h3><p>Here are the rules for this challenge :</p><ul><li>To select the app for the redesign (the app must be a <strong>well-known native mobile app) </strong>;</li><li>To redesign <strong>a minimum of 3 screens</strong> of your choice (homepage, profile page, result page, catalog page, product page, payment page, article page, order summary page, etc.). It is possible to do more screens, but the challenge is limited to <strong>a maximum of 7 screens</strong> ;</li><li><strong>No UX research required</strong> for this challenge ;</li><li><strong>The use of UI Kits is prohibited</strong>. Everything will have to be made from scratch.</li></ul><h3>My App Choice</h3><p>As a big music lover, married to an artist and with several friends who are involved in the music business in their professional or free time, I didn’t hesitate for a second to choose <a href="https://open.spotify.com/"><strong>Spotify</strong></a>.</p><p>I have to admit that at first I was a little worried that I wouldn’t be able to meet the challenge, as Spotify is such an elaborate application that is reviewed by dedicated, well-staffed teams.</p><p>But this feeling did not last, <strong>so much the challenge fascinated me during these 3 days.</strong></p><h3>Audit &amp; Cloning</h3><p>The first thing I did was <strong>to reproduce the existing screens</strong> I chose because <strong>each redesign</strong><em> — no matter how small or big —</em> <strong>always begins with an audit of the existing design.</strong></p><p>The pages I chose were : 1/ the Homepage, 2/ the Settings page and 3/ the Librairy’s page.</p><p><strong>Why ? Because, even before conducting any more detailled research or reflexion, I already felt that this pages could have been better, as well as the content organization, the navigation logic and sequencing.</strong></p><p>For this challenge, I followed my instincts a bit at the very beginning, but then I couldn’t help but anchor each of my thoughts and work on data from user research phases. Doing a purely UI redesign without basing it on UX Research seemed too fragile and less relevant to me: I might reconcile the two worlds as best I could.</p><p>Here are the screenshots of the original page (on the left) and my clones (on the right).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UtDbOeG1V3HjOLjt4EQCQA.png" /><figcaption>My clones of 3 of the original Spotify App screens.</figcaption></figure><blockquote>Note : I made every single icon, and for some of them, it was a real challenge ! Fortunately, it’s always possible to find what you’re looking for thanks to Youtube and its many UX/UI designers contributors.</blockquote><h3>Next Step of my Strategy : Heuristic Analysis</h3><p>Right after cloning the selected screens,<strong> I found it logic to conduct a Heuristic analysis of the current app</strong>. Indeed, if something isn’t working, I’ll be able to fix it with my redesign and this approach would be a good starting point.</p><p>This analysis and all the interesting things it highlights aims to be helpful for my final hi-fi prototype, in explaining my choices.</p><blockquote>When redesigning an app,<strong> experiment with new things, step outside of the comfort zone, and use creativity is essential. </strong>Another tip in this kind of challenge is to prefer quality over quantity (moreover when you only have 3 days): 3 well-designed screens are better than 7 sloppy ones.</blockquote><p>I share with you below my Heuristic Analysis where I found ideas in 5 of the 10 general principles for interaction design. The 5 other principles were less relevant in my case.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-dqjjyQivB3ho2BqeRIZuA.png" /><figcaption>My Heuristic Analysis.</figcaption></figure><h3>Sitemap Analysis</h3><p>Or the way to answer, at this stage, what is the current sitemap and how it could be improved.</p><p>I had to proceed by iteration to reach the final sitemap proposal (for example, I needed to know better my user persona).</p><p>Here is what I came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*rntpUEI-JB-yNjU-G9IhTg.png" /><figcaption>SiteMap V2.</figcaption></figure><h3>Visual Competitive Analysis</h3><p>Or how to analyze logos, colors, imagery &amp; brand attributes of competitors, as references. This step consists in<strong> understanding the competitive space</strong> my product will be in and how to position myself in it.</p><p>In other terms, the questions I aim to answer at this stage are :</p><ul><li>What other products are in <strong>my space</strong> ?</li><li>What <strong>other products</strong> do people use my app use?</li><li>What do their sites or apps <strong>look like </strong>?</li></ul><p><strong>I have to think of both direct</strong> (Deezer, Apple music, etc.) <strong>and indirect competitors </strong>(Canva, Facebook/Messenger, Shazam, BackMarket, LeBonCoin, Netflix, etc.). It is important because when looking at the competition, I want <strong>to identify the current identities that are being used within the market</strong>, so that :</p><ul><li>I am aware of <strong>current trends</strong> in this space ;</li><li>Have an idea of <strong>what my customers may expect</strong> ;</li><li>I set my product <strong>apart from the competition</strong> ;</li><li>I want to make <strong>my</strong> <strong>product’s identity look different</strong> from what’s already out there.</li></ul><p>This is inbetween getting inspired from the other, fitting my market and finding the unique identity for my product.</p><p>I also <strong>got inspired from the desktop view of Spotify </strong>to see how Spotify looks on other devices. The idea was to check and analyse the differences (if any) between the mobile app and the desktop version in order to keep the good practices and extend them to the app, if relevant to my project and how I imagine it thanks to the previous step + the UX research phase I conducted with real users of Spotify and other music apps.</p><p>Apps as FB messenger (“bubbles” for messages), Deezer (global display) and Netflix (buttons, sections) or LeBonCoin (settings page) inspired me. I had to make all those inspirations match the expectations I found in my researches and how I was going to redesign the app consequently.</p><blockquote>Note : It could have been great to try some A/B testing (for example to opt fro buttons or carrousels in the homepage) to confirm my choices based on real data.</blockquote><h3>My Proto-persona</h3><p>I created a proto-persona to have a first idea of my target without having done the usual extensive User Research. I based it more on secondary research in the objective of drawing a first silhouette of my target.</p><blockquote>What you have to understand here is that the proto-persona is used when time and financial resources are not available. Indeed, it’s always better to have a proto-persona than no persona at all, even if it might be biased by preconceptions and does not correctly reflect reality.</blockquote><p>To be sure to have a good proto-persona, or at least in improved one, I quickly spoke with 3 different people I consider close to my targeted profile. I shared with each of them my proto-persona and corrected it so that it looks more like them. I did it in person with a time of +/- 10 to 15 minutes for each person.</p><p>I also read a lot about the actual personas of Spotify. There are plenty of articles in the internet.</p><p>Here is the proto-persona I came up with, Meloman Travis :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vcKmDWyD6aPXwiMhZmJTNA.png" /><figcaption>My proto-persona : Meloman Travis.</figcaption></figure><h3>Moodboard &amp; Brand Attributes</h3><p>Now comes the more UI design part of this visual redesign project. It is now more about redesigning the app’s look and feel.</p><p>To work on this more visual part, I started to define my brand attributes : what are the words which best describe my brand ? I based my reflexion on my proto-persona, my secondary research and more information I looked for.</p><p>Here is what I came up with :</p><ul><li><strong>Universal</strong>, as music is one of the most universal thing in the world, it can be shared and declined in so many possibilities, everywhere, and by everyone ;</li><li><strong>Passionate</strong>, as music is about art, passion, vibes and feelings ;</li><li><strong>Collaborative</strong>, since by nature music is meant to be shared among people ;</li><li><strong>Playful</strong>, as music is fun and makes us feel alive ;</li><li><strong>Innovative</strong> ;</li><li><strong>Sincere</strong>.</li></ul><p>Very connected to the previous step, comes the moodboard, direct visual expression of the brand attributes.</p><p>Below is my moodboard and brand attributes :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rkjk4qPsCPAniYd2zMPyxA.png" /><figcaption>Moodboard &amp; Brand Attributes.</figcaption></figure><h3>Color Palette</h3><p><strong>I really hesitated on changing the color at the very begining</strong> as I was thinking that the “Spotify Green” was really unchangeable. I could imagine the potential outcry from the original Spotify supporters. It was probably my shyness that was expressing itself at that time, or my fear of not offering something good enough. I fortunately made it disappear quickly, highly motivated by this huge challenge, connected with music, something that I love so much.</p><p>So, here is the new color palette I proposed and why : <strong>music spectrum is known to go from blue to red (in frequencies/light spectrum), so this fact has been the starting point of all my thoughts</strong>. Inbetween blue and red is the <strong>purple color</strong>, and <strong>these</strong> <strong>3 colors perfectly match out with the new brand attributes</strong>, in the meaning of colors (spirituality, energy, creativity, passion, innovation, sincerity). I also redesigned accordingly the Spotify logo, keeping the “music waves” but changing the colors in a gradient.</p><p>Here is a nice summary of the flow of my thoughts :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*m7jYj3p2F6K_sZNB7MZxJA.png" /><figcaption>My reasoning for the new color palette.</figcaption></figure><h3>Typography</h3><p>To finish my new style tile, I had to choose a <strong>new typography</strong> for this new Spotify.</p><p>What more logic and consistent than trying to find <strong>the most universal font ever created</strong> ?</p><p>It is by relentlessly searching for this attribute (perfect universality) that I managed to find the perfect font. I love the story behind this font, and what it conveys to its reader.</p><p>The new font is SST and is declined in 17 variations which makes it be an even better choice as a UXUI designer.<br>Another good point is that SST is more scannable than Proxima Nova. As I am looking for more accessibility, this font perfectly matches my requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djGdkF2ioVbZ-QGALnpeOA.png" /><figcaption>My new typography choice (SST) and why.</figcaption></figure><h3>Hi-Fi wireframes &amp; Prototype</h3><p>Now that all the previous steps are completed, I could move to the Hi-Fi Wireframe and Prototype.</p><p>I show you the final result (hi-fi wireframes) below :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*iZbCif0i405USIS6iVAEwA.png" /><figcaption>New Homepage (Hi-Fi).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZJm0Ikk7szaOB9hYzkHZQ.png" /><figcaption>Hi-Fi Wireframe of the Prototype.</figcaption></figure><p>If you want to try my final prototype or see the video, feel free to contact me, I’ll be pleased to share it with you :-)</p><h3>Tests &amp; Feedbacks</h3><p>I really wanted to do user tests in order <strong>to confront my design to my target and get valuable feedbacks to improve my project</strong>. I tested my prototype on 3 users, and what is valuable is that 2 of them work in the musical industry and use Spotify intensively.</p><p>I received pretty <strong>positive feedbacks </strong>overall about the visual redesign (colors choice ; background gradient ; typography; etc.) and the new information architecture and components (new profile page highly appreciated).</p><p>Here are some improvements I identified thanks to these users feedbacks :</p><ul><li>to balance the use of buttons/scrolls (I would have liked to conduct A/B testings on this specific point);</li><li>to rethink the order for the first screen (ex. to start with playlists).</li></ul><p>I listed all of the feedbacks in my figma file and if I had had more time, I would have made more changes <strong>to converge with the user need</strong>.</p><h3>Key learnings &amp; Next steps</h3><p>As the only judge of the extent of my redesign, I decided not to work on a “simple” redesign (i.e. updating current components) but to work on a more complexe one (i.e. redesigning entire screens, revisit the full information architecture, redefining the brand’s identity). <strong>It is important to adapt the scope based on many parameters</strong> (ex. 3 days to work on the project, number of screens, etc.).</p><p>Next steps could be to work on a “light mode” (light background with a limited use of the gradient, as it could be hard to scan sometimes or for some people) or a solid background with some gradient touches, and test it again on more users matching with my proto-persona.</p><p>I also would have liked to work on all the other pages, to propose a fully finished and consistent product. Another opportunity could have been to polish the final result and work on the contrast and on a redesign maximized in terms of accessibility (to be fully aligned with the “universal” underlying which guided my project).</p><p>I hope that you enjoyed this article, please feel free to comment, share, ask questions… I’ll be pleased to answer and receive feedbacks ;-)</p><p>Thank you for reading me !</p><p>See you for the next project…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21549700910c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[| Case Study #2 | Ecommerce Website]]></title>
            <link>https://medium.com/@lpsfrantz/case-study-2-ecommerce-website-e4512208e60c?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4512208e60c</guid>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Sun, 26 Jun 2022 12:07:16 GMT</pubDate>
            <atom:updated>2022-06-26T12:07:16.199Z</atom:updated>
            <content:encoded><![CDATA[<p>Or the answer to the question : “How might we help local shops &amp; professionals create or improve their online presence to increase their visibility, sales, revenue… and more ?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvHh5vRRauI3yZ7NVxAw-A.png" /></figure><h3>Background</h3><p>Even today, <strong>few local businesses have an online presence</strong>. And when they do, it is frequently to a simple landing page, which is insufficient. However, for a local shop, <strong>an online presence is just as important as the physical location</strong>. An e-commerce website is often the best way to promote the shop, as search engines do support local businesses. It is also a great way to increase sales and revenue by offering services such as delivery or click-and-collect.</p><blockquote>Let’s help local shops and professionals create or improve their online presence to increase their visibility both online and offline.</blockquote><h3>The Challenge</h3><p>Design a responsive website for a local business or professional. In this project, we have to focus our efforts on <strong>organizing the information in a clear way for both the customers and the stakeholders</strong>.</p><p>We planed to use most of the research time for benchmarking and market research.</p><p>In our case, the local shop would like to develop a website in the future. The access to the clients and to the stakeholders was granted, as we spoke with the owner to clearly explain to him what we will work on and what would be very helpful for us.</p><h3>First step : Market Research &amp; Benchmarking</h3><p>We started our project with an extended market research.</p><p>The aim ? To understand the market, who are our competitors, what’s their positionning, do they have a website, and if yes, with which functionnalities, etc. In a nutshell : to have an extensive overview and comprehension of the market in which our client (La French restaurant) is evolving, of our client, and of its competitors. We used 3 complementary tools : the <a href="https://drive.google.com/drive/folders/1_mjBFzBqwQ7DjZ0VLih2zHQkutBa3gHH">SWOT</a>, the <a href="https://drive.google.com/drive/folders/1_mjBFzBqwQ7DjZ0VLih2zHQkutBa3gHH">BRAND BENCHMARKING</a> (on a visual mapping) and the <a href="https://drive.google.com/drive/folders/1_mjBFzBqwQ7DjZ0VLih2zHQkutBa3gHH">FEATURES COMPARISON</a>.</p><p>Thanks to these powerful tools, we gathered a lot of valuable informations as the Strenghts &amp; Weaknesses of the business we are working on (internal factors), the Threat &amp; Opportunities of the market (external factors) but also where are our competitors and where should we position our business (see map) and of course the mandatory features and the ones which could differenciate us regarding our future website. This was very intense, inspiring and we found a lot of valuable data.</p><p>Then, we worked on primary research with 2 different points of view : the one of the stakeholder and the one of the user. Why ? To consider both and have the right balance of each of them in our process. That way, our solution should be fully answering our problem and ideally fit with both worlds.</p><p>We first started with the <strong>stakeholder interview guide</strong> as an appointment was already set up at 4pm the same day.</p><p>The stakeholder interview lasted 1h20min, as the owner was really happy to share his experience and many valuable things about his new business (the one on which we are working on). I have to share with you that 1h20min is a bit too long, but, the good thing is that we get a lot a very good pieces of information and insights.</p><p>Once this step has been done, we wrote our <strong>user interview guide</strong>. This phase of the primary research is really essential as we are designing the (future) product for THIS user and all the following steps derive from this UX research phase.</p><p>I’m not going to speak about the guide in itself, as we already saw this phase in detail in <a href="https://medium.com/@lpsfrantz/case-study-1-wicked-problems-food-sustainability-5ca1e9781061">this article</a>, but I’m going to share the <strong>main insights </strong>we found, using the<strong> affinity diagram tool</strong> :</p><ul><li>Our user <strong>wants to avoid queuing</strong> at the restaurant for diner (even more, on Friday/Saturday nights) even for a very popular restaurant ;</li><li>Our user <strong>prefers to have all the information</strong> regarding the place (contacts/table availability) and food (detailled menu) <strong>before going</strong>, so that he’s sure of his possibilities and avoid any « suspens » so that he can fully enjoy the moment with his friends ;</li><li>Our user (for lunch time) <strong>has little time to eat but doesn ‘t want to compromise on quality</strong>. He wants preferably to order in the neighborhood (as there are plenty of good restaurant) so that he can have a short break walking to collect his food directly at the restaurant and enjoy the walk. Our user can sometimes also ask for delivery, depending on the proximity of the place where he orders food for lunchbreak.</li></ul><p><em>Note. I have to confess that — in trying to do better — we finally had a bad idea (but we didn’t know it yet) : using google forms to get more data from our users and thus have a more representative sample (i.e. 10+ users). On paper it’s a good idea but by making it anonymous +by not putting all the questions as “mandatory”, we ended up with a nice mishmash of data very difficult to sort. Fortunately, we had conducted several interviews in person and there the data collected was much easier to process and use, without wasting time. If we use it again in the future, we’ll have gained experience and will be very sharp about how to proceed efficiently.</em></p><h3>Moving on to our user persona</h3><p>Thanks to all our primary research, what clearly detached is that <strong>our user’s needs are time-dependant</strong>.</p><blockquote>What does it means ? Our user needs slightly change between lunchtime and diner. Why ? Because the context, environments and potential constraints are different between those 2 timeslots.</blockquote><p>Also, what is interesting is that some things remain constant to our users (fitting the demographics and more), as :</p><ul><li>the search for <strong>conviviality</strong>,</li><li>eating dishes with <strong>quality </strong>ingredients (both beautiful and good),</li><li>or even the attraction for <strong>new places </strong>or places offering a beautiful visual aesthetic (view/concept).</li></ul><p>All the interviews we did —<em> complemented by the stakeholder’s experience in the profession</em> — allowed us to draw up the following persona : <strong>FOODIE ANNE-SOPHIE</strong>, a 31 years-old entreprise worker, living and working in the 11th district of Paris, very sociable and epicurean. She likes to take care of herself and eating healthy &amp; bio is definitely a way to do that. She’s a fan of french cuisine. She loves to discover new dishes, to share her lunch with her coworkers and friends and to have good quality and ready meal for her weekday work lunch breaks. Nevertheless, she’s facing a major frustration which is that she doesn’t have time on her lunch break to enjoy the quality of her favorite (french) restaurants.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*m5Sa5PSCLO1-2N0pq0VAZA.png" /><figcaption>Our user persona : Foodie Anne-Sophie.</figcaption></figure><p>This being said, let’s move on to our User Journey Map (UJM).</p><h3>User Journey Map</h3><p>With a perfect knowledge of all aspects of our persona, we are able to stage it in a <strong>perfectly adapted and realistic scenario</strong> as to what our persona could go through, and thus highlight the difficulties that our persona goes through during this precise experience.</p><p>We identified this <strong>double painpoint</strong> which we transformed into a HMW question in anticipation of our phase of ideation :</p><blockquote>« <em>HMW help Anne-Sophie reduce her waiting time for getting her restaurant order and paying ? </em>»</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5nFWT0Ly2eqzqg975602BQ.png" /></figure><p>Now comes the problem statement stage : what is THE exact problem we’re working on ?</p><h3>Problem Statement</h3><p>And as design is about solving problem, let’s capitalize on all that we’ve learned during the previous steps to make our problem statement as much relevant and specific as possible.</p><blockquote>Why ? Because I truly believe that with a really good problem statement comes an even better solution to this problem, since all aspects of it are identified.</blockquote><p>Here is our final problem statement :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*pmcP8PGlLS1RF5F3U6BTZw.png" /><figcaption>Our Problem Statement.</figcaption></figure><p><em>Note. I have to confess that we re-worked a lot on our problem statement because our previous problem statement was focusing on an effective problem (time issue for the user &gt; online reservation) but it was not matching the e-commerce instruction. So we had to change it and rework on most of the previous stages, as it was not aligned anymore (unless for the research phase).</em></p><p>Consequently, we reviewed all the previous steps to come back with something that perfectly fits the brief.</p><h3>Ideation session</h3><p>Now that we have a very clear understanding of who are we speaking to and what is the problem for our user, we need to reflect and generate various ideas. That way, we’ll be able <strong>to taylor the most accurate and adapted solution, based on this.</strong></p><p>We worked quite hard, so much that we ideate very good ideas. We decided to keep the the two most promising which were fitting the needs of our user : a « click &amp; collect » feature on the restaurant’s website and a « QR code » directly on spot (= at the restaurant).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jqy-7yA6M4I-TLooh7KqCQ.png" /><figcaption>Our Crazy 8’s ideation outputs.</figcaption></figure><h3>Sitemap</h3><p>As we are working on a website creation, <strong>we need to be very clear on its organization and its content</strong>. At this stage comes the sitemap elaboration. Based on our benchmark + user insights + our problem, we imagined this sitemap :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n1pthVIbmIn9UY4WQ2pXOQ.png" /><figcaption>Our sitemap.</figcaption></figure><p>Here are some explanations :</p><p>1/ The menu page responds to our user’s request of <strong>knowing what the restaurant exactly serves</strong> (as he is looking for qualitative products, innovative/elaborated dishes or may have a very specific diet) ;</p><p>2/ The <strong>contact page is mandatory</strong> to enable customers to come (+ see features comparison) ;</p><p>3/ We can add that the <strong>reservation page is highly recommanded</strong>, based on our interviews and what the user is clearly expecting ;</p><p>4/ An finally comes our <strong>« click &amp; collect » page</strong>, the solution we provide to meet our user’s needs in this « e-commerce » study case.</p><h3>User Flow</h3><p>Based on our persona and all the knowledge with have around her, we imagined her « happy path » and created the userflow consequently.</p><p>Here is how we created it :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nEX7jQ5UsDUN0giR25Q_AQ.png" /><figcaption>Our User Flow.</figcaption></figure><p><em>Notes. I can add here that </em><strong><em>the step « checking the menu » is not mandatory for the regular customer but could be very useful for new ones</em></strong><em> (as they’re not sure of what they’ll find here, in terms of food). Our regular user will probably directly go to the « click&amp;collect » tab/page as he’s already knowing the restaurant and the food they serve. The blue part means that it is not new pages but « sub-sections » of it or other displaying configurations.</em></p><h3><strong>Lo-Fi Wireframes</strong></h3><p>As we were working remotely, <strong>we decided to make the lo-fi wireframe digitally</strong> (ususally, it is hand-drawn). We represented the main « blocks » with the minimal necessary information for our user to clearly understand what it is about.</p><p><strong>Wireframing (lo-fi &gt; mid-fi &gt; hi-fi) are essential steps in any design process</strong>, from lo-fi to mid-fi and then hi-fi.</p><blockquote>Why ? Because it allows us to define the information hierarchy of our design, making it easier for us to plan the layout according to how we want our user to process the information, based on the user research already performed. Wireframing is also a great way to understand how a user interacts with our interface (a website in this case), through the positioning of buttons and menus on the diagrams.</blockquote><p>Below is our « happy path » in lo-fi wireframe :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lq6QpWZ97bqlYd5WfTwO1Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3EYzI1kKYAIUlpHEERUNw.png" /><figcaption>Our low-fidelity wireframe.</figcaption></figure><p><strong>Our primary device is a desktop as our user is usually at work</strong>, working on a computer, when planning to go at the restaurant.</p><p>Other devices will be : phone (2nd position, because our user could already be outside while looking for a restaurant for dinner) and tablet (3rd position).</p><h3>Concept test &amp; Iteration (on lo-fi wireframe)</h3><p>At this stage, <strong>we want to test it as soon as possible</strong> with real user matching our demographics to validate the concept. It has been done and feedbacks were pretty positive. Since the changes to be done were minimal, we decided to apply them directly in our mid-fi wireframe/prototype.</p><p><strong>Now that we have the confirmation that our concept is useful and clearly understandable by our user, we have to work on a mid-fi wireframe</strong> (and then mid-fi prototype), and then to conduct a usability test to make sure that our product is fully functional and easy to use for our user.</p><p><em>Tips : Testing is an important part of the process : it allows us to deceale many things (from big bugs to small details), at every stage of the design process, and to iterate to improve our product/concept. Good designs are all about consistency.</em></p><h3>Mid-fi Wireframe</h3><p>So, now comes the mid-fidelity wireframe step.</p><p>Here are all the wireframes relevant to our userflow in our persona’s primary device (= computer) :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6-UzGAOSRB0Y7bn5T2nJEA.png" /><figcaption>Mid-fidelity Wireframe, pages 1 &amp; 2.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_q6LKdUQV1JQw-_y-GimJQ.png" /><figcaption>Mid-fidelity Wireframe, pages 3 &amp; 4.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*ZEHUke_VlFF85pnL2huWnw.png" /><figcaption>Mid-fidelity Wireframe, page 5.</figcaption></figure><p><strong>As our user will also go on our website from secondary devices as a smartphone </strong>(for example, on their way to go home right after work) <strong>and a tablet</strong> (after work, already at home, looking for a restaurant where to have diner at night), we also created the responsive designs for both devices.</p><p><strong>We slightly modified the overall look of the website based on 1/ our user’s previous feedbacks + 2/ our researches + 3/ the size of the respective screens.</strong> Our goal is to be <strong>consistent</strong> and make the most possibly <strong>intuitive product</strong> at this stage, for our users.</p><p>Here is shown our happy path’s Mid-fi wireframe for phones :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*BqmIvMhpMbFaCfVesgVsIA.png" /><figcaption>Mid-fedility Wireframe for Phone.</figcaption></figure><p>And for tablets :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n9TePPd5BUE1Ule0-cBeRQ.png" /><figcaption>Mid-Fi Wireframe for Tablet.</figcaption></figure><p><em>Note : through our user research, it was found that the use of the tablet was not necessarily relevant but as the exercise was about responsiveness on 3 devices, we decided to do it anyway (even if it’s not an usual device to be used in this context).</em></p><blockquote>Tip : To use components &amp; variants allows us to update our designs efficiently. With them, we save time, improve the organisation of the components and make the design be more consistent.</blockquote><h3>Mid-Fi Prototype</h3><p>Once we’re done with the mid-fi wireframe, <strong>let’s add some interaction and move on to the mid-fi prototype</strong>. Still based on our previous work, we added the interactions accordingly to our user flow happy path.</p><h3>Usability Tests</h3><p>Thanks to « Useberry », <strong>we conducted Usability Tests with 10 relevant users.</strong></p><p>Here is the heatmap and our results to the test :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/925/1*KFv7NpVMdrPhqeSGfr15zA.png" /><figcaption>Usability Test Results.</figcaption></figure><p>This test was a real sucess. So that the review &amp; iteration here were not necessary. If it was not the case, we should have done some rework on this stage. Thanks to those positive results/feedbacks, we persevered in the exact same way.</p><p>Now that we’re confident on all the previous work already done, and now that we have all the signals in the green from users feedbacks, we can work on our (future) hi-fi prototype.</p><p>In order to proceed, we need to work first on our Brand Attributes.</p><h3>Brand Attributes</h3><p>What does it mean ? When you think of La French, and based on our extended research, what are the attributes you think of ? So, we brainstormed separately (not to influence each other and to see what are the words we chose : are they identic ? different ?) and gather our work.</p><p>Many similar words were picked up so that we came up with 4 brand attributes we totally agreed on :</p><ul><li>NATURAL</li><li>LIVELY</li><li>ELEGANT</li><li>INVITING</li></ul><p>Now that it is clearly defined, let’s move on to the moodboard.</p><h3>Moodboard</h3><p>The next logical step is to work on the moodboard of La French.</p><p>First of all, let’s define the term to clearly understand it : a moodboard is an arrangement of images, materials, pieces of text, etc. intended to evoke or project a particular style or concept.</p><p>Thinking of the 4 brand attributes, and after a quick review (thanks to the design critique done in class with some teammates), we end up with this moodboard :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/1*uJuzJ0BWoGieH63aUfc3_w.png" /><figcaption>La French’s Moodboard.</figcaption></figure><p>After our review (design critique), the alignment with our objective was such that we kept this version.</p><p>Once all the UX has been done, let’s look a bit closer to our UI part.</p><h3>Tile Style: color palette &amp; typography.</h3><p>We wanted our colors and typographies (for logo, headers and body) to perfectly reflect the brand attributes of La French. Once again, everyone in my group brainstormed alone, and then we gather all the information together.</p><p>It was really nice to see that a conscensus on colors was already existing : tones of green for the natural attribute, tones of cream &amp; beige for the lively x inviting attributes, tones of brown for the natural x elegant attributes. Same for the typographies.</p><p>Here is what we came up with :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*UNMKXbmZhc1gP5kpA-xJnw.png" /><figcaption>Our Tile Style.</figcaption></figure><h3>Hi-Fi Wireframe/Prototype</h3><p>Now that we have all the elements we need (both UX &amp; UI), we can create the Hi-Fi prorotypes.</p><p>We started with our user’s primary device : the computer.</p><p>We translated our mid-fi into hi-fi, adding the typographies, colors and always reminding of our brand’s attributes. We tested it during a design critique and the feedbacks were pretty positive so that we persevere in that way and modified just a few things based on the received feedbacks.</p><p>After this quick iteration, please let me introduce you to our Hi-Fi Wireframes of La French’s website, first, on computer :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywzenTULO-CBN2INP8-dkw.png" /><figcaption>HiFi Wireframe on Computer.</figcaption></figure><p>On phone &amp; tablet :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*4WvShagn9KEeXU_K4o6D0Q.png" /><figcaption>HiFi Wireframe on Phone &amp; Tablet.</figcaption></figure><p>And here is <a href="https://youtu.be/Rx4bC_z2Nic">the link to our prototype</a> : I hope you’ll enjoy our video ! :)</p><h3>Key learnings &amp; next steps</h3><p>Ideally, at this stage, a <strong>desirability testing</strong> is good to be done to even more improve the design of our solution.</p><p>Also, our next steps could be to work on the reservation feature (as all the competitors have it + it is plebiscite by the users), to test and then iterate again on our work (to improve again and again) and to developp a client gallery.</p><h3>What’s next ?</h3><p>Next challenge is a 3-days UI challenge : we have to chose an app and redesign it.</p><p>As it has to be well-known, I chose « Spotify ». Why ? Because everybody knows spotify and also I’m currently living for one week with people making music (8 persons) ! It could be great to have some good insights for potential users.</p><p>See you for the next project ;-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4512208e60c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[| Case study #1 |Wicked problems : Food Sustainability.]]></title>
            <link>https://medium.com/@lpsfrantz/case-study-1-wicked-problems-food-sustainability-5ca1e9781061?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ca1e9781061</guid>
            <category><![CDATA[wicked-problem]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[food-sustainability]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Mon, 13 Jun 2022 00:20:18 GMT</pubDate>
            <atom:updated>2022-06-13T16:47:44.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>| Case study #1 | Wicked problems : Food Sustainability.</h3><p>The first project I’ve been working on during the IronHack’s bootcamp was about a very interesting topic : <strong>food sustainability</strong>. We were a group of 3 people to work on this one-week project : Jana, Kübra and I. I won’t tell you more about it right now and I will try, in this article, to share with you the steps of my project, the questions I went through as well as my learnings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_kMCnmGu-edf5LfgtOS7xw.png" /><figcaption>Make organic and local produce be accessible to everyone.</figcaption></figure><h3>Background.</h3><p>In the last few decades, people have become more aware of the importance of good nutrition. But organic food is not accessible to everyone, and is often only available to people who can afford it. Supermarket chains and big food corporations benefit more from the rise of the organic food market than the local producers. Instead of fixing the problem, they are harming the environment with unsustainable models.</p><blockquote>How Might We help people access local seasonal produce, while also fostering fair and honest relationships between producers and customers ?</blockquote><h3>First of all, let’s start with the Research phase.</h3><p>Every UX design project starts with Primary &amp; Secondary Research.</p><p>Let’s start with a <a href="https://www.thehartford.com/business-insurance/strategy/market-research/primary-second-research">definition</a> : <strong>primary research </strong>is <strong>information gathered through self-conducted research methods</strong>, while <strong>secondary research </strong>is <strong>information gathered from previously conducted studies</strong>. Secondary research is usually where most research begins.</p><p>After conducting a secondary research on the internet to be more involved in the subject (with more figures, data and information from reliable sources), we have completed our approach with interviews directly conducted with users fitting with our demographics.</p><p>Our first interview guide was composed of 7 main questions (with follow-ups), all open-ended, to gather as much information as possible from the interviewees. <strong>To listen to the user and to gather information is essential for the whole process of UX design</strong>. After a first test on a potential user, we realized that the interview guide needed some improvements to collect even more accurate/relevant information which will be very useful next.</p><p>We finally came up with 2 interview guides : one for the users already sensitive to this topic, and one for the others. The aim was to adapt the best in each circumstances to obtain the most valuable information &amp; insights possible.</p><p>I share with you some quotes :</p><blockquote>“More simplicity will definitely make me buy more products directly from local producers”.</blockquote><blockquote>“My last experience was at the supermarket because I missed the Sunday market”.</blockquote><p>At this stage, we’re looking for themes &amp; patterns among all the information we gathered from the users. The objective is to analyze &amp; synthesize all the data. Consequently, we started to cluster the elements and name the groups with the appropriate tool called : <strong>affinity diagram</strong>.</p><p>Here is a global overview of how it looks :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VNo0fhJnvGyFSOFPlUAvmw.png" /><figcaption>Affinity Diagram.</figcaption></figure><p>Based on the previous steps, here are the insights we get from this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jzfRpA7lUb7PlHhElBCHnA.png" /><figcaption>Main Insights.</figcaption></figure><p>Now that we have the main insights directly from users, let’s move on to the next step of the process : who exactly is our user ?</p><h3>The user persona.</h3><p>Personas are <strong>fictional</strong>, <strong>composite archetypes based on behavior patterns uncovered during the research phase</strong>. They are used <strong>to set a common understanding of the final user</strong> (regarding its demographics, needs, behaviors, attitudes, goals, motivations…).</p><p>So, here is our persona, “<strong>Conscious Claire</strong>” :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*W3G32ipcJaM9aITmPEli4w.png" /><figcaption>User Persona.</figcaption></figure><blockquote>She is a 35 years-old women, living in a big stressful city (London). She is very busy and has very little time for everything. She wants to leave a positive environmental footprint, to have an impact but with little effort. She’s frustrated because she wants to do more for sustainability but she doesn’t know how.</blockquote><p>Now that we know Conscious Claire better, let’s <strong>further empathize with her </strong>using<strong> </strong>the<strong> User Journey Map</strong>.</p><h3>The User Journey Map and the HMWs.</h3><p>This tool allow us to <strong>map the experience</strong>.</p><p>Why ? To help us <strong>understand and address our user needs and pain points</strong>.</p><p>The scenario we chose here was the following one : it’s Monday evening, in summer, and Conscious Claire has to buy strawberries. As she missed the Sunday market, she has to go to the supermarket. At the end of the experiences, even if she completed the task, she feels really bad about the situation which is not aligned with her environmental values.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-mqoCbhh-wRZo5C_78sLcg.png" /><figcaption>User Journey Map.</figcaption></figure><p>Mapping the experience, we can <strong>clearly identify UX design opportunities</strong> (the orange section, and above all, the red section).</p><h3>The problem statement.</h3><p>Thanks to all the previous steps, and as <strong>design is about solving problems</strong>, we are now going to come up with our final problem statement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*aC5ZWNG3GPI_qRBHw2XFgA.png" /><figcaption>Preparation phase to Problem Statement.</figcaption></figure><p>After a quick preparation phase (see above), here is our final problem statement :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/539/1*9hFVmgU_OJQYFeh_Elwy0w.png" /><figcaption>Final Problem Statement.</figcaption></figure><p>Once the problem statement phase is completed, let’s continue with the ideation phase.</p><h3>Ideation.</h3><p>All the necessary building blocks for our reflection are now in place, so we need to launch <strong>a creative process of production, development, and communication of new ideas</strong>. This phase is called “ideation”.</p><p>The objective? To obtain the <strong>best possible ideas</strong> <strong>which will shape a solution that is all the more appropriate and relevant</strong>.</p><p>There are many methods to do so, but we used the C<strong>razy 8s</strong> and <strong>Worst idea</strong> for this project as they are complementary.</p><p>Here is how ideation looks like :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_R01NI_Gocyfru7vcQQEJw.png" /><figcaption>Crazy 8s ideation method.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J2w8BxC5eH200qWTO8FF-Q.png" /><figcaption>Worst Idea ideation method.</figcaption></figure><p>While we came up with plenty of good ideas (reverse ingeneered or directly coming from the Crazy 8s), the aim is <strong>to select the best one(s)</strong>, which means <strong>the one(s) solving in the most appropriate way our user’s problem</strong>. This is what we call the <strong>feature prioritization</strong>.</p><h3>UserFlow.</h3><p>Once we proceed we feature prioritization, the next step is to draw the user flow. We will focus on the Happy Path of our user which is like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Az3HIxzMMUO1Rq5f2s1V_A.png" /><figcaption>The User Flow.</figcaption></figure><p>With this user flow, we clearly directly respond to our user’s problem : to quickly and easily localize around them all the organic/local product they’re looking for. The <strong>interactive</strong> <strong>map</strong> (+ route in GoogleMap) and the <strong>search bar </strong>(product search)<strong> </strong>are our main features.</p><p>Now that we have the UserFlow, let’s <strong>prototype</strong> our solution : an app.</p><h3>Lo-Fi Wireframing.</h3><p><strong>The earlier we prototype, the best it is to deceal any issue and avoid expensive errors</strong>. Low fidelity wireframing is the way to do so.</p><p>That way, with a lo-fi prototype easy to conceive, we will be able to test it with our users and <strong>check that our solution is fully responding to our user’s need asap</strong>.</p><p>Low-fidelity wireframing and prototyping is in tones of grey, just showing the essential and making it understandable, like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LD9vYgeWtagWCXgULboS5w.png" /><figcaption>Low-Fidelity Wireframing.</figcaption></figure><h3>Concept testing.</h3><p>Of course, making one lo-fi prototype is not enough : if we don’t test our solution, we don’t learn, so we don’t improve and so we risk to miss our objective of perfectly solving our user’s problem.</p><blockquote>Everything now is about iteration.</blockquote><p>We have to iterate and amend consenquently the prototype which embodies our solution.</p><p>Thanks to concept testing, we’ve been able to collect user feedbacks. That way, we modified the previous version of our app to perfectly match with our user’s need.</p><h3>Key learnings &amp; next steps.</h3><p>One of my personnal key learning of this project is that <strong>going through a task analysis before doing the userflow can be useful and so avoid wasting time</strong>. This way, you will feel more comfortable with the user flow to be drawn and it will probably be more relevant than if it had not been done.</p><p>Next steps on this project will be to do the <strong>Mid-Fi</strong> and then the <strong>Hi-Fidelity prototypes</strong>, and also <strong>to develop the other features</strong> of our app to make it <strong>fully effective for</strong> <strong>both our primary and</strong> <strong>secondary persona</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ca1e9781061" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[| IronHack’s pre-work |Challenge #1 : Design thinking.]]></title>
            <link>https://medium.com/@lpsfrantz/ironhacks-pre-work-challenge-1-design-thinking-d5d9baf33bf5?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5d9baf33bf5</guid>
            <category><![CDATA[ux-ui-design-thinking]]></category>
            <category><![CDATA[ux-ui-bootcamp]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Sun, 22 May 2022 13:42:20 GMT</pubDate>
            <atom:updated>2022-05-22T13:42:20.984Z</atom:updated>
            <content:encoded><![CDATA[<h3>| IronHack’s pre-work |Challenge #1 : Design thinking.</h3><p>Hey ! Today I’m going to share with you my experience about the 1st challenge from the IronHack’s pre-work. Ready ? Let’s go !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PE5e2Kgf5aYww08Lcss8NQ.png" /><figcaption>View of the Citymapper app (French version).</figcaption></figure><h3>Introduction to the app : Citymapper.</h3><p>First of all, let’s talk a bit about the company and the application I am going to work on.</p><p><a href="https://citymapper.com/paris?lang=fr&amp;l=fr">Citymapper</a> is<strong> a mobile application for urban travel and route calculation</strong> created in 2011, in London. The application allows users of urban transport to calculate their itineraries in real time, combining several modes of transport (RER, metro, bus, Vélib’, Autolib’, VTC, on foot…). It takes into account public transportation networks, cab and VTC rentals, as well as self-service rental networks, from scooters to bicycles. As of 2022, the application covers almost <a href="https://fr.wikipedia.org/wiki/Citymapper">100 cities</a> worldwide.</p><h3>The problem.</h3><p>Although the current product of Citymapper already solves some of the main problems of urban mobility, there is one pain point for many users : <strong>the different amount of public transport tickets the users have to purchase</strong>.</p><blockquote>Public transport tickets come in paper or plastic cards. Very often buying different public transport tickets is necessary to go from point A to B. And the process of buying these tickets can be very annoying (queues, vending machines that don’t work, etc).</blockquote><p>Finally, things like pricing or purchasing the correct ticket can become a real pain when you are abroad.</p><p>That being said, the objective here is <strong>to create a feature for the app that solves the pain of having to purchase different public transport tickets by different channels</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LhxaQq4g4Ruwom_y08RUMA.png" /><figcaption>Design thinking’s 5 steps.</figcaption></figure><h3>Using the power of design thinking.</h3><p>You might think : “But, how can we proceed to do so ?”. And my answer is simple : using the best tool we have to do so. Design thinking, i.e. five powerful steps can help anyone solving any issue and greatly improve any of the user experience (see previous picture).</p><h3>Step 1 : Empathize.</h3><p>Before engaging more in the task, <strong>I asked myself different questions </strong>(things like : what is the problem I’m solving, who are my personas, which apps are Citymapper’s competitors, what’s the tone/feeling…). The purpose of doing so is to find answers <strong>to sharpen my point of view and thus bring the best possible solution to the problem raised</strong>.</p><p>Then, I prepared an interview guide in order to interview 5 of my friends which have used public transport, and especially abroad. <strong>The aim of this work is to find out what the main pain-points are, or differently said : what are users having the most trouble with</strong>.</p><blockquote>Here are some questions of my guide. The questions are open-ended and the interview is loosely bounded on purpose, to open conversations about the subject and make me see the user’s point of view. At this stage, it’s all about listening.</blockquote><blockquote>— How do you travel in your city ? And abroad ?</blockquote><blockquote>— Do you have any preference in the kind of transportation you chose (in your city/abroad) ? And why ?</blockquote><blockquote>— How do you pay for your transport services (all kind : simple, multimodal, etc.) ?</blockquote><blockquote>— Can you share with me your experiences of paying for transport ? Have you had any bad experiences that you can describe to me ?</blockquote><blockquote>— Do you have an idea of what improvement could be developed for maximum user comfort ?</blockquote><h3>Step 2 : Define.</h3><p>According to these interviews, the main pain points raised by this user panel are :</p><ul><li>A great difficulty to know what ticket to buy for the specific journey planed and where to buy it ;</li><li>Many different public/private transport operators, which potentially means a complex multiplication of applications to download (+ difficulty to download it abroad, if not planned in advance) ;</li><li>Frustration of spending a lot of time in queues to pay for transport tickets (instead of visiting) ;</li><li>The lack of flexibility in payment options in some specific transportation (ex. have the extra money on the bus to pay the ticket directly to the driver) which can be particularly penalizing for users ;</li><li>[Depending on the country,] the language barreer which can be particularly hard in some countries.</li></ul><h3>Step 3 : Ideate.</h3><p>After a brainstorming session, I came up with many different ideas. For sure, not all were good but the idea is to think about plenty of possibilities. I share here, with you, 3 of them as examples :</p><ul><li>Integrate a functionality which generates a kind of already set-up “pre-order” materialized by a temporary QR code. Then, you’ll have to go to an automatic terminal (available in most of the bar-tobacco shops, at the post-offices, at the supermarkets, in the stations, etc.) to pay and validate your order. As there will be a lot of these terminals in every common place, queues will be very short (if any);</li><li>Integrate a functionnality which integrates re-directions links to the differents plateforms and make the user pay for his differents tickets ;</li><li>Integrate into the app a functionality which directly allows the user to pay for the selected tickets corresponding to a selected route thanks to the QR code technology (see pictures right after &gt; prototype).</li></ul><p>I chose very different propositions of very different qualities to illustrate the fact that a brainstorming aims to generate a lot of ideas, some goods, some less. But gathering all the best features, we can obtain a quite good solution at the end.</p><h3>Step 4 : Prototype.</h3><p>Here’s the prototype I drew that I want to show you :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1FfU3Jdwdvf8hIBbOQX8Qg.jpeg" /><figcaption>Lo-Fi prototype : screens 1 to 3 of the paiement feature.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4lx6ViittU2rbzROCGOKkQ.jpeg" /><figcaption>Lo-Fi prototype : screens 4 to 6 of the paiement feature.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPpJt9womhw4jhcbaj5WUg.jpeg" /><figcaption>Lo-Fi prototype : screens 7 to 9 of the paiement feature.</figcaption></figure><p>The main idea is that I wanted the imagined solution to be easy/clear/instinctive. In other words, the most suitable and smoothest way to solve the payment problem both in the simplest cases and in the case of multi-modal transports or different/non-uniform networks.</p><h3>Key learnings.</h3><p>Learning by doing is the best way to improve : the more you practice, the better you become… and it’s very satisfying ! It’s a virtuous loop that you quickly get used to :-)</p><p>I enjoyed applying to a specific context the design thinking five-stage process and get more in details into stages (as the interview guide redaction, the brainstorming process, the drawing of lo-fi prototypes, etc.). Always centered on the user.</p><p>In addition, it was a good exercise of how to conduct an opened-enough interview to get many insights directly from users (without influencing them) and of how to truly listen and practice empathy.</p><p>Thank you for reading my article, and I hope you enjoyed it !</p><p>Take care,</p><p>Laura</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5d9baf33bf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sharing my experience about the IronHack Wireframing Challenge.]]></title>
            <link>https://medium.com/@lpsfrantz/sharing-my-experience-about-the-ironhack-wireframing-challenge-108485c2214e?source=rss-fe48be95801a------2</link>
            <guid isPermaLink="false">https://medium.com/p/108485c2214e</guid>
            <category><![CDATA[uxui-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[ironhack-prework]]></category>
            <dc:creator><![CDATA[Laura Frantz]]></dc:creator>
            <pubDate>Fri, 20 May 2022 21:13:14 GMT</pubDate>
            <atom:updated>2022-05-20T21:13:14.950Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey ! I just finalized the 2022 IronHack’s “Wireframing Challenge” and I wanted to share my experience with you from tree different dynamics : what I’ve learned, what I’ve enjoyed and what I’ve found challenging.</p><p>Let’s go !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TB8YL10HXTuqU0HsXpWJjQ.png" /><figcaption>Illustration for “Wireframing”.</figcaption></figure><h3>Learning.</h3><p>As a newbie in the fabulous world of UX/UI design, I can say that I’m learning at every instant… and I really love that !</p><p>In this specific IH challenge, the aim was to work on WIREFRAMING at different levels, from low-fidelity (by drawing, with tones of greys) to mid-fidelity (main characteristics without too many details) and then high-fidelity (close to the final design).</p><p>I share with you some pictures and screenshots of my work, step by step :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4WOkpa8X0pMejWQ4yFZdHA.png" /><figcaption>Screenshots of the app I chose to analyze and mimic fot his exercise : Canva.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tr331eZrPhukA1-KZhRb8g.png" /><figcaption>Lo-Fi wireframe of the 5-to-7 screens flow I’ve chosen (here: the log-in step).</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t53G5eiPCa3QNqko3aPrPQ.png" /><figcaption>Hi-Fi wireframe of the chosen flow. And I’ve protoyped it so it’s interactive on Figma ;-)</figcaption></figure><blockquote>In fact, my real first step in this exercise was to draw the wireframe with a pencil and a paper, but as it is a real piece of art, I prefer to keep it for me :-P</blockquote><h3>Enjoying.</h3><p>I truly believe that in every thing we invest ourselves in, we need to enjoy doing it. If not, the effort will be useless or impactless.</p><p>The fact is, from my point of view, learning new things in connection with design, tech, questionning the things, creativity, psychology, sociology, analysis,… and so much more really make me feel enthusiastic and highly motivated to dig further !</p><p>Every step is a pleasure for me. Can’t wait to see more !</p><h3>Challenging.</h3><p>What is great when drawing, is that the brain is thinking about what we’re doing and at the same time it’s pushing the reflexion further. It helps conceptualize and anticipate. It’s a great exercise.</p><p>Of course, things can get difficult sometimes, but I truly believe that the best way to improve is to keep doing ! So, don’t drop out when you’re having a hard time, keep trying, searching, testing… and you’ll be highly rewarded !</p><blockquote>UX/UI design seems to be a world full of challenges, that’s exciting !</blockquote><p>I hope you enjoyed reading my experience, it has been a good exercise for me to share it with you :-)</p><p>Take care,</p><p>Laura.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=108485c2214e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>