Wie gehen Sie mit einem Stakeholder um, der auf eine bestimmte Funktion drängt, obwohl das Feedback der Benutzer etwas anderes vermuten lässt?

Translating impact of the feature in terms of business impact or metrics that matter to the stakeholder helps in such a scenario. If impact assessed is low, we may not have got hold of the issue well enough, or in as much detail.

Even if you disagree with what stakeholders said, you should at least send a note thanking them for taking the time to share their thoughts. The goal is to make the stakeholders feel heard. That way, you'll be able to keep them engaged so that you can continue to get their feedback later on.

Steven Covey once said “Seek first to understand, then to be understood.” This captures the essence of engaging with stakeholders who are adamant about a specific feature. Actively listening and uncovering the motivations but outcomes desired behind their request is the goal. Use the process of questioning to lay a foundation of genuine interest, empathy and to build trust and mutual respect. This approach doesn’t just facilitate better communication—it opens the door to finding solutions that align with both business who are adamant about a specific feature. Sometimes multiple paths exist to deliver customer outcomes.

Approach the situation with openness and collaboration! Start by asking questions like, "When this feature is released, what will be different?" to clarify the objective. Consider if there's overlap and if possible, find a balanced solution addressing both perspectives. Gather insights by collecting product analytics and additional data for a comprehensive understanding. Prepare your pitch by integrating the stakeholder's request with user feedback or create two separate pitches, each supported by insights. When presenting, maintain a collaborative mindset. This isn't about winning an argument; it's an opportunity to demonstrate your product thinking and communication skills. Aim to reach a consensus benefiting users and the business.

Hot take: Using data to prove a case goes both ways. Stakeholders need to understand this too and come prepared with more than just a hunch.

"Data tells, but stories sell." Presenting user feedback to stakeholders requires more than just sharing numbers—you need to craft a compelling narrative. Armed with quantitative data and qualitative insights, you can show why a requested feature might not align with user needs. Visual aids like graphs and user journey maps help illustrate your points, but the true impact comes from weaving these insights into a story that resonates. By connecting data to the stakeholder’s goals and the broader product vision, you guide them toward prioritizing user-centric decisions and steering the conversation toward a beneficial outcome for all.

Para manejar a una parte interesada que insiste en añadir una característica específica, es crucial usar datos. Recuerdo un caso en el que directivos pidieron incluir funcionalidades que, aunque interesantes, complicarían el uso del producto para más del 60% de los usuarios. Por otro lado, casi el 90% de los usuarios solicitaban mejoras en un proceso específico. Presenté gráficos y mapas del recorrido del usuario para mostrar cómo optimizar este proceso resolvería problemas más urgentes. Al proponer priorizar esta mejora y luego considerar otras funciones, alineé las decisiones con las necesidades reales de los usuarios, mejorando la experiencia y demostrando competencia en la gestión de proyectos basada en datos.

When a stakeholder pushes for a feature that contradicts user feedback, presenting data is crucial. Start by showcasing quantitative data from surveys or analytics that highlight user behavior and preferences. Complement this with qualitative insights from user interviews or usability tests to add depth to your findings. Use visual aids like graphs or user journey maps to illustrate key points, making it easier for the stakeholder to see the bigger picture. By connecting the dots between the data and the product's goals, you can guide the conversation towards decisions that best serve the users and the product's success.

In presenting data to stakeholders, it is important to maintain simplicity by using short labels, colours, and scales to label all visuals and exclude whatever may lead to confusion. Define your purpose before you start presenting stakeholder feedback, you need to have a clear purpose and objective for your communication. You may also highlight significant points through notes or call outs to draw attention to key insights.

I was designing the GUI for a Malibu surf boat and ran into this problem. My client wanted to offer flexibility to easily and quickly change between functions. The way they were recommending introduced ambiguity to new users and unnecessary steps to familiar users. I built out simple prototypes of their solution along with alternatives that corrected the issues. There were trade-offs for each one but they were able to let their idea go once they saw and understood the issues it created. From my experience, people who envision a solution have a hard time seeing the problems with it, so you have to show them. Focus on the desired outcome. Design their idea. Designs alternatives. Go over the pros and cons.

When a stakeholder pushes for a feature that contradicts user feedback, it’s crucial to offer alternatives that balance both perspectives. Instead of outright rejecting the idea, propose solutions that align with user needs while still addressing the stakeholder’s goals. For example, if the intent is to boost engagement, suggest enhancements that improve usability or add value in a way users appreciate. By refining the idea, you demonstrate a commitment to collaboration and a shared objective, ensuring the product evolves in a way that satisfies both business goals and user expectations.

Cuando una parte interesada insiste en una característica específica que los comentarios de los usuarios no respaldan, reviso los datos y propongo alternativas que mejor se alineen con las necesidades del usuario. Presento opciones que mantienen el objetivo de la característica original pero que también incorporan el feedback recibido. Esto muestra mi compromiso con la satisfacción del usuario final y con los objetivos del proyecto, permitiendo encontrar un equilibrio que beneficie a ambas partes.

