I don't think it would make sense any other way. When doing rituals like refinement and sprint planning, POs want features but have no idea how they interact wi

I don't think it would make sense any other way. When doing rituals like refinement and sprint planning, POs want features but have no idea how they interact with what's already there, or how integrations are implemented, or how things are optimized. Simple features might be very complex to change for example, often because product itself asked to make something that does not scale for the sake of velocity, and now wants to build on top of that. There should be a conversation, engineers should inform POs about risks, alternatives, workarounds, etc. Sometimes POs are just not aware that there is a much better way to do X.