1. Focus on the User 2. Set Clear Priorities 3. Collaborative Roadmap Planning 4. Compromise with Data-Driven Decisions 5. Foster a Collaborative Culture

À mon sens, la seule et unique réponse à apporter à cette problématique n'est pas de savoir qui des chefs de produits ou des ingénieurs à raison MAIS ce que nos clients attendent et souhaitent de notre application. Il faut penser client avant tout. Le client et l'expérience client doivent être au centre des préoccupations de l'entreprise (cf Amazon qui excelle dans ce domaine).

Busque alinhar os objetivos de negócio com as limitações técnicas, promovendo conversas claras e regulares entre os times. Traduza prioridades em valor para ambos os lados.

Product engineering tools like Posthog should be the first go-to for ingesting actual user data from production products. Someone with experience in building sophisticated dashboards should bring these insights to a shared group of product and engineering. This group should look hard at the data to overcome innate biases. I've found that engineers often over-prioritize fun and easy problems, and product over-prioritizes the needs of politically connected or especially loud users over the majority.

back to basics: we don't build product neither for product manager neither for engineers. we build product for users and we only build what they want to solve their problem. A good tip, is to put the teams in the shoes of an entrepreneur who's long term existence depends on product market fit. No market no product. No users request no product features (unless an enabler for user need)