You finish the presentation. The slides go dark, someone says "thanks, that was great," and the room empties. Your manager passes you in the hallway and says, "Nice job." You nod, smile, and spend the next three days wondering what that actually meant.

Here is the uncomfortable part: you could have found out. You just didn't ask, or you asked in a way that made an honest answer almost impossible.

Most of us treat feedback as something that happens to us. We wait for it, dread it, and then lean on whatever scraps arrive. But the people who improve fastest at work tend to do something quieter. They go get it, and they ask in a way that makes the truth easy to say.

Why we don't ask in the first place

Researchers who study this call it feedback-seeking behavior, and a body of work associated with Susan Ashford and colleagues has described the tension at its center. Feedback is valuable information. It is also a threat. Every time we ask, we weigh two costs: the effort of asking, and the risk to our image. Asking might signal that we're insecure. Worse, it might produce an answer we can't un-hear.

So we do the math in our heads and, often, stay quiet. We tell ourselves the silence means things went fine. It's a comfortable story, and it's usually untested.

The cost compounds. A habit you can't see doesn't get fixed. Maybe you rush the last three slides every time. Maybe you bury the recommendation on page eleven. The people in the room noticed, and nobody said so, because nobody was invited to.

Why "How did I do?" fails

Suppose you do work up the nerve. You catch a colleague afterward and ask, "How did I do?"

Look at the position you've put them in. They are being asked to deliver a verdict on you, face to face, with no preparation, while you watch their expression. Social norms are very clear about what comes next. They'll say "Great!" or "Really solid." Smoothing things over is the kind move, and most people are kind.

The question is too broad to answer honestly and too personal to answer comfortably. It invites a grade, and a grade invites politeness.

There's a second problem. Even when someone does give you a critique, receiving it in the moment is hard. Our defensive reflexes fire quickly. We explain, justify, wince. The person delivering the feedback sees all of that and learns, correctly, not to do it again.

The swap: ask for advice, not feedback

There's a finding worth knowing here. Research from Harvard Business School, led by Leslie John, compared what happens when people ask for feedback versus when they ask for advice. Asking for advice tended to produce input that was more specific and more forward-looking, and the people giving it were less hesitant to be candid.

The reasoning is intuitive once you see it. Feedback is about the past. It looks backward and judges something that already happened and can't be changed. Advice looks forward. It treats you as capable and asks the other person to be a collaborator rather than a critic.

The management coach Marshall Goldsmith popularized a related idea he calls feedforward: instead of asking how you did, you ask for one or two suggestions for how to do it better next time. It's a practitioner's technique more than a lab result, but it rests on the same logic. Nobody has to rate you. They only have to help.

Compare:

  • "How did my presentation go?" invites a grade.
  • "What's one thing you'd change if I were presenting this again next month?" invites a suggestion.

The second question is easier to answer and harder to answer falsely. Everyone can think of one thing. Saying "nothing" feels strangely lazy, so people dig.

Make it specific, make it small

Broad questions get broad answers. The more narrowly you aim, the more useful the response, and the less it feels like an audit of your whole personality.

Somewhere in your head you already know what you're unsure about. Maybe it's whether you went too long. Maybe it's whether the financial section landed. Ask about that.

"I'm trying to get tighter on the opening. Did the first two minutes pull you in, or should I cut straight to the point?" That's a question about one piece of the work, not a referendum on you. It's also a signal: you've already been thinking critically about your own performance, which makes the other person feel safe adding to it.

Pick the right person and the right moment

Not everyone in the room is equally useful. Look for someone who:

  • paid attention (the person who was on their laptop can't help),
  • has a different vantage point than yours, such as someone from another team or someone more senior,
  • is likely to tell you the truth when it's inconvenient.

Timing matters too. Asking in the hallway thirty seconds after you finish catches people before they've formed a thought. A message a few hours later, or a short conversation the next morning, gives them time to reflect. "I'd love your advice on that presentation when you have five minutes" signals that you're ready for something real.

Receiving it: the part that determines whether they'll ever tell you again

How you react to the first honest answer decides whether you ever get a second one.

The goal isn't to agree with everything. It's to make the person feel that telling you was safe. Write it down. Say thank you. Ask one clarifying question if you need to ("Can you give me an example of where it dragged?") and resist the urge to defend. You can decide later what to do with the advice. In the moment, your only job is to receive it.

If you've ever noticed that your manager's feedback dries up after you've bristled at it once, this is why. People protect themselves from our reactions. They also protect us from the truth to spare us.

Your next moves

  • Today: Think of your last presentation or meeting contribution. Write down the one part you're least sure about. That's your question.
  • Within 24 hours: Message one person who was in the room: "I'm working on getting sharper at [specific thing]. What's one thing you'd do differently if you were presenting that?"
  • Before your next presentation: Choose your "feedback partner" in advance and tell them what to watch for. Their attention will be sharper and their answer more useful.
  • When it arrives: Reply with only a thank-you and, at most, one clarifying question. No explanations, no justifications. Save your reaction for later.
  • A week later: Tell the person what you changed. People who see their advice used are far more willing to give it again.

What you were actually missing

The silence after a presentation feels like information, but it isn't. It's an absence, and we fill it with whatever our anxiety suggests. Usually that's either "it went fine" or "it went terribly," and both are guesses.

If you want a place to turn those guesses into something you can learn from, MeetingMortem is built for that. It's a way to look back at a meeting while it's fresh and work out what happened and what to do differently next time, instead of carrying the vague feeling around for days. If that sounds useful, you can find it at meetingmortem.lumenlabs.works.