Who is truly responsible for delivering business value to the organization: the product owner or the engineering team?

I recently spoke with a product owner about his experiences working with engineers who are also focused on outcomes rather than just delivering requested features. Here's what he shared:

• "When engineers focus on the outcome, I find myself trusting them more with technical decisions."
• "Focusing on outcomes opens up new opportunities and ideas. The outcome is the key to having discussions about solutions."
• "I love discussing outcomes with engineers because they simply have a different perspective than I do."
• "I can create tickets for all these ideas, and then we'd have to discuss them. But then an engineer looks at it and thinks: I can fix this in half an hour. These everyday low-hanging fruits are really valuable."

The role of a product owner, as we know it, is to serve as the exclusive conduit of business value between IT and the business. But what if that model isn't working as well anymore?

Here's an excerpt from Mark Schwartz's The Art of Business Value on the topic.