Workplace Communication
You Receive Vague or Unfair-Sounding Feedback: Ask for Examples and Choose a Next Step
Completed fictional peer dialogue and followup record distinguish accepted behavioral corrections, missing expectations and unresolved labels across two later reviews.
When feedback sounds vague or unfair, ask for a particular situation, the behavior the person noticed, its effect, and what they wanted instead. Repeat back what you understood before choosing a response. You can acknowledge someone's experience, change a specific behavior, and still disagree with a broader label about your attitude or ability.
Aim to leave with a fair next step and an accurate record of any disagreement. This LandOffer.ai guide covers ordinary feedback between people who are continuing to work together. Its dialogue and follow-up record are entirely fictional. They are not a performance-rating appeal, a disciplinary response, or a report of an actual employee conversation.

Pause long enough to understand the request
“You need to be more collaborative” can mean several things: a missed handoff, an interrupted discussion, an unclear decision, or a preference the speaker has not explained. Do not choose a remedy before finding out which problem they mean. Equally, do not assume that an awkwardly delivered comment contains nothing useful.
MIT Human Resources' coaching guidance advises recipients to seek behavioral examples, check their understanding, consider other feedback, and allow time to process a response. It also recognizes that someone can appreciate the feedback without agreeing or taking the suggested action. That supports a considered response rather than instant compliance.
If you cannot listen well in the moment, request a specific return time: “I want to understand this. Could we talk privately at 14:00 after I review the handoff?” Avoid announcing a pause and then disappearing. A short acknowledgement can recognize the effort involved without stating that the judgment is correct.
Check the purpose as well as the content. A peer may be offering a preference, while a manager may be communicating a work expectation. If that is unclear, ask whether this is a suggestion to consider or an expectation that needs clarification with the relevant owner. The speaker's role matters; it does not make a vague description more specific.
This method assumes an ordinary collaboration discussion. If the situation is a formal process or a concern requiring another organizational route, use the relevant process and support rather than treating a conversational script as a substitute. This article does not determine whether conduct or a complaint meets any policy or legal threshold.
Ask for an example without turning it into a trial
The Management Center's receiving-feedback guidance encourages a pause, questions about behavior and impact, and a repeat-back. It cautions against making questions feel like a demand that the other person prove a case. It also describes several possible responses, including changing behavior or exploring the feedback further.
Begin with a recent situation the person can describe. Ask what you said or did, where the work was happening, and what they experienced as a result. A feeling or impression is information about that person's experience; it is not automatically a verified account of everyone else's experience or your intention.
Then ask what the colleague wanted you to do differently in that situation. “What would have helped at that point?” is more actionable than agreeing to “be better.” You may discover that the expected behavior was never shared. That can create work for both people: you clarify your handoff, and the colleague makes a deadline or decision request explicit.
The Center for Creative Leadership's active-listening article, published September 1, 2026, recommends clarifying ambiguity and summarizing the speaker's perspective before moving into problem-solving. Use that sequence to check meaning, not to imitate a prescribed personality or promise a relationship outcome.
Keep the inquiry proportionate. One useful example may support one change; it does not establish a permanent pattern. If the person cannot recall an example, ask them to flag the next occurrence privately. Record the comment as unresolved instead of generating your own supposed evidence or canvassing colleagues for votes against the speaker.
A completed conversation: separate the handoff from the label
In this fictional case, software engineer Mira and product designer Anton are preparing internal documentation for a permissions-settings panel. On April 8, Anton tells Mira, “You are dismissive in reviews and keep blocking design.” Neither person manages the other. The conversation concerns their current working arrangement, not a formal rating.
Mira: “I want to understand the part I can change. Can you walk me through one review where you experienced that?”
Anton: “At Monday's review, you wrote that the design was not ready. I had already asked the team to choose the wording. I felt the conversation stopped.”
Mira: “Was that the April 6 document comment about the reset option, or something I said in the meeting?”
Anton: “The comment. It just said, ‘Not ready: reset behavior unclear.’ I could not tell which wording decision you needed.”
Mira: “So my comment did not explain what was missing or how you could move it forward. You experienced that as stopping the decision. Have I understood?”
Anton: “Yes. And you did not approve the wording before the meeting ended.”
Mira: “I agree that my comment was too broad. My concern was whether Reset would restore the team's default settings or the last saved personal settings. Those lead to different descriptions. I was not asking for the wording to be abandoned. What would a helpful comment have looked like?”
Anton: “Name that choice and say which answer you need. I can check it with the product owner. I also want a reply by the review deadline.”
Mira: “I can write the two possible meanings and the question. I did not see a deadline in the document or invitation. Where was it agreed?”
Anton: “I had assumed the end of the meeting. I did not put that in the request.”
Mira: “Then I accept the unclear-comment point. I do not agree that withholding wording approval before the behavior was decided establishes that I was blocking design. Can we ask Priya, the product owner, to confirm the intended behavior, and put an explicit response time on the next review?”
Anton: “Yes to the question and deadline. I still think your tone was dismissive. I don't have another example in front of me.”
Mira: “I hear that the comment landed that way. I will make the question and requested action clearer. I am not agreeing to the broader label. If another comment has that effect, please point to it privately so we can discuss it while the context is available.”
The conversation resolves an actionable handoff problem while leaving a disagreement visible. Mira does not deny Anton's reported frustration, claim to know his motives, or concede a missed deadline that was never communicated. Anton's agreement to a clearer review process does not establish that he withdrew the tone concern.
Priya has not yet answered the product question. The dialogue therefore creates a request for the decision owner; it does not silently assign that authority to either Mira or Anton.
Choose a response that matches what is known
Sort the feedback into parts before deciding what to do. A concrete observation may justify a change even when its accompanying explanation is disputed. Conversely, agreeing that a colleague felt frustrated does not require endorsing their conclusion about your character.
| Feedback from the example | What the conversation establishes | Chosen response |
|---|---|---|
| The April 6 comment gave no precise question or next action | Mira accepts the text was too broad; Anton explains the resulting uncertainty | Rewrite it as the two reset meanings and a question for Priya |
| Mira missed the review deadline | Anton says he assumed meeting-end; no explicit deadline had been shared | Add a response time to the next request; do not record a proven missed commitment |
| Mira was blocking design | Mira had an unresolved behavior question; Anton experienced a stalled decision | Keep the product question open for Priya; disagreement about the label remains |
| Mira is generally dismissive | One example and Anton's experience have been discussed; no further example is available | Recognize the reported impact and invite a timely specific example; do not claim a confirmed pattern |
This is partial acceptance with reasons. Partial acceptance still carries the commitments each person made. Mira still owes the clearer question she agreed to write. Anton still owes an explicit deadline in the next request. The product owner still owns the behavior decision.
When the expectation comes from your manager, clarify its scope and priority rather than treating disagreement as permission to disregard it. Ask how success will be observed and what existing work should change if the request needs time. If the feedback remains unclear and affects your work, a proportionate next step may be a bounded discussion with the appropriate manager about expectations, rather than escalating an accusation about the speaker's motives.

