How can you handle resistance to new project management software?

In my opinion, this should be very aligned with organizational maturity and portfolio and project management. See, there is no point in implementing a robust tool, if team and leadership are not highly mature. It's like a ladder, it structures the basics, you can start with a spreadsheet and a well-structured Power BI Dashboard. As soon as the organization and the team involved become more mature, you will have a greater opportunity to implement something more structured, for instance, Oracle PPM and Clarity PPM softwares.

Conducting a thorough assessment of the current situation, you'll gain valuable insights into the underlying reasons behind the resistance, identify potential obstacles to adoption, and develop targeted strategies to address them proactively. This comprehensive understanding will enable you to lay a solid foundation for a smoother transition and successful implementation of the new project management software. By proactively addressing resistance and concerns, you can increase user buy-in, minimize disruptions, and maximize the benefits of the new technology.

Before evaluating any specific PPM solution, you should conduct an "as-is" and "to-be" business process mapping exercise. It's crucial to clearly identify the root cause of existing problems or opportunities. Oftentimes, issues with business process workflows are mistakenly attributed to the current management system's features and capabilities. Once you have a technology-independent understanding of the desired "to-be" process, you can begin evaluating PPM solutions to see which ones best align with your business needs. In some cases, a strong PPM system may prompt you to modify your "to-be" process, but it's important to define that process before reviewing potential solutions.

💡 In my experience, resistance often stems from a lack of clarity or fear of the unknown. 🔍 Clear Objectives Ensure user comprehension of the switch's purpose. Strategic alignment fosters support. 🚀 Training & Support Offer thorough training. Confidence reduces resistance to the new system. 🔗 Feedback Mechanisms Establish user feedback channels. Swiftly addressing concerns boosts acceptance. 🌟 Quick Wins Showcase Highlight early successes. Real-time benefits gain user buy-in and momentum. 📌 Effective communication, training, and showing tangible benefits can mitigate resistance significantly.

Siempre debemos involucrar y comunicar a las partes interesadas. Es importante antes de realizar cambios obtener feedback y analizar la situación actual, para en etapas posteriores compartir cuales son los pro y contras del cambio. Siempre trabajar en pro de la consecución de los objetivos, teniendo en cuenta la cultura organizacional y su forma de trabajo.

This is one of the main points to successfully implement a new tool or software. You must show case the real benefit that it could bring to the organization and measure it during and after the implementation. Don’t forget to register all the steps, share the success through the organization and celebrate with your team!🎉

The organization should assign a PM to communicate and inspire the change, follow the respective metholodogy and manage "manual" approvals in the software transition. It is meaningful to involve stakeholders and assign them some small tasks such as tests and surveys to keep them motivated. 10 years ago, when I was working in Hewlett Packard, we migrated from Oracle to SAP, we had a great Project Manager that showed us the benefits of time reduction in purchase orders creation, spare parts buying, planning tasks, invoicing and increasing customer satisfaction. He involved us in tests, regular meetings and some colaborators became super users and mentors. Undoubtly, there were some errors but after some months later SAP was amazing.

Resistance to new PPM software might actually be a blessing in disguise, as it reveals underlying inefficiencies or gaps in the processes that may have gone unnoticed. Instead of viewing resistance as a hurdle, take it as an opportunity to bring improvements. 1. Conduct root-cause analysis sessions: before jumping into solutions, organize a brainstorming session with the resisting team members to understand their concerns. 2. Consider adopting the new software in parallel, only to add some new functionalities: this provides a safety net, allowing users to gradually transition without the fear of losing control. 3. Celebrate Small Wins: as teams start using the new software, highlight and celebrate small successes and milestones.

Turn resistance into assistance! Address concerns, highlight benefits, and guide the way for a seamless shift to your new PPM software.

El trabajo de la elección del software es de todas las partes, tecnología y áreas del negocio. No es necesario adaptar a la organización al software, sino que el software tiene que ser lo bastante flexible y sencillo para adaptarse a las metodologías de trabajo y procesos existentes en la actualidad y con visión a futuro que impliquen cambios bajo el concepto de mejora contínua.

Turn the old one off. I think software should be weeded out. Like wardrobes. One new piece in, two have to go. End of life software starts to cost more than it saves. Anything marketed appropriately can have a great uptake. Just don’t let technical folks up in front of a crowd. You need to abstract away the complexity.