The Feature Nobody Asked For

A builder we worked with added a notifications panel to their product. It looked good, but nobody had asked for it. No user had said "I can't tell when something happens in this app." No payer had objected to its absence. They just thought it would be nice to have.

Three weeks later, a bug fix touched the code the panel depended on, and it broke the login flow sitting next to it. Nobody had budgeted time to maintain a feature nobody needed, so nobody caught it until a user did.

That's the cost of building without a strong reason behind it: You have to maintain it. You think about it every time you touch adjacent code. And if a user eventually notices it, the reaction might be confusion or backlash instead of the gratitude you were hoping for.

So the question before adding anything isn't whether it would be useful or would look impressive. It's whether a user or a payer has told you, directly, that something is missing. Or have we learned through careful experiments if that will solve a user's specific problem. If yes, build it. If the honest answer is "no, but I think they'd like it," that's a guess, not a requirement.