The Curse of Knowledge is the bias that makes implementation fluency obscure the user's perspective. An engineer sees database tables, API routes, and workers; a user may experience only relief from scheduling anxiety. section 5.1
One button, two realities
A developer may describe scheduling as checking whether two date ranges overlap. A sales manager experiences replacing nine emails, double-booking fears, and calendar coordination with one link. The implementation is a mechanism; the product is the pain it removes. section 5.1
Counter the bias by asking:
- What user pain exists before the feature? section 5.6
- Does the description explain why the product exists, rather than merely inventorying features? section 5.6
- Could someone reproduce the product from one sentence? section 5.6
