Developers are pushing back on new IA methodologies. How can you win them over?

When introducing new IA methodologies, resistance often stems not from the change itself but from concerns over workload or disrupting established workflows. Engaging developers by listening to their concerns and acknowledging their expertise is essential. By outlining the tangible benefits—like streamlined navigation or improved user experience—you can show how these changes aren’t just “new” but opportunities to refine their processes. Emphasizing collaboration and demonstrating how these shifts enhance both the project and their day-to-day work can transform hesitation into buy-in, making progress a shared goal.

I'm not sure it's true that developers "fear an increased workload." Developers are rejecting the trope that they work to be "lazy." They make tools to reduce avoidable effort and risk. They seek safety and efficiency. Computers perform repetitive and computational tasks better than people. Developers create tools in code so that people can avoid spending unneeded effort or making dangerous mistakes. Too many project timelines fail to budget for developers creating tools that are safe and easy to use. This leaves tools that are dangerous and difficult: an accident waiting; debt; risk. "Increased workloads" tend not to consider the accumulating debt and lingering risk. Developers fear they will shoulder the debt and risk professionally.

When developers push back on new Information Architecture (IA) methodologies, it's important to approach the situation with understanding and collaboration. To win them over, start by involving them early in the decision-making process. This ensures their concerns are heard, and they feel invested in the change. Clearly communicate the reasons behind the new methodology and how it will address current challenges, making their work easier in the long run. Provide proper training and support to ease the transition. By fostering a collaborative environment and showing the benefits, developers are more likely to embrace the change.

People always want to know "what's in it for them" and I've often found that spending time on this with them uncovers much of the answer. Whilst I've always gone for customer first I think the fast follow is to take the same approach with employees, or in this case developers. Developer centric IA is how it has to feel for them!

To win developers over to new IA methodologies, involve them early in the process, demonstrate clear benefits like improved efficiency or reduced errors, provide comprehensive training, and highlight successful case studies where the methodologies have delivered tangible results.

To win over developers on new IA methodologies, I’d start by listening to their concerns and understanding their perspectives. Then, I’d explain how the new approach improves the overall user experience and can make their work easier in the long run. By sharing real-world examples and showing the benefits with data or case studies, I’d aim to demonstrate the value of the change. Finally, I'd encourage open dialogue, invite their input, and look for ways to collaborate on solutions that work for everyone. It’s about creating buy-in through respect, understanding, and shared goals.

1. Show Existing IA vs New IA Comparison 2. Show Card Sorting Method results from TG 3. Ask if developers still want to use old IA and document their responses with great detail. if step 1 and 2 are done right, the 3rd won't happen and they'll just nod to the new IA. Moral of the story: patiently ask enough why questions and watch/learn something new happen.

To win over developers who are pushing back on new IA methodologies, I start by understanding their concerns and the reasons behind their resistance. I then present the benefits of the new methodologies with clear, data-driven examples showing how they improve user experience and project outcomes. I demonstrate how these methodologies can integrate with existing workflows and address potential technical challenges. I also involve developers early in the process, seeking their input and feedback to ensure the methodologies align with their needs. By fostering collaboration and showing the value of the new approach, I build support and facilitate smoother implementation.

When developers push back against new IA methodologies, it’s often due to concerns about increased workloads or disruptions to established workflows. To address this, start by genuinely listening to their concerns and demonstrating that their expertise is valued. Clearly explain how the new methodology will benefit the project, emphasizing improvements like more efficient navigation structures and enhanced user experience. Highlighting these advantages can help shift their perspective, transforming apprehension into an appreciation for the potential opportunities and improvements.

- Understand Pushback: Identify the root of developers' resistance, often related to workload or workflow disruption. - Listen Actively: Address concerns by showing that their expertise is valued. - Communicate Benefits: Explain how new IA methodologies will enhance project outcomes and daily tasks. - Highlight Advantages: Focus on improvements like efficient navigation and better user experience to shift perspectives. Understanding and addressing concerns while clearly communicating benefits can turn pushback into a collaborative opportunity for enhancing IA methodologies.

Aligned goals are an important condition for every new improvement or change in the team’s work. All new things must be aligned among all teams before the start of implementation, not after. Everyone must understand the main outcomes — this is the top rule for every manager. For example, in the current case, embracing the new IA methodology would influence business goals. It would allow releases to happen much faster — a great outcome for every team involved in that process.

Emphasize how a strong IA foundation contributes to a more maintainable and scalable codebase, making it easier to develop features and address issues quickly. Show how the methodology simplifies the process and reduces friction in daily tasks. By focusing on these practical benefits, you can build a bridge between IA improvements and developers' work, creating a shared vision that underscores the efficiency and long-term impact these changes bring to the project.

Ask your developers about the magnitude of this change. Be clear that the product will need to be able to adapt to new or changing methodologies, and work with them to identify how things should change now and may change in the future. Work with them directly to create a roadmap and define the delivery scopes.

Show developers that new IA methodologies aren't just another process, they're tools that make their work cleaner and faster. It's not about more rules; it's about less chaos in the code.

- Align Objectives: Show how new IA practices enhance the maintainability and scalability of the codebase. - Highlight Benefits: Emphasize that a well-structured IA simplifies feature development and bug fixes. - Create a Shared Vision: Connect IA improvements with practical advantages for developers to foster motivation. By linking IA methodologies to tangible benefits in development, you create a shared vision that encourages developers to embrace these practices.

Remember, you and the developers are on the same team. Great teams are made of people that trust one another and are trustworthy. Ask: "How can we make this well?"

A well-designed training program can make all the difference. Tailor sessions to developers' routines, focusing on practical exercises that relate directly to their tasks. Rather than overwhelming with theory, focus on hands-on applications that show how these methodologies can streamline workflows and improve outcomes. By providing the right knowledge and skills in a way that resonates, you build not just competence but also confidence in using these tools, turning initial hesitation into a proactive approach to new methodologies.

Procedimentos novos a serem implementados em uma determinada organização pode sempre gerar desconforto aos profissionais porque os tira de sua zona de conforto. Mudanças geram resistência, principalmente quando há desconhecimento total sobre o que está sendo implementado. É necessário criar um ambiente favorável no seio dos profissionais para que haja interação com o novo, a curva de Greiner pode ser considerada neste processo de mudança ela é um forte aliado na implementação de novos paradigmas dentro da organização.

Skip the jargon and dive into practical, hands-on sessions that fit their schedule. The easier it is to grasp, the quicker they'll see the value.

Developers want a say in what affects their workflow. Keep the conversation open, tweak based on their feedback, and, most importantly, show them that you’re taking action. It’s about building trust and making them feel heard.