The Feedback Questions That Actually Get Honest Answers

A useful test is simple: Could someone answer this question in one vague sentence and technically satisfy what I asked?

If the answer is yes, the question probably needs tightening.

Ask About Something the Person Can Actually Observe

The best feedback questions usually refer to something the person has actually seen, experienced, used, or been involved with.

"What's your honest opinion of my career?" is difficult because the responder may only know one small part of your work.

"What was the least convincing part of my presentation?" gives them something they can actually evaluate.

Likewise, "What do you think of my business?" is broad enough to produce almost anything. "What would make you more likely to recommend this to someone else?" gives the responder a specific experience and outcome to consider.

The more directly your question connects to something observable, the less likely you are to receive generic praise.

Ask About Behaviors Instead of Personality

If you're asking for personal feedback, questions about behavior are generally easier to answer honestly than questions about character.

"What's one thing I do in meetings that makes collaboration harder?" is much more useful than "Am I difficult to work with?"

The first asks for an observable behavior. The second asks the person to make a judgment about your personality.

That distinction matters because people are often uncomfortable assigning a negative label to someone they know, even when they're perfectly willing to describe something that person does.

You can learn much more from:

• "Do I interrupt people too often?"

• "Is there anything I do that makes it harder for people to disagree with me?"

• "What could I do to make meetings more productive?"

• "When do I communicate poorly?"

than from:

• "Am I a bad coworker?"

• "Do people dislike me?"

• "Am I annoying?"

The more concrete the question, the more useful the answer tends to become.

Don't Accidentally Ask a Leading Question

Specificity is useful, but there is a difference between a specific question and a question that tells the person what answer you expect.

"Was my presentation too long?" assumes the presentation was too long.

"How did the length of the presentation affect your experience?" leaves room for the answer to be positive, negative, or neutral.

Likewise, "What did you dislike about the proposal?" assumes there was something the person disliked. If you're genuinely trying to learn rather than confirm a suspicion, a better question might be "What worked well, and what would you change about the proposal?"

Good feedback questions narrow the subject without predetermining the conclusion.

Ask for One Thing When You Need One Thing

"Tell me everything that's wrong with this" sounds like an invitation to be thorough, but it can actually make people less likely to respond.

A large question creates a large amount of work.

If you're asking coworkers, customers, friends, followers, or collaborators to give feedback, a question that takes a minute to answer is much easier to complete than one that sounds like an assignment.

Compare:

"What are all the things you would change about this?"

with:

"What's the one change that would improve this most?"

The second question creates a useful constraint. The responder has to prioritize rather than produce a long list.

You can always ask another question afterward.

Use Different Question Types for Different Kinds of Feedback

Not every useful feedback question should be open-ended.

Sometimes you want a simple decision. Sometimes you want a reason. Sometimes you want an unexpected observation.

For example:

Closed question: "Would you recommend this to a friend?"

Follow-up: "What's the main reason for your answer?"

Or:

Rating question: "How clear was the presentation from 1 to 5?"

Follow-up: "What would have moved your rating one point higher?"

The first question gives you something easy to compare. The second gives you the explanation behind it.

This combination can be particularly useful when you're collecting feedback from several people because you can see the broad pattern while still getting the details behind individual responses.

Don't Make Every Question Negative

If every question is about what's wrong, people can start treating the feedback exercise like a criticism session.

That isn't necessarily what you want.

Sometimes the most useful questions are:

• "What should I definitely not change?"

• "What part worked better than you expected?"

• "What would you keep exactly as it is?"

• "What stood out to you in a good way?"

• "What made the biggest difference for you?"

These questions help identify strengths that might otherwise disappear when the focus is entirely on improvement.

Good feedback isn't simply a list of problems. It's information about what to keep, what to change, and what deserves more attention.

Questions for Coworkers and Teammates

If you're asking coworkers for feedback, avoid questions that sound like an informal performance review unless that's genuinely what you need.

Instead of:

"How would you rate my performance?"

try:

"What's one thing I could do differently to make working with me easier?"

Instead of:

"Do you think I'm a good team member?"

try:

"What do I do that helps the team, and what gets in the way?"

Instead of:

"Was my presentation good?"

try:

"What was the least clear part of the presentation?"

These questions are easier to answer because they focus on things the coworker has actually experienced.