A lot of times, stakeholders that are adamant about their product feature are looking at a deadline and or a short term win. In many instances they can get their way if they wait, it just won't be immediate. Invite them to a mini strategy session that shows how their perspective will eventually roll into features further down the line, while the greater team works towards fulfilling more immediate impacts and current customer demands. This will allow the stakeholder to feel heard, and better understand the needs of the greater project. Most importantly they will see that their features are projected to make an impact, albeit a little further down the line.

This is the most interesting part, as a product owner you need to find a path that both fits the user and the request at the same time! Often it involves reimagining the solution altogether and sometimes is meeting the requirement somewhere in the middle. This is also the part where knowing more technical stuff helps you to offer a solution which can satisfy both parties midway.

Stakeholder engagement helps organizations to proactively consider the needs and desires of anyone who has a stake in their organization, which can foster connections, trust, confidence, and buy-in for your organization's key initiatives. Stakeholder alignment is the process of ensuring that the interests, goals, and expectations of all relevant stakeholders are aligned with the organization's mission and objectives.

I approach a stakeholder pushing for a specific feature against user feedback with a strategic and collaborative mindset. I start by aligning with the stakeholder on our shared objectives and emphasizing the importance of user-centric design. I present clear, data-driven insights from user feedback to illustrate why the proposed feature might not meet current user needs effectively. I then explore potential compromises, such as testing the feature in a limited scope or integrating it in a future release. Engaging the stakeholder in this dialogue ensures we balance their vision with user needs, fostering alignment and maintaining focus on our product’s success.

When a stakeholder insists on a feature despite user feedback to the contrary, it's crucial to align their goals with the broader objectives of the product. Start by emphasizing that the ultimate aim is market success, customer satisfaction, and ROI—goals that benefit everyone. Highlight how focusing on user needs leads to a more successful product, which in turn fulfills these shared goals. By framing the conversation around common objectives, you can guide stakeholders to see that prioritizing user feedback is essential not just for users, but for the long-term success of the product and the business.

Revisão de Impacto é primordial. Se o cliente é uma parte interessada chave, proponha uma revisão do impacto que o recurso pode ter no produto, incluindo um pequeno experimento ou teste. Isso pode mostrar concretamente como o recurso se alinha (ou não) com os objetivos gerais do produto. Outra sugestão também é manter a documentação e acompanhamento registrando a solicitação e o motivo pelo qual não será implementada no momento, mantendo uma trilha de feedbacks e decisões. Isso demonstra que a solicitação foi considerada cuidadosamente e caso não tenha sido, pode servir de insumo para manutenção ou descontinuidade da parceria.

Once there is a conflicting issue regarding the feature, revisiting the issue, the what and the why helps the search for how to solve the problem and the discussion. Review the objectives and expected outcomes with the proposed solutions. This will certainly lead to a better understanding and alignment of the best option.

In situations like this, I believe in clear communication as Clear communication in this situation means using data-driven insights to show the stakeholder why the feature may not align with user needs. I begin by presenting data-driven insights from user feedback, demonstrating why the requested feature might not align with user needs. I then transparently explain the product development process, timelines, constraints, and associated risks. I believe by grounding the discussion in concrete data and clear explanations,helps the stakeholder understand the broader implications of their request, facilitating informed decision-making that aligns with both business goals and user needs.

You can't lose your cool or ignore stakeholders pushing for misaligned features. Instead, communicate with the team clearly, explaining why you're heading in a particular direction and how this strategy benefits the product overall. If other features align better with customer data, use that as a solid reason to move forward. Prioritizing logically among competing interests leads to product improvements. It's crucial to handle this process transparently across teams. The team will feel more confident when everything is communicated clearly and openly. No surprises, no drama.

By clearly articulating user feedback and its implications, you can align the stakeholder's expectations with the needs and preferences of the actual users. This helps in making sure that decisions are based on evidence rather than opinions. Effective communication involves presenting user feedback data and research findings in a structured manner. This evidence helps justify why certain features may be prioritized or deprioritized. Open discussions about the rationale behind user feedback can foster mutual understanding. It helps stakeholders grasp why the feature they are advocating for may not align with current user needs.

Clear communication is crucial when managing stakeholder expectations, especially when they push for a feature that contradicts user feedback. Transparency about the product development process, including timelines, constraints, and the impact of feature changes, is essential. Explain the risks of ignoring user feedback, such as increased costs, delays, or poor adoption. Presenting a clear, honest assessment helps stakeholders understand the implications of their requests, leading to more informed decisions and aligning everyone toward the product's success.

Humans are driven by social relationship and communication is the heart in this case. Clear communication, politely, based on facts and respecting assumptions (they are part of the game), avoiding feeding conflicts and the collision routes, pragmatisms with flexibility, confidence on argumentation and making decisions are key elements of leadership.

The point is relevant. It highlights the importance of post-discussion follow-up in product development. By documenting decisions and sharing them with stakeholders, you ensure everyone is aligned, reducing the chances of misunderstandings or unnecessary backtracking. This practice also helps build trust and maintain open communication, which are essential for effective collaboration and decision-making throughout the product development process.

Product development is a learning journey and it is important to communicate, confirm and follow-up on what has been learned and how that is being applied to the product or development process. It is not only important for the stakeholder, or future users/customers, but also for the departments involved like engineering and manufacturing to ensure the final product will be useable, makeable, and profitable.