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.

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.

Showing the reasons why that or this technology is best for the business and processo, decrease time for to do some task or make that easier than before

Find common ground. Hold a round table with stakeholders and as many key users as you can realistically. Begin by acknowledging that the change comes with challenges and that they may come across as a pain from the beginning. However, those challenges will become the new norm, and everyone should then be asked to contribute some challenges with the previous process/software. Once you have established the idea that there were challenges before that everyone got used to, have people start calling out things they like about the new platform. This should then begin getting people to agree that, while change is hard, there are benefits and things to be excited about.

To navigate resistance to new software platforms, focus on clear communication, involve key stakeholders early, and highlight the platform's benefits. Offer training, address concerns openly, and encourage collaboration to find common ground.

1. Understand Concerns •Listen to the Team: Ask why they’re hesitant—maybe it’s cost, time to learn, or fear of change. •Find the Root Issue: Are they worried it’ll slow down deadlines or make processes harder? 2. Highlight Benefits for Architects •Show How It Helps: Will it make designing faster, presentations smoother, or models more accurate? •Relate It to Projects: Explain how it can improve key tasks like rendering, BIM modeling, or client presentations. 3. Make Training Easy •Start Small: Run short workshops or give hands-on tutorials with real project examples. 4. Find Champions •Involve Enthusiasts: Get tech-savvy team members to test the software and share their wins. 5. Encourage Open Discussion

Transition to a new software cannot happen in a day, few points that would help here is: 1. Understand the need/benefits from technology, people, process and business strategy perspective. 2. Chalk out the pros and cons 3. Understand and acknowledge resistance. Look through it to decide which are real vs which could be resolved 4. Engage stakeholders early with the above information for decision making 5. Educate and train people on the software. Make it easy and beneficial for them to learn and use it. Once benefits are seen, disagreements reduce. 6. Regular periodic check-ins to ensure the ease of use and sentiments of people using it. If there is anything to fix then fix it.