When we are interacting with teams, there will often come a period of giving feedback.
Non-descriptive feedback is generally based on your overall experience
"Please revise, this looks confusing."
"This is not good."
"Change the UI."
"I didn't like it."
This sort of feedback is hard to act on and can often be seen as rude.
Instead, give detailed feedback on what areas you want to see the changes in. Descriptive feedback acknowledges the issue and also suggests a call to action.
Examples:
- The button looks a little off on my machine. Please check the screenshot and acknowledge if it's the same.
- This particular article you wrote lacks examples, and would appear more meaningful with the set of examples. You can use this tool to create pleasing code snippets and check this guide to implement in your article.
While giving feedback feels cumbersome, writing descriptive feedback can guide them to make the required changes faster. It's a win-win for both sides. Next time you give feedback, give actual feedback rather than just a comment.