The point is though, product never challenged on approaches, and you’re right. They never came from technical backgrounds. Product managers were promoted from the BA ranks. They never raised technical questions like that - “Is it a bad thing if the customer has to connect this way for this API and another way for another API?” If the idea is that engineering asks those questions, I’d counter with that’s venturing squarely into product’s realm.
- Someone to understand the customer's desires and shut down unnecessary work.
- Drive the team to deliver features that the customers/business actually needs.
- drive tech decisions to prevent future inoperability with other products
- roadshow and maintain a team's reputation across the org
- etc
I can think of a bunch of different ways of solving this that would take a few days to build out.
APIs using different TLS versions falls into the same category. Unless the TLS version is part of the product (which is the case for e.g. API Gateways, webservers and proxies) PMs will likely not care. They should however care about the difference between no TLS at all and a "somewhat modern TLS", because "no security" is definitely an important gap in the product.