<?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 Maciej Kownacki on Medium]]></title>
        <description><![CDATA[Stories by Maciej Kownacki on Medium]]></description>
        <link>https://medium.com/@m.kownackis?source=rss-b6cfa6237f0a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*prJ0Y8zP-N4U05MN4mqflQ.jpeg</url>
            <title>Stories by Maciej Kownacki on Medium</title>
            <link>https://medium.com/@m.kownackis?source=rss-b6cfa6237f0a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:11:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@m.kownackis/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[What I’ve learnt about designing while baking Neapolitan-style pizza]]></title>
            <link>https://uxdesign.cc/what-ive-learnt-about-designing-while-baking-neapolitan-style-pizza-aa5dc9b34b02?source=rss-b6cfa6237f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa5dc9b34b02</guid>
            <category><![CDATA[food]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Maciej Kownacki]]></dc:creator>
            <pubDate>Sun, 30 Aug 2020 14:44:52 GMT</pubDate>
            <atom:updated>2020-09-01T11:22:27.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A picture of pizza made by me." src="https://cdn-images-1.medium.com/max/1024/1*LR25ruG4-YnRmryHSu7VVQ.jpeg" /><figcaption>One of the pizzas I baked last month.</figcaption></figure><p>There are countless areas that can bring new conclusions &amp; lessons about designing and I love to discover such inspirations in everyday activities. Specifically in my hobbies, because lessons that I get from them are the most valuable ones, they don’t cost me anything, they’re fun and they’re the most memorable lessons I can get. Moreover, hobbies are a helpful way to maintain a healthy work-life balance, studies (<a href="https://news.sfsu.edu/creative-activities-outside-work-can-improve-job-performance">https://news.sfsu.edu/creative-activities-outside-work-can-improve-job-performance</a>) have shown that having a hobby can improve one’s work performance.</p><p><strong>I needed to fail a couple dozen times before I made a great <em>pizza.</em></strong></p><p><em>“It has long been recognized that user interfaces should be designed iteratively in almost all cases because it is virtually impossible to design a user interface that has no usability problems from the start” — Jakob Nielsen <br>(source: </em><a href="https://www.nngroup.com/articles/iterative-design/"><em>nngroup.com</em></a><em>)</em></p><p>It is fair to assume that it’s possible to both bake good pizza and make a decent design, not necessarily at the same time*(it might be dangerous)*, but both can be achieved with “moderate” efforts. Nonetheless, bringing the game to the A-level might be a tough nut to crack and Aristotle sums it up pretty nicely. “<em>We are what we repeatedly do. Excellence, then, is not an act, but a habit.”</em></p><p>In relation to designing this quote means to me that a single good design is an act of work, which can be finished in a finite amount of time, whereas excellence is a state that one attempts to achieve over and over by improving the good, the better and the best. In practice it means that excellence isn’t and end to be met, but rather a goal to strive for.</p><p>Before I first learned how to make “good” pizza I had spent some time researching authentic Italian recipes, dug into AVPN (Associazione Vera Pizza Napoletana) to learn what is the gold standard for proper Neapolitan pizza. I synthesized my knowledge and made a couple dozen attempts to create the perfect “pie”. Once I got to the point where I was fairly satisfied with my pizza I could’ve stopped, but I didn’t and started exploring even more details related to making perfect pizza such as water quality, experimenting with different kinds of mozzarella and so on.</p><p>For me, the same applies to design, once one gets to the point of “good” design it might be really hard to push oneself beyond that and make even better work and in order to effectively question <em>status quo</em> one needs to use data &amp; feedback as the tools for improvement.</p><p><strong>What works for other designers might not actually work for you.</strong></p><p>There aren’t many areas with effective “one-size” solutions that fit everyone, as we are all distinct people designing different products that deliver spectrum of values. By no means I am implying that cross-domain benchmarking and research can’t bring good results, I am just saying they Can’t be taken for granted. For instance, let’s take an example from a physical world, a car steering vehicle is a perfect device that lets drivers turn the wheels of their car. It’s round and it allows the driver to turn using circular motion, very intuitive and accessible solution, but it won’t work in for the other vehicles.</p><figure><img alt="Photo presents a bicycle with car’s steering wheel attached instead of handle bars." src="https://cdn-images-1.medium.com/max/1024/1*BKrcEAgcCMZuTaNUk6GXrA.png" /><figcaption>My private photo collection, I’ve spotted this bike in the city centre of Warsaw. It’d very tempting to try this out, but I am not able to afford replacing my entire jaw of teeth.</figcaption></figure><p>A good solution in product design works effectively in its place, because it’s tailored to trigger certain responses in a very specific context. While I value researching solutions from different domains than the one I am designing for, I am very careful when judging the usability of the particular function in the context I want to use it.</p><p><strong>There’s not a perfect end. The basically is no end.</strong></p><p>Once I get to the point where stakeholders, myself and product managers are satisfied with the design results I know that we’re just getting started, because agreeing on a concept is a fruit of teamwork and it only proves only one thing at that stage. We agreed on something and we understand one another’s expectations towards the product/feature we’re working on. From this point on design work is all about improving what we’ve learnt and confronting our concept with our users.</p><p>With pizza it can work similarly, I and people came to a point when we agree that my current pizza tastes good, but I wouldn’t be able to learn what I should do to make it appeal to a larger crowd. In order to learn that I need to confront myself with people outside my “bubble”</p><p>In conclusion, I believe craftsmanship plays an important role in the live of a product designer and having a life outside work can help one remember that achieving a decent level at any craft can be convenient. I appreciate cooking (especially) baking pizza, because I can directly confront fruit of my work with the guests I am hosting at home and it’s a very fun way to get feedback from the people I am baking for (most of them are foodies, so no sugarcoating included).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*iPZiwFZAiMYB8q8a" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa5dc9b34b02" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/what-ive-learnt-about-designing-while-baking-neapolitan-style-pizza-aa5dc9b34b02">What I’ve learnt about designing while baking Neapolitan-style pizza</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[A handful of non-technical skills to pursue as a product designer]]></title>
            <link>https://uxdesign.cc/a-handful-of-non-technical-skills-to-pursue-as-a-product-designer-d8bef2118cb2?source=rss-b6cfa6237f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8bef2118cb2</guid>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Maciej Kownacki]]></dc:creator>
            <pubDate>Mon, 03 Aug 2020 13:35:13 GMT</pubDate>
            <atom:updated>2020-08-03T16:05:50.060Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>“If something is going to be better, it is new, and if it’s new you are confronting problems and challenges you don’t have references for. “ </em>— Jonathan Ive</h4><figure><img alt="A designer in front of his working desk communicating design via couple different media at once." src="https://cdn-images-1.medium.com/max/1024/1*nFFxbH673eRFANUIoPgYNA.png" /><figcaption>A simple illustration I’ve drawn for this story.</figcaption></figure><p>While designing for the new and unexplored areas a designer needs to be able to solve problems and identify user needs in a way that it meets business goals. To achieve that one has to not only master visual crafts but be able to…. <em>Be able to do what?</em></p><p>Nowadays it’s becoming more and more important for product designers to be able to use different skills to execute their work and it’s difficult to answer oneself whether everyone needs to become a jack of all trades. The role that a modern designer fulfills is often interpreted differently across organizations and even within the particular organization a designer can be expected to perform distinct tasks, which as a result might be a daunting experience for us, but it’s a substantial factor, which drives our professional development.</p><h3><strong>Empathize with the user</strong></h3><p><em>“More and more, we live in bubbles. Most of us are surrounded by people who look like us, vote like us, earn like us, spend money like us, have educations like us and worship like us. The result is an empathy deficit, and it’s at the root of many of our biggest problems.”</em><br> (source: <a href="https://www.nytimes.com/guides/year-of-living-better/how-to-be-more-empathetic">https://www.nytimes.com/guides/year-of-living-better/how-to-be-more-empathetic</a>)</p><p>While designing it is essential to get out of one’s bubble to better understand the surrounding perspective and different circumstances of the people one’s designing for. It is impossible to become completely unbiased, but researchers discovered that empathy isn’t an immutable character trait and can be developed like any other skill (check out how here: <a href="https://andrewsobel.com/eight-ways-to-improve-your-empathy/">https://andrewsobel.com/eight-ways-to-improve-your-empathy/</a>). A contemporary product designer job is a multidisciplinary role and one needs to quickly adapt to surrounding circumstances. One day we’re designing screens for a banking app, the other day for social media chat, but what happens when we are asked to design “in-vehicle” interfaces for spaceships? Handy hint, empathizing with the target group is gonna make the job a lot easier.</p><h3><strong>Communication</strong></h3><p><em>“Product design is first and foremost teamwork. The ability to be a good communicator will never disappear from the designer’s list of responsibilities. A product designer must be able to describe their work in a way that a project manager and an engineer can understand. In addition, from time to time it is necessary to defend one’s opinion or to reach consensus. To become such a good communicator, a product designer should accumulate experience of communication with different participants of the product development.”</em></p><p>With the recent pandemic related restrictions, a surge in remote jobs might be observed. Most of the companies were forced to change their visions on how to treat remote work and as a result, new communication challenges arose and it has become clear that without decent communication the digital workplace can’t properly function.</p><p>To better communicate one’s ideas through a variety of channels, the designer needs to be fluent with numerous tools, but I think that following are especially important, mind-mapping, wireframing, rapid prototyping, facilitation skills, and requirements gathering. Why these in particular? In a certain way, product design is about channeling expectations, data, and requirements input into output mockups, prototypes, and specifications. So to effectively prepare deliverables, one needs to fluently operate between gathering input and making outputs. Moreover, a contemporary designer should be able to present his or her concepts using the media that different parts of the team will understand. And for this purpose, one might use mindmaps, user flows, or wireframes. BUT these are helpful only when the story is presented.</p><h3><strong>Facilitating meetings</strong></h3><p>As a designer one often presents his or her work in front of management, developers, business specialists, stakeholders, and users and it is essential to have productive meetings, especially when many parties are involved because costs grow proportionally to the participants involved.</p><p>There is a lot of literature related to designing &amp; facilitating meetings at MIT Human Resources website(you can check out the literature here <a href="https://hr.mit.edu/learning-topics/meetings">https://hr.mit.edu/learning-topics/meetings</a>)</p><p>In a nutshell, a typical meeting has content to be discussed, is guided by the process or lack of it, and has a host or facilitator, who drives it towards a certain goal. When planning a meeting it is essential to consider a couple of things such as: including the purpose, participants, and logistics of it. But, what’s even more important is the purpose of the meeting and the agenda, it is always worth to ask oneself “What do I want to achieve with this meeting?”, this is helpful when preparing the agenda of the meeting. So what’s the role of facilitator of the meeting? It’s driving participants towards achieving certain outcomes by following the agenda.</p><p>(<a href="https://hr.mit.edu/learning">https://hr.mit.edu/learning</a> topics/meetings/articles/basics).</p><h3><strong>Desk research</strong></h3><p>When designing for screens it is quite easy to make leaps in the process and jump straight from step one to Sketch or Figma. But it isn’t really what one should do, especially if designing for people. Desk research is essentially gathering secondary data on a given subject, it is collecting data of what others already accomplished in a field. Its role is to review the work of others about what one wants to accomplish. (<em>source:</em> <a href="https://www.userfocus.co.uk/articles/desk-research-the-what-why-and-how.html">https://www.userfocus.co.uk/articles/desk-research-the-what-why-and-how.html</a>)</p><p>Running desk research is especially important for product designers because it helps us avoid reinventing the wheel and finding an optimal solution that is familiar to the users. And if something isn’t new for the users it usually means that it has been previously developed by another party and as a result, it probably can easily be copied or adapted to one’s needs. It doesn’t mean that at all times one should copy what already exists, but in many cases, one needs to find the right, missing puzzle to match the needs of the product one’s designed for.</p><p>This list isn’t in any way complete as I believe that there are some more “soft” skills that a modern product designer should have. However, I believe the ones in the article are essential to improve our day-to-day work and allow us to ship better projects, improve communication, and help us with a design based on the data approach.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8bef2118cb2" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-handful-of-non-technical-skills-to-pursue-as-a-product-designer-d8bef2118cb2">A handful of non-technical skills to pursue as a product designer</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[4 reasons why feedback is a powerful factor in the Product Design process]]></title>
            <link>https://uxdesign.cc/4-reasons-why-feedback-is-a-powerful-factor-in-the-product-design-process-19a4c0bcaa83?source=rss-b6cfa6237f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/19a4c0bcaa83</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Maciej Kownacki]]></dc:creator>
            <pubDate>Mon, 13 Jul 2020 11:16:13 GMT</pubDate>
            <atom:updated>2020-07-15T14:03:38.412Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Critique is inseparable to Product Design process, it drives change, helps us understand user perspective, helps us become better designers, and is a powerful tool in our design kit.</strong></h4><figure><img alt="Energically gesticulating man in office work environment. Talking about a project he’s working on." src="https://cdn-images-1.medium.com/max/1024/1*Nlshv_TwE2OBpTAoh7dC5g.jpeg" /></figure><p>Design is, was, and will always be a debatable matter because everyone responds emotionally towards a product he or she uses. People respond to what they see, feel, hear, or touch and it’s our senses, which guide us on how to use a thing or what to mentally make of it. A car, a fridge, a tv, or a bicycle, all of them enable us to accomplish certain tasks. While looking at any of them a mental model representing one of them is recalled and we get an idea of how to use it (if a designer did well his / her job) and while we fail to use a product we tend to blame ourselves that we didn’t succeed at the task at hand and at many times it isn’t us that we should blame, but the people responsible for calling the product shots.</p><p>In such cases, It is self-evident that “shot-callers” didn’t take the time to reflect on their choices or simply rejected surrounding critique, and to make a well-informed design decision one has to confront the fruit of one’s labor with other people. Only then one can consciously deliver products grounded in mature decisions. We are people designing for other people.</p><h3><strong>Feedback can be a powerful tool in making well-thought strategic decisions</strong></h3><p>Analytics data, feedback, animation, color, typography, layout, copy, technological constraints, platform limitations, system patterns, design systems, and so on… are just the tools that designers use to deliver their work and each of them plays an important role in the product design process. I reject the idea of making design decisions solely based on any of these alone, in the vacuum that doesn’t welcome real users people voices. One can’t let any of these alone guide his/her work. I’ve seen product environments where analytical data was worshipped in the design process, but nothing else besides that. It led to situations where features were developed not to answer users’ problems but improve metrics alone.</p><p>Take, for instance, a relatable problem, “increase CR by x % between steps 1 and 2 in the flow”, it is absolutely fine to have such goals. But instead of reflecting where the problem was, the focus was around the analytics data and “how to hack it” not what problems the users had. In the end, it led us nowhere, analytics data became was such a high factor in the process that it was worshipped, it became a great bias for the team, and didn’t welcome any wider perspective, nor any other voice than the one about data. There wasn’t any space to influence the decision-making process with constructive feedback.</p><p>The tools one has might impair his or her decision-making process and can inefficiently drive the decision-making process. When decisions are made inside a bubble or are guided just by one person alone it usually leads to trust issues, the delivery process should be transparent and welcome as many people as possible to bring in their voices, and this, as a result, helps with making better strategic decisions.</p><h3><strong>Sometimes the ego is too big to cope with feedback</strong></h3><figure><img alt="A Dribbble shot presenting couple conceptual interface screenshots with cute colours and 3D images." src="https://cdn-images-1.medium.com/max/1024/0*ty0LAHQNlwlsGKI8.png" /><figcaption>source (<a href="https://dribbble.com/shots/13372241-Blurr-Series-Creator-Dashboard">https://dribbble.com/shots/13372241-Blurr-Series-Creator-Dashboard</a>) by <a href="https://dribbble.com/tranmautritam">Tran Mau Tri Tam</a> (This is an example of interesting visual design, I am sharing it to just point out strong focus on one of the aspects of the interface)</figcaption></figure><p>I see plenty of designers that frown on me when I take time to provide them with honest critique grounded in my knowledge and experience. This can be observed especially in social media or platforms that let designers share their work /dribbble/ or other social media. Try critiquing one’s UI decisions in one of these platforms and see what happens. Designing graphic images for such platforms became such a detached experience compared to designing experiences and products that it generates a lot of toolkit bias, in this case, UI bias. I see people reject feedback they receive towards their UI, taking it personally and not being able to cope with it.</p><p>Many people believe that it is just supposed to look nice, but I think that design visual aspect is one of the means to create a great product, not the goal. If I wanted to make just nice things I’d try myself at painting still nature. It is difficult to accept feedback as it comes, but if one can’t accept his/her peer’s feedback he or she would be devastated after finding out what people feel while using his or her product.</p><p>Not being able to cope with feedback should be a clear sign that one needs to reflect on one’s understanding of the product designer’s role. We aren’t designing just for ourselves, but the outcome of our work is supposed to enable people to solve their problems and fulfill some expectations. Design is a front-face of the product, it is supposed to sell and when it fails at this task it doesn’t mean that consumers didn’t appreciate great visual design, but somewhere in the process user wasn’t considered with enough care. To illustrate my point, take a look at Product Designer job advertisements, for instance:<br><a href="https://resources.workable.com/product-designer-job-description#:~:text=Product%20Designer%20responsibilities%20include%20defining,requirements%20into%20practical%20product%20features.">https://resources.workable.com/product-designer-job-description#:~:text=Product%20Designer%20responsibilities%20include%20defining,requirements%20into%20practical%20product%20features.</a></p><h3><strong>It is worth to get feedback at all stages of the product design process.</strong></h3><figure><img alt="Two people working closely to one another on computers in a modern workspace. It looks like they’re discussing a project." src="https://cdn-images-1.medium.com/max/1024/1*reqsR1o8ovCkqOIFFPgt7g.jpeg" /><figcaption>source (<a href="https://unsplash.com/photos/Lks7vei-eAg">unsplash.com</a>)</figcaption></figure><p>“<em>At its core, design is about communication. Constructive criticism is a part of that, but it’s something that many designers need but seldom actually receive. Designers are often criticized by clients, professors, and even colleagues but rarely does it take the form of “constructive criticism.” (source: </em><a href="https://creativepro.com/what-does-constructive-criticism-for-design-look-like/#:~:text=At%20its%20core%2C%20design%20is,form%20of%20%E2%80%9Cconstructive%20criticism.%E2%80%9D">What Does Constructive Criticism for Design Look Like?</a> <em>by Roberto Blake)</em></p><p>While working on a feature I try to gather as much feedback as possible, because I don’t know what I don’t know. I believe that confronting my work with open-mind with other people helps me improve it, heavily. Don’t get me wrong I do not try to validate my concepts by placing them in front of others and waiting for their approval of x and y. I rather use the opinions of others to make conscious decisions about improving my designs.</p><p>While working for a prolonged time on a feature or a new product there’s a limited number of ideas that I can generate over the X period of time. When my creative juices are dried what should I do? Confront people. I am aware that at work I am biased by my own limited set of skills in the choices I make, so the opinions of other people with a completely different set of skills open so many doors for me as a designer that I should be thankful for the words of others. Not neglectful nor offended. Even if the words I get are not pleasing or rude.</p><h3><strong>I, myself, giving myself feedback, am my biggest bias.</strong></h3><p><em>“When you evaluate design as an activity, you’ll realize that you spend the majority of your time getting it wrong, getting rejecting and getting it wrong again. A very small amount of your time will be spent getting it right. That’s what we do as designers.” (source: </em><a href="https://uxdesign.cc/nobody-told-me-ux-would-be-like-this-2fa8a30b7a84"><em>Nobody Told me UX Would Be Like This</em></a><em> </em>by<em> </em>Chris Kiess<em>)</em></p><p>My senses and my experience are my biggest advantages and at the same my biggest biases when designing, without those I wouldn’t be able to efficiently produce the work I make. While it might be easy and refreshing to conceptualize something new and generate a couple of new ideas, it isn’t simple to spend a month working and iterating a feature. When working for a prolonged period of time on a given subject it is more and more difficult to question status quo or to take a step back and look at one’s project from afar. One can experience <em>Anchoring Bias </em>which is <em>“Anchoring or focalism is a term used in psychology to describe the common human tendency to rely too heavily, or “anchor,” on one trait or piece of information when making decisions.” (source: </em><a href="https://www.sciencedaily.com/terms/anchoring.htm">https://www.sciencedaily.com/terms/anchoring.htm</a><em>). </em>For me<em> </em>it means that the further I go in the work I produce the deeper I am anchored in the decisions the team made and in my own view of the work I’ve made. To take a step back and see a project with a pair of fresh eyes one has to listen to others.</p><p>It might be difficult at times to hear that one’s designs are ugly or not functional or to cope with negative feedback, but one has to remember that designer’s job isn’t supposed to pet his or her ego but help people achieve certain goals with the products they design. Feedback is one of the tools that I try to use in my every day’s work, I believe it is even more important than Figma or Sketch because it enables me to stop being myself and look on the things I make with a perspective of a different person. Of a person that I might be designing for.</p><p>Food for further reflection, from <strong>Winston Churchill </strong>on feedback.</p><blockquote><em>“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*pGCVx5Ye6UA7J7kn" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://twitter.com/uxminaspretas">UX Para Minas Pretas</a> (UX For Black Women), a Brazilian organization focused on promoting equity of Black women in the tech industry through initiatives of action, empowerment, and knowledge sharing. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19a4c0bcaa83" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/4-reasons-why-feedback-is-a-powerful-factor-in-the-product-design-process-19a4c0bcaa83">4 reasons why feedback is a powerful factor in the Product Design process</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[A short story of how I changed my career track from QA to Product Designer]]></title>
            <link>https://uxdesign.cc/a-short-story-of-how-i-changed-my-career-track-from-qa-to-product-designer-4e59f4cbc393?source=rss-b6cfa6237f0a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e59f4cbc393</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Maciej Kownacki]]></dc:creator>
            <pubDate>Thu, 12 Jul 2018 14:08:03 GMT</pubDate>
            <atom:updated>2018-07-16T12:41:45.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EaIw1cKm9SywAjgMliMB-g.jpeg" /></figure><blockquote><em>“Those who cannot change their minds cannot change anything.” — George Bernard Shaw</em></blockquote><p>Each six months for most of my life I had a different idea of what I want to do for a living. I dreamed of being an architect, concept artist, diplomat, developer, professional athlete and some more. Those usually were some plans that would have never come true. At one point of my life I calmed down. I graduated from a University and this was about time I was ought to move out from my parents. I took a junior QA position in one of the biggest software houses in Poland. That was my first “serious job”, which I considered worth pursuing.</p><p>I applied, I got in. I got promoted to a regular QA. I got my first raise. I got excited about some testing frameworks. Then I got bored by lack of real influence on the product. I got bored by staying aside. I strived for making more decisions in my job. I came to conclusion that I can’t work without creating stuff. Don’t get me wrong. At the end of the Day when I went to bed I couldn’t feel that I created something. This bothered me the most.</p><p><strong>Frontend</strong></p><p>After a few months of testing I remembered that in Mid School I’ve learnt some HTML and CSS and had coded a few layouts for some pocket money. So I jumped into courses. I started learning at Treehouse and Pluralsight.</p><p>I quickly finished couple of courses.</p><p>Then I’ve learnt how Bootstrap works and coded a few layouts with more or less satisfiable results. I designed some of them as well, but at that point I didn’t think it would become my main point of interest, so I didn’t dedicate too much effort to them. Trust me, you don’t want to see those layouts. I had been doing that for a while(circa 2–3 months), but then the moment came. I couldn’t imagine doing it for 8 hours a day for the next couple of years. I started digging around and looking for something else.</p><p>Then the backend episode came! I figured, hey I didn’t like frontend, perhaps backend is the way to go. So I grabbed a Python book and started following it. The course itself was better than anything I’ve coded online, exercises in the book were more challenging for me. But again, it didn’t last longer than 3 months. Yet again I couldn’t imagine spending 8 hours a day writing this kind of code. I enjoyed it, but it wasn’t as rewarding for me as I wished. Don’t get me wrong — Financial gratification for both backend and frontend developer can be great, but money isn’t the only reason I am working for. I want my work to be enjoyable for me. I want to stay motivated to become better every day.</p><p><strong>Design</strong></p><p>I am not really sure how it happened, but after my brief episodes with both frontend and backend I started learning about interfaces. I had tried designing some UI before, but it was for the pictures sake only. I hadn’t considered constraints related to development and business goals. Working for Software house as a QA allowed me to have as much insights into others’ work as possible. Not only did I learn how products are planned, but I was first to witness how development cycle looks like.</p><p>I decided to use that opportunity so I started learning by redesigning interfaces of existing apps. In the company I worked for I’ve received lots of guidance from other designers (@channel, Kudos for all of your help guys!)</p><p><strong>Hardships</strong></p><p>If you are new in the game you can have bad time when making decisions what to learn and how to prioritize this process. I don’t think there’s a right recipe for that. One got to figure it out on his/her own</p><p>QA to PD transition brought communication challenges along. As a QA I didn’t really have to talk much about my work. Each day could be summed up as:</p><ul><li>Today I did this and that</li><li>Tomorrow and this week I am planning to…</li></ul><p>If everything worked as expected that was enough. I didn’t have enough passion for testing. I was good at what I was doing but I would never be great.</p><p>I do not imply by any means that being a QA doesn’t require communication skills. I wasn’t passionate enough to elaborate on my work in bigger details or dig into it more.</p><p>As a designer I needed to make a transition as it is one of the most important skills to communicate clearly about one’s work when creating anything. That was tough at the beginning, but over time I began enjoying it, because I felt that words I speak can have huge impact on the product we’re designing.</p><p>I’ve been experiencing decline in terms of my finances because of starting over, but that has passed over time. Doing what I love I am sure that some more changes are about the corner.</p><p><strong>Education Resources</strong></p><p>Before I joined the team as a junior designer I had been learning for 8–10 months. In that period I planned what I wanted to accomplish weekly and used my private account at Toggl to find out how much time each task consumes for me. I used to spend 15–20 hours a week learning in my own time. I focused on designing full products from mobile products to their Landing Pages. I wanted to master the wider perspective. That allowed me to learn how to accurately estimate my own work. Over that period I used various resources.</p><p>I can’t recall all the things I’ve read, but I believe the listed ones were the most important.</p><p><strong>Conclusion</strong></p><p>Eventually, I decided that I want to be a Designer specialising in User Experience and illustrations. Since then I’ve been pursuing my career by improving my skills. I still have some hard times deciding what I want to learn. As a result I sometimes tackle too much tasks at once, but as I grow as a designer and a person I know that one simply can’t be great at more than 2–3 things. If I could give my past self some advice, it would be:</p><ul><li><strong>Never</strong> use dummy copy in design</li><li>Iterate until you’ve felt that all efforts have been made.</li><li>Lay out well though Information Architecture, don’t jump to designing before that, even wireframes.</li><li>Speak out.</li></ul><p>I hope that I can give some courage to those of you who are scared to change their career track. This might sound cliche, but <em>anything is possible</em>. Almost anything. If you are healthy, literate and have decent internet connection.</p><p><strong>Books:</strong></p><ul><li>Don’t Make Me Think: A Common Sense Approach to Web Usability by Steve Krug</li><li>Blink: The Power of Thinking Without Thinking by Malcolm Gladwell</li><li>How to Make Sense of Any Mess: Information Architecture for Everybody by Abby Covert</li><li>Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days by Jake Knapp</li><li>100 Things Every Designer Needs to Know About People by Susan Weinschenk</li></ul><p><strong>Web resources:</strong></p><ul><li><a href="https://www.smashingmagazine.com/">https://www.smashingmagazine.com</a></li><li><a href="https://uxdesign.cc/">https://uxdesign.cc/</a></li><li><a href="https://uxplanet..org/">https://uxplanet..org</a></li><li><a href="https://www.nngroup.com/">https://www.nngroup.com/</a></li><li><a href="http://www.oracle.com/webfolder/ux/applications/index.html">http://www.oracle.com/webfolder/ux/applications/index.html</a></li></ul><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=4e59f4cbc393" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/a-short-story-of-how-i-changed-my-career-track-from-qa-to-product-designer-4e59f4cbc393">A short story of how I changed my career track from QA to Product Designer</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>