<?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 Antoine Pittilloni on Medium]]></title>
        <description><![CDATA[Stories by Antoine Pittilloni on Medium]]></description>
        <link>https://medium.com/@antoine.pittilloni?source=rss-3e2eed324a4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b9lyNpg2X3QIYicMGilleg.png</url>
            <title>Stories by Antoine Pittilloni on Medium</title>
            <link>https://medium.com/@antoine.pittilloni?source=rss-3e2eed324a4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:03:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@antoine.pittilloni/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[Bloom — A self-growth app]]></title>
            <link>https://medium.com/@antoine.pittilloni/bloom-a-self-growth-app-34549c65e491?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/34549c65e491</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[self-growth]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[wellness]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Sun, 26 Feb 2023 13:30:15 GMT</pubDate>
            <atom:updated>2023-02-26T13:40:23.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*qCUkPGfy25S4-ZG3_MtPIQ.png" /></figure><h3>Bloom — A self-growth app</h3><h3>Scope of the challenge</h3><p>The Daily Health Conference — a non-profit organization dedicated to promoting health and wellness through impactful public talks- is willing to create more values to its audience with a series of <strong>digital apps</strong> that could bring <strong>health improvement</strong> in people’s <strong>routine</strong>.</p><p>With my team of 3 people, we have<strong> 8 days</strong> to present an app that would answer this challenge.</p><h3>Gratitude ?</h3><p>We began this project focusing on <strong>gratitude</strong>, a self-growth related aspect of wellness. This topic apears to be <strong>niche and specific</strong>, we felt that it would offer <strong>good design opportunities</strong>!</p><p>We started to do some <strong>secondary research</strong>, aiming to learn what was the impact of gratitude on health and guess what:</p><ul><li>It is good for mental health</li><li>It increases happiness <em>(source:</em><a href="https://greatergood.berkeley.edu/"><em>greatergood.berkeley.edu</em></a><a href="https://research.com/education/scientific-benefits-of-gratitude#TOC4"><em>research.com/education/scientific-benefits-of-gratitude#TOC4</em></a><em>)</em></li></ul><h3>The market</h3><p><strong>Competitor analysis</strong> has confirm our assumptions that this topic was a good choice to invest our time in. We noticed that self-growth and gratitude apps weren’t innovative nor entertaining, wtih often big similarities and standards.</p><h3>What about our target ?</h3><p>We decided to focus on <strong>people already interest in gratitude</strong> and self-growth not only because they <strong>will match our client’s audience</strong> and topic but also because focusing on people not interested at all apears to be way to complex for such a small timeframe.</p><p>We conducted a <strong>survey on 119 people </strong>as well as <strong>personal interviews </strong>to understand their feelings and behaviors toward gratitude and self-growth. So, we learnt that<strong> 87%</strong> of them were familiar with this topic, knowing the benefits of practicing gratitude.</p><h3>BUT…</h3><p>At this stage <strong>we couldn’t find any real pain points</strong> about practicing or expressing this feeling… We noticed that they were already in a positive and good state of mind when feeling it. People having a struggle to overcome in their life won’t think about it.</p><p>We decided to create a <strong>journey map</strong> with the data we had to have a clear overall vision of their self-growth practice. It appears that we also have really interesting data about self-growth in general, because people tend to merge it with gratitude. We can sum it up like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Kp4CrBgeczwUmdtHAlYlDg.png" /><figcaption>Journey map</figcaption></figure><p>We noticed that self-growers would find self-growth methods on their own when they need it, they will practice until they overcome their struggle. Once they fell better, <strong>32% them will quit</strong> because they claim not having enough time… a good design opportunity knowing that they also would like to keep practicing!</p><p>With all this information in mind, we can synthesize our typical user (persona) for whom we need to design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Gue9CY23Y35ZGkPpFjHlrA.png" /></figure><h3>Problem statement</h3><p>Let’s sum up what we need to resolve in a simple problem statement</p><blockquote>Self-growth enthusiasts, <strong>familiar with self development practices</strong>, need a way to keep <strong>prioritising their practice</strong> when they overcome a problematic situation so, they could <strong>face better the next struggle.</strong></blockquote><h3>Ideation — concept</h3><p>After rows of <strong>crazy 8th</strong> and <strong>bad ideas/good ideas </strong>we have our concept:</p><p>An app that would propose daily self-growth exercise that would fit into daily routine. We will use some <strong>gamification features</strong> to encourage consistency, but the flow should be a simple as possible because self-growth must be <strong>practice outside the app</strong>.</p><p>Self-growing is taking care of your personal mental health, we would like to illustrate this with the metaphor of <strong>cultivating a garden. </strong>This idea will <strong>strengthen the concept</strong> and make the design entertaining.<strong> Users will have to practice regularly to keep his plants growing and prevent them from withering</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWBIS4KqGRBynQ4o9SUDxA.png" /><figcaption>Moodboard</figcaption></figure><p>With this <strong>moodboard</strong> in hand, we have the feel and overall visual idea of the concept. We can know start prototyping and test!</p><h3>Low-fi to High-fi</h3><p>Thanks to<strong> feature prioritization</strong> methods such as the <strong>MOSCOW </strong>and the <strong>Value versus Complexity Quadrant </strong>we have a clear idea of what we should aim for the first Low-Fi prototype: aknwoledge a daily exercise, pratice, and come back the app to fill in the answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzZRCxeI5lLNdfPppb3MyA.png" /><figcaption>Low-Fi prototype</figcaption></figure><p>In the same time, we conducted some <strong>user testing</strong> to know how our target would perceive this concept, collect insights about it, and make sur we’re on the right track.</p><p>Then we created the<strong> mid-fi prototype </strong>on figma, allowing us to conduct <strong>usability test </strong>with interaction, and find opportunities for improvment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D95gj7UGCeMBGDJzfq533g.png" /><figcaption>Mid-fi</figcaption></figure><p>Last but not least… the <strong>High-fi prototype</strong></p><p>This step isn’t just adding some icons and colors to make it beautiful, we must follow the<strong> CRAP Principles of Graphic Design</strong> (<strong>contrast, repetition, alignment, and proximity). </strong>This method will allow us to make the solution accessible, consistent, and understandable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5v6TUsXKUrF7gaaqnj5-5A.png" /></figure><p>Now it’s time to present our solution having in mind our desire to:</p><ul><li>Conduct new usability tests</li><li>Work with self-growth specialists to enrich the concept</li><li>Improve the logic of the game part</li><li>Work with a graphic designer to create beautiful plants visuals</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34549c65e491" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redesigning Leboncoin]]></title>
            <link>https://medium.com/@antoine.pittilloni/redesigning-leboncoin-2158b323b0ad?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2158b323b0ad</guid>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Sun, 19 Feb 2023 10:50:34 GMT</pubDate>
            <atom:updated>2023-02-20T07:58:36.275Z</atom:updated>
            <content:encoded><![CDATA[<p>This project’s challenge is not the least, I have three days to redesign some Leboncoin’s app screens… alone!</p><blockquote>Improving UI skills through UI challenges is a common practice in the design community. — IronHack UI lesson</blockquote><p>Eventually, I’ll have to deliver a <strong>High-fi prototype</strong> with a <strong>style guide </strong>which present the feel and standards of my design, and will allow teams to stay align and <strong>keep consistancy</strong>.</p><h3>Where shall I start?</h3><p>I won’t be able to redesign all the app in three days, all the more the challenge is about deliver few screens and be able to <strong>explain design choices </strong>based on analysis.</p><blockquote>At this point I’m a bit worried about this challenge. The app is well known in France and seems to be also well made… — Thoughts</blockquote><p>To begin, I decided to work on the two screens which propose the <strong>main features</strong> of the service. By <strong>cloning them on Figma</strong>, I will detect and understand the patterns used by designers, as well as develop a <strong>clear vision of the overall architecture and hierarchy</strong>.</p><p>The first screen on the left is the <strong>search page. </strong>It features a searching bar, some categories, and provide insights based on last user research. The second screen on the right is the <strong>item’s page</strong>, features selected item’s description, CTAs, sellers review and delivery information.</p><h3>Before diving into redesign, let’s see what the competitors look like</h3><blockquote>Let’s be pragmatic, in this small time frame, we won’t reinvent the wheel… — Thoughts</blockquote><p>That’s why it is all the more important to do some <strong>design research</strong> on the standards practice of the market. By having a look on this, I might have some<strong> insights</strong> that I could adapt if needed. I will also <strong>understand</strong> what is their <strong>design logic and compare it to Lebecoin</strong>: how they use color, shapes, architecture of the app and hierarchy of information…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3U_ryIh05ap7lXp6zGCBA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c0kM_93i1f2ItxGST_WiQQ.png" /><figcaption>Left: Amazon — Right: Ebay</figcaption></figure><h3>Heuristic analysis</h3><blockquote>This stage was a reliever for me — Thoughts</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LetpCqAnmy9S0wCO_tCZIA.png" /><figcaption>Heuristic analysis categories</figcaption></figure><p><strong>The Heuristic analysis</strong> is a essential tool to bring purpose to each decision of redesign. It also allows to prioritize improvement and design opportunities based on their <strong>severity</strong>. First, I was worried not to find anything but if you do it in depth, you will always find things that can be improved. <strong>Nothing is perfect, isn’t it?</strong></p><h3>Main faults:</h3><p>During this step, I couldn’t find very big and sever issues. Categories 8, 7 ans 4 were the most affected. For instance: overcrowded card, icons not always consistent, categories duplicated and not distinguished enough, the hierarchy isn’t really clear on item screen… To me, the graphic choices are already good, I know now that my redesign will consist on <strong>small adjustment here and there.</strong></p><h3>The clock is ticking, let’s prototype</h3><p>After a quick <strong>Lo-fi prototype</strong> on paper, I must directly jump into the <strong>High-fi</strong> on figma because of the <strong>very short time frame</strong> before the feedback session. I’m starting with the Homepage, from top to bottom, focusing on main design opportunities I could notice during the heuristic evaluation:</p><ul><li>Saving space on top by merging logo, search bar and notification icon</li><li>Reshaping and merging duplicates categories</li><li>Creating a sorting option which will save space in items’ description and keep consistency</li><li>Create an icon to inform about delivery avaibility</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/361/1*scokgwKPxgA-YZotYkeEgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*oOMAEgcfu6h3YWdrE7U7-A.png" /><figcaption>Left: Before, Right: After</figcaption></figure><p>For the Item screen, I’m focusing on the clarity and the <strong>information hierarchy. </strong>I gathered delivery information into one place, emphasized the seller section with a colored background and keep only one buying CTA not have them duplicated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*RwE6EdowuegiFJy00OHr3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*mdGfw3XrJ22XNy75T7pqPg.png" /><figcaption>Left: before, right: after</figcaption></figure><h3>Style guide</h3><p>Now that I have my new design, I will <strong>gather all visual information</strong> about it in one place. This guide should keep Typeface with hierarchy used, icons, buttons, colors… every design elements!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mK96LqSu0C9ZuBUZDb0-IQ.png" /></figure><h3><strong>Feedbacks and improvement</strong></h3><p>Having feedbacks from other designers is necessary to be able to <strong>think out of the box</strong> and <strong>put thing into perspective</strong>. During the process, we are sometimes like in a tunnel and won’t have ditance with the work we’re providing. Also, this step is a good way to notice if our choices are understandable, as well as what we can <strong>keep on improving</strong>.</p><p>After this session, I <strong>validated some choices</strong> as the hierarchy, the clarity of overall layout, and the sorting feature. What I could improve is the cards’ size, the place of icons on item screen and replace the “Option” label with “information” not to misslead users about the section. I would also work on icons, for instence I could keep the share button with the bottom CTAs, which will be fixed on scroll.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2158b323b0ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Wholesome Wondrous]]></title>
            <link>https://medium.com/@antoine.pittilloni/the-wholesome-wondrous-5b03904c7428?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b03904c7428</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[redesign]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[children]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Sun, 12 Feb 2023 14:50:44 GMT</pubDate>
            <atom:updated>2023-02-12T14:50:44.348Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4t9Q7Ifr4ylURNfp35gzQ.png" /></figure><p><strong>Baby needs a new toy? Let’s see what UX-UI design can do.</strong></p><p>For this project, I’ll work with two other UX designers, putting our design <strong>process and methods</strong> at the service of “The Wholesome Wondrous”: a brand new website specialised in <strong>baby’s toys and books, </strong>for kids between 0 and 6 years old.</p><p>Although we already spotted some improvements that we could implement on the current website (overall design and structure that feels a bit messy), we will stick to the <strong>design thinking process</strong> in order to come up with a Hi-fi prototype data-based, aiming to find the <strong>good balance</strong> <strong>between the</strong> <strong>stakeholder vision and the users’ needs.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*DoB5TAojLPDg7tiVN0PlTw.png" /></figure><h3>What is your goal with this business ?</h3><blockquote><strong>“I’d like to bring knowledge and simple toys to develop children’s needs.” </strong>Mehrnosh — The Stakeholder</blockquote><p>To start this project we’ll have to <strong>interview the stakeholder</strong> to understand what is her purpose with this business and how it is currently going. Those information are crucial to lead and <strong>our secondary research</strong> and target our <strong>users’ interviews</strong>.</p><p>We can know <strong>compare her business vision</strong> to what the <strong>current website </strong>looks like, as well as the <strong>user’s needs</strong>, and guess what ? It seems that everything isn’t quiet align:</p><p>Mehrnosh (the stakeholder), wishes to transmit knowloedge about parentality, as well as propose quality toys that can develop children’s needs.</p><h4><em>From the user side…</em></h4><p>So far, so good, we have a <strong>pattern</strong> from the<strong> young parents we interviewed, </strong>they are also looking to develop their children through play ! <strong>But</strong> the issue is that they also need a safe place to shop, with good and direct advices. This isn’t what we feel on the website, so we have our first lead of design !</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKMUBoDsm6de9FHgOlbrow.png" /><figcaption>Current website</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k6nyUuG5RKwTpEyvKzfhKg.png" /><figcaption>Current website</figcaption></figure><h3>Let’s see what the market says</h3><blockquote><strong>3.5 billion euros in France in 2020 (</strong><a href="https://www.fjp.fr/">https://www.fjp.fr</a>)</blockquote><p>The baby’s toy business is a very competitive market with often <strong>well organised websites</strong> selling a lot of toys… but thanks to our <strong>research</strong> we also learnt that the<strong> fewer the toys, the better is the development of children (</strong>https://www.itsmyfavoriteday.com/too-many-toys/).</p><p>So the selectivity of products and the willing to transmit knowledge are some of our main strengths compared to competitors. <strong>We need to clearly implement those in a better organised website</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPk5ZlkkmoD_XfUUfjFLMw.png" /></figure><h3>Heuristics and prioritization</h3><p>With all this information in mind, let’s conduct a proper <strong>heuristic analysis </strong>of the current website to have a precise understanding of what we should prioritize.</p><p>This step confirms that the main issues are<strong> too many categories</strong> and no real <strong>architecture:</strong> <strong>ontology, taxonomy, and choreography</strong> are neither well design nor consistent (42 categories, duplicate pages…). We also find that the content isn’t very clear and well explained to the client.</p><p>We decided to <strong>ideate</strong> on how we could improve those points and conclued to focus on :</p><h4><strong>Visibility</strong></h4><p>enhance global structure and improve hierarchy</p><h4>Trustability</h4><p>add reviews’ space, more descriptions, a chat box</p><h4>Strenghten the concept</h4><p>create a categorisation based on children skills to improve, a blogging space, and give items attributes.</p><h3>Prototyping</h3><p>We need to conduct usability test as soon as possible in order to be able to itterate and improve our solution. After creating a <strong>Lo-fi prototype</strong>, we quickly jumped <strong>into figma</strong> to add interactivity and learn from our yound parents ! We had a lots of good insights: <strong>bigger images, add an age range sorting to faster the search, and more materials descriptions.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a7aMa4dvi4J9_BWHuR3LXg.jpeg" /></figure><p>Before implementing into a final High-fi, let’s create<strong> a moodboard</strong> in order to have a clear vision on the<strong> overall visual</strong> <strong>apsect</strong> we want to <strong>share to the stakeholder</strong>. Our moodboard needs to transmit the<strong> feeling of the brand</strong>, with its core values (sustainable, progress), colors (safe, and peaceful), and typeface we want to use (avenir because it’s easy to read as well as elegant with rounded shape).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BbKuIZt5tP-wj1RCYgfu_g.png" /><figcaption>Moodboard</figcaption></figure><p>With this document we could create a High-Fi that really stick to all our research, and we are proud to present</p><h3>The Wholesome Wondrous new website idea !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U4Yk0SoBYy69R61bBNhg3w.png" /><figcaption>Homepage</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UA9gQC1Ay-2je-O3Gs4U4g.png" /><figcaption>Item</figcaption></figure><p>Now time is over for this project, but we have good clues about where we would like to go further is we could. For instence, conduct new interviews to have an even clearer pain point pattern, as well as usability tests with the improvment we made during the Mid-fi prototype step.</p><h3>Process wrap-up:</h3><ul><li>Conduct secondary research</li><li>Primary research (interview business side, user side to create persona and define a problem statement)</li><li>Competitor analysis (SWOT)</li><li>Conduct heuristic analysis</li><li>Ideate and create new sitmap to improve architecture and hierarchy</li><li>Create Lo-fi, Mid-fi and conduct usability test</li><li>Create a moodboard and implement on High-fi prototype</li><li>Think about how we could improve our solution</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b03904c7428" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Take me to the museum !]]></title>
            <link>https://medium.com/design-bootcamp/take-me-to-the-museum-f950e36b72f0?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f950e36b72f0</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[museums]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Sat, 28 Jan 2023 20:30:05 GMT</pubDate>
            <atom:updated>2023-01-30T08:31:45.510Z</atom:updated>
            <content:encoded><![CDATA[<h3>Take me to the museum !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1NmvObI9vwqsqlsunJ6eBw.jpeg" /></figure><h3>Since the 70s, people go less to museums… why ?</h3><p>I live in Paris, the “city ​​museum”. I can see ads for new exhibitions everywhere : in the subway, in the street, on social networks. Everything is encouraging us, yet there is something missing... let’s use <strong>design thinking </strong>to resolve this enigma !</p><blockquote><strong>In France in 2018, 35% of people between 25 and 39 visited a museum. (</strong>Published by <a href="https://www.statista.com/aboutus/our-research-commitment">Statista Research Department</a>)</blockquote><p>This was the smallest group of people whom visited a museum and we want to know why ! If we<strong> discuss with them</strong> and really understand their experiences and relation with cultural journeys, we will surely come up with an idea that could<strong> help museums regain and enlarge their audience !</strong></p><h3>Museum goer, who are you exactly ?</h3><p>As we need an in-depth understanding of behaviours, motivations, experiences and feelings, we need to narrow down our target and use<strong> qualitative methods</strong> such as <strong>interviews</strong> to get some insights about the problem !</p><p>Luckily we live in Paris and are directly in touch with young Parisians museum goer. Eventually, we interviewed <strong>5 people</strong>, and guess what ? We found some really interesting <strong>patterns </strong>that would help us to create our <strong>persona</strong> : <strong>Sophie Dubois, a young busy Parisian.</strong></p><h3><strong>“I would like to go more but I’m busy and it’s hard to make time while museums are opened!”</strong></h3><p>Dear Sophie, thanks to <strong>our research, </strong>we can see some<strong> pain points </strong>revealing that you feel frustrated because <strong>you would like to go more often</strong> to museums but you <strong>struggle with time management and scheduling</strong>… but don’t worry. Thanks to you, we have a clearer view of the issue and we can get going !</p><h3>Stick to the data !</h3><p>To be honest at this point, <strong>things didn’t get as planned</strong>. Before comming to an agreement about what was the <strong>main pain point to overcome (</strong>time management<strong>)</strong>, we might have made some missleading assumptions… At the beginning, we though the problem was a lack of <strong>targeting information</strong> coming to Sophie… but something felt wrong and we couldn’t clearly define a problem statement. Hopefully, <strong>we went one step back</strong> and <strong>read over the interview</strong> to see that this fact wasn’t <strong>clearly mentioned</strong>.</p><p>Back on track with right data, the problem statement came naturally:</p><blockquote><strong>Active Parisian</strong>, who is a keen museum-goer, needs more opportunities to be able to <strong>fit her cultural experiences into her busy lifestyle</strong>, because her schedule doesn’t always match the opening hours.</blockquote><h3>Here comes my favorite part !</h3><p>With this clear problem statement, we could <strong>ideate</strong>, and quickly find a solution to <strong>prototype, test and improve </strong>! Even if I’m not such a good drawer , using drawing brainstorming methods is a perfect way to stimulate the team and don’t lose time with long discussion. We want to prototype and <strong>test as soon as possible</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2Yaupuu8WVXRaLFwxE_GQ.png" /></figure><p>One solution is to create an app that would propose exhibitions directly to your calendar (google meet, Ical…). With this feature, no need to research information and deal with scheduling issues. Everything is found in the space you already use in your daily life ! Select the day of your choice in your calendar and exhibitions we’ll be proposed.</p><h3><strong>Team-working !</strong></h3><p>To face this <strong>one week challenge</strong>, teamwork was very powerful to avoid mistakes and not to miss anything. As we are beginners, one week is short ! Our 4 brains plugged, we decided to overcome each step together as we discovered them.</p><p>I enjoyed our long discussions trying to make the <strong>best decisions</strong> for the project. Practicing this stimulates me because I like to <strong>listen to others’ ideas, </strong>doing my best to<strong> </strong>understand and use them to <strong>enrich the project</strong>.</p><p>This project is my first project with english speakers only, a good practice and good way to learn technical vocabulary. <strong>After all, design thinking is about learning and testing, isn’t it !</strong></p><blockquote><strong>“I would like to use this app ”</strong> — Marcia — test user</blockquote><p>To sum up, design thinking method has proved its efficiency: we came to a simple solution which pleased the user and was concidered as useful when it comes to resolving the issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yqj7tRxVFPPx16xv_b-K2A.png" /></figure><h3><strong>“Trust the process” will surely be my next tattoo project !</strong></h3><ol><li>After conducting some secondary research, we empathize with interviews (primary qualitative research)</li><li>Using interviews’ results we create an affinity diagram as well a a persona</li><li>User journey map is a great tool to spot main pain point and <strong>define</strong> a clear problem statement.</li><li>We ideate, using brainstorming technics such as the “bad ideas” methods and the “crazy 8th” one.</li><li>We think about a user flow and create a lo-fi <strong>prototype</strong></li><li><strong>Testing </strong>the prototype is the best way to validate the solution and<strong> iterate </strong>thanks to concret insights coming directly from the user.</li></ol><p>Now I know the process, next project I want to improve my team management skill and organise the totality of it, planning each steps at the beginning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f950e36b72f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/take-me-to-the-museum-f950e36b72f0">Take me to the museum !</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[Lydia’s money transfer flow]]></title>
            <link>https://medium.com/@antoine.pittilloni/lydias-money-transfer-flow-d6407db4f92b?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6407db4f92b</guid>
            <category><![CDATA[wireframe]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ironhack]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Thu, 22 Dec 2022 13:25:07 GMT</pubDate>
            <atom:updated>2022-12-22T13:25:07.740Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Logo Lydia" src="https://cdn-images-1.medium.com/max/1024/1*F8UpMvyuSYdB_TMg97WZOA.png" /></figure><p>You might know this great smartphone app which gives us a very convenient solution for private money transfer.</p><p>In 2017, this french app claims to have more than <strong>1.4 million registered users</strong> over 5 european country. Being a regular user, I wanted to analyse and breakthrough the secret of its payement flow, and understand<strong> why it’s more pleasant than doing it with my bank account app</strong>.</p><h3>Money transfer’s flow</h3><p>The goal is to transfer money to a friend or a relative quickly. As it is the main feature, money transfer ought to be immediately <strong>accessible</strong> and very <strong>easy to use</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LOHmYesswIYslC7aaOUC7A.png" /><figcaption>Screenshots</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9PbKPBjtibZMfJVz-UNN3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QpGJJFwD_cz4kpJgJMZ-0w.jpeg" /><figcaption>Lo-fi wireframes</figcaption></figure><p>I started by taking screenshots of this feature to identify the main steps, create a <strong>Lo-fi wireframe</strong> and <strong>breakthrough</strong> this high-level task. Those steps also allowed me to list and gather all UI elements I will need to prototype in FIGMA.</p><ol><li>Tap the money transfer button to <strong>reach transaction space and choose a contact</strong></li><li><strong>Enter amount</strong> to transfer</li><li><strong>Choose withdraw source</strong></li><li>Add a motive if needed and<strong> check information</strong></li><li>Confirm transaction with personnal code</li></ol><p>With this in hand I can go deeper and create a full diagram of the flow using miro’s diagram template (f<a href="https://miro.com/app/board/uXjVP4FqFG4=/?share_link_id=306201447126">ull size available here</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SbuCPm2mW4ZJj1EGMuWGQA.jpeg" /><figcaption>Diagram</figcaption></figure><p>The digram gave me a <strong>clear vision of the overall process</strong> with related path and add some option frames given to user. Working with this information made me understand that the feature <strong>appears very simple and fluid</strong> for users, but are the result of a more <strong>complex design hidden</strong> underneath.</p><h3>Wireframing using FIGMA</h3><p>Here is my wireframe! I struggled a bit <strong>finding the good amount</strong> of information, more specifically choosing icons or just writing the name of the function. I also wander <strong>which level of animation</strong> you should put in this level of design. For instance, I realised that animation is used to <strong>make user understand </strong>that he had to fill the amount first or that his transaction is loading… is animation part wireframing? I hope to find out soon!</p><p><a href="https://youtube.com/shorts/slMI6wYbELo?feature=share">Wireframing Lydia</a></p><h3>Conclusion</h3><p>This challenge is a very nice way to learn disign. Deconstructing a well known app is a great <strong>source of inspiration and learnings</strong>. I have the feeling that <strong>efficient designs</strong> are the ones that <strong>reduce the number of manipulations</strong> to reach a precise task. In this exemple I noticed that the high-level task could be done in <strong>only 5 simple steps</strong> with the possibility to edit options during the entire process.</p><p>I still wonder if my wireframe is to much graphically produced, and if the level of information is good enough for a wireframe.</p><p>What do you think ?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6407db4f92b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ideate Citymapper’s new feature]]></title>
            <link>https://medium.com/@antoine.pittilloni/ideate-citymappers-new-feature-3ab213c742?source=rss-3e2eed324a4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ab213c742</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[ideate]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Antoine Pittilloni]]></dc:creator>
            <pubDate>Wed, 07 Dec 2022 23:08:25 GMT</pubDate>
            <atom:updated>2023-01-12T10:39:43.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*pZDepj-_-D4-9IT9c_RPwA.png" /></figure><h3><strong>Citymapper</strong></h3><p>Created in 2011 in London, Citymapper is a public transport service app which compare and provide transport option from a point to an other.</p><p>Like Moov’it or Google Map, Citymapper uses Global Positioning System and real time data to calculate and propose the fastest way to reach a place using public transport, bike, walking or driving. What sets it apart is the precision of the information, its design and its very specialized functions, such as the indication of the most suitable exit or disturbed routes.</p><p>The chalenge is to use a <strong>design thinking method</strong> to ideate about a new feature that could relieve the <strong>painful </strong>process of buying tickets by different channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4YslrOY-lg5pWz3Mv4ZtQ.png" /></figure><h3>Emphasize : Interviewing public transports users</h3><p>I asked 5 people of my surrounding about how they use public transport for <strong>daily trips</strong>, how do they acquire tickets, what are there feelings about those payement pocess, also if they use transports app and how do they use it. Then I asked them what was the difference when they had to use them <strong>abroad </strong>or in an unknown city.</p><p>For<strong> daily trips</strong>, all of these people have a monthly or annual pre-payed pass. The <strong>payement is automatic</strong>, and the pass allow them to travel freely. They often use mobil app, like Google maps or Citymapper to <strong>anticipate and schedule</strong> there trips, they find it <strong>reassuring and useful. </strong>If they had no pass<strong>, </strong>they would find it convenient to be able to purchase <strong>directly on a transport app</strong>, because buying tickets is a <strong>stressful and time taking</strong> process, they also want to <strong>avoid the payement procedure.</strong></p><p>When it comes to <strong>abroad or in unknown city</strong> usage, people find this process <strong>less stressful.</strong> As they often got more time, they want to discover and have contact with inhabitant. However, they would find it convenient to be able to know the <strong>exact prices of routes</strong> and be <strong>able to chose</strong> between physical and digital payement. They’re affraid of <strong>keeping everything in there phone</strong> and be out of battery.</p><p>To summerise, I would note these main problems when purchasing tickets :</p><ul><li>They paye to access but they don’t know the price of routes</li><li>They have no choice but to go to a local dealer or station terminal</li><li>Payement procedure is time-taking</li><li>They don’t want to keep everyting on there phone</li></ul><h3>Define : What is the issue ?</h3><blockquote>We should have the <strong>choice</strong> to purchase a <strong>complete journey</strong> as well as stock <strong>standard tickets </strong>— Camille</blockquote><p>According to what I’ve heard during the interviews, as long as they have a pre-payed pass, everything seems to be great. But as soon as they have to purchase tickets, they would like to be able to <strong>do it rapidly online</strong>.</p><p>The issue is to avoid<strong> contraining payement process have alternative solution</strong>. The underlaying issue, is that public transport often has turnstyles or gates to walk by. The solution should allow them to pass those gates everywhere, even abroad.</p><h3>Ideate : How to solve this problem ?</h3><p>My idea is to implement a quick buy button that would allow users to purchase tickets <strong>directly on journey’s details. T</strong>he idea is to enter bank informations just once and purchase with face ID or personnal code afterward. The app will also provide a <strong>ticket area</strong>, where users would be able to buy and stock traditional tickets of the city they are in (using GPS or texte search).</p><p>The ticket will let the user pass the gates using <strong>NFC technology</strong> like a traditionnal pass. I imagine that, the<strong> digital ticket</strong> should also allow to be <strong>printed or collected </strong>at a terminal, using mail address and personal code.</p><p>Conversly, terminals should also <strong>let user collect tickets</strong> which have been brought on Citymapper app. I presume that NFC technology could do that because it’s cuurrently used with “Navigo Pass” in Paris.</p><h3>Prototype</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OVIO899GZfOpjTMJq2Infw.jpeg" /><figcaption>User Flow</figcaption></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCWRBLKkhmHA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCWRBLKkhmHA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCWRBLKkhmHA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4d6877c528a710275d7c2064077bf940/href">https://medium.com/media/4d6877c528a710275d7c2064077bf940/href</a></iframe><h3>Learnings</h3><p>During this design thinking session, what stricked me is that you have to <strong>put your preconvinced ideas aside </strong>in order to emphasize the right way and stay focused on interviewed people feelings and opinions. Even if the client’s brief is admiting facts (here the fact that buying tickets is a painful process).</p><p>Before the interview I thought that everyone would have pretty much the same opinion about having to physically buy tickets. When I interviewed people, I notice that it was <strong>way more nuanced</strong>. Some people told me that when they were abroad, they usually had more time and they wanted to discover and <strong>interact</strong> with the environment and inhabitants. Other just have some fears about <strong>stocking</strong> everything on there phones…</p><p>This made me think about a way to propose to stock ticket on the app, but also to be able to <strong>print or collect</strong> them from a terminal if users wanted.</p><p>To conclue, I would say that this challenge has truly made me understand that interviewing people is a essential process, because no matter what you think, <strong>ideas and needs emerge from those interviews</strong> and allow you to think about features that you wouldn’t have imagine at the first place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ab213c742" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>