The design team is pushing for change during ideation. How will you convince the engineering team to pivot?

The focus of any engineering / development is to achieve an objective / metrics; and engineering team is one of the team (like sales, marketing, ops etc) who helps achieve org goals. Here, the objective on an organization level is to inc. Revenue Key pointers to be discussed w/ engineering team 1. Driving what to build comes from customer need / pain point (and not building a superior product which is unwanted in the market). 2. Hence, in the meeting as a PM, I should explain my findings of Customer/Pain point research . If required, deep dive into explaining how / what of my analysis and how you arrived at the conclusion.

Vision is first and foremost thing to be evaluated properly. It is pivtol for both management and employees. It is based on continuous improvement in product quality. The improvement may be on cost, machinery,introduce new technology and major replacement for new design. The real care is tagged when forecast technical support is provided to business as early birds are hatched to gain fame and brand. The customers friendly products will be most appreciated.

Always open your bucket mouth to listen everyone without who is saying is the higher one or the lower one just have the capacity to listen then it would be easier to digest everything or it from higher authorities or from design section or from your labor side

When design proposes changes, data becomes our common language. I'd gather user feedback, A/B test results, and market trends supporting the design team's proposal. Then, I'd present this data alongside potential technical challenges and benefits to the engineering team. It's crucial to frame the pivot as an opportunity for innovation, not a critique of previous work. By focusing on data and shared goals, we can turn potential conflict into collaborative problem-solving.

It is imperative to consider the design teams ideas as this could help engineers to bring in new features and solutions that are more use friendly by analysis of pros and cons.

In the world of asset management, the roles are slightly different but the principles are the same. Product developers have to balance the goals and concerns of two essential teams: the investment team and the distribution team. And although the overall goals of the teams are the same, the incentives are different. In mediating these situations, product developers need to internalize the concerns and goals of each party and then chart a path forward by making an independent assessment that also relies on original analysis of data. This is the essence of product development.

Convincing the engineering team to pivot during ideation requires a strategic approach that respects their perspective and expertise. Here are some ways- 1. Present clear data and evidence 2. Collaborative approach 3. Address feasibility concerns 4. Prototype and test 5. Leadership support By combining evidence-based arguments with a collaborative and respectful approach, you can increase the likelihood of gaining the engineering team's support for a pivot during the ideation phase.