Resolve conflicting stakeholder feedback on a design
Sorts contradictory feedback from different stakeholders into the real underlying concerns, options, and a reply that moves to a decision.
The prompt
Help me deal with conflicting feedback on my design.
The design and its goal: [WHAT IT IS, WHO IT IS FOR, SUCCESS METRIC]
Feedback received, by person: [NAME OR ROLE - THEIR FEEDBACK, VERBATIM IF POSSIBLE]
Who owns the final decision: [ROLE, OR "unclear"]
Deadline: [WHEN THIS MUST BE SETTLED]
Evidence I have: [RESEARCH, DATA, PATTERNS - or "none"]
Steps:
1. For each piece of feedback, identify the concern behind it (e.g. "make the logo bigger" may mean "brand is not recognizable"). Mark which are about user outcomes, business risk, technical cost, or preference.
2. Show where the feedback truly conflicts and where it can all be satisfied with one change.
3. Give 2-3 design options that address the underlying concerns, with trade-offs.
4. Suggest the cheapest way to settle any remaining disagreement with evidence (quick test, data pull, precedent) instead of opinion.
5. Draft a short message to the group that summarizes concerns fairly, presents the options, recommends one, and names who decides by when.
Tone: neutral and respectful of each stakeholder. Do not take sides by name.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- WHAT IT IS, WHO IT IS FOR, SUCCESS METRIC
- NAME OR ROLE - THEIR FEEDBACK, VERBATIM IF POSSIBLE
- ROLE, OR "unclear"
- WHEN THIS MUST BE SETTLED
- RESEARCH, DATA, PATTERNS - or "none"
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a design decision record for a key choiceDocuments a design decision with context, options considered, evidence, trade-offs, and reasons, so the team stops reopening it.
- Turn research insights into problem statements and How Might We questionsConverts research findings into sharp problem statements and well-scoped How Might We questions ready for an ideation session.
- Turn a vague stakeholder request into a clear problem statementA one-page problem brief that separates the ask from the underlying need, before anyone commits to a solution.
- Prioritize a product roadmap or backlogScores and orders features with a transparent model (RICE, value vs. effort) and builds a roadmap.