The feature shipped perfectly. The timing was wrong by about six months.

Built a collaboration feature during a period when our customers were operating in heavily siloed environments. Individual users working independently. The feature was well-designed and technically solid. Nobody used it because the organizational behavior it required didn't match how teams were actually working at that moment.

Six months later, several of our larger customers reorganized toward more collaborative workflows. Suddenly the feature that had been ignored started getting adoption. Not because we changed anything about it but because the context around it shifted to match what it was designed for.

This is the kind of thing that doesn't show up in standard product analysis. The feature wasn't bad and the users weren't wrong. The timing was off in a way that no amount of user research would have revealed because it depended on organizational changes that were in motion but hadn't yet manifested in daily behavior.

I've become more patient with features that don't immediately find adoption. Some of them are genuinely wrong and should be removed. But others are right and early, waiting for the market context to catch up with the product vision. Distinguishing between the two is mostly a matter of talking to customers about their trajectory rather than their current state. If they're moving toward a way of working that makes the feature valuable, patience is justified. If they have no plans to work differently, the feature probably missed.