Read a sample: 1. Feedback as a Two-Way Conversation
A manager notices that a project handoff did not go as expected. The receiving team had questions, work paused while people searched for answers, and the manager spent part of the afternoon untangling the details. The next morning, the manager says, “We need to communicate better.”
The employee nods. The meeting ends. Both return to work.
Has useful feedback taken place? Perhaps the employee knows there was a problem. But the manager has not identified what happened, explained which part mattered, or discovered what the employee understood about the handoff. The employee may leave thinking the concern was the timing of a message, the amount of detail in a document, or the choice of people copied on an email.
Now imagine a different opening:
“When the handoff went out yesterday, the document didn’t include the current owner for the open customer questions. The receiving team asked me who was following up, and I couldn’t tell from the document. What was your understanding of what needed to be included?”
The concern is still direct. The difference is that the employee has something concrete to respond to. They might explain that the owner had not yet been assigned, that the template did not call for that information, or that they had overlooked it. The manager can then work with what actually happened rather than guessing.
Feedback is most useful when it creates that kind of exchange. It offers a clear observation, makes room for another perspective, and leads toward a useful next step. The manager brings a point of view, but not necessarily the whole story.
This chapter introduces a simple sequence for doing that: describe, discuss, and agree. It applies when you are recognizing a contribution, addressing a concern, or receiving feedback about your own leadership. Before practicing the sequence, it helps to separate feedback from several activities that can look like it but serve different purposes.
Managers communicate expectations, make decisions, assess performance, solve problems, and express appreciation. These activities often overlap. Naming the purpose of a conversation helps you choose the right approach and helps the other person understand what you need from them.
An instruction tells someone what to do. It may be necessary when the next action is already clear:
“Please send the revised agenda before the meeting.”
That sentence does not need to become a long discussion. The person may still need an opportunity to ask questions or explain a conflict, but the primary purpose is to communicate a direction.
Feedback adds information about an action or its effect:
“The agenda arrived after the meeting started, so the group didn’t have a chance to review the decisions in advance. What got in the way?”
The manager might eventually give the same instruction—send the agenda earlier—but now the conversation can address the conditions that made the previous approach difficult. If the employee was waiting for the manager’s approval, for example, the next step may involve both people.
Instructions are not inferior to feedback. A busy team needs clear direction. The problem comes when a manager assumes a direction alone will resolve a recurring issue without checking whether expectations, resources, or responsibilities are understood.
Evaluation makes a judgment against a standard. A performance review, a hiring decision, or an assessment of whether work meets a requirement may involve evaluation. Managers are often responsible for making those judgments, and a conversation can include both an evaluation and feedback.
Suppose you say, “The proposal does not yet meet the requirement for a complete implementation plan.” That is an evaluation. To make it useful, add the details the person needs: which required elements are missing, why they matter, and what revision or discussion should happen next.
The distinction matters because a judgment by itself can leave someone unsure how to improve. It also matters because a discussion does not necessarily erase the manager’s responsibility to decide. You can listen carefully, consider new information, and still conclude that a requirement has not been met.
Be honest about which parts of a conversation are open to discussion and which are not. Asking “What do you think?” while concealing a decision that has already been made can make the invitation feel misleading. A clearer opening might be: “The deadline is set for Friday. I’d like to discuss what needs to happen to make that possible.”
Venting releases frustration. A manager might say, “I’m tired of having to fix everything at the last minute,” and feel some immediate relief. The employee, however, may hear a broad accusation without knowing what to change.
Your frustration can be useful information for you: it may signal that something needs attention. It is not, by itself, a plan for a productive conversation. Before speaking, identify the event or pattern you can describe and the purpose you want the conversation to serve.
That does not mean hiding every feeling or speaking without warmth. “I was concerned when we couldn’t answer the customer’s question” can be a straightforward account of your reaction. The useful question is whether your words help the other person understand the issue and participate in addressing it, or whether they mainly transfer your frustration to them.
Praise is not a separate universe from feedback. When you tell someone what they did well and why it mattered, you give them information they can use again.
“Great job” may be welcome, but it leaves the contribution unspecified. Compare it…