Useful feedback: separating facts, interpretations and requests

Feedback can be one of the most valuable forms of collaboration, or a conversation that leaves people more defensive than before. The difference rarely depends on sincerity. Saying everything you think isn’t automatically helpful. Feedback becomes useful when it helps someone see a situation, understand its impact, and choose a possible next step. To do this, you need to separate three elements that are often confused: facts, interpretations, and requests.

When these levels are mixed up, a seemingly simple sentence can sound like a judgment on the person. “You’re not trustworthy” contains an interpretation and leaves little room for discussion. “The last two submissions were missed, and we haven’t received an update” describes an observable situation. It doesn’t solve the problem by itself, but it creates a basis for discussion without first having to discuss the identity of the person receiving the feedback.

Start with facts without pretending they are neutral

A fact is something an outsider could observe or verify: a date, a sentence spoken, a missed step, a delivery, a change in behaviour. It doesn’t yet contain the explanation for what happened. This doesn’t mean it’s cold or devoid of emotion. It just means it offers a common starting point, especially when people have interpreted the same situation differently.

To build feedback, it can be useful to answer three questions: What happened? When or in what context? What concrete effect did it have? For example: “During Tuesday’s meeting, when the decision was made before consulting the person who prepared the data, the group had to reopen the topic the next day.” The sentence doesn’t imply intentions. It describes a sequence and makes the impact on the work clearly visible.

Facts aren’t always easy to sort out. In a conflict, the mind tends to gather evidence that confirms a pre-existing interpretation. This is why it’s useful to limit oneself to a few relevant episodes, rather than building a database of errors. Feedback that provides ten examples rarely helps correct behaviour. More often, it communicates that the relationship has been viewed with resentment for a long time. Precision protects the conversation from a spiral of recriminations.

This doesn’t mean that the facts speak for themselves. Even choosing which episodes to cite requires responsibility. It’s helpful to choose those closest to the current problem, those the other person can relate to, and those that can be addressed. Citing an example to humiliate or demonstrate superiority turns feedback into a show of strength. Citing it to make the problem understandable creates the possibility of correction.

The timing is as important as the content. Feedback given in front of others, in the midst of an emergency, or immediately after a tense situation can be difficult to hear, even if it’s well-formulated. When possible, choosing a dedicated time communicates that the relationship deserves attention. If the situation requires immediate intervention, you can name the incident and postpone the broader discussion to a more appropriate time.

State interpretations and turn them into questions

After an incident, an interpretation almost always comes. It’s human. If someone responds late, we might think they’re not prioritizing the project. If someone doesn’t speak much, we might assume they’re not engaged. Interpretation isn’t a mistake to be eliminated. It becomes a problem when it’s presented as if it were the only possible explanation.

A more helpful formulation makes the hypothesis explicit: “When I do not receive updates, I worry that the project is not a priority. Is that a fair interpretation, or am I missing something?” This preserves honesty while opening space for a response. The other person can confirm, correct, add context or reveal a blind spot. It does not make the discussion effortless, but it does make it more truthful.

Questions are also important for the person giving feedback. Before speaking, it’s worth asking yourself: What story am I telling myself about this person? What other explanation could there be? What don’t I know yet? These questions aren’t meant to challenge every perception. They’re meant to prevent an immediate reaction from turning into a judgment.

In a professional context, the distinction is crucial. Saying “you are not being cooperative” can put the other person on the defensive. Saying “we have not received a response within the agreed timeframe for the last three requests, and the team has had to reorganise the work” makes it possible to discuss the process. Perhaps the workload is not sustainable, responsibilities are unclear or there is a difficulty that has not been mentioned. Feedback can support a diagnosis instead of assigning definitive blame.

Being asked a question does not mean having to produce an immediate, satisfactory answer. A person may say: I need to think about it; I want to reconstruct the episode more carefully; I had not noticed this effect. This, too, is collaboration. Feedback works when both people can remain in the discussion without immediately having to choose between defence and surrender.

End with a request that can be acted on

Feedback remains incomplete if it doesn’t lead to a request. Not a generic request like “be more attentive” or “communicate better,” but an observable change. For example: “When you anticipate a delay, can you let me know by the morning with a new estimate?” or “In meetings, can we leave two minutes to hear from the person who prepared the material before making a decision?” A workable request states what could change and leaves room for a real response.

A good request is not a disguised order. It takes the other person’s circumstances into account and remains open to negotiation. The proposed solution may not be possible, while the underlying need remains valid. In that case, the conversation can seek another route. This step distinguishes feedback from criticism. Criticism stops in the past; feedback seeks a practical agreement for the future.

It is also helpful to agree on how the change will be reviewed. There is no need for continuous monitoring. It may be enough to return to the subject after a few weeks and ask whether the new practice has helped. This check-in protects both parties: the person who received the feedback knows that their effort will be noticed; the person who gave it does not have to leave the problem open in silence and wait for it to resolve itself.

When feedback is received, a useful response can begin with a summary: if I understand correctly, you observed this fact and this was its effect. Repeating the message back does not mean accepting every interpretation. It shows that the message has been heard. The person can then add their point of view, propose a solution or ask for clarification. The conversation stops being a duel and becomes joint work on the problem.

Not all feedback will lead to full agreement. Sometimes a difference in priorities will emerge, along with a non-negotiable responsibility or a choice that requires a boundary. Even in these cases, speaking from facts, stated hypotheses and clear requests makes the disagreement easier to understand. It does not guarantee that everyone will be satisfied, but it prevents the conflict from turning into a confused judgement of individuals.

We asked Alessandro Garau, CEO of Vision to Value: “Useful feedback does not tell a person who they are. It shows them the effect they are having and opens a choice about what they can do next.” Clarity is not the same as harshness. It can be a form of respect when it restores a person’s ability to understand and act.

For more information about Alessandro Garau and the perspectives developed by Vision to Value, explore the project pages and the articles on vision, coaching and strategic marketing.

Subscribe to the Vision to Value Letter to receive new articles and a considered selection of tools, ideas and books that help turn direction into practical decisions.