Start with the purpose, not the criticism

Feedback is easier to hear when its purpose is clear. Before raising an issue, ask yourself what you hope will improve. Are you trying to make a shared task smoother, prevent a misunderstanding, or help someone prepare for next time? If you cannot name a useful outcome, you may need more time to sort out your reaction before starting the conversation.

Choose a moment when the other person can pay attention. A quick question such as “Is now a good time to talk about how the meeting went?” gives them some choice, especially if the topic is not urgent. Keep the conversation private when possible, and focus on one issue rather than unloading a list of complaints. You do not need a perfect script; you need a fair starting point.

Describe what you observed

An observation is something the other person could reasonably recognize, even if they remember it differently. “You interrupted me twice while I was explaining the schedule” is more useful than “You never listen.” The first describes a behavior in a particular setting. The second makes a broad judgment about character and invites an argument over the word “never.”

Be as specific as your memory allows without pretending to have recorded every detail. You might say, “During the handover, I noticed the deadline was not mentioned,” or “In the draft, the action items were spread across several paragraphs.” If you are unsure what happened, say so. “I may have missed it, but I did not hear a deadline” leaves room for correction while still raising the concern.

Explain the impact without claiming to know their intent

The impact tells the person why the observation matters. It connects a behavior to its effect on you, the work, or the shared situation. For example: “When the deadline was not mentioned, I was unsure which task to prioritize.” That is more informative than saying the handover was “bad,” and it does not assume the omission was careless.

Use language that reflects what you actually know. You can describe your confusion, extra work, or difficulty contributing; you may not know what the other person meant to do. If an impact is partly your interpretation, make that clear: “I took the pause to mean you wanted to move on, so I stopped asking questions.” This gives them a chance to explain their perspective without erasing yours.

Offer one specific, workable suggestion

A suggestion turns feedback toward the future. It should be small enough to try and closely related to the issue you described. After discussing a handover, you might ask, “Could we put the deadline beside each task next time?” After a meeting, you might say, “Could you let me finish the schedule overview before we take questions?” Both requests identify an action rather than demanding a vague change such as “communicate better.”

A useful suggestion is not always the only solution. The other person may have information you lack or a better way to address the problem. Treat your proposal as a starting point: “Would that work for you, or is there another approach?” If they disagree, return to the shared goal and ask what would help. Feedback can be direct without requiring the other person to accept your exact plan.

Make it a conversation

Once you have shared the observation, impact, and suggestion, pause. Ask how they saw the situation and listen to the answer. You might learn that the deadline changed, that your request was unclear, or that they were managing a constraint you did not see. New context does not necessarily cancel the impact you described, but it can change what a practical next step looks like.

For everyday matters, close with a simple agreement if one is possible: who will do what, and when you will check whether it helped. If the other person is not ready to respond, you can give them time rather than pressing for immediate agreement. Helpful feedback is not a polished speech that guarantees a particular reaction. It is a clear account of what you noticed, why it mattered, and what you would like to try next.

Back to category ↗