To handle disagreements about new software platforms, start open talks to resolve concerns and emphasise benefits. Provide training and resources to aid with the transition. Encourage feedback and consider useful recommendations. Showcase success stories and fast triumphs to boost confidence. Emphasise long-term benefits and connection with corporate objectives. Foster a collaborative environment in which team members feel heard and supported, resulting in a more seamless adoption process.

Acknowledge concerns, facilitate open discussions, demonstrate the software’s benefits, and offer training to build confidence and alignment among stakeholders.

In my experience implementing new software platforms, addressing resistance starts with transparent communication. Begin by involving key stakeholders early, using gamified workshops to align goals and ease concerns. Highlight the platform's benefits with clear data, focusing on efficiency, cost savings, and user-friendly features. Tailor training sessions to different skill levels, incorporating hands-on demonstrations and incentives for early adopters. Foster a culture of feedback, using surveys and open forums to adapt the rollout process. By demonstrating value and maintaining collaboration, it’s possible to turn resistance into advocacy effectively.

Transitioning to a new software is always challenging. As the saying goes 'old habits die hard' but if done strategically it will be alot easier. Here is my approach 1. Formally introduce the software tonthe whole team 2. Start giving easy to bite size lessons to everyone for about 30 min daily. 3. As the team start getting used to it, they will see perks of it. And that's how you achieve it.

Resistance to new software platforms is much like encountering diverse site conditions in architecture—each challenge offers an opportunity to rethink the design approach. When opinions conflict, I treat the dialogue as a conceptual charrette, focusing on the core purpose: enhancing efficiency, creativity, or collaboration. By framing the software’s adoption as a shared design journey, I emphasize flexibility, gradual integration, and the transformative potential it holds for evolving workflows, rather than a disruption to comfort zones.