Useful feedback gives someone something they can understand and act on. “Be more professional” leaves the listener guessing. A clear description of what happened, why it mattered and what could change creates a much more workable conversation.
You can give feedback as a colleague, manager or project lead without turning every discussion into a performance review. The aim is to improve a piece of work or a shared way of working while leaving room for information you may have missed.
Prepare Before You Start Talking
Write down the issue in one sentence. Is a handover missing important information? Are meetings ending without decisions? Has someone developed a helpful way of explaining a difficult topic? Choose one main point rather than collecting every frustration into a single conversation.
Separate what you observed from what you concluded. You may have seen an unfinished document; you do not automatically know whether the cause was competing priorities, unclear instructions or a technical problem. If you cannot name a concrete example, check the facts before presenting an interpretation as a settled judgment.
Also ask whether the expectation was clear. A teammate cannot reliably follow an unwritten rule they have never encountered. Sometimes the first useful action is agreeing on a standard together.
Use a Short Sequence for the Conversation
Choose a Suitable Moment
Discuss the issue reasonably soon, while you can both remember it. Choose privacy for a sensitive correction and allow enough time for a response. A rushed comment on the way out of a meeting may leave the recipient with questions and no opportunity to ask them.
You might say, “Could we take ten minutes this afternoon to review the client handover?” Name the purpose without creating unnecessary suspense. For remote work, consider a call when tone or context would be difficult to convey in a short message.
If an immediate safety or security problem needs attention, address the immediate risk through the appropriate workplace process. Save the longer developmental discussion for a suitable moment.
Describe the Work You Actually Saw
Locate the example in a specific task, document or interaction. Describe an action rather than assigning a personality label. This makes it easier to check whether you both mean the same thing.
For example, “The draft sent on Tuesday did not include the implementation owner” is more useful than “You never think things through.” The first statement can be checked and corrected. The second invites an argument about character.
Be equally precise when recognizing good work. “Your summary separated the decision from the background information, so I could find the approval request quickly” tells someone what was helpful and worth repeating.
Explain Why It Matters
Connect the observation to a real consequence. Perhaps another person could not complete a task, a decision was delayed or an explanation made a handover easier. Avoid adding dramatic consequences you cannot support.
Keep the scale proportionate. One missing attachment does not establish that someone is unreliable. If there is a recurring pattern, prepare dated examples and explain the pattern without using “always” or “never” as shortcuts.
It also helps to distinguish your own experience from a claim about everyone. Say that you could not locate the decision, rather than claiming the whole team was confused unless you have a sound basis for that statement.
Ask for Their Perspective
Pause after explaining the issue. Ask what was happening from their side, then listen before proposing a solution. You may discover an instruction changed, information was unavailable or you misunderstood the task.
An open question such as “How did you understand the handover requirements?” usually provides more room for explanation than “Why didn’t you follow the process?” Clarify what you heard and correct your account if new information changes it.
Listening does not require abandoning a legitimate concern. It helps you identify the right problem to solve. A missing skill, an unrealistic deadline and a disagreement about responsibility need different responses.
Agree on a Small, Observable Next Step
Translate the conversation into something practical. “Communicate better” is difficult to verify. “Add the decision, owner and due date to the handover summary before sending it” gives both people a shared reference.
Check that the action is possible with the available time, information and authority. A manager may need to resolve competing priorities or provide an example. Peers may need agreement from a project owner rather than assuming they can set each other’s workload.
For a skill gap, connect the action to a personal learning plan. A focused practice task and a chance to review it can be more useful than an instruction to improve everything at once.
Close the Loop
Confirm who will do what and when you will check progress. Keep any written recap short and appropriate for the sensitivity of the conversation. Avoid distributing personal performance details through a shared project channel.
At the follow-up, review the agreed behavior and the result. Recognize progress specifically, and adjust the plan if the obstacle remains. If the issue concerns a formal performance process, follow the organization’s established procedure rather than improvising one through casual messages.
A Worked Example You Can Adapt
Suppose a project update is difficult to use because it describes activity without stating what needs a decision. An illustrative conversation might begin:
“In yesterday’s update, I could see the tasks completed, but I could not find the approval you needed from me. I sent it back for clarification, which added another exchange. How were you expecting me to identify the decision?”
After listening, you might agree that future updates will begin with a short decision request, followed by the supporting detail. The next review can focus on whether the request was clear enough to act on.
This is an example to adapt, not a script to recite. The same approach can apply to a shift handover, design review or shared document. For meeting-related problems, a clear agenda with action items can provide a common place to record the change.
Keep Praise and Correction Clear
Do not make someone decode the main message from a long introduction. If a revision is needed, explain it respectfully and directly. If something worked well, identify it without immediately attaching an unrelated criticism.
You can appreciate someone’s effort while still discussing an unsuccessful result. Be clear about which part needs attention. Likewise, praise should describe a contribution rather than ranking colleagues against one another.
For feedback upward, consider the working relationship and available channels. Focus on a specific interaction and the support you need. If direct discussion feels unsafe or concerns serious misconduct, use an appropriate confidential reporting or support route.
Check Your Message Before Sending It
Before giving feedback, ask yourself:
- Can I identify the task and behavior without guessing at motives?
- Have I explained a consequence I can support?
- Is the expectation relevant and within the person’s control?
- Have I left room for a different account of what happened?
- Is the proposed next step clear enough to review later?
If you would struggle to say the message calmly, draft it privately and remove accusations before starting the conversation. Avoid sending a heated response simply because a messaging tool makes it immediate.
Good feedback does not guarantee agreement. It gives both people a fairer chance to understand the issue and choose a useful action. Start with one specific example, hear the other account and leave with a next step you can both recognize.
