Yeah, most PO/PMs I've encountered know awfully little about the business processes, their constraints and complex interactions within their own product. They know quite a bit about priorities the various customers voiced, fancy stuff they'd like to demo on the next review or trade fair or customer relationship meeting, or new features they want to get customers interested in. But don't ask them how those features interact with others!
If you want to go into detail with that kind of stuff, your best bet is not the PO, but the lead engineer of the team. If the team was properly staffed, the lead engineer will have a solid knowledge of the business aspects of the product while at the same time being able to cross-reference that with the most important technical aspects.
LLMs will make more people into "lead engineers", even if all they're "leading" is the LLM agents and not other humans, as it was common before the LLM age. One of those will then emerge as the "lead lead engineer" who's going to lead the humans which in turn lead the LLMs. If it wasn't for the "engineer" in the meaning of "code monkey" dying out - which I also expect - we'd have to invent a new title, but I'm currently expecting this shift to go without that. It'll still leave some engineers who made themselves comfortable just churning out code that does whatever a ticket requests, without even understanding one iota of the business process behind the ticket, without a job, but that's the kind of "software engineer" who in my opinion shouldn't ever have taken up the profession anyway.
If you want to go into detail with that kind of stuff, your best bet is not the PO, but the lead engineer of the team. If the team was properly staffed, the lead engineer will have a solid knowledge of the business aspects of the product while at the same time being able to cross-reference that with the most important technical aspects.
LLMs will make more people into "lead engineers", even if all they're "leading" is the LLM agents and not other humans, as it was common before the LLM age. One of those will then emerge as the "lead lead engineer" who's going to lead the humans which in turn lead the LLMs. If it wasn't for the "engineer" in the meaning of "code monkey" dying out - which I also expect - we'd have to invent a new title, but I'm currently expecting this shift to go without that. It'll still leave some engineers who made themselves comfortable just churning out code that does whatever a ticket requests, without even understanding one iota of the business process behind the ticket, without a job, but that's the kind of "software engineer" who in my opinion shouldn't ever have taken up the profession anyway.