If you're specifically trying to get feedback from colleagues without making the relationship awkward, anonymous feedback for coworkers can remove some of the pressure that otherwise causes people to soften their answers.

Questions for Friends and People Who Know You Well

Personal feedback has its own problem: people who care about you may be even more reluctant to say something critical.

Instead of asking:

"What do you think of me?"

try:

"What's something about me you think I don't notice?"

Or:

"What's one habit of mine that you think holds me back?"

Or:

"What do you think I should stop doing?"

Those questions give the person permission to tell you something you may not already know without requiring them to deliver a general verdict on your personality.

Questions for Creators and Small Businesses

If you're a creator, freelancer, founder, or small business owner, broad questions can be especially dangerous because your audience may want to be supportive.

"Do you like my content?" can easily produce a stream of positive but strategically useless answers.

Try asking:

• "What type of post would you like to see more often?"

• "What makes you stop scrolling when you see one of my posts?"

• "What's one thing that makes my content harder to understand?"

• "What would make you more likely to recommend my work?"

• "What's something you expected me to offer that I don't currently offer?"

These questions turn general approval into information you can actually use.

And if you are asking an audience rather than a colleague, remember that your audience may not use the same language you use to describe your own work. Their answers can reveal how people actually experience what you're making, rather than how you intended them to experience it.

Questions for a Specific Decision

Sometimes you don't need general feedback at all. You need help making a decision.

In that case, say so.

Instead of:

"What do you think I should do?"

try:

"If you were in my position, what would make you choose option A over option B?"

Or:

"What's the biggest risk I'm overlooking with this decision?"

Or:

"What information would you want before making this decision?"

These questions are particularly useful because they invite the responder to contribute something beyond approval or disagreement.

You're asking them to identify a factor, risk, or piece of information that might not already be obvious to you.

What If You Don't Know What You're Looking For?

Sometimes you genuinely don't know what the problem is.

That's when a broad question can be useful — but it helps to give it a little structure.

Instead of simply asking "What do you think?", try:

"What was your first reaction, and what stood out to you most?"

This still leaves room for unexpected feedback, but gives the responder two places to start.

Another useful option is:

"What surprised you, confused you, or made you hesitate?"

That question is broad enough to surface things you hadn't considered while still giving the person specific categories to think about.

Ask Questions That Give You Something You Can Act On

The ultimate test of a feedback question isn't whether it produces a long answer.

It's whether the answer helps you decide what to do next.

"What do people think of my website?" might produce twenty responses and still leave you unsure what to change.

"What is the first thing you would improve on the homepage?" gives you something much more actionable.

Likewise, "How am I doing as a manager?" is broad.

"What is one thing I could do in our team meetings that would make them more useful?" gives you a behavior to examine.

Before sending a feedback question, ask yourself:

If someone gives me an honest answer, will I know what to do with it?

If not, make the question more specific.

Ask the Same Question in Different Ways When the Answer Matters

If you're making an important decision, one question may not be enough.

You don't necessarily need to ask the same thing repeatedly. Instead, approach the same underlying issue from different angles.

For example, if you're testing a new product idea, you might ask:

"What would make you hesitate to use this?"

Then:

"What would make you recommend it?"

And finally:

"What would you change before this was ready?"

The answers may overlap, but the differences can be revealing. Something people hesitate about may not be the same thing they would change, and neither may be the same thing that would make them recommend the product.

Ask, Then Actually Leave Room for the Answer

One more thing worth building in: a follow-up prompt or a second, more specific question after the first. Sometimes the honest answer takes a beat to surface, and a single question with no room to elaborate can end the conversation before the real feedback shows up. If you're building an anonymous feedback request for coworkers or collaborators, mixing one specific closed question with one open-ended follow-up tends to get more complete answers than either alone. The same holds if you're a creator asking an audience rather than a colleague, where one well-aimed question tends to beat an open invitation to comment.

The follow-up doesn't have to be complicated.

"Why?" can be useful, but it can also feel abrupt.

Questions like these tend to give people more direction:

• "What makes you say that?"

• "What would you change?"

• "Can you give me an example?"

• "What would have made this better?"

• "What stood out to you most?"

• "Was there anything you expected that was missing?"

