<?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 Michelle Claessens on Medium]]></title>
        <description><![CDATA[Stories by Michelle Claessens on Medium]]></description>
        <link>https://medium.com/@michelleclaessens?source=rss-3e140b6a6c72------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xVcAqKG2fS_W1iEcwKdltQ.jpeg</url>
            <title>Stories by Michelle Claessens on Medium</title>
            <link>https://medium.com/@michelleclaessens?source=rss-3e140b6a6c72------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:18:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michelleclaessens/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[The 7 habits of highly effective designers]]></title>
            <link>https://uxdesign.cc/the-7-habits-of-highly-effective-designers-3c806ebf8b8?source=rss-3e140b6a6c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c806ebf8b8</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Michelle Claessens]]></dc:creator>
            <pubDate>Mon, 25 Mar 2019 13:56:40 GMT</pubDate>
            <atom:updated>2019-03-26T00:03:21.691Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently finished reading Stephen R. Covey’s infamous book, The 7 Habits of Highly Effective People. Originally published in 1989 — and as applicable today as it was then — the book has helped many people achieve true interdependent effectiveness in their lives and jobs. As I was reading the book, I couldn’t help applying the 7 habits to my day-to-day life as a product designer. And so, below you will find the 7 Habits of Highly Effective Designers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5rL3gsJXqfUqyovnpV73rA.png" /></figure><h3><strong>Habit 1: Be Proactive</strong></h3><p>Being proactive means creating or controlling a situation through your own decisions rather than reacting after a situation has happened.</p><p>Someone who thinks reactively believes that there’s nothing they can do, things are the way they are, the “higher-ups” won’t allow that. As a designer, this means that you won’t take any risks. You’ll say “if only” — if only I had more time, more resources. You won’t push to make the product better because you believe that you can’t have an impact on it.</p><p>Imagine if instead you thought proactively: you know that when one approach fails, there’s always a different one to try. You value failure because you can learn from it. You think “I will” — I will find a great solution that I can do with the time and resources I have. If you’re having trouble convincing stakeholders of the benefit of addressing a certain usability problem, you can create a better presentation to explain. You constantly push to make the product better because you know that somehow you will make a difference.</p><p>Being proactive does not mean being aggressive or pushy, it means knowing that you can make things happen. By believing that you can have an impact, you will. This habit is critical because the more proactive you are, the more likely you are to practice the other 6 habits.</p><h4>Homework</h4><p>Keep track of how often you use reactive language like “if only,” “I can’t,” or “I have to.” Catch yourself and think about how you can change your perspective on the situation.</p><h3><strong>Habit 2: Begin with the End in Mind</strong></h3><p>Habit 2 tells you to start with a clear understanding of your end goal: what are you trying to accomplish by redesigning this part of the app or by adding this feature? How will this help your users? What specific metrics are you trying to impact?</p><p>At <a href="https://influitive.com/">Influitive</a>, we define user stories before starting any design work. You can use job stories, tasks or any format that you find best — so long as the users and their goals are defined. These help ensure that the entire team knows what we’re aiming for. They’re how we ensure that the project stays on track. We also include the specific metrics that we’re trying to impact — which we will measure once the feature goes live — so that we can set a benchmark and keep these top of mind.</p><p>Beginning with the end in mind is helpful for project goals, but it also applies to our career progression as designers. Do you want to be a creative director some day? Do you want to be a master at your craft? If you focus on where you want to be, you can gain the right experience, take the right courses, read the right books, and ultimately get there.</p><p>It’s easy to get caught up in day-to-day tasks or to get pulled off course by feedback. In Steven Covey’s words: “to work harder and harder at climbing the ladder — only to discover it’s leaning against the wrong wall.” As the team works through a project, and as we progress in our careers, the end goal helps us check that we’re still on the right ladder.</p><h4>Homework</h4><p>Next time you’re starting a new project, start with the end goal: define the user, their key goals, and how you will measure success. Keep these somewhere so that they will be top of mind as you work through the project. At the end, evaluate if you met the end goal.</p><h3><strong>Habit 3: Put First Things First</strong></h3><p>Once you have your end goal clearly defined, how do you go about getting there? Habit 3 is about managing your life to focus on what truly matters. When planning your time, you can take your overall end goal, break it into smaller goals, create plans to achieve these smaller goals, and then schedule time or delegate. Covey recommends doing this planning weekly, so that you can set aside time for the important stuff — the things that help you achieve project success or progress in your career.</p><p>Covey talks of four quadrants:</p><ul><li><strong>Urgent and important:</strong> things that have to be addressed in the moment, like crises and deadline-driven projects.</li><li><strong>Urgent but not important:</strong> daily distractions, like interruptions and emails.</li><li><strong>Not urgent and not important:</strong> time wasters or mindless activities that allow you to turn your brain off.</li><li><strong>Important but not urgent:</strong> things that help you in the long run, like planning, relationship building and learning and development.</li></ul><p>Ultimately, you need to learn to say no to unimportant things so that you can make time for the things that may not be urgent, but are important in the long run. Set aside time to focus on a specific design project, without distractions, so that you can do your best work. Leave time for learning and development. Make an effort to network and build relationships. The more time you spend in the “important but not urgent” quadrant planning and doing things that lead to long-term gains, the less you’ll have to spend in the others.</p><h4>Homework</h4><p>Identify an important but not urgent activity that you have been neglecting. Write it down and commit to doing it.</p><p><em>The first 3 habits help you become a focused, independent designer — capable of achieving results through your own efforts, and capable of setting and working towards long-term goals. You need to be independent before you can become interdependent — before you can build relationships and make things happen as a team. This is where the next 3 habits come in.</em></p><h3><strong>Habit 4: Think Win-Win</strong></h3><p>Habit 4 is about thinking in a way that seeks mutual benefit for everyone involved, or about thinking “win-win.” This can be applied to many of the relationships that you need to consider when designing—to name a few: you and your users, your clients and their users, and you and your teammates.</p><p>When designing solutions, it’s always a combination of the user’s needs and your company’s needs (technical feasibility and viability with available resources). To be successful, your solutions need to meet both of these. However, there’s a reason why you start by defining the users and their key goals: if a solution doesn’t fit the user’s needs, it really doesn’t matter if it’s feasible and viable.</p><p>Another relationship to consider is that between your clients and their end users. As a third party in this relationship, it’s especially important to put yourself in their shoes. Interview your customers, survey their end users, go to an event and watch users interact with your product — do everything you can to truly understand each side’s needs and concerns. Habit 5 is all about understanding your users, so for now, just note that without this understanding, you can’t know what will truly meet the needs of both sides. Only once you have this understanding can you define a “win-win” solution.</p><p>Creating a great solution is a collaborative effort. When people with diverse backgrounds and skillsets work together, we end up with a wider variety of ideas, we uncover technical insights earlier, requirements are clearer and more flushed out, and everyone feels more ownership in the outcomes of the design process. When you can, get the whole team involved in:</p><ul><li><strong>User research:</strong> the more everyone understands the user, the better. It never hurts to invite the engineering team to user interviews!</li><li><strong>Identifying users and key goals: </strong>defining these together leads to shared understanding, and a better chance that you’re all working towards the same goals.</li><li><strong>Design activities:</strong> stick with sketching and other collaborative design methods as long as possible so that everyone can get involved.</li></ul><p>The next 2 habits provide the processes that help to achieve win-win.</p><h4>Homework</h4><p>Identify someone who embodies win-win thinking, and watch and learn from their example.</p><h3><strong>Habit 5: Seek First to Understand, Then to Be Understood</strong></h3><p>Always remember: you are not your users. Habit 5 is about seeking to truly understand the people who use your product — their backgrounds, paradigms, behaviour patterns, the context in which they use your product… The better you understand them, the more likely you are to design a product that will meet their needs, and that they will actually use.</p><p>Most people don’t listen with the intent to understand; they listen with the intent to reply. They’re either speaking or preparing to speak. This applies to design as well — when we’re conducting user research, we tend to do it through the lens of the problem that we’re trying to solve. We often already have potential solutions in mind, and we’re just trying to validate.</p><p>The next time you kick off a project, forget all this and try to start with no biases. Seek to first get inside your user’s frame of reference and to truly understand where they’re coming from and what they need from your product. Talk to them as much as possible. Even better, watch them use your product in the actual context that they would use it day-to-day. Then start to think about solutions. You will likely come up with so many more potential solutions — things you would not have thought of — and, since they’re based on the user’s actual needs, they will be so much more likely to solve them.</p><h4>Homework</h4><p>Next time you kick off a project, stop yourself from solutioning until you have gained an understanding of the people who use your product. Notice when you start thinking about potential solutions too early, and put them aside.</p><h3><strong>Habit 6: Synergize</strong></h3><p>Synergy means that the whole is greater than the sum of its parts. In a synergistic setting, the real value is in the differences between people. By gathering input from many different people with diverse backgrounds and perspectives, the solution will be better than anything you could have accomplished on your own.</p><p>Working synergistically means staying open to new possibilities. Great ideas can come from anywhere — co-workers, customers or a stranger that you come across while out for a jog. It means having a high tolerance for ambiguity — because you’re confident in your process, you can value the unknowns.</p><p>The real power of Habit 6 is in how the 7 Habits come together — the sum of the habits. The more proactive you are (Habit 1), the more likely you will be to set clear goals (Habit 2) and to work towards them (Habit 3). The more you seek to understand (Habit 5), the more likely you will be to create synergistic, win-win solutions (Habits 4 and 6).</p><p>The last habit, Habit 7, is about renewing.</p><h4>Homework</h4><p>Next time you’re working on a project, actively seek out people who see things differently than you do. Get their view on the problem, and use the different perspective that they provide to create a better solution.</p><h3><strong>Habit 7: Sharpen the Saw</strong></h3><p>Imagine you’re out in the forest trying to cut down a tree. You could saw mindlessly for hours until it’s done… the tree will be cut down eventually. Alternatively, you could stop when your saw gets dull to sharpen it. Ultimately, this will get you there faster. Habit 7 is about renewal. It’s the habit that allows you to keep doing the other 6 habits.</p><p>As a designer at any level, it’s important to make time to learn and grow. Read, <a href="https://uxdesign.cc/just-write-why-product-designers-should-write-and-how-to-get-started-672cb3294d6d">write</a>, take courses. Learn about design as well as things outside your wheelhouse (these will expand your perspective).</p><p>It’s also important to take time for breaks: get away from your computer, get out into nature, exercise, eat healthy, and make time to interact with people. All of these things will help you maintain balance and will make you a better designer.</p><h4>Homework</h4><p>Commit to doing “sharpen the saw” activities every week. Write them down at the beginning of the week and, at the end, think about how they made you feel.</p><p><em>I believe that Covey’s book has stood the test of time because it focuses on core human tendencies, rather than specific tactics or techniques that could change over time. I feel that the learnings as they are applied to design are the same — they’re overarching principles that don’t change depending on the project, team, company, or times. If you haven’t read it, I highly recommend it and I’d love to hear how you apply the habits to your own career.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c806ebf8b8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/the-7-habits-of-highly-effective-designers-3c806ebf8b8">The 7 habits of highly effective 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>
        <item>
            <title><![CDATA[How to give and receive better design feedback]]></title>
            <link>https://uxdesign.cc/design-feedback-how-to-give-and-receive-better-feedback-5efd76188029?source=rss-3e140b6a6c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/5efd76188029</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[design-critique]]></category>
            <dc:creator><![CDATA[Michelle Claessens]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 15:02:03 GMT</pubDate>
            <atom:updated>2019-01-08T01:06:22.241Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’ve all had good experiences with feedback — and some less good. What is it about certain feedback that gets our defences up, while some is crystal clear?</h4><p>When I think about the people who gave me input that encouraged me to better my designs and the designers that I’ve witnessed who were able to effortlessly pull great feedback out of others, I see a few similarities. Focus on these, and you’ll be giving and receiving better feedback in no time!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lvRBLP040TJVBEnz8XgVw.png" /></figure><h3>Giving effective feedback</h3><p>It may not always seem like it, but designers love feedback. We genuinely want the product to succeed, and we want to be better at what we do. We just might not always agree with the feedback we’re hearing. Keep in mind that giving feedback is an art. It’s not about what is said, but what is heard. Here are a few tips to help with this:</p><h4><strong>Be clear and specific</strong></h4><p>When giving feedback, be as clear and specific as you can. “It doesn’t pop” is not very helpful. What does “pop” mean to you? Make sure to start with the aspect of the design that you’re referring to (the colour palette, the main photo, the sign up button). Then describe the problem with that aspect, or how it isn’t solving the problem (is it too subdued? Too sad? Too small?). Finally, explain the impact (a colour palette that is too subdued might make users feel sad—not the tone that we want on a Christmas campaign!). Examples are always helpful as well.</p><h4><strong>Make it a discussion</strong></h4><p>Remember that the designer you’re giving feedback to has spent days, or even weeks, immersed in the project you’re giving feedback on. They’ve interviewed customers, looked through data, created user flows — all in an effort to fully understand the problem and the user. Giving them a bulleted list of things to change will not help them (not to mention, it will most likely be misinformed).</p><p>Any feedback that you give them should be a discussion. Ask questions so you can understand the problem, the user and how the designer arrived at the design you’re looking at. A conversation focused on the problem the design is trying to solve will lead to more helpful, informed feedback — and ultimately a better solution. It also gives the designer a chance to explain and stand up for their ideas, helping them grow as a problem solver.</p><h4><strong>Provide the problem, not the solution</strong></h4><p>Make sure the discussion is focused on the problem the design is trying to solve, not potential solutions. You want your feedback to lead to open discussion. Saying something like “I think this button should be orange” is easy to dismiss as personal opinion and does not leave room for dialogue. Compare this with “I’m not sure the button stands out enough,” which should get people talking about the initial problem and brainstorming potential solutions.</p><p>Focusing on the problem also helps you avoid subjective feedback. Comments should never be about what you like or don’t like. Focus on the problem. How will people use this product? Will this new button solve the initial problem?</p><h4><strong>Build trust</strong></h4><p>A designer’s experiences play a huge role in how they accept feedback, so try to get to know them. Tailoring your feedback to the person you’re providing it to is just as important as making it clear and specific (on the flip side, the designer should also make an effort to let you know how they prefer to receive feedback — more on this below).</p><p>Never point out changes or take over the design. Instead, help the designer understand what isn’t working and allow them brainstorm solutions. This will allow them to learn, while maintaining a sense of ownership. At the same time, make sure that your feedback is always about the design, never the designer.</p><h3>Receiving effective feedback</h3><p>When we receive feedback that we don’t understand or agree with, we often blame the person who gave us that feedback, instead of realizing that the problem is in how we asked for it. Here are a few things to keep in mind when asking someone for input:</p><h4><strong>Set the stage</strong></h4><p>Before jumping into the feedback session, there are some things that you should do to set the stage.</p><ul><li>First, try to give people advanced notice and share work ahead of time. This will ensure that they have enough time to think.</li><li>If possible, provide a working prototype rather than a static mockup. Allowing them to click through a prototype and truly experience the design will help gain more insights.</li><li>Always start by providing context. What’s the overall goal that the design is meant to solve? Who’s the target audience? What are the use cases for the design? What constraints are you working within? The more information you can provide, the more informed the feedback provider will be — and the better the feedback they’ll be able to provide.</li></ul><h4><strong>Ask questions</strong></h4><p>Prompt people for feedback by asking specific, open-ended questions. For example, rather than “do you like this design?” which is vague and allows for a yes/no answer, try “does the call to action draw your attention?” or “what do you think the purpose of this section is?”</p><p>Always ask clarifying questions so you can better understand comments and get to the core of the issue. Remember that feedback is a discussion!</p><h4><strong>Stay problem-focused</strong></h4><p>If feedback veers away from the goal or problem (the one that you explained at the beginning when you <em>set the stage</em>), bring it back. Remind them of the objectives, users and constraints, and ask questions to lead them back down this track.</p><p>If feedback gets too subjective (“I like this” or “I don’t like this”), bring it back to the problem using guiding questions. “Is there anything specific that you don’t think is working to solve the problem?” or “think about our target user — how do you think they would react?”</p><h4><strong>Stay open and positive</strong></h4><p>Accept feedback graciously. If you’re not open to receiving feedback, your peers will be hesitant to give it to you in the future. Remember that they have your best interests in mind, they are commenting on the designs, not you as a designer, and are only trying to help improve the design. Instead of feeling embarrassed or insulted, keep a <a href="https://en.wikipedia.org/wiki/Mindset#Fixed_and_growth">growth mindset</a> — your skills and abilities can be developed, and this is an opportunity to learn and improve.</p><p>It also helps to let people know how you like to receive feedback. Does receiving feedback in front of a group make you nervous? Do you prefer to receive feedback in person, or over email or Slack? Let them know, and your feedback providers can adapt.</p><h4><strong>Take lots of notes</strong></h4><p>You can’t analyze and act on feedback that you can’t remember. So when you’re receiving feedback, be sure to take lots of notes. There are many ways to do this: marked-up screenshots, InVision comments or recordings are just a few.</p><h3>Creating a culture of feedback</h3><p>Creating a culture where feedback is always welcome and people give it readily is essential. Feedback not only accelerates personal growth, it also builds trust, creates consensus and helps teams learn and grow faster. Design feedback leads to higher-quality, more innovative designs — and ultimately a better product.</p><p>At <a href="https://influitive.com/">Influitive</a>, we have a small design team, and so lots of opportunities for informal feedback. Collocation and Slack allow us to work very closely with fellow product and design peers. Our design team makes an effort to ask for feedback about ourselves and our work regularly. We strive show that we respect and value the opinions of others and to demonstrate how to accept and act on feedback.</p><p>The input of non-designers is also vital to coming up with the best solutions, so we make sure to create lots of opportunities for people outside of the design team to weigh in. We share designs on Slack or print them out and post them around the office so that members of teams across the company can contribute. We have weekly Design Alignment meetings, which have an open invitation to anyone in the company. People from Marketing, Customer Success and Engineering attend and we share what we’ve been working on that week — whether it be early research or final, polished designs. This input at all stages of the design process is invaluable.</p><p>As many makers (product designers, engineers, product managers…) often seem to forget, we aren’t designing for ourselves. Our audience has a unique set of experiences and skills, and it’s important to round out feedback with input from actual users. At Influitive, we make an effort to talk to our customers and the end users of our product as much as possible. We are constantly conducting surveys, interviews, discussion threads, and various design activities so that we can better understand their needs. They provide insights we would never think of ourselves.</p><p><em>We’re always looking for new ways to build on our culture of feedback, and would love to hear what you do at your company!</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fux&amp;image=https%3A%2F%2Fucarecdn.com%2F6e8986c7-e64a-4116-9afb-fd71a476f0a9%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href">https://medium.com/media/a19f46680bac3cbdc42953c920d0c104/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5efd76188029" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/design-feedback-how-to-give-and-receive-better-feedback-5efd76188029">How to give and receive better design feedback</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[Just write: why Product Designers should write, and how to get started]]></title>
            <link>https://uxdesign.cc/just-write-why-product-designers-should-write-and-how-to-get-started-672cb3294d6d?source=rss-3e140b6a6c72------2</link>
            <guid isPermaLink="false">https://medium.com/p/672cb3294d6d</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Michelle Claessens]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 14:54:07 GMT</pubDate>
            <atom:updated>2018-11-08T22:29:45.338Z</atom:updated>
            <content:encoded><![CDATA[<h4>Writing is part of design and the best way to get better at anything is to do it. So here goes!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgXIOzD5brB3yXajM3A1KA.png" /></figure><p>For a long time I’ve felt that I should write, but I’ve struggled to start. Why? I worry that my writing won’t be authentic, I won’t be able to convey my thoughts in an eloquent way, or I won’t say anything that people want to read. Ultimately, the idea of putting my thoughts out there for the world to see scares me.</p><p>I’ve tried to tell myself that I don’t need to write: “I’m a designer, not a writer.” I’ve put it off by consistently prioritizing it below day-to-day tasks. I’ve avoided writing because it scares me, and because it’s hard. But there are so many reasons why I <em>should</em> write. And here’s the thing: the best way to get better at anything is to do it. So here goes!</p><h3><strong>Why I’ve decided to write now</strong></h3><h4><strong>1. Writing is part of design</strong></h4><p>The web is mostly words (imagine Twitter without words!). Writing UI copy — headings, calls to action, instructions — is part of being a designer who creates products for the web. That copy needs to be clear and set the right tone. If your beautiful, usable UI falls apart because of a single unclear sentence, all your design work’s been for nothing. Even if you have a copywriter on your team, you need to be able to communicate the purpose of each element to them.</p><h4><strong>2. It’s a great way to learn</strong></h4><p>Writing about a topic forces you to look at it in a different way. When you write about something you tried that didn’t work, for example, you’ll look at the situation more objectively and analyze where things went wrong. You learn more from failure than you do from success, and writing about mistakes will only accelerate that learning.</p><h4><strong>3. It will help me think and communicate more clearly</strong></h4><p>To write, most people will jot everything down, then finesse the points into a coherent narrative. This is a lot like how I design, where I start by outlining the content and components. If you can’t finesse your brain dump into a coherent narrative, people won’t understand what you’re trying to say — and, when it comes to your designs, they won’t be able to use your product.</p><h4><strong>4. It will make me a better storyteller</strong></h4><p>Product design has often been compared to storytelling. Your target user is the protagonist. They have a goal they want to accomplish and obstacles to overcome to achieve that goal. Your design will either help or hinder them from reaching that goal. Being able to analyze the story, identify points of friction and remove them is an essential skill for a designer. In addition to this, all designers need to be able to sell their designs. To get people to understand what you made and why, you need to be able to tell a compelling story about your user achieving their goals through your design.</p><h4><strong>5. It’s important to share ideas about design</strong></h4><p>I’m continually learning from the writing of other designers and I believe that it’s important to keep this cycle going. I hope that sharing what I’ve done will help others learn and grow in their turn.</p><p>At the end of the day, I believe that writing regularly will make me a better designer.</p><h3><strong>How I’m going to get started</strong></h3><h4><strong>1. Commit</strong></h4><p>I plan to make time to write regularly. I won’t worry about the quality to start, I’ll focus on getting my ideas out there. Even if I write seven articles and only share one, I’ve gotten so much more practice!</p><h4><strong>2. Keep an idea list</strong></h4><p>This is something I’ve been doing for a while. Every time an idea for an article strikes, I add it to a page in my Notes app (I use Notes to organize my life, so it’s always nearby and top of mind). Even if I don’t have time to write then, I’ve captured the idea.</p><h4><strong>3. Seek ideas from a wide variety of places</strong></h4><p>When I’m starting a new design, I look for inspiration in many places (design inspiration sites, competitor products, unrelated websites, books, the outside world, etc.). In design, the more sources, the better. It makes sense that the same would be true for writing. Some of the ideas on my list have come from:</p><ul><li>Something new that I’ve learned</li><li>Something I’ve struggled with</li><li>A mistake I’ve made</li><li>Questions I’ve gotten from clients, customers or coworkers</li><li>Interesting conversations with peers</li><li>A behind-the-scenes look at something I made</li><li>The design process or rituals that we use at <a href="https://influitive.com/">Influitive</a></li><li>Tutorials, tips and tricks</li><li>Things that have helped me become a better Product Designer (books, courses, habits)</li><li>Anything that inspires me</li></ul><h4><strong>4. Make an outline first</strong></h4><p>There’s nothing more daunting than a blank page. When designing something new, I start with the project objectives, then outline the content and components. Only then do I start designing. I approach writing the same way: start with an overall thesis statement (what do I want to say?), then create a skeleton that highlights the key points I want to make. Just like at the wireframing stage of design, don’t waste energy fussing about style, format or how well it reads — just get the ideas down. A first draft outline helps you focus on the topic first, and how it’s written later.</p><h4><strong>5. Read more</strong></h4><p>I read a lot. Books, blogs, articles, publications… The more you read, the more ideas for topics you’ll have (believe me — I have a long idea list, I just need to act on it!). Read outside of your industry, as well. You never know what will inspire you!</p><h3><strong>And that’s it (for now)</strong></h3><p>The most difficult part of anything is starting. Starting to write by writing about why I don’t write may seem strange (it’s also a mouthful), but it’s still a start!</p><p>Design is about getting things out there — not perfecting them — and seeing how they do. Writing is similar. Get it out there and see how it does. Learn from that, then improve. I’m here to learn and improve my own skills, so please let me know what you thought of this article.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Ff%2F50d69a%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F50d69a%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href">https://medium.com/media/05d5fd32eda31cbd1b83287606744532/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=672cb3294d6d" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/just-write-why-product-designers-should-write-and-how-to-get-started-672cb3294d6d">Just write: why Product Designers should write, and how to get started</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>