You Asked for Feedback. You Got a Wishlist.

You just walked your team through the quarterly roadmap. It’s tight. The strategy is sound, the problem is clear, and the proposed solutions are backed by research. You feel good about it. You get to the end of the presentation, take a breath, and ask the fatal question: “Any feedback?”

The first hand goes up. It’s the head of sales. “This looks great. Could we also add a CSV export to that new dashboard? A few big clients have been asking for it.”

Before you can answer, marketing chimes in. “Love the focus on activation. While we’re in that part of the app, can we add a field to capture the user’s job title? It would really help our segmentation.”

Suddenly, the air is thick with ideas. Good ideas, mostly. But they aren’t feedback on your plan. They’re a different plan entirely. Your focused, strategic proposal is now buried under a pile of feature requests. The meeting ends, and you’re left with a list of nice-to-haves, a diluted strategy, and no actual critique of your original proposal.

The problem wasn’t the audience. The problem was your question. “Feedback” is a dangerously vague word. When you ask for it without constraints, you invite a wishlist. People default to additive thinking—what else can be done? You didn’t ask them to find the flaws in your logic, you invited them to an open mic night for their pet features.

To get useful input, you must stop asking for “feedback” and start asking better, more specific questions.

Frame the Goal, Not Just the Features

Before you ask for a single comment, anchor the room. Don’t just show them a list of features. Reiterate the single most important objective and the primary constraint.

Start the conversation with something like this: “Our primary goal for Q2 is to reduce churn by 15% among new users. We have to accomplish this with our current team of four engineers. Everything on this plan is designed to hit that specific goal within that constraint.”

This simple framing changes the entire dynamic. It builds a fence around the conversation. Now, a suggestion isn’t just a good idea; it has to be a better idea for hitting the stated goal within the given constraints. The CSV export for sales? A valid request, but it has nothing to do with new user churn. It can be acknowledged and put in the backlog for later.

Ask “What’s the Biggest Risk?”

Instead of the open-ended “What do you think?”, replace it with a question that forces critical, rather than creative, thinking. My favorite is: “What is the biggest risk with this plan?”

This question shifts the focus from what’s missing to what might fail. It prompts your stakeholders to act as partners in de-risking the plan, not just customers with a shopping list.

Other sharp questions include:

• “If this plan failed, what would be the most likely reason?”
• “Which of our assumptions feels the shakiest to you?”
• “What have we overlooked?”

These questions don’t invite a wishlist. They invite scrutiny. They invite genuine critique that will make your plan stronger.

Make the Trade-Offs Explicit

A strategy isn’t just what you decide to do; it’s what you decide not to do. Make those trade-offs the centerpiece of your conversation. Use an "even over" statement to make the choice clear.

For example: “We are choosing to build a guided in-app tour for new users even over adding more customization options for power users this quarter. Do we agree that this is the right trade-off to reduce churn?”

This forces a focused debate on a specific strategic choice. Instead of a sprawling discussion about every possible feature, you are having a high-level conversation about priorities. Anyone who disagrees must argue why the other side of the trade-off is more important for achieving the goal.

Validate and Park Off-Topic Ideas

When someone inevitably offers an idea that’s out of scope, don’t shut them down. Dismissing their thought makes them feel unheard and defensive. Instead, validate the idea and consciously move it to a different space.

You can say: “That’s a great point about improving the reporting for power users. It’s not directly tied to our new-user churn goal for this quarter, so I’m adding it to our ‘Parking Lot’ doc to review during our next planning cycle. For now, let’s get back to the churn plan.”

This simple act of writing it down shows you value the input, but maintains the focus of the meeting. You’ve acknowledged their contribution without letting it derail the conversation.

The quality of the feedback you get is a direct reflection of the quality of your questions. Asking for “feedback” is lazy. It’s an invitation for scope creep and wishful thinking. If you want to pressure-test your strategy, you need to be disciplined. Frame the goal, ask about risks, and force a conversation about trade-offs. You won’t get a wishlist. You’ll get the insights you actually need.