💬 Join the discussion: When sharing designs with your team to get feedback, how do you make sure it is useful?
Discover more from Low Fidelity
💬 Join the discussion: When sharing designs with your team to get feedback, how do you make sure it is useful?
Share your tips and techniques in the comments
🤟 Happy Friday Yall! I wanted to get your thoughts on something I am tackling with at work and maybe you are as well and that is getting feedback on our designs.
Working remotely has a lot of benefits but it has also brought challenges which we need to be overcome so we can do our best work. Getting feedback on our designs and ideas is one of those challenges especially when previously we were able to walk up to our team members to ask for their feedback in person but now we need to schedule time and sometimes even share links through Slack which feels so impersonal. But asking for feedback is a crucial part of the design process. It helps us get out of our design bubble to make sure we are actually solving the problem for our users. The more people we share the designs the more viewpoints we can examine our ideas from. It's great when it works but sometimes it can add confusion, doubt, and turn into a painful experience. Which brings us to our question, when sharing designs with your team to get feedback, how do you make sure it is useful?
To join the conversation, just type a comment below👇🏼
💬 Join the discussion: When sharing designs with your team to get feedback, how do you make sure it is useful?
Make feedback meaningful by removing the meaningless.
Row heights, button widths, patterns, those should all be defined somewhere.
This makes your feedback about breaking new ground, and pioneering new things.
No more doubt. No more confusion.
Invest in design systems.
Invest in playbooks.
Invest in guidelines.
Invest in pattern libraries.
And most of all, you will see that these things are really a sign of you investing in your people.
Which is what matters most.