I highly advocate for an Incremental Adoption strategy when integrating new methodologies into your team's culture. ? Start with small, low-risk changes Example: Introduce daily stand-ups for one project team ? Pilot new methods on a single project Example: Apply Agile methodology to a 4-week sprint for a minor feature update ? Offer training and support during transition Example: Provide a 2-day workshop on Scrum basics, followed by weekly Q&A sessions ? Celebrate early wins to build momentum Example: Highlight a 20% reduction in bug reports after implementing code reviews

I would start by communicating the “why” of the needed change using examples, data and various types of evidence. I would also articulate the intended impact of the change and any associated risks and benefits. I would allow the team to absorb this and comment, contribute to optimizing the change. I would not assume that the team will simply adopt a change because it comes top down. I would allow them to understand and subscribe to the benefits of the change and the intended impact. Then, I’d allow them to critique the proposed implementation and take part in the crafting an improved one. By getting the team to be aware and to engage in defining the implementation there is a better chance of success.

What is the goal of a team? Is it a particular methodology? It is being "a culture open to change?" Methodology is less important to me than results. Is a team delivering value, frequently, at a sustainable pace? If no, observe, make changes, the usual. Are you getting healthy results? Can you do better at getting those results (assume the answer is yes, you might not know how.) Do you need ideas on things to try? Great, sample a methodology. Mix & match. But to me, if a team isn't attempting to reduce feedback time, deliver value / validated learning, the method is irrelevant. Methods are training wheels. So I am not bothered by resistance to being told how to do things. Maybe the culture isn't open to being told what to do.

Fostering change starts with leading by example—demonstrating adaptability and enthusiasm. I’ve found success in involving the team early in the process, gathering their input to address concerns and make them feel part of the change. Clear communication, regular check-ins, and celebrating progress go a long way in building trust and excitement for new methodologies.

The main reasons for resistance to adopting new methodologies often stem from previous negative experiences and fear of failure. To overcome this resistance, it is important to encourage your team to experiment with new approaches. We organize a meeting every Friday to have fun, learn new things, and discuss whether these innovations can benefit our projects. Additionally, senior team members should develop proof of concepts (POCs) to demonstrate improvements and facilitate a gradual transition to the new methodologies.