When teams list what they shipped, they rarely mention what they killed. The author highlights two common but misguided features: a "document hub" and a "notifications centre." Both seem simple, yet each stakeholder adds another requirement, turning the project into a complex rebuild of existing services like Google Drive or Gmail. Legacy systems generate PDFs for compliance, and stakeholders push for persistent communication channels, leading to bloated platforms that are costly to maintain across iOS, Android, and web updates.

The author emphasizes that the real challenge is not building but the ongoing running costs—maintenance, security, and adaptation to platform changes. To decide what not to build, illustrate long‑term expenses and rigorously evaluate each use case. The answer often is to use simple or existing solutions instead of creating a one‑size‑fits‑all platform.

The author advises being selective about additions and militant about removal, noting that deleting features is undervalued despite its importance. Gerry McGovern’s research shows stripping 80‑90% of site content can improve performance, reinforcing that less can be more.