~/talk

How to ask for web design feedback

links:none on file
slides:none on file

Explains how to get useful client feedback by combining real-time + asynchronous review, using collaboration tools like Figma and Penpot, and asking targeted questions that tie each design choice to business goals. Recommends frequent checkpoints (don’t move weeks ahead without sign‑off), framing problems not solutions, anticipating three common requests (bigger logo, more menu items, “add more”), offering limited alternatives and A/B testing, and accepting that the client pays and can request changes even after justification.

AI-written summary · about

  1. 0:00Introduction and personal story
  2. 2:35Speaker introduction and background
  3. 4:23What is asking for feedback
  4. 6:11Why asking for feedback matters
  5. 7:41Barriers to asking for feedback
  6. 9:06Tips for effective feedback requests
  7. 11:38Building trust and asking specific questions
  8. 13:44Leveraging co-creation benefits
  9. 15:30Focus on business objectives
  10. 17:17Anticipating client needs
  11. 19:12Common client requests explained
  12. 23:10Audience questions begin
  13. 24:13Receiving feedback as a client
  14. 25:40Real-time vs asynchronous feedback
  15. 28:34Handling non-user feedback
  16. 32:08Website is for customers, not you
  17. 33:11Closing and thanks
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.