{"id":369481,"date":"2024-05-21T04:04:27","date_gmt":"2024-05-21T04:04:27","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=369481"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=369481","title":{"rendered":"Giving and receiving feedback as a UX Designer: a short guide on how it should be done<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n

Getting feedback on the design of a digital product from the other members of the development team, stakeholders and clients is an essential part of a UX designer\u2019s job. Ideally, it provides constructive criticism of the design, helps improve the product and perfect it as much as possible to present the best result of work to the users. But getting feedback doesn\u2019t always happen smoothly \u2013 when communication is not established properly or the goals of the process are defined incorrectly, things can go the wrong way. In fact, both asking for feedback and giving it requires following some unwritten rules in order to make this experience useful and comfortable for all parties. In this article we\u2019d like to discuss two things: how to ask for feedback correctly and what to consider if you\u2019re the one who\u2019s giving it.<\/p>\n

<\/figure>\n

6 tips for asking your team’s feedback on UX design correctly<\/u>\u00a0<\/p>\n

    \n
  1. \n

    Define the goal of the design project\u00a0<\/strong><\/p>\n<\/li>\n<\/ol>\n

    In order to evaluate your design, people should know exactly which product it is made for and what goals it pursues. So before asking for feedback, be sure to define the goals of the given design project — for example, \u201cto attract new audience\u201d or \u201cget more users to open this page\u201d. Apart from that, state the problem that you are trying to solve with your design — for example, \u201cThis element has to catch users\u2019 attention\u201d — instead of \u201cI think this element should be bright-red\u201d. Clear definition of goals and problems will help you get constructive criticism instead of subjective judgment.<\/p>\n

      \n
    1. \n

      Clearly state what you want from feedback<\/strong><\/p>\n<\/li>\n<\/ol>\n

      Feedback can be of various types depending on what you want to get from it. Be sure to explain what you need exactly from people reviewing your work. Do you want them to point out mistakes? Or do you want to hear some tips and suggestions on how to make your design better? Or maybe you want them to compare the product with the products of competitors? The more specific feedback you get, the more useful it is.\u00a0<\/p>\n

        \n
      1. \n

        Use special tools to structure reviews<\/strong><\/p>\n<\/li>\n<\/ol>\n

        In the modern reality, the majority of collaborative working processes happen remotely. If you are getting feedback this way, it is helpful to use some tools for organizing team collaboration, structuring information and storing all feedback in one place.\u00a0<\/p>\n

          \n
        1. \n

          Back up your design choices with research data<\/strong><\/p>\n<\/li>\n<\/ol>\n

          In order to understand why you\u2019ve made this or that design choice in the product, people should be familiarized with the data that you\u2019ve collected beforehand by conducting user research, testing and other methods. If your design is centered around this data, it will most likely make much more sense and eliminate some objections.\u00a0\u00a0<\/p>\n

            \n
          1. \n

            Ask reviewers specific questions<\/strong><\/p>\n<\/li>\n<\/ol>\n

            Don\u2019t expect the reviewer to touch all the necessary points themselves while giving you feedback. Encourage them with questions that will help you understand more about their opinion on your design. For example: \u201cWhat did you like the most\/the least? Which elements did you find memorable\/confusing\/boring? What would you add\/remove?\u201d<\/p>\n

              \n
            1. \n

              Whatever the feedback, react politely<\/strong><\/p>\n<\/li>\n<\/ol>\n

              One of the key rules when getting feedback is to behave professionally and politely. Reviewers can be different, and not all of them give constructive criticism. But even if you don\u2019t agree with their opinion, it\u2019s important to not take it personally. Remember that receiving feedback is a necessary part of any design process, and if you don\u2019t understand the reviewer\u2019s point of view, it\u2019s better to ask a few more questions and encourage a fruitful discussion rather than starting a conflict.\u00a0<\/p>\n

              8 things to consider when giving UI\/UX design feedback<\/u>\u00a0<\/p>\n

              The situations where you may be asked to give feedback include stating your opinion on the work of your colleagues at team meetings, evaluating the projects of the job candidates (if you are a member of a hiring team) or supervising the projects of your company\u2019s interns. Giving valuable and objective feedback is not as easy as it may seem: one needs to be able to not bring everything to a gruff criticism while also not be reluctant to give an honest evaluation of a given design. That\u2019s why it\u2019s important to train your feedback skills, and that can be done by putting your own designs on display and listening to how other professionals analyze them. If you have been asked to give feedback for the first time recently and don\u2019t feel confident yet, here is a list of things that you should pay attention to when doing that.\u00a0<\/p>\n

              <\/figure>\n
                \n
              1. \n

                Overall impression<\/strong><\/p>\n<\/li>\n<\/ol>\n

                When a user opens the product for the first time, the instant overall impression is what defines whether they will continue using it or leave. That\u2019s why it plays major importance in design. Start evaluating the work by how it makes you feel and whether you think that impression corresponds to the product\u2019s idea.<\/p>\n

                  \n
                1. \n

                  Content placement<\/strong><\/p>\n<\/li>\n<\/ol>\n

                  After getting the first impressions, our eyes start looking through the content of a product. Analyze whether there\u2019s a hierarchy in how the content is placed and if it\u2019s easy for your eyes to travel through it and quickly grab the main parts.\u00a0<\/p>\n

                    \n
                  1. \n

                    Structure of elements<\/strong><\/p>\n<\/li>\n<\/ol>\n

                    In well-performed design, elements should be aligned, structured and grouped according to their function and relation. Is it easy to find a certain element in the product you\u2019re reviewing? Are the elements combined into logical groups and the groups divided by a certain amount of white space to avoid cluttering?\u00a0<\/p>\n

                      \n
                    1. \n

                      Integrity<\/strong><\/p>\n<\/li>\n<\/ol>\n

                      One of the main indicators of a good UX is integrity of design throughout the whole product. All elements should combine harmoniously in terms of color, shapes, size, fonts. If you see poorly matched colors, buttons of varying shape, inconsistency in text fonts or unregulated size of elements, be sure to mention that in your feedback.\u00a0\u00a0<\/p>\n

                        \n
                      1. \n

                        Clarity<\/strong><\/p>\n<\/li>\n<\/ol>\n

                        The main goal of a UI\/UX design is to navigate users through the product, showing them what actions they should perform to complete a certain task. Check whether the design you\u2019re evaluating has clear calls to action. Is it easy to intuitively understand which button bears which function? Is there clarity in how you are supposed to navigate through the product, or have you stumbled upon some difficulties in understanding how to perform some tasks?<\/p>\n

                        <\/figure>\n
                          \n
                        1. \n

                          Compliance with the products\u2019 goals<\/strong><\/p>\n<\/li>\n<\/ol>\n

                          UI\/UX design should not only be aesthetically pleasing and functional, but also meet the product\u2019s goal and correspond to its target audience. For example, if the product is aimed for kids, but it has a dark and gloomy color scheme, it would make users’ experience much less enjoyable. Do the colors, functions and other elements of the design reflect the product\u2019s goal and TA needs, or is there any imbalance between what the product is and what you expect it to be?<\/p>\n

                            \n
                          1. \n

                            Accessibility\u00a0<\/strong><\/p>\n<\/li>\n<\/ol>\n

                            Accessibility has become one of the most important product design requirements. Here you should evaluate whether the product would be comfortable to use for people with visual\/hearing\/physical impairments. Is there a way to choose dark mode, increase text size, use voice search?<\/p>\n

                              \n
                            1. \n

                              Flexibility<\/strong><\/p>\n<\/li>\n<\/ol>\n

                              A good modern design should be very flexible. This is due to the fact that because of constantly changing trends and technology capabilities, software products need to be updated regularly — and therefore, their UI\/UX design should be easy to change and update. Is it easy to imagine the product you\u2019re reviewing in different colors, with different buttons, different elements structure and so on? Or do you feel like any update would break the product\u2019s usability?<\/p>\n

                              Conclusion<\/strong><\/p>\n

                              <\/figure>\n

                              Feedback is a powerful tool in UX design that should not be disregarded during the working process on any product. If given correctly, it can have a huge positive impact on the user experience, making the product align with user expectation to the highest level. The most important rule when giving or receiving feedback is to stay professional and respectful, giving deliberated constructive criticism and carefully noting errors and any issues, improving which can make the product better for everyone. <\/p>\n<\/div>\n<\/div>\n<\/div>\n

                              <\/div>\n


                              \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 https:\/\/habr.com\/ru\/articles\/796879\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

                              <\/div>\n
                              \n
                              \n
                              \n
                              \n

                              Getting feedback on the design of a digital product from the other members of the development team, stakeholders and clients is an essential part of a UX designer\u2019s job. Ideally, it provides constructive criticism of the design, helps improve the product and perfect it as much as possible to present the best result of work to the users. But getting feedback doesn\u2019t always happen smoothly \u2013 when communication is not established properly or the goals of the process are defined incorrectly, things can go the wrong way. In fact, both asking for feedback and giving it requires following some unwritten rules in order to make this experience useful and comfortable for all parties. In this article we\u2019d like to discuss two things: how to ask for feedback correctly and what to consider if you\u2019re the one who\u2019s giving it.<\/p>\n

                              <\/figure>\n

                              6 tips for asking your team’s feedback on UX design correctly<\/u>\u00a0<\/p>\n

                                \n
                              1. \n

                                Define the goal of the design project\u00a0<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                In order to evaluate your design, people should know exactly which product it is made for and what goals it pursues. So before asking for feedback, be sure to define the goals of the given design project — for example, \u201cto attract new audience\u201d or \u201cget more users to open this page\u201d. Apart from that, state the problem that you are trying to solve with your design — for example, \u201cThis element has to catch users\u2019 attention\u201d — instead of \u201cI think this element should be bright-red\u201d. Clear definition of goals and problems will help you get constructive criticism instead of subjective judgment.<\/p>\n

                                  \n
                                1. \n

                                  Clearly state what you want from feedback<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                  Feedback can be of various types depending on what you want to get from it. Be sure to explain what you need exactly from people reviewing your work. Do you want them to point out mistakes? Or do you want to hear some tips and suggestions on how to make your design better? Or maybe you want them to compare the product with the products of competitors? The more specific feedback you get, the more useful it is.\u00a0<\/p>\n

                                    \n
                                  1. \n

                                    Use special tools to structure reviews<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                    In the modern reality, the majority of collaborative working processes happen remotely. If you are getting feedback this way, it is helpful to use some tools for organizing team collaboration, structuring information and storing all feedback in one place.\u00a0<\/p>\n

                                      \n
                                    1. \n

                                      Back up your design choices with research data<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                      In order to understand why you\u2019ve made this or that design choice in the product, people should be familiarized with the data that you\u2019ve collected beforehand by conducting user research, testing and other methods. If your design is centered around this data, it will most likely make much more sense and eliminate some objections.\u00a0\u00a0<\/p>\n

                                        \n
                                      1. \n

                                        Ask reviewers specific questions<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                        Don\u2019t expect the reviewer to touch all the necessary points themselves while giving you feedback. Encourage them with questions that will help you understand more about their opinion on your design. For example: \u201cWhat did you like the most\/the least? Which elements did you find memorable\/confusing\/boring? What would you add\/remove?\u201d<\/p>\n

                                          \n
                                        1. \n

                                          Whatever the feedback, react politely<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                          One of the key rules when getting feedback is to behave professionally and politely. Reviewers can be different, and not all of them give constructive criticism. But even if you don\u2019t agree with their opinion, it\u2019s important to not take it personally. Remember that receiving feedback is a necessary part of any design process, and if you don\u2019t understand the reviewer\u2019s point of view, it\u2019s better to ask a few more questions and encourage a fruitful discussion rather than starting a conflict.\u00a0<\/p>\n

                                          8 things to consider when giving UI\/UX design feedback<\/u>\u00a0<\/p>\n

                                          The situations where you may be asked to give feedback include stating your opinion on the work of your colleagues at team meetings, evaluating the projects of the job candidates (if you are a member of a hiring team) or supervising the projects of your company\u2019s interns. Giving valuable and objective feedback is not as easy as it may seem: one needs to be able to not bring everything to a gruff criticism while also not be reluctant to give an honest evaluation of a given design. That\u2019s why it\u2019s important to train your feedback skills, and that can be done by putting your own designs on display and listening to how other professionals analyze them. If you have been asked to give feedback for the first time recently and don\u2019t feel confident yet, here is a list of things that you should pay attention to when doing that.\u00a0<\/p>\n

                                          <\/figure>\n
                                            \n
                                          1. \n

                                            Overall impression<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                            When a user opens the product for the first time, the instant overall impression is what defines whether they will continue using it or leave. That\u2019s why it plays major importance in design. Start evaluating the work by how it makes you feel and whether you think that impression corresponds to the product\u2019s idea.<\/p>\n

                                              \n
                                            1. \n

                                              Content placement<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                              After getting the first impressions, our eyes start looking through the content of a product. Analyze whether there\u2019s a hierarchy in how the content is placed and if it\u2019s easy for your eyes to travel through it and quickly grab the main parts.\u00a0<\/p>\n

                                                \n
                                              1. \n

                                                Structure of elements<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                In well-performed design, elements should be aligned, structured and grouped according to their function and relation. Is it easy to find a certain element in the product you\u2019re reviewing? Are the elements combined into logical groups and the groups divided by a certain amount of white space to avoid cluttering?\u00a0<\/p>\n

                                                  \n
                                                1. \n

                                                  Integrity<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                  One of the main indicators of a good UX is integrity of design throughout the whole product. All elements should combine harmoniously in terms of color, shapes, size, fonts. If you see poorly matched colors, buttons of varying shape, inconsistency in text fonts or unregulated size of elements, be sure to mention that in your feedback.\u00a0\u00a0<\/p>\n

                                                    \n
                                                  1. \n

                                                    Clarity<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                    The main goal of a UI\/UX design is to navigate users through the product, showing them what actions they should perform to complete a certain task. Check whether the design you\u2019re evaluating has clear calls to action. Is it easy to intuitively understand which button bears which function? Is there clarity in how you are supposed to navigate through the product, or have you stumbled upon some difficulties in understanding how to perform some tasks?<\/p>\n

                                                    <\/figure>\n
                                                      \n
                                                    1. \n

                                                      Compliance with the products\u2019 goals<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                      UI\/UX design should not only be aesthetically pleasing and functional, but also meet the product\u2019s goal and correspond to its target audience. For example, if the product is aimed for kids, but it has a dark and gloomy color scheme, it would make users’ experience much less enjoyable. Do the colors, functions and other elements of the design reflect the product\u2019s goal and TA needs, or is there any imbalance between what the product is and what you expect it to be?<\/p>\n

                                                        \n
                                                      1. \n

                                                        Accessibility\u00a0<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                        Accessibility has become one of the most important product design requirements. Here you should evaluate whether the product would be comfortable to use for people with visual\/hearing\/physical impairments. Is there a way to choose dark mode, increase text size, use voice search?<\/p>\n

                                                          \n
                                                        1. \n

                                                          Flexibility<\/strong><\/p>\n<\/li>\n<\/ol>\n

                                                          A good modern design should be very flexible. This is due to the fact that because of constantly changing trends and technology capabilities, software products need to be updated regularly — and therefore, their UI\/UX design should be easy to change and update. Is it easy to imagine the product you\u2019re reviewing in different colors, with different buttons, different elements structure and so on? Or do you feel like any update would break the product\u2019s usability?<\/p>\n

                                                          Conclusion<\/strong><\/p>\n

                                                          <\/figure>\n

                                                          Feedback is a powerful tool in UX design that should not be disregarded during the working process on any product. If given correctly, it can have a huge positive impact on the user experience, making the product align with user expectation to the highest level. The most important rule when giving or receiving feedback is to stay professional and respectful, giving deliberated constructive criticism and carefully noting errors and any issues, improving which can make the product better for everyone. <\/p>\n<\/div>\n<\/div>\n<\/div>\n

                                                          <\/div>\n


                                                          \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 https:\/\/habr.com\/ru\/articles\/796879\/<\/a>
                                                          <\/br><\/br><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-369481","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/369481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=369481"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/369481\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=369481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=369481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=369481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}