Every idea matters, the approach should be to listen to everyone and try to align their views with the final goal. The team needs to understand the final goal and have to respect others points of view too. We need to guide them to understand what is Plus and minus points in their views. And finally together we can agree on a common way of design to complete the project.

Demonstrate the current design and then outline the impact of design modifications. Make sure to have prep meetings before a final review. Ensure the business stakeholders and development team's inputs are completely baked into the plan after you whet them. You are not going to get anything done without their buy in. Break things down into smaller topics to be managed and ensure an open forum for all to discuss

1. Encourage open communication and discussion with your team regarding the change. 2. Check the necessity of this change ? 3. Do a SWOT Analysis against this change with your team. 4. Identify the Pros & Cons of this change and explain the same to your team as well. So that they will prepare themselves for this movement.

What I've found helpful is to encourage the team to empathize with each other in choosing a design that is desirable for the user, economically viable from a business perspective, and technologically feasible. In addition, the four pillars of design thinking helps in any decision making steps - * Understand by asking people * Explore by finding patterns * Prototype by making tangible * Evaluate by iterating