Managing Expectations
summary
A six-week rush for a membership + e-commerce site with a “ginormous” budget collapses after skipping scoping and discovery, hitting an unexpected Drupal migration with large metadata, missed UI milestones, exhausted team and a client who switches to Squarespace. Practical prescriptions: require a deposit and milestone structure, treat scope changes as scope adjustments not “change orders,” enforce boundaries and response SLAs (example: two business hours), follow every conversation with written confirmation, and make clear that a services client owns the work product.
AI-written summary · about
chapters (11)
- 0:00Introduction and client call
- 6:18What went wrong analysis
- 10:16Lessons from the failure
- 16:37Key principles for success
- 20:24Tips for managing expectations
- 37:20Best communication methods
- 40:00Client owns the work product
- 49:13Customer is always right
- 53:12Firing a client advice
- 57:49Payment and project boundaries
- 1:03:34Handling scope adjustments
