Feedback (and Other Dirty Words): Three Roles, Three Fs

Key Ideas

1. Use growth as the purpose and focus as the boundary

The authors’ definition makes development the purpose of feedback, while focus is one of its quality tests. In this guide’s application, ask what the person could understand or do differently after the exchange. If the answer is unclear, the comment may need a narrower subject or a different kind of conversation.

In the original training-session example, saying that the presenter needs more presence gives them little to work with. Describing how participants responded when the new process was introduced identifies a more useful area. The question becomes whether listeners could recognize the situation in which to use the process. That can lead to a concrete change in the next session, such as explaining a contrasting case before demonstrating the steps.

Before sharing a comment, write the work situation, the observation and the learning opportunity you see. Keep one exchange small enough that the person can examine it. This matters because unloading every frustration at once can bury the useful information and make a reply feel like a defense of the person’s whole competence. A focused discussion also makes disagreement easier to investigate. The presenter can ask which part caused confusion and compare the observer’s account with their own. You are then discussing a particular event with potential for improvement, rather than trying to settle a global verdict about the person.

2. Become a seeker by asking for information someone can notice

Chandler’s author article recommends a targeted request made in advance, input from different perspectives and attention to strengths as well as problems. The seeker role helps shape the conditions under which useful information can be collected. It does not require knowing the answer before asking or selecting only people who will reassure you.

Before the training session, ask one observer to notice when the audience starts asking which cases belong in the new process. Ask another to watch whether the example makes the distinction clearer. These are different viewpoints on the same learning goal. They are more workable than a request to judge everything about your presentation. Give the observers time to understand the request and decline if they cannot attend to it.

Choose a question about behavior or audience experience that could inform your next attempt. Include what worked: a successful explanation is useful information you can preserve. This matters because improvement is not only the removal of faults; it also involves understanding the choices that already help. After receiving the observations, explain what you learned and what you plan to test. If accounts differ, ask about the situations each person noticed rather than holding a vote on your competence. The request creates an opportunity to learn from several positions, with enough specificity that each contribution can be understood in context.

3. Give the receiver role time before choosing a response

The licensed receiving preview emphasizes taking information in and making a thoughtful choice about the response. Receiving is therefore a distinct activity, even when you initiated the request. You can be interested in learning and still feel the urge to explain yourself before you know what the observer actually noticed.

After the training session, an observer says that several participants looked confused during the example. Your immediate explanation may be that they had not read the preparation material. Before offering it, ask which moment they noticed and what happened next. You may discover that a phrase you used referred to two different things. You may also find that the observer inferred confusion from silence and has no clearer evidence. Both possibilities are useful to distinguish.

Summarize the information you received, including the uncertainty, before deciding what it means. This matters because listening does not oblige you to treat every interpretation as fact. You can appreciate the effort, ask for detail and then assess what is relevant. If you need time, say when you will return to the question. Choose an experiment proportionate to the evidence, such as revising one explanation and asking whether the decision becomes clearer. The receiver’s work is to understand and evaluate the information well enough to make a considered choice, rather than either surrender immediately to the judgment or reject it before examination.

4. Extend observations fairly and let the person examine them

The extender role belongs to anyone sharing information, including peers and people responding to a request. Fairness is a useful test of that contribution. In this guide’s exercise, separate the event you observed from the meaning you assigned to it, and make the basis of the comment available for discussion.

Suppose you watched the training session and noticed three questions about when the process should be used. You can describe those questions and identify the point at which they arose. Saying that the presenter never understands the audience goes well beyond the observation. It also hides the information that could help them revise the session. If there were moments of clarity, include those examples because they are part of the account, not because every critical comment requires a compliment.

Check whether your information serves the development purpose you named. If you are primarily trying to vent, win a disagreement or display expertise, reconsider the comment before presenting it as feedback. This matters because the label alone does not establish helpful intent or accuracy. State what you can support, acknowledge what you could not observe and invite the person’s context. Their explanation may change your interpretation. A fair exchange can still include difficult information, but it gives the receiver something specific to examine and a chance to participate in understanding what happened.

5. Make frequency support learning and trust

Frequency is the third F, and the book treats trust as an important foundation. An ordinary learning rhythm can provide more chances to use information than a distant retrospective. The practical question is whether each exchange adds something useful and whether the participants can rely on how the information will be handled.

For the training example, agree to revisit one revision after the next session. The observer can report whether participants now identify the intended use case, and the presenter can explain what they changed. That makes the next exchange connected to an actual attempt. Repeating an old complaint after every meeting would be frequent, but it would not create the same learning opportunity.

Set a cadence appropriate to the work rather than demanding constant comments. Ask what kind of observation is welcome and respect commitments about where it will be discussed. This matters because trust can be weakened if a private development conversation unexpectedly becomes public criticism. Follow up when you promised, and explain what happened to the suggestion even if you chose a different adjustment. Over several attempts, examine whether the exchange is becoming clearer and more usable. Useful repetition includes noticing a change that worked, revising a mistaken interpretation and deciding that a question has been answered. Feedback should help the work develop, not become an endless evaluation of the person doing it.