The Client is Always Right {But Sometimes They Need a Little Help}
summary
A practical method claims that spending 30–45 minutes on three short exercises — why who how what when where, alphabet what, and adjusting the periscope — yields concrete outcomes: avoid permission/format surprises (no more copying text from the browser), force platform choices (web vs native), capture sentences via voice memo or whiteboard, and catch usability gaps like voice recognition missing women’s voices. Teams report fewer reworks, a tighter feature list, and aligned scope across design, dev, and content.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:37Client needs misunderstood
- 9:33Storytelling foundations
- 11:17Exercise: Who what when where
- 17:58Exercise: Product storytelling
- 20:54Exercise: Alphabet soup clarity
- 24:19Exercise: Scope clarity
- 29:58Closing and opening the floor for questions
related talks
56mFocus on the User: Making the World a Better Place
23mHow To Win Designers And Influence Developers
48mMastering Cross-Organizational Teamwork
58mLet's Work Together!
49mAll Aboard: Tools and Tactics for Building Team Consensus.
52mQuestioning the "why"
49mHow to Speak Designer
21mHow top designers find their path and creative spark