Complexity bias is the tendency to give undue credit to complex ideas and systems instead of simpler alternatives. Complexity can signal effort, mastery, innovation, or more features, even when it adds little practical value. section 8.1
A baseline counters this bias by keeping the initial system simple and agile. It provides a reference point for judging later changes without assuming that sophistication automatically improves outcomes. section 8.1
Treat complexity as a decision to justify, not a default signal of quality:
- Compare complex proposals with a credible baseline before investing in additional features or modeling sophistication. section 8.1
- Skip a baseline when accuracy is life-critical, requirements are already certain, or an existing system has been proven in production. section 8.1
- Optimize an already valuable system only after recognizing that its working version already serves as the baseline. section 8.1
