> The biggest mistake I see PMs make is coming in with an over optimism bias and assuming that your product must be top of mind for all users when the reality is that the most often scenario you discover from user interviews is that the problem you're trying to solve is of relatively minor importance to most people.
You see this come through in products all. The. Damn. Time.
Some PM, and probably one or more designers who were on their side, wanted an "experience". The user just wants to get in and out of your thing as fast as possible and in a way that requires minimal attention.
I just wanted to pay my fucking water bill. A barely-formatted HTML form with nothing else on the page would have been better than almost anything they might come up with. Anything but expert and extremely tasteful efforts to improve on that, will just make it worse. But no. The PM wanted an "experience".
And don't get me started on people in software who complain about users complaining about redesigns. Those users just wanted to do the three clicks they do every morning to do the one thing they do with your software, then forget about it again until tomorrow. You surprised them with a full screen "LOOK WHAT'S NEW" they didn't want and had to figure out how to get rid of, then made them waste some time playing "Where's Waldo" for the element they usually click, and maybe even made it so they couldn't figure out how to do that one thing at all. Of course they're not happy.