Features follow an S-curve of value. Early effort yields little, then a steep rise, then diminishing returns. Use this model to determine if a feature needs more investment to become valuable or if you've already extracted its maximum worth and should stop investing.

An Anthropic engineer, drawing on experience from Slack, notes that users deeply invested in a platform's workflow will resist switching to a new, theoretically "better" tool. The cognitive overhead of adopting a new interface outweighs small productivity gains.

What developers dismiss as obscure 'edge cases' in legacy systems are often core, everyday functionalities for certain customer segments. Overlooking these during a rewrite can lead to disaster, as the old code was often built entirely around handling these complexities.

Adopt an "unshipping" culture. If a feature doesn't meet a predefined usage bar after launch, delete it. While a small subset of users may be upset, removing the feature reduces clutter and confusion for the majority, leading to a better overall user experience.

People are unreliable at predicting their future behavior. Instead of asking if they *would* use a new feature, ask for a specific instance in the last month where it *would have been* useful. If they can't recall one, it's a major red flag for adoption.

When prioritizing features, don't just ask what percentage of your current customers will use it. Sometimes, it's strategic to build features that very few existing users need, specifically because those features will attract a new, more desirable customer segment. This is a risk, but it's a calculated bet on moving your business upmarket or into a new vertical.

Figma learned that removing issues preventing users from adopting the product was as important as adding new features. They systematically tackled these blockers—often table stakes features—and saw a direct, measurable improvement in retention and activation after fixing each one.

StatusGator discovered a core use case by observing user inaction. When customers turned off the primary alert feature, the founders realized the 'single pane of glass' dashboard had standalone value, which led to the development of public status pages.

Adding numerous features to a service offering can hurt retention. Customers who don't use every component feel they aren't getting full value, creating a perception of waste that leads to cancellations. It's better to offer fewer, high-impact deliverables that ensure high utilization.