Questions such as “How do you handle feedback from multiple stakeholders?” or “What do you do when two senior people give you conflicting feedback?” come up in interviews for analysts, designers, marketers, project staff, engineers and anyone whose work is reviewed by more than one person. The interviewer is not asking whether you can please everyone. They are asking whether you can collect competing input, decide what to act on, and keep the relationships intact.
This tutorial covers the method first, then shows how to compress it into a two-minute answer.
Why interviewers ask it
Multi-stakeholder feedback exposes three common failure modes: trying to apply every comment and producing something incoherent; siding with the most senior or loudest voice by default; and stalling until someone else decides. Each is expensive in a real project.
Project management bodies treat this as a core skill. The Association for Project Management (APM) lists ten principles of stakeholder engagement, including “Consult, early and often”, “Compromise” and “Understand what success is”. Under the last, APM notes that “Project success means different things to different people.” Conflicting feedback is often just that principle showing up in a review cycle.
The method in five moves
Move 1: Know who the stakeholders are and how much each one matters to this decision
Before reconciling feedback, understand who is giving it. A common tool is the power-interest grid, which the Open University’s OpenLearn course on change management attributes to Mendelow (1991). Nielsen Norman Group’s guide to stakeholder analysis describes the four quadrants: high-power, high-interest stakeholders need to be managed closely; high-power, low-interest stakeholders should be kept satisfied; low-power, high-interest stakeholders should be kept informed; and the low-power, low-interest group can be monitored. The same guide stresses that stakeholder mapping “is not a one-time activity”, because positions shift when, for example, leadership changes.
In interview terms, showing that you thought about who the reviewers were before reacting to their comments signals maturity.
Move 2: Clarify decision rights
Feedback conflicts often persist because nobody has agreed who decides. A RACI matrix (Responsible, Accountable, Consulted, Informed) is one way to settle this. In the University of Oxford’s Focus toolkit version, the Accountable person “is ultimately accountable and has Yes/No/Veto”, the Consulted person needs to “feedback and contribute”, and the toolkit states that there should only ever be one person or role Accountable for a task.
That single rule resolves many feedback disputes. If the legal reviewer is consulted on tone but accountable for compliance, their comment on a disclaimer outranks the marketing lead’s preference; on headline wording, it does not.
Move 3: Consolidate feedback into one log
Scattered comments in emails, chats and meetings are impossible to reconcile. Pull them into one place and sort each item into a category:
- Agreed: several people want the same change.
- Uncontested: one person raised it and nobody objects.
- Conflicting: two or more stakeholders want incompatible things.
- Out of scope: valid, but not for this version.
Most of the log usually turns out to be agreed or uncontested. Applying those quickly builds goodwill and leaves time for the real conflicts.
Move 4: Resolve conflicts against the objective, not the person
For each conflicting item, go back to the agreed goal of the work. Ask what each stakeholder is trying to protect: risk, brand, cost, user experience, a deadline. Often both can be satisfied with a third option. Where they cannot, take the conflict to the accountable person with a short summary of the options and a recommendation, rather than asking them to read the whole thread.
APM’s “Compromise” principle describes starting by establishing the most acceptable baseline across stakeholders’ diverging expectations. In practice, that means proposing a version everyone can live with, then flagging what each party has conceded.
Move 5: Close the loop
Tell every stakeholder what you changed, what you did not, and why. People accept a “no” far more readily when they can see it was considered. This step is the one candidates most often forget to mention, and it is the one that shows you protect relationships for the next round.
A worked example
The following is an illustrative scenario. A business analyst circulates a draft requirements document for a new customer onboarding form. Four stakeholders comment.
| Feedback | From | Category | Resolution |
|---|---|---|---|
| Reduce the form to five fields | Head of sales | Conflicting | Compromise: five fields at sign-up, the rest collected after the first purchase |
| Collect full ID details at sign-up | Compliance lead | Conflicting | Compliance is accountable for regulatory fields; confirmed which are mandatory at sign-up and which can wait |
| Add an Arabic language option | Customer service | Uncontested | Accepted |
| Use the new brand colours | Marketing | Agreed (also raised by sales) | Accepted |
| Integrate with a loyalty app | Head of sales | Out of scope | Logged for the next phase, with reason given |
The analyst applies the agreed and uncontested items immediately, meets sales and compliance together with the list of regulatory fields, proposes the two-stage form, gets sign-off from the accountable product owner, and emails all four stakeholders a summary of decisions. That sequence is the answer the interviewer wants to hear.
Turning the method into a two-minute answer
Use the STAR structure. The National Careers Service describes it as the situation, the task you were given, the action you took, and the result, including what you learned, and advises keeping examples short and to the point. For this question:
- Situation and task (20 seconds): the deliverable, how many stakeholders, what conflicted.
- Action (60 to 80 seconds): pick three of the five moves that you actually used. Do not recite all five as theory.
- Result (20 seconds): sign-off, delivery date, adoption, fewer revision rounds, and what you now do by default.
Illustrative answers
These are illustrative examples written for this guide, not real candidates’ answers.
UX or product design role
“On a checkout redesign, I had feedback from product, engineering, legal and the marketing team, and two pieces directly contradicted each other: marketing wanted an upsell banner on the payment step, and product wanted that step as clean as possible. I put every comment into one tracker and found that most of it was compatible, so I applied those changes first. For the banner, I went back to the project goal, which was reducing drop-off, and suggested testing the banner on the confirmation page instead. The product owner was the decision-maker, so I took both options to her with usability findings from our last round of testing. She chose the confirmation page. I then sent everyone a short note explaining what had changed and why. We had fewer review rounds than on the previous project, and I now start every review with a single tracker and an agreed decision-maker.”
Early-career or internal role
“In my internship I prepared a monthly report that went to three managers, and each wanted different charts at the top. Rather than switching the layout every month, I asked my supervisor who owned the report. She did, so I listed each manager’s request and why they wanted it, and suggested a one-page summary with each manager’s key figure, followed by detailed sections. She approved it and I let the three managers know. The requests for changes dropped off. It taught me to ask who decides before trying to satisfy everyone.”
Variations by role
- Business analysts: emphasise requirements traceability and sign-off. The business analyst resume builder includes sections for stakeholder-facing achievements.
- Designers: emphasise evidence such as usability testing as the tie-breaker. See the UX designer resume builder for portfolio-linked CV layouts.
- Marketing and communications: emphasise brand guidelines and approval workflows.
- Engineering: emphasise technical constraints, written design decisions and trade-off records.
Mistakes that weaken the answer
- Saying you “try to incorporate everyone’s feedback”. It sounds accommodating but implies no judgement.
- Saying you “go with the most senior person”. Seniority and decision rights are not always the same.
- Describing a stakeholder as difficult or unreasonable. Describe what they were trying to protect instead.
- Leaving out the result. Sign-off, delivery or a measurable improvement makes the story credible.
Projects that involved several reviewers are also strong CV material. When you add them, state the number and type of stakeholders and the outcome; a resume builder with achievement-focused bullets can help structure that.
Frequently asked questions
What if there was no clear decision-maker on my project?
Say so, and explain how you created clarity: for example, asking your manager to confirm who would approve the work, or proposing that the sponsor make the final call. Establishing who decides is itself a strong action to describe.
Should I mention frameworks like RACI by name?
Only if you actually used one. Naming a framework you have not applied invites follow-up questions you may not be able to answer. Describing the behaviour (agreeing who decides) is enough.
How is this different from a question about handling criticism?
Criticism questions test how you react emotionally to negative feedback. Multi-stakeholder questions test how you reconcile competing input and decide what to act on. Keep the focus on judgement and process.
What if a senior stakeholder overrode the agreed decision?
That can be a useful example if you handled it professionally: clarify the impact, confirm the change with the accountable person, and update everyone. Avoid framing it as a complaint about the stakeholder.
Sources
- 10 key principles of stakeholder engagement, Association for Project Management (APM)
- Stakeholder Analysis for UX Projects, Nielsen Norman Group
- Hybrid working: change management, section 3.4, The Open University, OpenLearn
- RACI responsibility matrix, University of Oxford, Focus Online Toolkit
- The STAR method, National Careers Service (UK)