You need to know why the client disagreed on your changes and do they expect from the change being done. Listen carefully to understand their concerns to be able to implement what they want. Be sure to find a common ground with their changes and yours.

I’d start by really listening to their concerns to understand where they’re coming from. Then, I’d explain how the changes align with the app’s goals and share any data supporting them. I’d ask for their input and see if there’s a way to find a balance between their feedback and the app’s objectives. I’d also explain any trade-offs between their preferences and the bigger picture. If needed, I’d suggest revisiting the changes together to make sure we’re aligned moving forward.

Navigating disagreements with a key stakeholder requires clear communication and collaboration. Begin by understanding their concerns and the reasoning behind their objections. Present the rationale for the proposed changes, backed by data, user feedback, or alignment with the app's goals. Encourage a constructive dialogue to explore compromises or alternatives that address their concerns while maintaining the project's vision. This balanced approach fosters mutual respect and ensures decisions are made in the app's best interest.

When I have faced this challenge, in particular with a client that had another agency that had hired them and one that had hired the agency above that and then, finally the true original client above that, I reverted to my favorite tactic, which is to use first principles thinking. However, rather than use this for my own benefit, I did it as a method of explaining the rationale and justification for our design changes and walked them through it step by step logically. Wherever possible I have listened and acknowledged their opinions where different, but where I needed to hold my ground I reminded the client about the foundational needs of the client at the top of the flowchart.

When a key stakeholder disagrees with changes to the mobile app, my first step is to listen actively to understand their concerns and the underlying reasons for their objections. I ask open-ended questions to clarify their perspective and demonstrate empathy. I then present data, such as user feedback, analytics, or industry best practices, to justify the changes and explain how they align with the app’s goals. If necessary, I collaborate with the stakeholder to find a compromise that addresses their concerns while still meeting the app's objectives. The key is open communication, transparency, and a willingness to collaborate toward a solution that benefits all parties.

Give the stakeholder space to express their concerns fully. Use open-ended questions to clarify their perspective and demonstrate that you value their input. Share user feedback, analytics, or examples from successful implementations to explain the rationale behind the changes. Ensure your data connects with their concerns.

When disagreements arise with stakeholders, I focus on creating a collaborative and open dialogue. First, I actively listen to their concerns, asking clarifying questions to fully understand their perspective and underlying motivations. I then present data and user insights to show how the proposed changes align with the app's goals and address user needs. If their concerns remain, I work to find a compromise that meets both their priorities and the app’s objectives, offering alternatives where possible. Throughout, I maintain a solution-oriented mindset, ensuring that we can align on a path forward without compromising the app’s vision or the stakeholder’s concerns.