Follow up with commitments and an honest mixed result
A short follow-up can prevent the conversation from being remembered as either total agreement or total rejection. Keep it with the relevant work, in a channel appropriate for the people involved. Do not forward a private discussion broadly just to establish that you have a record.
Here is Mira's completed fictional April 8 follow-up, addressed only to Anton:
“Thanks for discussing the April 6 review. I understand that my ‘not ready’ comment left you without a clear question or next action. I will replace it today with the two reset meanings and ask Priya which behavior is intended. That will be a product question, not an approval of either behavior.
“For the next review, you will include a response deadline and the decision requested. I will reply by that agreed time with an answer or a specific unresolved question and the owner needed. We agreed to inspect the next two review exchanges on April 22.
“We have not agreed on the broader description ‘blocking design.’ Your concern about the comment's tone also remains open; please flag a specific future example privately. I will make questions and requested actions clearer while retaining technical concerns that still need a decision. Please correct anything I have summarized inaccurately.”
Sending that note would not by itself establish Anton's agreement. In the fictional record, Anton replies on April 9 that the commitments and unresolved points are accurately summarized. Priya separately confirms on April 10 that Reset restores the team defaults; only then can Mira assess wording against that decision.
At the April 22 check-in, they inspect the two planned exchanges rather than declaring the relationship repaired:
| Review checked | Observation in the fictional record | Disposition |
|---|---|---|
| April 13 help-text review | Anton included a deadline and decision question; Mira identified one specific term, its impact and the needed revision before the deadline | Both regard this exchange as clearer; retain the format |
| April 17 confirmation-dialog review | Anton included the deadline; Mira responded on time but wrote “still confusing” without naming the confusing sentence | Mira accepts the recurrence and replaces it with the sentence, alternative interpretation and question |
| Broader tone concern | Anton says the second comment still felt dismissive; no agreement is reached about the general label | Keep the disagreement explicit; discuss the next specific occurrence rather than record the concern as solved |
The mixed result matters. One improved exchange does not erase the second weak comment, and the second comment does not prove every earlier criticism. For the next review, Mira will check each critical comment for the exact sentence, competing interpretation and needed answer; Anton agrees to flag any unclear comment promptly. They set no claim about long-term improvement beyond the two exchanges they inspected.
End with a bounded next step
You do not need to settle someone's full view of you to improve one piece of work. Leave the conversation knowing which behavior you will change, which expectation needs an owner, what remains disputed, and when the limited change will be reviewed. If no example is available, say what you can and cannot infer from the comment.
For your next ordinary feedback conversation, choose one recent example and write a brief record with the observation, reported effect, expected alternative, agreed action, and unresolved interpretation. Ask the other person to confirm or correct the summary, and keep their response status visible until they do. Return to LandOffer.ai for further workplace guides.
Sources and Further Reading
- MIT Human Resources: Ongoing Coaching and Feedback — asking for behavior examples, processing and responding to feedback.
- The Management Center: How to Receive Feedback, Part 1 — clarification, repeat-back and deciding on a response.
- Center for Creative Leadership: Active Listening Techniques — clarifying and summarizing before problem-solving; published September 1, 2026.


