Se enfrenta al rechazo de proveedores externos a un nuevo diseño de software. ¿Cómo puedes vencer su resistencia?

To overcome vendor pushback on new software design, first, understand their concerns—whether about compatibility, cost, or perceived value. Engage in open dialogue to ensure their input is heard and valued. Highlight the long-term benefits, such as efficiency gains or future-proofing, and show how the new design aligns with mutual goals. Offer support, such as training or resources, to ease the transition. Collaborate on solutions, ensuring they feel like partners in the process rather than obstacles.

You expect resistance to change mostly due to lack of knowledge of big picture or fear of unknown, in additon to disruption to existing path. For example, I had prolonged discussion with one of the vendor on the data needs for their development environment at the end we understood each others point of view and met in the middle. But this requires a open and trusted relationship, which thankfully we developed at the begininnig of the project.

To overcome resistance from external vendors on a new software design, start by understanding their concerns and identifying the root causes of their pushback. Foster open communication, addressing their issues with data-driven insights that demonstrate the value and practicality of the design. Highlight how the new design aligns with mutual goals, such as improving efficiency, user experience, or market competitiveness. Engage them in collaborative problem-solving to find compromises that work for both parties. If necessary, offer phased implementation or additional support to ease the transition and build trust.

Quando você enfrenta resistência de fornecedores externos, é hora de jogar limpo e entrar no happy hour do diálogo. Primeiro, sente com eles e entenda o que está pegando. Pode ser medo de custos, falta de clareza ou receio de impactos nos processos deles. O truque é ouvir mais do que falar, e mostrar que você está no mesmo barco.

To overcome pushback from external vendors on a new software design, start by actively listening to their concerns and understanding their perspective. Schedule a meeting to discuss the proposed design in detail, clarifying the rationale behind your choices and how it aligns with project goals. Provide data or case studies that illustrate the benefits of the new design, showcasing its potential for improved efficiency or user experience. Encourage collaboration by inviting their input and suggestions, making them feel part of the process. Lastly, be open to compromise where feasible, demonstrating flexibility while reinforcing the importance of the design change for overall project success.

You expect resistance to change mostly due to lack of knowledge of big picture or fear of unknown, in additon to disruption to existing path. For example, I had prolonged discussion with one of the vendor on the data needs for their development environment at the end we understood each others point of view and met in the middle.

Explique os benefícios do novo design em uma linguagem acessível, sem aquele monte de jargão. Mostre o que eles ganham na prática, como mais eficiência ou economia de tempo.

There was a case where we kept pushing back to the changes our client was adamant on till we got on a call and understood how our application is fitting in to bigger picture and why those changes are important to the overall process flow .

Às vezes, só falar não resolve, então mostre algo concreto – pode ser um protótipo, números de sucesso ou até exemplos de outras empresas (mas nada de big techs clichês!). Isso ajuda a transformar resistência em parceria.

This requires a open and trusted relationship. If either party is afraid or suspicous of other then they will be working at arm's length, creating doubts in each others' minds. When everyone works as one team , collaboration starts improving. We had a vendor who worked with is on improving our processes to complement product changes we expected. The end result was more efficient system than we initially thought.