The key is not to interrogate the person. Give them one opportunity to go deeper, then let them decide how much detail they want to provide.

Closed Questions and Open Questions Work Better Together

There is a tendency to treat closed questions and open-ended questions as competing approaches.

They aren't.

A closed question is good at establishing a direction. An open question is good at discovering something you didn't think to ask.

For example:

"Would you use this again?"

followed by:

"What is the main reason for your answer?"

The first gives you a clear signal. The second gives you context.

That combination is often stronger than either question by itself.

Don't Ask Five Questions When Two Will Do

There is another easy mistake when trying to make feedback more useful: adding too many questions.

A feedback form with ten thoughtful questions can still produce worse answers than a two-question form if people feel overwhelmed and rush through it.

If you have several things you want to know, decide which ones actually matter.

Ask the question that would change your decision.

Ask the question that could reveal a blind spot.

Ask the question that would tell you what to improve.

Then stop.

More questions don't automatically mean more useful feedback.

Let the Question Match the Relationship

The same question can land very differently depending on who you're asking.

A question you would comfortably send to a customer might sound strange coming from a friend.

A question that works with a close coworker might be too personal for someone you barely know.

Consider what the responder actually knows about you and what they're in a position to evaluate.

The goal isn't to make the question maximally probing. It's to make it appropriate enough that the person can answer honestly.

Anonymous Feedback Doesn't Replace Good Question Design

Anonymity is powerful because it removes one of the biggest reasons people soften feedback: the fear that honesty will affect the relationship.

But anonymity can't fix a question that is vague, leading, overly broad, or difficult to answer.

Think of it as removing friction from the response, not doing the thinking for the responder.

A strong anonymous feedback request therefore has three parts:

A clear subject. What exactly are you asking about?

A focused question. What do you actually want to know?

Room for explanation. If the person has something useful to add, can they explain it?

Get those three things right and anonymity has a much better chance of producing something genuinely useful.

A Simple Formula for Better Feedback Questions

When you're stuck, this formula is usually enough:

Ask about one thing + make the desired answer clear + leave room for a reason.

For example:

"What's the weakest part of this proposal, and why?"

Or:

"What's one thing I could change to make this easier to use?"

Or:

"What would make you more likely to recommend this?"

None of these questions is clever.

That's the point.

Good feedback questions don't need to sound sophisticated. They need to make it easy for another person to tell you something you can actually use.

The Best Feedback Question May Be the One You Almost Don't Want to Ask

The most valuable question is sometimes the one that makes you slightly uncomfortable.

"What's the weakest part?"

"What am I not seeing?"

"What should I stop doing?"

"What would make you say no?"

Those questions can produce answers you don't enjoy hearing.

That's also why they're often more useful than "What do you think?"

If you're genuinely trying to improve something, the goal isn't to collect reassurance. It's to discover information you don't already have.

FAQ

What is the best question to ask for honest feedback?

There isn't one universal question, but "What's one thing I could improve?" is a strong general-purpose option because it is specific, easy to answer, and actionable.

How do I ask for honest feedback without sounding insecure?

Focus the question on the work, behavior, decision, or experience you're asking about rather than asking for a general judgment about yourself. "What could make this better?" usually sounds more constructive than "Is this good?"

Should anonymous feedback questions be open-ended?

Not necessarily. A specific question followed by an optional open-ended explanation often produces better feedback than a completely open-ended prompt.

How many questions should I ask?

As few as you can while still getting the information you need. One strong question is better than five vague ones, and two focused questions can be better than a long questionnaire.

Should I ask for positive and negative feedback?

Usually, yes. Asking what to keep as well as what to change helps you avoid "improvement" that accidentally removes something people already value.

How do I get feedback about something people are reluctant to criticize?

Make the question specific, give people enough context to understand what you're asking, and remove unnecessary social pressure. An anonymous feedback format can help when the main obstacle is concern about how the answer will affect the relationship.

The Goal Is Information, Not Just Answers

A feedback question has done its job when the response tells you something you didn't already know — something you can think about, act on, or use to make a better decision.

That's why the best questions tend to be narrower than the questions people instinctively ask.

Don't ask, "What do you think?"

Ask what you actually want to know.

The difference may be only a few words, but those few words can determine whether you get another "looks good" or finally get the answer you were hoping someone would be honest enough to give you.