Handling objections when delivering a project
summary
Practical workshop on handling client objections during project delivery and demos, covering common complaints like “add wow effects,” “I pay you—what for?”, requests for more variants, and disputes over following or not following client instructions. It presents techniques and responses developers can use when facing these specific objection types during demonstrations.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:09Customer objections
- 10:22Classic sales scheme
- 15:24Project workflow
- 22:07Case: handling feedback
- 32:59Objection handling goals
- 42:58Template objections
- 52:33Recommendations and resources
- 56:07When to reject client
related talks
35mSatisfying Collaboration with a Non-Technical Client
57mDebugging Difficult Conversations - Or "How not to chicken out"
06mLightning Talk: Undefined Behavior - Toolkit to Improve Communication With Clients
23mHow To Win Designers And Influence Developers
56mDebugging Difficult Conversations - Or "How not to chicken out"
47mImprove your code by improving your communication
38mNobody Wants to Work With You
48mDon’t Fear the Final Boss: Explaining Improvement Ideas to Management