<?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 Matt C on Medium]]></title>
        <description><![CDATA[Stories by Matt C on Medium]]></description>
        <link>https://medium.com/@matthieuchaminade33?source=rss-85860eebb126------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*I89GchQr4MZ3yW2ep8xjUg.jpeg</url>
            <title>Stories by Matt C on Medium</title>
            <link>https://medium.com/@matthieuchaminade33?source=rss-85860eebb126------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:51:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@matthieuchaminade33/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[Designing with empathy begins with yourself]]></title>
            <link>https://uxdesign.cc/designing-with-empathy-begins-with-yourself-4c3136497630?source=rss-85860eebb126------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c3136497630</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <dc:creator><![CDATA[Matt C]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 16:01:01 GMT</pubDate>
            <atom:updated>2019-12-20T16:16:17.695Z</atom:updated>
            <content:encoded><![CDATA[<h3>Identifying pain points through empathy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3QJwsyVFhYzzaOHDQGDTA.jpeg" /></figure><p>Designing with empathy is not a new concept at all, in a way design has been focusing on empathy since the very beginning by solving problems specifically for human pain points. Most of the various manifestations of design are rooted in making the world more usable for humans. Typography was continuously refined to suit long-form reading in books and then transformed again to better cater to the needs of digital devices. Interior design can create more functional spaces to fit someone’s lifestyle or needs, industrial design leads to new tools making our interactions with the physical space more effective. These are all tangible manifestations with clear paths for solving problems, but to get there they all need to start by understanding how the human feels when experiencing the problem. This is where empathy comes in to play, but what does it look like to design with a feeling and even further someone else’s feeling? When I was first exposed to the idea of designing with empathy it seemed clear what it was but when it came down to execution understanding how to apply it was missing. I was still left with what felt like a lack of tangible advice or a way to really practice designing with this fundamental feeling that can lead to meaningful solutions and my desire to apply it was meet with confusion. This all changed when I designed something for myself to attempt and solve a real problem I was experiencing.</p><h3>The Why</h3><p>This journey all began with my dog, Skywalker. At the time he was 5 years old healthy with no problems in sight. One day he abruptly woke up from his sleep, yelped, feel over, and began violently convulsing out of control, eyes rolling back into his head and foam coming from his mouth. Adult-onset epilepsy was the verdict, supposedly caused by his flea medication or as the vet put it “We don’t know was causes the seizures, but it could be the flea medication”. The cherry on top was that this was going to be a life long condition with lots of pills which will eventually cause more health issues down the line. I had a problem, a pain point, something that would make my life more difficult and a reason for a product/solution to exist. I decided to design something that would solve the problem, <strong>something that I wish existed</strong>.</p><h3>Becoming the user</h3><p>Understanding that someone is struggling with something is the first step, focusing on what they feel, their frustrations and what they wish they had will provide valuable insights. From the significant like someone with diabetes who wished they didn’t have to draw blood every day to track their blood sugar to the mundane like keeping your phone from dying while you travel because you use it as your boarding pass, have feelings attached to them and a desire for a better solution. For me in this case, it was the constant unknowing of when Skywalker would have another seizure, he often has them while falling asleep so anytime he begins to relax I being to worry. I had identified the main pain point for me, the main thing that was causing me frustration, the thing I wanted to be solved the most and what would lead to the MVP. The problem that if the product could solve for and that alone would hold value for me. In this case, I knew that I wanted a product that could help identify when a seizure would occur so I could be alerted and prepared when it came but at ease when I knew it would not. This came naturally since I was the person for whom the product was designed for and close to the source of the frustration, I had all the insights on hand, I understood how I felt.</p><p>The solution for my personal project came easier for me because I was very close to the pain points which provided direction and priority in terms of which things need to be solved. In a professional environment where you are tasked with creating solutions for other people who’s problems you may have never even considered, the insights must be discovered. Without being familiar with how a problem feels, the way it affects the day to day, other pain points caused by it, the most frustrating issues, and the goals of the people experiencing them we are in a way guessing what those things could be. Unfortunately more often than not our guesses will be based on biases and not accurately represent the real picture. To gain genuine insights we need to go to the source, the human dealing with the issues, someone deeply involved with them, an expert on how it feels and learn from them. This is where we must practice the most empathy, this is where you listen and understand their frustrations and understand what matters most to them. They are the “experts” of those issues, they know them the best and which ones are the most valuable to solve for and this will lead to the inception of an MVP.</p><h3>Better understanding = Improved value</h3><p>Once I clearly understood what was causing me the most frustration and a clear vision of what I wanted to solve for I began to research on the topic. I wanted to become an expert myself and turn over every rock I could about the condition, the causes, and the existing solutions all with the goal of solving my pain point in focus. During my research and the amazing help from my girlfriend who possesses significantly better research skills than myself, I came across various causes, theories and stories from people experiencing the same issues. I discovered pain points other people were experiencing that were very similar to mine and recognized other areas that if I could solve for would increase the value of the product. For example, tracking how often seizures occur, the time of day, and the duration of the seizure is very important because if they surpass certain durations they require medical attention. This led to the inception of a log where you could review timelines and graphs with all of this information. After a seizure, a dog’s behavior will be abnormal since they will be completely disoriented. This insight guided the inception of a community forum, a latest studies section, and Q&amp;A with vets to make sure the post-seizure symptoms aren’t out of the ordinary because they will definitely seem that way for the owner.</p><p>These were pain points caused by a source problem, and being immersed in the situation they were easy to identify and easier to recognize in other people’s stories. This is another area where it is crucial to listen to the people for whom you are designing because it may be more clear to identify the bigger more visible problem, but there are smaller less visible issues that if solved over time will add continued value for the users. This will not only make the product more meaningful by solving not just one but multiple pain points around a bigger issue, but it will help maintain adoption rates and continued usage of the product, a win-win you could say.</p><h3>To conclude</h3><p>To design for how someone feels begins by designing for yourself to learn what it feels like to interpret feelings into features. Once you understand that process it will be easier to design for users like you would for yourself. You will know what features are meaningful because you are experiencing the pain points yourself and in a real-world setting this is where you listen to the users. You will be an expert in what it’s like to live with the pain points, this is where you must learn from users. You will have a clear vision of when the problem is solved and the pain point is no more, this is where you will solve for users. From big to small like the legibility of a typeface to the monitoring of health conditions, understanding how people feel and injecting your empathy can create meaningful solutions. The first step though is to feel what it’s like to transfer empathy into a product for yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c3136497630" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/designing-with-empathy-begins-with-yourself-4c3136497630">Designing with empathy begins with yourself</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Core principles for product designers]]></title>
            <link>https://uxdesign.cc/core-principles-for-product-designers-3cedd3631788?source=rss-85860eebb126------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cedd3631788</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Matt C]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 16:01:01 GMT</pubDate>
            <atom:updated>2019-08-09T20:13:59.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*793xYblC5QPRX5OVcTEXIQ.jpeg" /></figure><h3>The pain point</h3><p>As a designer working in an incubator lab alongside researchers, engineers, product managers, and stakeholders to build new digital products, it’s clear that there is an opportunity for design to take a bigger role in the overall product development. To further infiltrate design into the base of any project I think we need to re-structure the role of designers and the way teams are built. In the digital product design space, there are a variety of design roles that create unnecessary points when ideas and context must be shared amongst the design team between members with different skill sets. Designers are increasingly being forced to pick a road towards being in a role when they are required to primarily strategize and troubleshoot or in a role where the visual aesthetic takes the forefront and are not involved with the preliminary strategies, user needs or stakeholder goals. This is a problem and I believe it stems in part on how the role and skillset of a designer is misinterpreted by other professionals that collaborate with design but primarily amongst designers themselves.</p><h3>What can we do?</h3><p>The Bauhaus created a revolution in how design should be taught and executed by encouraging that each designer possess the skills of various creative disciplines. Unfortunately, the industry has been taking a step backward by dividing the different areas of the design practice into specific roles. This has lead to multiple design teams within one design team and designers that identify with a single discipline. I have heard UX designers claim they aren’t creatives, and visual designers say they aren’t interested in the strategy and research. There are obvious issues to that thinking but one of the main problems is that it completely ignores the symbiotic relationship that occurs during the entire design process. Providing value and a good experience to humans doesn’t stop at the feature level, it doesn’t stop at the wireframes it doesn’t stop at the illustrations. The best way to ensure the initial spark of a product turns into a flame and reaches the final touchpoint with a user, the same designers need to be involved from beginning to end to ensure the vision, context, and thinking are holistically applied to the whole design process as each step informs and supports the next.</p><h3>So how does this actually translate into day to day skills and work for the design team?</h3><p>The idea is that there would be a stronger emphasis on core skills with fundamentals in design thinking, strategy, UX, visual design, and an understanding of design theory as well as the fundamentals of their chosen design discipline(view chart). For example, the idea is that a design team tasked with building products would only have product designers who would all possess skills in user experience design and visual design. They would have the skills to design UI one minute and become an investigator the next as soon as changes in the product arise as they often do. The goal is that during each step of the process, every member will have the available skills to be present when features change, design reviews amongst researchers and engineers, and be able to fight for good UX and UI. Every designer on the team should possess some basic research skills, for example when designing the UI of any product having the ability to research accessible colors palettes, user behaviors regarding UI, available mental models, various typefaces and their impact on legibility, will significantly improve the UX of a product but in some cases aren’t covered during the UX process. This model will still include junior to senior roles but the idea is that even at the junior level designers will have the opportunities and fundamentals to be involved from the very beginning till the end. This idea doesn’t just apply to digital product design either, this can be applied to a variety of design teams, from apparel to branding, to industrial design all with their corresponding fundamental skills that go beyond mastering either just the visual or the practical. Designers should be able to problem solve at every step of the project. The goal is that designers are viewed as experts in designing experiences for people, not just creating visuals or translating features into a flow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MT6NLBL8gTCGwUs7A6YhHQ.jpeg" /><figcaption>Digital product designer core skills and deliverables (Chart)</figcaption></figure><h3>How we will get there?</h3><p>Design already has the necessary disciplines to contribute at each stage, the key is that each designer should practice those disciplines. Practices like strategy, user experience, research, collaboration, psychology, communication, as well as other soft skills, and very importantly the processes of design thinking should be part of every designer’s tool kit. The goal is that if each member has the same core principles the collaboration will continue from beginning to end with a consistent vision and each member able to contribute both to elevating the level of design but also to defend and explain it throughout the entire process. A great place to start developing these skills should be at the design education level. Ideally, student’s education would have an emphasis on craft, problem solving, and empathy as well as how to apply those skills in a variety of design practices. The goal is that design and its full capabilities are introduced at the very beginning of a designer’s relationship with the practice. That they understand how design is beyond focusing on visuals, focusing on aesthetic, focusing on strategy and that the holistic application of all those elements is what makes design great. The goal would be to show the beauty that exists in a well thought out site map and the pure function in a great UI. Of course a formal education is not the only way as many people learn in variety of other formats. For professionals taking online courses, collaborating with coworkers or simply practicing during the after hours is a great place to start and besides its important to always keep growing even as pros.</p><h3>To conclude</h3><p>Every product designer must have design thinking as their core skill with the ability to focus on user needs, pain points, empathy, visual design, typography, and the list goes on. Possessing and applying these skills will add further significance and value to a design team’s role in the world of innovation, lead to value creation for humans, and push the roles and responsibilities of designers everywhere.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cedd3631788" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/core-principles-for-product-designers-3cedd3631788">Core principles for product designers</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>