You’re in the design review. The Figma prototype is on the big screen. You’ve just walked everyone through the new onboarding flow, the culmination of weeks of research and iteration. You take a breath and ask the fatal question: “So… what does everyone think?”
The VP of Sales speaks first. “I don’t love the blue. It doesn’t pop.”
The lead engineer squints. “The whole thing feels a bit clunky to me.”
Someone from marketing chimes in. “Can we add a link to our latest case study on the first screen?”
You leave the meeting an hour later with a notebook full of contradictions. You asked for feedback, but what you got was a collection of personal tastes, vague feelings, and pet-project requests. You got opinions. And opinions are cheap, conflicting, and rarely actionable.
Feedback is different. Feedback is a tool for de-risking a decision. It’s a specific, goal-oriented critique that helps you get closer to the right answer. An opinion is “This feels slow.” Feedback is “Our P75 load time for this component is 1.2 seconds, which is 40% higher than the component it’s replacing. That will impact our conversion goal.”
The problem isn’t your team. It’s your question. You asked an open-ended, opinion-based question, and they obliged. To get real feedback, you have to architect the request.
Frame the Request Around a Goal, Not a Design
Stop asking “Do you like this?” and start asking “Does this solution successfully solve this specific problem for this specific user?”
Before you show a single screen, anchor the room in the objective.
Don’t say: “Here’s the new checkout flow. What do you think?”
Say this instead: “Our goal is to reduce checkout abandonment by 15% for first-time mobile users. They told us in interviews that the current process feels too long and asks for too much information upfront. We believe this new two-step flow addresses that directly. Does this design solve that stated problem?”
This simple reframe forces everyone to put on their problem-solving hat, not their art critic hat. The conversation shifts from subjective preference to objective evaluation against a stated goal.
Give Each Person a Specific Job
A room full of smart people will default to opining on everything. Don’t let them. Give each stakeholder a specific lens through which to view the work. You are the director, and you must assign them their roles.
- To your engineer: “Can you focus on the technical feasibility and potential edge cases? I need you to be our reality check on implementation.”
- To your sales lead: “I need you to wear your ‘customer objection’ hat. What will a prospect say to push back on this? Where is the value proposition unclear?”
- To your legal counsel: “Please focus only on compliance and data privacy risks. Are we exposing ourselves to any issues with the data we’re collecting here?”
- To your support specialist: “You know where users get stuck. What’s the most likely support ticket this new flow will generate?”
By assigning jobs, you prevent the engineer from bikeshedding the button color and the sales lead from questioning the database schema. You get targeted, high-value feedback from the person most qualified to give it.
Ask Constrained Questions to Get Concrete Answers
Open-ended questions invite rambling opinions. Constrained questions demand clear, decisive feedback.
| Instead of This Open Question... | Ask This Constrained Question... |
|---|---|
| "Any feedback on the PRD?" | "What is the single most confusing sentence in this document?" |
| "What do we think of these mockups?" | "Which of these two designs (A or B) more effectively guides the user to the primary call-to-action?" |
| "Is this ready to build?" | "On a scale of 1-10, how confident are you that this will achieve our primary success metric?" |
| "Is the copy clear?" | "If you had to cut 20% of the words from this screen to make it simpler, which ones would you remove?" |
Constraints force trade-offs and reveal priorities.
Translate Opinions into Feedback
Even with perfect framing, opinions will slip through. Someone will inevitably say, “I just don’t like it.” Don’t get defensive. Get curious. Your job is to convert their vague feeling into a specific insight. Use this question:
“Help me connect that feeling to a specific user outcome or business risk.”
- When they say: “This feels clunky.”
- You ask: “I hear you. When you say clunky,
Generated by Reportify AI — Automate your team's status reports, standups, and weekly updates. Try free →