<?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 Mathieu Mestre on Medium]]></title>
        <description><![CDATA[Stories by Mathieu Mestre on Medium]]></description>
        <link>https://medium.com/@mathieumestre?source=rss-d4f80bd18488------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*OQ1SzXZdXlZ_tXJvjc1Bug.jpeg</url>
            <title>Stories by Mathieu Mestre on Medium</title>
            <link>https://medium.com/@mathieumestre?source=rss-d4f80bd18488------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:56:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mathieumestre/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 CityDrops — Ironhack, Final Project]]></title>
            <link>https://medium.com/@mathieumestre/case-study-citydrops-ironhack-final-project-56542749416a?source=rss-d4f80bd18488------2</link>
            <guid isPermaLink="false">https://medium.com/p/56542749416a</guid>
            <dc:creator><![CDATA[Mathieu Mestre]]></dc:creator>
            <pubDate>Fri, 28 Apr 2023 21:44:58 GMT</pubDate>
            <atom:updated>2023-04-28T21:44:58.852Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case study CityDrops — Ironhack, Final Project</h3><p>Hello dear reader,</p><p>This article is about my last project of the Ironhack UX/UI bootcamp. For this project, we worked with Mike van de Noordt, founder of CityDrops. Mike is a designer part of the design collective LuzidLab that founded CityDrops, an app that creates Augmented Reality Content and Experiences in the public space.</p><h3>Brief</h3><p>The brief for this project was to create an MVP of the app (native IOS) by focusing specifically on the flow of dropping a drop. Dropping a drop is basically dropping an element in augmented reality. This element can be a digital artwork, a photo, a video, an audio or just a comment for example. Mike wanted us to imagine the most simple and userfriendly userflow for his most basic functionnality : dropping a drop. Mike already had a working prototype but he wasn’t fully satisfied on the userflow he had created. Our main focus on this project was thus interactive design.</p><h3>Research</h3><h4>Competitor analysis</h4><p>We started off by doing secondary research. We first had a look at the competitors by doing a competitive analysis and a competitor feature comparison.</p><p>We found out with our research that competitors had developped AR apps mainly for city tours or for events. Competitors in this field have few functionalities for everyday users and usually suppose a technical background to integrate designs and templates for example. Overall, competitors in this field seemed to be a bit late technology-wise (with AR not being fully persistent for example) and a lot were still in Beta versions.</p><h4>Interviews and affinity diagram</h4><p>We then proceeded to conduct interviews. We interviewed 4 different people to learn more on AR use and habits.</p><p>During the interviews we discovered actually that people did not use AR that much and some had never used it at all. An important insight we got was that people would only see use of AR if there was a specific need.</p><p>We learned that a specific need was for example using AR to discover new cultural and artistic elements in their city. Our interviewees felt that they didn’t know enough local spots in their city, especially went it was related to culture and arts.</p><p>This led us to focus our usecase on discovery of events and cultural and artistic pieces in a given city.</p><p>With the interviews we were able to create an affinity diagram with the main topics that stood out from our interview insights such as experience with AR, frustrations of users or AR applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qKIdg597WG3N8k6QcJGRxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xatALywSHvLHJFQvnr0gCQ.png" /></figure><h3>User persona</h3><p>With our interviews we were able to construct our user persona. We went with the name of Experimental Eva. Our persona basically represents a city dweller curious to discover more cultural and artistic venues and pieces in her city.</p><p>Her goals are : <br>-Connect with the local community and like-minded people<br>-Attend orchestrated events<br>-Explore the urban city<br>-Discover street art and live events<br>-Share her whereabouts with friends</p><p>Her frustrations are : <br>-Overwhelming information on things to do in a big city<br>-Sold out events she wants to attend<br>-Lack of curated local recommendations<br>-Lack of centralised information</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*qtOuhlLAi3-rouY2377NzA.png" /></figure><h3>Ideate</h3><h4>How might we’s and Mosocw Method</h4><p>Once our persona created, we moved on to the ideation phase and proceeded with how migh we statements. This helped us to write down problems concerning our subject matter and all the functionalities that could help solution these.</p><p>We came up with a brainstorm of all the functionalities we though of and then classified them by using the moscow method. For example, amidst the must have functionalities we decided to go with a heatmap, a localisation option and search filters to find out where cultural and artistic events are held near you according to the quantity of drops that are left.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nv8m9pJsYp-tggkXIEnc8A.png" /></figure><h3>Prototype</h3><h4>Low-fi</h4><p>We then moved on to create our low-fi prototype. As mentioned, we focused on the flow of leaving a drop in AR.</p><p>We did our low-fi sketches having in mind that the users had to leave a drop easily from their camera and the AR option opened.</p><p>One major concern was to make it easy for the user to leave a drop while having a clear view of his surroundings. We didn’t want to overcrowd the screen as it is supposed to be an immersive experience.</p><p>We tested our Low-fi and got positive feedback on our prototype. The flow was easy and understood by our interviewees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QRcDH9Y-_gLdbhMN6ifj9g.png" /></figure><h4>Mid-Fi</h4><p>For the mid-fi, we focused on the editing of the drop. This was a tricky functionality to integrate and during our tests, we realized it was a part that wasn’t well understood by the users.</p><p>We tried to make it clear for users that they could edit their drop and add titles for example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u_Z-pl6tf9oyT5r4ylIBdg.png" /></figure><h4>Hi-fi</h4><p>Our Hi-fi was basically an application of our style guide to our mid-fi. Since we finished the main flow, we had the opportunity to develop other flows such as finding an event based on the quantity of drops in places in your cities and the heatmap to have a visual view of popular drops near you.</p><p>In our style guide, we tried to take complementary colors to the lumo green that was already characteristic of the brand. We also made a lot of 3D buttons by using effects since it is an AR app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*xZgsByYuqAVhgPPPgVApsQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*b8auM1DUi5-axCAkZNRfjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*Xsk8hV0vkH1tZmOoV7Z4XA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*9EtJu-lBW-yY6hxQLWQCRg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*OyNBi7zbXAtoO4f7NWQY-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*WLcsrFBnzzBzzHyRiSyk3Q.png" /></figure><h3>Learnings</h3><p>This project was quite challenging because the subject matter was AR. It was difficult to imagine our low-fi, mid-fi and hi-fi so that it conveys the AR feeling in 2D.</p><p>Overall, it was a great and interesting project and I thank Mike for this super opportunity.</p><p>Thank you for you reading !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56542749416a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project 3 Ironhack — Redesigning an app (Tricount)]]></title>
            <link>https://medium.com/@mathieumestre/project-3-ironhack-redesigning-an-app-tricount-a72f1887a7a9?source=rss-d4f80bd18488------2</link>
            <guid isPermaLink="false">https://medium.com/p/a72f1887a7a9</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Mathieu Mestre]]></dc:creator>
            <pubDate>Sun, 26 Mar 2023 21:17:06 GMT</pubDate>
            <atom:updated>2023-03-26T21:17:06.033Z</atom:updated>
            <content:encoded><![CDATA[<h3>Project 3 Ironhack — Redesigning an app (Tricount)</h3><h3>Intro and brief</h3><p>Hello reader!</p><p>For this project, we were asked to clone and redesign an existing app. I chose to go with <em>Tricount</em>.</p><p>Tricount is an app that allows to organize finances between friends. The principle is simple : you create a “project”, for example a trip between friends or a project to layout expenses between roomates. Each person enters their expenses and indicates who is concerned by the expense. The app then automatically calculates the balance between participants and indicated who owes who and how much each each owes to one another.</p><p>I chose this app because it is a very popular app in France but I thought that there was room for improvements in terms of UX and overall design.</p><p>I personally like this app because it is so simple to use and straight to the point. In my opinion, that is why people use it and why it is so widespread in France, even though other apps offer similar features (Lydia for example).</p><p>However, I have always found some elements to be incoherent and I use this app because it is functionnal but I don’t particularly enjoy using it otherwise.</p><h3>The cloning</h3><p>We were first asked to clone between 3 and 5 screens of the app. Here are my clones of Tricount (on the right) and the original screenshots of the app on the left :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*cunCwUBr6TA62yKyIH5TeA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*8fN7XTy2gXVQTZjUOMY7Mg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*zqpZ-P_lE79OEYy7UyBm_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*HIhBh_b0tp7hogGcgRKFKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*nLYdU8d8utWHCqOgmsLvGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*ixkc5EVlWX8NBoEkobWI1A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*jX-YexaTmWvmC8r0x-JmSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*e5_7feMaxN92UMkOePRQ6Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/1*eEOBRalJeOn-FF3AW3j8dA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*LSUeusjUN255zX8itDDlbw.png" /></figure><p>This exercise was interesting. It allowed me to train my skills on Figma and play with components, variants and elements of components. I also sketched some icons that I couldn’t find.</p><p>It was interesting to see that some elements that I have always felt a bit “off” on the app were actually problems of alignment for example. I also noticed that some UI elements were unclear such as the green and red button on the left of projects (first 2 pictures) or the blue notifications on the right of the name of the projects.</p><p>As you can tell, the app is very simple but still some unnecessary information appear in some places such as the information question mark regarding the reimbursment mechanism on the app.</p><p>I noted all those elements while doing the clone so that I could take this into account into my redesign.</p><p>Heuristic analysis</p><p>After the cloning, I had a good idea of the attributes of the app and proceeded to do the heuristic analysis.</p><p>This tool helps to understand how an app and a visual design organizes information and communicates the right messages to the users.</p><p>Some elements important to the heuristic analysis are the visibility of system status, the match between the system and the real world, user control and freedom, consistency and standards or error prevention for example.</p><p>Doing this exercise, I found out that the tricount app was pretty well built and not too confusing for the user. In other terms, it serves its basic purpose which is finance organization and reimbursments between friends.</p><p>Some elements were still unclear such as tags on projects or notifications but as they are secondary on the app, this does not cause too much struggle for users.</p><h3>Visual competitive analysis</h3><p>We were then asked to do a visual competitive analysis which basically means analysing the design elements of competitors.</p><p>To do so, I simply went on the app store and typed in Tricount to see which other apps would pop up in the same field that I didn’t know of.</p><p>I found 2 similar apps which are Splitwise and Split. Here are the visual competitive analysis I did :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zE3NWNWgmxBoeflSJoNMxQ.png" /></figure><p>I found during this exercise that these two applications had quite modern and colorful designs for finance apps. However, the icons felt a bit off to me and a bit outdated. The rest was pretty classic with a very simple design that didn’t take much risk.</p><p>The UX of the apps however could clearly be improved in my opinion and tricount felt much more intuitive and straight to the point with the + button in particular on the homepage which allows you to create a project right away, and + button inside the projects to quickly enter an expense.</p><h3>Moodboard</h3><p>After completing the visual competitive analysis, I went on to do my moodboard for tricount’s redesign.</p><p>I didn’t want to go for a classic finance app design in plain blue, which is what you usually seen for this type of sector.</p><p>After finding some modern designs with colors with “noise”, I opted for this option which I found visually appealing and modern, but without compromising the reassuring aspect of finance apps, which at the end of the day remains important.</p><p>One of the feedbacks I had was that I put too much UI elements in the moodboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yIcskiU0fiKsr9rhFUC8Dg.png" /></figure><h3>Redesign</h3><p>After doing my moodboard I could proceed to the redesign.</p><p>As I mentioned, I opted for a modern design especially playing with the colors. Here is below the color palette I decided to use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*biDo1SsoCSohR8Wsak8ueQ.png" /></figure><p>I got these colors playing with gradients and I found this match to be visually satisfying.</p><p>I decided to add “noise” (grain basically) on the colors because I really enjoy this effect and am myself a big fan of this type of design and texture. In my opinion, it feels modern and a bit original, as I feel we don’t see “noise” too often on colors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*5pojUuDMhbzJZCBQhTx4Xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*TCwYI2N0GniPiixT5T3oXQ.png" /></figure><p>I basically kept the original features of tricount because as I mentioned, I love the simplicity of the app. That is why I kept the button at the button so users know immediately what to do when opening the app : creating a project or entering an expense.</p><p>I added photos of the participants and icons for each project and a possibility to archive past projects so that the screen is not overloaded. Also, all the projects do not appear and you can click on “show all” to have more details. Again, so that there is a bit less information on the screen for the users.</p><p>I also made the green and red colors of the projects more obvious and added the amount owed or the credit a user has for each project to make it more clear on the homepage. I hesitated to do a small dashboard on the homepage but I thought this was unecessary considering how simple tricounts tries to be (and I like it that way).</p><p>One of the feedbacks I got was to make the button smaller. It was intentional to draw the users to it immediately, but i understand now that it was a bit too big.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*IsZ5CJGH7_ivpNc7rikVsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*CorKq-Rsg_KnFYMUh6foAw.png" /></figure><p>On the screens below I also kept the main features of tricount. I made it a bit more visual and added an option to take a photo of yourself for each project. Tricount is an app where friends make jokes and add themselves funny names according to the project so I thought this could be a fun feature. I also took out a few icons when creating a project to leave in more space.</p><p>For the expense frame I also tried to make it more visible and have icons and participants displayed so that users immediately understand what the expense is about and who is concerned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*GtioR9r8uIM5nyMzWc3fGQ.png" /></figure><p>For the final frame I tried to keep the balance feature of tricount which I find very useful and made the reimbursments cleared. Again, in a glance, users know how much they owe or how much a friend owes them. Here it is not shown but there is of course a possibility to reimburse a friend directly on the app.</p><p>Here in retrospect, I am not very satisfied with proportions and I would have made the reimbursment buttons smaller and with more space between them.</p><h3>Learnings</h3><p>I learned a lot during this project. It was hard at first choosing an app because I wanted something challenging in the redesign but I didn’t want to pick an app for which I already loved their UX/UI. I wanted some flaws to implement improvements on the redesign.</p><p>It was a really fun project to work on and I learned a lot, especially on the heuristic analysis that I found super helpful.</p><p>I also learned that it is not easy to redesign an app and at the same time keep the main features but also reorganize information. Also, I found it quite difficult to take distance from the original app to create something totally new. There is always the original design of the app in the back of your head and I think it is important to take distance from this in order to be more creative.</p><p>I hope you enjoyed this case study and thank you reader for making it this far, I appreciate !</p><p>Have a great day :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a72f1887a7a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Case Study One : Public Hospitals]]></title>
            <link>https://medium.com/design-bootcamp/ironhack-case-study-one-public-hospitals-68bfd3221b6b?source=rss-d4f80bd18488------2</link>
            <guid isPermaLink="false">https://medium.com/p/68bfd3221b6b</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mathieu Mestre]]></dc:creator>
            <pubDate>Tue, 07 Mar 2023 07:59:52 GMT</pubDate>
            <atom:updated>2023-03-09T03:12:21.493Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Ironhack Case Study One : Public Hospitals</strong></h3><h3><strong>The brief</strong></h3><p>Technology is changing the way we interact with each other. Many processes and tasks that required a long time to do in the past are now as simple as pressing a button.</p><p>As the public system incorporates technological solutions to big infrastructures, our experience as citizens should see that change too. <strong>How Might We transform the end-to-end experience in public hospitals?</strong> For this project, you could take the point of you of a patient, a doctor or even a visitor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*dokyP61Nq5xUwhHO" /></figure><h3><strong>Approach</strong></h3><p>For this project we followed the design thinking method and it’s 5 classical steps : Empathize (1), Define (2), Ideate (3) Prototype (4), Test (5).</p><h3>1. Empathize</h3><p><em>Secondary research</em></p><p>We started this project with secondary research on the theme of Public Hospitals to learn more on the challenges found in this sector. The subject being broad, we decided to narrow things down by searching for recent news in the public hospital sector.</p><p>We found several interesting inputs on this topic. Amongst these, some information on current problems that public hospitals face in different countries regarding patient and medical staff experience. For example long registration times, long waiting lines for medical treatment, long waiting time for a bed, risk of infection from other patients or even stressful working conditions for healthcare professionals because of congested ward. We also read about interesting innovations being tested in hospitals such as 3D mapping and geolocalization in hospital premises or hardware solutions helping pre-diagnosis of patients in waiting rooms.</p><p>These articles made us dive into the subject and actually gave us some valuable inputs afterwards when brainstorming of solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c0-2C-mWO31EIRiK" /><figcaption>Summary of our findings in our research</figcaption></figure><p><em>User Interviews</em></p><p>This research was key to validating some assumptions that we now had to test during user interviews.</p><p>We thus decided to conduct 5 user interviews, each user having had a recent experience in a hospital, whether in their own country or abroad. In accordance with our findings during research, we decided to focus on users having made a spontaneous trip to the hospital. In other words, users who had to go to the emergencies department (excluding users and experiences with an appointment to the hospitals).</p><p>We first drafted an interview guided that we agreed on and went on with the interviews.</p><p><em>Affinity Diagram</em></p><p>Once the interviews concluded, we made an Affinity Diagram with the insights gathered. We organized the most important insights by themes and proceeded to vote (by use of the doting method) on the key themes that stood out the most. Some examples of themes that stood out were quality of medical process, clarity and communication, lack of technology or navigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a0KLhxMEK7RagvCc" /><figcaption>Our Affinity Diagram</figcaption></figure><h3><strong>2. Define</strong></h3><p><em>Empathy Map</em></p><p>With the help of the affinity diagram we had drafted above, we then proceeded to create an empathy map. This tool helped us qualify and define who our users were, what they felt, said and did but most importantly to understand more precisely what were their gains and frustrations regarding their experience in public hospitals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H8RmG4AsfPX5tnzD" /><figcaption>Our Empathy Map</figcaption></figure><p>To put it in a nutshell, we understood here that we were dealing with patients seeking immediate medical treatment in public hospitals and that found hard to navigate inside hospital campuses, had trouble understanding medical processes and that wanted a fast, clear but qualitative experience in medical treatment.</p><p><em>User Persona</em></p><p>The insights from these tools then led us to create a typical user persona for our case. We chose to go with Active Alexa who basically had an accident in South Africa while filming a scene on set (poor Alexa).</p><p>During this exercise, we would continuously look back at our insights from the tools used and in particular our user interviews to make an archetypical user (a patient here). A focus was made on her goals and pain points as we knew this would be of precious help after in the ideation phase, brainstorming for solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/0*VJ0-2C_VP07eIG5a" /><figcaption>Active Alexa, our User Persona!</figcaption></figure><p><em>User Journey</em></p><p>We were starting here to see much clearer into who we had in front of us and had a better understanding of the challenges faced by our Alexa.</p><p>We were therefore able to proceed to the user journey (here again, the insights from our interviews helped us a lot).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CFewdbDRnqg5dcbb" /><figcaption>And her journey!</figcaption></figure><p>This user journey was very insightful because it was now clear that the user experience in public hospitals (especially abroad) can be quite chaotic and the curve of emotion very unstable. Choosing the hospital to go to, getting to the emergency department, knowing how much time you will have to wait, having knowledge of medical procedures or even information on the followup can be a great challenge for users and a factor of stress.</p><p><em>Problem Statement</em></p><p>With all the information we gathered, and in particular now that we had the user persona and user journey in front of us, the problem that stood out was clear.</p><p>Stating this problem in a concise and formal way is however a major step in the design thinking process. It is an important exercise as we then referred to this problem statement at each step of our ideation and prototyping phase.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BAGgXJpWfQg_8Soh" /><figcaption>Our propositions and final draft of our problem statement</figcaption></figure><p>We all proposed a formulation to finally end up with a common problem statement by vote and discussion.</p><p><em>How might we’s</em></p><p>Our problem statement being set, we then directly addressed it with our How Migh We statement to put into solution our problem in a dynamic way.</p><h3>3. <strong>Ideate</strong></h3><p><em>Crazy 8s</em></p><p>Now that everything was set, we could finally sit down and brainstorm solutions. To do so, we decided to use the crazy 8’s method which consists of sketching 8 ideas that address our problem statement in 8mn (1mn per idea).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*agmGSVjzY0gDui5-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6Y980M5WY6OTlJZC" /><figcaption>Our Crazy 8’s propositions</figcaption></figure><p>As you can see, this exercise was quite challenging and it was hard to come up with 8 ideas in 8mn but we did our best haha.</p><p>We then discussed about the ideas that had a good potential for our app considering the insights we had gathered.</p><p><em>Concept sketches</em></p><p>First, based on our crazy 8’s, we drafted concept sketches of our product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gLpCDNBBI3Rsvm9M" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*k60QKzP3xZRnsGJP" /><figcaption>Our 1st concept sketches</figcaption></figure><p>We were trying to tackle a certain flow: when users without an appointment at the hospital try to find the correct hospital (having information on affluence) and getting there in the right department all while facilitating the admission process, both for patients and medical staff. We tried to keep it as simple as possible with the fewest frames possible (considering we are dealing with someone potentially in vital emergency).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W9ZAegHiTEEuOMrw" /><figcaption>Our iteration on concept sketches</figcaption></figure><h3><strong>4. Prototyping</strong></h3><p>We iterated until this final low-fi prototype version :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j99M0qm1tf4lJ2gd" /><figcaption>Our final low-fi prototype</figcaption></figure><p>Amongst the key features we decided to implement : <br>1) Emergency call button to the regional call central to call an ambulance or to know if it is necessary to go to the hospital or not<br>2) View of the live affluence of emergency rooms of nearby hospitals to help users choose the one they want to go to <br>3) Details and particularities of each of the hospitals proposed on the app<br>4) Easy online registration form to facilitate admission once the patient arrives at the hospital and to lay out specific needs (wheelchair, etc)<br>5) QR code on the user profile to present for medical admission <br>6) Possibility to upload medical documents</p><h3>5. Test</h3><p><em>Concept testing</em></p><p>We concept tested our low-fi prototype with 2 users. We had some great feedback to understand how users navigated on the app and what felt unclear to them. For example users didn’t seem to understand what the + button on the second frame was for. They also validated the usefulness of some key features such as the QR code or the affluence and live view on the map of capacity of the nearby hospitals.</p><h3><strong>6. Offline component</strong></h3><p>We were asked to come up as well with a non digital solution for our problem. This is where the secondary research helped us a lot.</p><p>Not inspired at first, we then remembered the article on french hospitals that were implementing hardware solutions for pre diagnosis in the form of a “smartphone like” device</p><p>that takes heart rate, tension, and reads general health infos of the patients.</p><h3>7. Learnings</h3><p>We learned a lot through this first project by applying the design thinking method and puttijng it into action with real deliverables.</p><p>In summary, the biggest pain points we identified were :</p><p>-Navigation on the hospital campus and finding the correct department are often stressful processes.</p><p>-The admission process is long and not fluid.</p><p>As a team, we tried to think of the difficulties that we might face with our solution. We identified that there could be disparity between hospitals and their ressources and it could make it hard to implement a common solution.</p><p>As a solution for our problem statement, we tried to make a simple product :</p><p>-We digitalized the classical admission process as well as the communication between patients and hospitals.</p><p>-Our solution tackles the two sides: we make patients save time and allow hospitals to better organize their ressources.</p><p>I think my team and I made a great job and most importantly, we had fun working on this project. I am super excited now to advance in my progress and to soon work on Mid-Fi Prototypes.</p><p>I hope you enjoyed this article and your read!</p><p>Have a great day :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68bfd3221b6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhack-case-study-one-public-hospitals-68bfd3221b6b">Ironhack Case Study One : Public Hospitals</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack Challenge 2 — Wireframing TooGoodToGo]]></title>
            <link>https://medium.com/design-bootcamp/ironhack-challenge-2-wireframing-toogoodtogo-9622b57df731?source=rss-d4f80bd18488------2</link>
            <guid isPermaLink="false">https://medium.com/p/9622b57df731</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Mathieu Mestre]]></dc:creator>
            <pubDate>Sat, 11 Feb 2023 17:07:15 GMT</pubDate>
            <atom:updated>2023-02-14T07:07:34.383Z</atom:updated>
            <content:encoded><![CDATA[<h3>Ironhack Challenge 2 — Wireframing TooGoodToGo</h3><p>For this challenge I chose the app TooGoodToGo (an anti-food waste startup) simply because I think it is not only an awesome idea but also a great mobile application. It is straight to the point, simple and fun to use. I use it almost on a daily basis and that is why I wanted to recreate the wireframe of one of the flows of the app, which is the reservation of a food basket from a nearby commerce (most common flow).</p><p>The UI elements of this flow are the following : <br>-Dropdowns <br>-Buttons and Call to actions <br>-Text input field (search engine)<br>-Toggles</p><p>The task analysis here is to make the users choose a nearby commerce they like and order a basket of unsold goods to pick up at a certain time of the day. During this process, the users can have details (or not) on the basket that will be prepared at their arrival and also check the reviews of other people that have already purchased and picked up an anti-waste basket there (info on the quantity and quality mostly). This helps the users make their decisions on which commerce they will order a basket from.</p><p>Here is the wireframe I made on figma for this particular flow on the app (with the screenshots of the real application on the right). You can read from left to right :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlwiXFlPuvg6PyvYgsj6pw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bFqp6A43IfqR4_uqrZyOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6UA67s0wHoGzWEQFMi05Rw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niDU18a6HOQ-milqkds8Ig.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dYHmcFIcxMmJZG3q__cpjQ.png" /></figure><p>I really enjoyed doing this challenge even though I had some difficulties to use figma at first. More precisely, I didn’t know how to hide the purple components that I picked up from the Ironhack Wireframe Kit from showing on the screen. Also, I didn’t know exactly how to align everything correctly and make everything coherent and harmonious in terms of scale, size, etc. I also had trouble being consistent on the use of the same shapes (for text elements or icons for example). Moreover, I didn’t understand how to modify quickly shape, size and colours from the components given in the kit which I found frustrating. Nevertheless, I am eager to learn more on how to use this powerful tool and I really had a great pleasure practicing on it. I learned a lot and I was really happy getting the hang of the tool.</p><p>I hope you have a great day !</p><p>Mathieu</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9622b57df731" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhack-challenge-2-wireframing-toogoodtogo-9622b57df731">Ironhack Challenge 2 — Wireframing TooGoodToGo</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ironhack’s Prework: Mathieu Mestre -Challenge 1 (Design Thinking City Mapper)]]></title>
            <link>https://medium.com/design-bootcamp/ironhacks-prework-mathieu-mestre-challenge-1-design-thinking-city-mapper-3e6aebe26d49?source=rss-d4f80bd18488------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e6aebe26d49</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Mathieu Mestre]]></dc:creator>
            <pubDate>Fri, 10 Feb 2023 17:53:45 GMT</pubDate>
            <atom:updated>2023-02-14T07:07:36.335Z</atom:updated>
            <content:encoded><![CDATA[<h3>Background of the company</h3><p>For the Challenge n°1 I decided to focus on the application CityMapper. It is an application that I use all the time and that I deeply love. It is rare to find such a good app in which I clearly see the everyday utility and that actually makes me want to use it all the time.</p><p>As a French person, I can tell you that we literally have an app for public transportation (RATP — the operator of the metro and bus itself) that existed before CityMapper. But the fact that CityMapper’s UX/UI is so good just made most people (in Paris at least) use it instead of the RATP one. This says it all.</p><p>I really like this app because it is straight to the point, so easy to use and has functionalities that I didn’t even know I needed such as live localization and notifications to remind me where to stop during my route for example. It is seemingless. Of course, as it deals with transportation, it is by definition a useful app, but still. I also very much like this app because it reconciled me with transportation by bus because the bus schedules are shown live and are made very clear.</p><h3>Identified problems</h3><p>What CityMapper however lacks is a functionality to buy tickets on the app. Back in Paris, I am used to taking public transports and having my “navigo” pass. This means that I don’t have to worry much about tickets and zones. However, where I now live (Lisbon), or whenever I travel, my main pain point is knowing where and what tickets to buy. In last january, I was abroad and actually bought the wrong ticket and got fined for that. Another difficulty can also be simply losing your ticket during your trip. So in general, buying one or more tickets for relatively complex routes can be stressful, and even when you think you have done things correctly, you could be wrong and get a fine like I did. This process of buying tickets abroad (knowing where and what tickets to buy) is also the main pain point I identified during the conduction of my interviews.</p><p>Indeed, a lot of anecdotes in the same sense as my own experience previously described were told to me during the interviews regarding the purchasing of tickets. People want to enjoy their time abroad, stress free, and usually have no clue as to how the transportation system in the country they are visiting works. They also want to have a good visibility and benefit from the special offers (student status, or the reduction you have buying 10 tickets for example).</p><h3>Difficulties met during the interviews</h3><p>The principal difficulties I had during the interviews was to cut through the chase without orienting the interviewees. Indeed most people would talk about their experiences, emphasizing the need for clear maps, routes, transport schedules etc. This was a difficulty because I wouldn’t get valuable insights as these topics are the pain points City Mapper <em>already</em> solves.</p><h3>Solutions</h3><p>When the aforementioned problem was presented to me, I tried thinking of different solutions:</p><ul><li><strong>The first one, </strong>which is the most simple, is integrating on the app a system to directly purchase the necessary tickets for your trip (without having to go to a guichet to buy them). So for example, the app geolocalizes me (or I enter the position from where I will be leaving) and I put the destination I want to go to. This for example makes me take a bus and then a metro let’s say. If I want to do this trip, I can directly checkout and buy the combination of tickets that is necessary directly from the app (connected to my credit card info). Once the purchase is done, the app confirms my purchase and I just have to present my QR Code if a control occurs during my trip.</li><li><strong>The second solution</strong> is a bit more complex but even smoother, in my opinion, in terms of user experience. Let’s say I have to make the same trip. Here, I can check the itinerary on the app first and it gives me an indicative price. Then, I go out directly to take my bus, without buying anything. When I start my trip, I indicate to the app where I am starting my trip (bus line 50 for example). I repeat this when I finish my trip. With my localization, the app understands what trip I made. The app recognizes the trip I am doing and will make me pay only for the trip I have taken (I can for example come out one metro station earlier). So when I am done, I just have to indicate that to the app which will then make me pay for the trip I actually did. The app sends me a reminder to do so when it sees I have finished my trip (my speed will have decreased and that is how the app would understand this). If I still forget to do so, the app understands where I finished my trip and takes into account the closest station to make me pay the correct price for the trip.</li></ul><h3>Prototype</h3><ol><li>Once you have put the itinerary on the app, here is what you would have : the detail of the route and the price in blue.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJhrqLGwJwKjhRiDJRoRLQ.jpeg" /></figure><p>2) If you scroll down, you would then have this below. Basically, all one has to do is click the button “start”. As explained, the app understands the trip that is going to be made by your search and live localization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHFKk0gKa7VZh8cJfRDXTw.jpeg" /></figure><p>3) Then, all one has to do is to indicate to the app when the trip has ended. Either manually, or through the reception of a notification (see below the 2 pictures) :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*agvA5fIwCF9Sd-7R9_4Vdg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vHDGihuoILlu2KA0jC-3EA.jpeg" /></figure><p>4) If the person did not click the stop button, to prevent paying more than the actual trip, the app understands that the trip has ended (with your speed and localization as explained before). Here is what you could receive :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iOCOO9010Ydl5inOPXSFsA.jpeg" /></figure><p>5) Finally, when the person has pressed the button stop, or if his trip has ended by intervention of the app, you would see this below (or receive it through a notification in the second case) :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHnR5NH4qZ6U4I0kSMybEQ.jpeg" /></figure><p>Just a precision here. In many countries, you can buy 10 tickets at a time for example (often at a reduced price). Instead of having to buy this beforehand, the application would understand that you have made 10 similar trips (in the same zones for example) and would make the discount at the 10th trip. This way, each person would get the proper discount on the trips they make without having to take that decision at the beginning and would not have to buy directly the 10 tickets. Also, it would entice people to take public transportation as it is somewhat “gamified”. This responds to one of the other painpoints the people interviewed had.</p><p>N.B : For the sake of the exercise, I assume that people have already indicated in their profile data their particular status to benefit from other price reductions (student, large families, etc).</p><h3>Learnings/takeways</h3><p>Here are the following things I learned through this process :</p><ul><li>Conducting interviews with potentiel users</li><li>Identifying relevant pain points and brainstorming solutions</li><li>Making a fast prototype with pencil and paper (thus organizing and prioritizing ideas into functionnalities)</li></ul><p>I hope this article was interesting and that it responds to the challenge!</p><p>Have a great day reader,</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e6aebe26d49" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ironhacks-prework-mathieu-mestre-challenge-1-design-thinking-city-mapper-3e6aebe26d49">Ironhack’s Prework: Mathieu Mestre -Challenge 1 (Design Thinking City Mapper)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>