Design feedback without context comes back as taste. With context it comes back as fixes.
Post:
- A screenshot or a link. One screen or one flow per thread.
- Who uses it and on what device
- What they are trying to do on that screen
- What you want them to do
- What you are unsure about
- Your constraints: a component library, a brand colour, no designer, a deadline
If you are replying:
- Start with what works. It tells the author what to keep.
- Describe the problem before the fix. "My eye went to the footer first" is more use than "make the button bigger".
- Separate "this confused me" from "I would have done it differently".
- One or two changes that matter beat fifteen that do not.
Useful defaults for non-designers: one typeface, one accent colour, generous spacing, real text in place of filler text, and one obvious action per screen. Most rough-looking products are fixed by removing things.