> What happens is that the things a PM does do not get done. Very few engineers want to maintain relationships with customers, interview users to identify poten

> What happens is that the things a PM does do not get done. Very few engineers want to maintain relationships with customers, interview users to identify potential features, manage leadership, play politics for resource allocation, and so on. So it doesn't get done. That's not what a PM does. You're missing leaders. Customer relations is generally under sales. Resource allocations, politics, that's engineering leadership stuff. Customer interviews is part of what a PM (or UXer) does. It's never been a critical pain point in any business I've been though. It's part of defining the product, oftentimes companies have a X years backlog of features users asked for and not enough time to build.