The most important product decision is what you don't build

The author argues that deciding what *not* to build is as important as what you do ship, using document hubs and notification centers as examples of features that consume disproportionate resources relative to their value. Rather than creating catch-all platforms to solve organizational problems, he advocates for addressing each use case individually and ruthlessly questioning whether it actually needs a dedicated feature or platform built to solve it. Demonstrating long-term maintenance costs to stakeholders, rather than build costs alone, has proven effective in killing unnecessary features.