How to manage design feedbacks strategically
Make it more prominent! Most prominent in the page… no entire universe.. slight more…
As a designer, managing feedback is quite important (and an underrated soft skill). When a project is being reviewed by multiple teams, there are loads of comment/feedback start floating around the Figma.
The effective design delivery depends entirely on the designer, that how s/he handles the design feedback, executes and understands the intent behind the multiple feedback.
A few of my key learnings to manage design feedback strategically, are as below -
1. Prioritise the feedback
Prioritising the feedback is important. The best way to implement feedbacks effectively is filtering out important, neutral, to be skipped (for now). This way you can get the most important feedbacks and improve the designs drastically in much shorter time.
Hence, Its not recommended to start working on all feedbacks one by one. Better if we decide the priority and simplify the execution.
2. Tell your current design status
A designer should always convey the design’s current status whether it is in progress, half-baked, or complete. Getting multiple feedbacks in between design processes (Since you have not completely crafted what you thought of) could lead to losing track.
Because stakeholders can perceive your design solution as the final one, and review it accordingly.
3. Match frequency with Product Managers
Sometimes, a Product manager may seem unable to convey constructive feedback that the designer can understand easily, as a designer we should ask nested questions to reach the same level that Product Manager is visualizing.
It happens many times that a Product Manager is highly attached to the design of other apps. It’s not that something worked for others, will work for us also, We should discuss and agree upon it collectively.
4. Do not work like a tool
A designer should not work as a tool, instead they should try to understand the thoughts behind micro-level feedback and share better alternatives. Because designers can visualise the output better before applying, than anyone else.
5. Leave your Ego (Yes, Its hard)
Never take feedback personally, instead consider it as a jury for your work!. It could be harsh sometimes, but ultimately it will help you to produce the best. (Definitely, you should convey if its way too harsh, and disturbs your creative state)
6. Never get too attached to your design
Most of the time, there is a scope for improvement, so never get attached to your design, be flexible to tweak. If you have a strong emotional bond or attachment for your craft, you will have very less chances for improvements.
It also depends on us what is our purpose, to build better products collectively or proving ourselves right.
7. Reduce subjective feedbacks
We all know UX design is subjective. It is possible that multiple persons can be right at the same time.
So instead of arguing with personal bias, defend your design decisions with the numbers, previous learnings, and your perspectives. This will reduce subjective feedback.
8. Respect developers’ feedback
Feedback from developers is important to improve product efficiency. If you can re-use the existing component/widget, do that. No matter how nicely you designed the new one, if it takes time to load, user will be frustrated.
For e.g. Designing custom elements every time is painful for both developers and products. Better using the existing one, if its not hampering UX.
That's all! Looks like something is missed in the list? Comment your way of working, and how do you manage the feedback.
If you find this article helpful, please hit that clap button to help others find it. One clap, two claps… or long-press for more!
