Whenever you’re presenting a design for feedback, it’s helpful to assume that the people who are reading your post or listening to your presentation have zero context.
Rather than jumping straight into your designs, it can be helpful to set the stage.
You might start with the problem statement. What problem are you trying to solve? More often than not, this should help convey the why behind the project.
It can be helpful to recap the things that you’ve learned so far. Especially if you’re multiple rounds of feedback in.
And before you share designs, it can be helpful to share any constraints that you face.
Then you’ll share your design—could be sketches, wire frames, mockups, prototypes, or high fidelity designs.
But before you wrap up your post, consider sharing some open questions, some things that you would like specific feedback around.
And lastly, be sure to outline the type of feedback that you’re looking for. Are you looking for feedback on anything? Just the layout. You looking for feedback on copy? On design aspects, like margin and padding.? Moving pixels this way in that? It can just be helpful to be clear about what level of feedback you’re looking for.
By adding context to your feedback requests, you will drastically increase your odds of soliciting helpful thoughts, questions, and feedback from others.