Your engineering team is resisting design suggestions. How can you navigate this challenging dynamic?

Product leaders should unite their teams into a cohesive “One Product Team” rather than maintaining separate design, engineering, and operations silos. By involving key tech/engineering members in the design process, they gain insights into customer issues. Simultaneously, designers should understand platform constraints to create feasible, user-friendly solutions. Early discussions about design feasibility prevent conflicts down the road.

Understand engineering team's concerns like feasibility, resource constraints, tech constraints etc. Understand perspectives to uncover underlying issues. This is important to avoid problems in implementation.

Begin by actively listening to your team's concerns and perspectives. Understanding their reservations can shed light on underlying issues or constraints that might not be immediately apparent. This approach demonstrates empathy and shows that you value their expertise and insights. In my experience, setting up dedicated feedback sessions or one-on-one discussions often helps in understanding the root causes of resistance.

Begin by actively listening to their feedback and identifying the root causes of their resistance. Foster open and respectful dialogue to address any technical or practical objections. Collaborate to find common ground and integrate their insights with design goals. Show appreciation for their expertise and highlight how the design aligns with overall project objectives.

Translating user experience goals into technical requirements is essential. While design visions are crucial, practical implementation is equally important. Facilitating conversations where both design and engineering teams discuss alternatives ensures system integrity while satisfying design intentions. This collaborative approach can uncover creative solutions that might be overlooked in isolated discussions. Example - In one project at my recent internship, our design team envisioned an intricate user interface that was not practical to implement due to existing technical constraints. Through collaborative meetings, we were able to simplify design while retaining the core user experience goals, leading to an effective implementation.

Start by fostering open communication to understand their concerns and perspectives. Hold collaborative workshops to align on shared goals and demonstrate the value of design changes. Highlight user feedback and data to support the design recommendations. Encourage mutual respect and empathy between teams, emphasizing the benefits of an integrated approach.

As a product leader, I've faced resistance when integrating new design ideas. Here's how to bridge the gap: - Listen First: Understand engineers' concerns. Example: During a project, our engineers pointed out potential performance issues with a new feature. Listening helped us refine our approach. - Collaborate and Co-Create: Involve engineers early. E.g.: Joint brainstorming sessions led to innovative solutions we all owned. - Show, Don't Just Tell: Use prototypes or live demos. Example: A quick mockup turned skeptics into advocates, minimizing abstract debates. Building mutual respect and shared goals turns resistance into collaboration. #ProductManagement #Leadership #Teamwork

Clearly communicate how the proposed design changes align with broader objectives, such as improving user experience, increasing efficiency, or meeting business goals. When the team sees the direct correlation between their work and these objectives, they are more likely to be open to suggestions. Providing concrete examples of successful past projects where similar design approaches yielded positive results can reinforce this alignment.

Start by facilitating open discussions to understand their concerns and perspectives. Clearly communicate the design rationale and how it supports the overall product goals. Find common ground by aligning the design suggestions with the team's technical objectives and constraints. Encourage collaboration and iterative feedback to refine ideas together.

Balance of design and engineering deliver good product experience. So, it's crucial to consider the engineering team's perspective and feedback, and include them in decision making process. Provide them with the autonomy to find the best technical solutions that align with design goals. This can reduce resistance.

Start by fostering an environment of mutual respect and open communication. Encourage the engineering team to voice their concerns and suggestions, and listen actively. Provide clear rationales for design decisions, backed by data and user feedback. Involve engineers in the design process early on, giving them a sense of ownership and investment.

It's crucial for the PMs/POs in the teams to clearly communicate the business goals of the product to the development teams. This can be done by outlining the projected targets of key product metrics (retention, CSAT, NPS, ARPU, etc.) if the features are implemented. Highlighting the impact of their work will help showcase its value. Additionally, explaining the importance of the feature for the end user and how it benefits them will motivate the team to align their efforts with the desired outcomes.

Sometimes, resistance stems from a lack of understanding of the design rationale or its potential benefits. Take the time to educate your team on the reasoning behind the design suggestions and advocate for their importance. This can involve sharing design principles, usability studies, or industry best practices that support your recommendations. When team members understand the "why" behind the changes, they are more likely to support them.

Start by explaining the rationale behind the design suggestions, highlighting the benefits and alignment with project goals. Facilitate open discussions to address concerns and incorporate engineering feedback. Advocate for the design by demonstrating its value through data or prototypes. Build a collaborative environment where both design and engineering perspectives are valued.

Have engineering teams in the initial design phase for their suggestions, feasibility checks and feedback. For instance, while designing a mobile app, engineers can provide valuable insights on technical feasibility and suggest optimisations for using widgets or evaluate performance for backend connectivity.

- Iterate and Prototype: Use iterative prototyping to quickly test and validate design concepts, incorporating feedback from the engineering team along the way. - Celebrate Successes: Recognize and celebrate successes, both big and small, to build morale and reinforce the benefits of collaborative efforts. - Continuous Improvement: Emphasize a culture of continuous improvement where feedback is welcomed and used to refine designs over time.

When your engineering team resists design suggestions, navigating this challenge requires empathy, communication, and collaboration. Begin by understanding their concerns and perspectives; there might be technical constraints or valid reasons behind their resistance. Arrange a meeting where both designers and engineers can openly discuss their viewpoints. Facilitate a collaborative environment where everyone feels heard and respected. Find common ground by focusing on shared goals, such as user satisfaction and product success. Consider involving a mediator if needed, like a project manager, to ensure productive discussions. Compromise and iterate on the design to address engineering constraints while still meeting design objectives