What do you do if your boss disagrees with your web design approach?

My standard approach is to first establish a detailed project brief (scope of work) and get it approved by my manager before starting any development. Then, I deliver a Proof of Concept (POC) to validate key functionalities before moving forward with full-scale development.

El objetivo siempre será el norte. En mi experiencia es de vital importancia entender y aprender a comunicarnos, hacer todas las preguntas necesarias antes de comenzar a diseñar, así podemos garantizar el avance del proyecto.

When faced with a boss that does not agree with your approach. Then consider if you have provided a set of options and have demonstrated how they have been successful in the real world. If there is still push back. Then the issue is not the options, but control that is being asserted. If this happens then it’s best to go with the version your boss wants to build trust, then try and weave in some adjustments along the way. Overtime your boss may losen the reigns. It’s always good to know the motivation behind pushback, before pushing an idea too far.

One thing i found helpful to do if your boss does not like your design approach is to firstly listen to their feedback and comment, then revise the goal and what the website is to achieve, align everything together and if need be that you need to explain your approach, do so with some research backup and always value your boss input

El cliente siempre tiene la razón, es casi lo mismo de que el jefe siempre tiene la razón. Sin embargo, es posible que realmente este equivocado. "defender" el diseño, no puede convertirse en una pelea, por que perderás, debes saber escuchar, empatizar y ser persuasivo para que reconozca tu aporte.

As one who is coming from the executive side (not the designer side), recognize that few initiatives get from concept to completion unscathed. Quality creativity may come from emotion not just heartless skill, but if you are going to be effective, you have to get beyond your emotions. Instead of seeing disagreement as rejection or the enemy, discover what are the hot buttons of those pushing back against your design. What appear as sweeping rejections are often one or two key aspects that turned them off. Asking good questions is one of the best ways to get to the bottom of their concern. Ask, "What do you see as the biggest drawback to the present design?" Instead of immediately defending, reply, "Tell me more."

In my experience, conflicts over site design don’t usually come from a lack of communication—they stem from someone feeling unheard. Admittedly, in my early years, I’d mentally prep a rebuttal while stakeholders tried in vain to explain to me what they valued the most. But I’ve learned you get farther by truly listening and even restating what you’ve heard, when it makes sense. This kind of active listening builds trust, reduces resistance, and is especially critical in the design process where priorities and perspectives vary widely. Acknowledgment goes further than argument.

When I have spoken to my boss in the past in regards to a landing page I had designed, he stated that he didn’t like several components of the Figma high fidelity design even after reviewing the low fidelity and wireframes. As a designer, it’s frustrating to hear, but often times it may take seeing the visual of the mock up for someone to truly understand the design. I found it best to put your ego aside as everyone has a different perspective. I listen to the feedback, ask clarifying questions, and make suggestions on what can be improved based off what was being requested. At the end of the day, your boss will have the final say. You can educate them on why certain design aspects were made, but it is our job to bridge that gap.

This is real. Most “design disagreements” with a boss aren’t actually about the design. It’s misalignment on goals, context, or fear of risk. What helped me: - Share the “why” behind the design, not just the design. - Make it feel like a team decision, not a design hill to die on. - When in doubt, test both — let users decide. Design is half visuals, half politics. And that’s okay.

Winning design often comes down to clear, collaborative explanation—not lectures. Present wireframes and IA schematics as conversation starters, not conclusions. Invite questions, share learnings from focus groups, UAT, and past analytics. Use A/B testing to explore unknowns together. When stakeholders feel included in a learning journey, not just handed a solution, you build alignment and uncover stronger design paths as a team.

Recuerda que el que se especializó en tu trabajo fuiste tu, no el jefe, puede tener algunos conocimientos, pero no tiene por que conocer todo lo que tu sabes. Para eso estas tu, para guiarlo y darle algunos tips bien fundamentados para que sume a sus conocimientos y entienda tu punto.

One time at my work, I was asked to create a few designs for social media posting and I really worked hard and prepared it and showed to my boss. He asked me a few changes and I listened him and understood that it was necessary to do so I applied. So, it is that simple. If anyone disagrees with you on any point, it is necessarily on you to understand their opinion and deliver accordingly. That's best to do 👍

É sempre uma questão de equilíbrio. Ouvir os outros, explicar tranquilamente o nosso raciocínio por detrás de cada processo e como atingimos aquela solução. Educar mentes demora, a perceção do design, seja web ou no geral, nem sempre é igual para todos e nada melhor do que ouvir e ser ouvido para chegarmos todos, no caso de uma equipa, à melhor solução possível, sabendo que agradar a todos é impossível e que por vezes as melhores ideias surgem em contextos fora do local de trabalho e quem sabe, muitas vezes de quem nem é da área.

When consensus isn’t possible, be ready to negotiate. While it’s your job to advocate for smart design, sometimes the best path forward is compromise. Focus on the priorities that truly move the needle, and don’t be the person who always has to win. Adopting a collaborative posture earns trust—and over time, that trust often gives you more influence, not less.

El jefe siempre gana, si no hay forma de hacerlo entender, y esta en tus tiempos, no te queda otra que entregarle lo que quiere y esperar que reflexione al ver el resultado. Yo por mi parte suelo hacer dos propuestas, una con lo que el quiere, y una con los ajustes que el se imagina pero mejor enfocados. Nunca descartes su opinión. Siempre buscale la vuelta.

In the digital age, adaptability is everything. Be curious, open, and eager to learn—because online behavior constantly shifts. If you assume you always know best, you’ll find yourself wrong more often than right. Great designers slow down, seek input, and absorb wisdom from others. Conflict will happen—it's inevitable—but it doesn’t have to be feared. When embraced, it becomes a powerful tool to refine and strengthen your work over time.

Lo suyo es intentar hablarlo y entender el porqué de las dos posiciones, que además jerargicamente no están al mismo nivel. Si se jusfican las posiciones y se explican sin ostilidades se pasará de una posible crisis a una oportunidad de mejora