Few ways to manage conflicting opinions in system architecture are - All the contributor should be in sync with the system architecture design process - Let the contributor have say in case of conflict to try and explore their thought process by running a parallel pilot project - All opinions matter just need to funnel them at the right place in systems engineering

An architecture is a means to an end, enabling the business to achieve their strategic outcomes. Therefore, architecture goals should align with the business strategic outcomes. Business success and IT's alignment in achieving that generally helps drive consensus between teams and leadership. Once this is achieved, an architect needs to focus on defining: 1. The measures of success 2. Leading and lagging metrics for the architecture goals and business outcomes 3. Architecture guiding principles, policies and patterns for implementation teams to progress autonomously 4. Automated cross functional tests that ensure that architecture qualities are being met 5. An operating model that drives continuous alignment and continuous improvement.

Try to understand the mindset of the contributors to the architecture. Some prefer to 'reuse' the previous patterns and practices while some try to simplify things further every time an opportunity arises. Arrive at 'better' options with discussions, so that all can know the reasons behind a choice. Seek simplicity.

When opinions clash on system architecture, I focus on finding common ground. Aligning on the core goals—whether it’s scalability, performance, or security—helps everyone see the bigger picture. In one project, I facilitated a workshop where each team member presented their view, which helped surface key priorities and concerns. This structured dialogue allowed us to build consensus while valuing individual input. If things remain deadlocked, I’ve found that bringing in an external expert can help. Their fresh perspective often cuts through the noise, offering unbiased insights that lead to a balanced solution without compromising the project's long-term goals.