Whenever you see one of these "it's product" or "it's engineers" all I can think of is "someone has more business context or knowledge than the others" The bes

Whenever you see one of these "it's product" or "it's engineers" all I can think of is "someone has more business context or knowledge than the others" The best teams I've ever worked on as a product manager/owner is where we have shared context. These problems described here are minimal. In those teams I could provide technical input to engineers, and engineers gave me "consumer facing" suggestions on features. I've believed for a long time that lack of business/use context drives a lot of these issues. Take for instance I currently work at an IoT company, and if I'm working with engineers who have no idea what a thermostat does/how it works other than "makes it hotter or colder" then we have much more difficulty building shared understanding of a feature request. I also know this because 10 years ago that was my simple understanding of a thermostat... so it was much harder for me to understand why we were doing certain things.