What Is Redirecting Feedback?
Redirecting Feedback is the specific move of naming a behavior that needs to change, explaining its impact, and making an explicit request for the future. It is Rep 4 of the LeaderReps Accountability System, and it is the Rep most likely to be delivered badly when it finally happens.
Redirecting Feedback is not criticism. It is a Rep. Its purpose is behavior change, not release of frustration.
The short answer
Redirecting Feedback is a three-move Rep. Name the observable behavior (Evidence), connect it to impact (Anchor), and make an explicit request for the future (Request). Applied with composure and the Camera Test, delivered close to the event, it is the fastest way to change a behavior on your team without damaging trust.
Want a fast read on your team's accountability? Take the free 3-minute Team Accountability Check for a personalized Accountability Blueprint.
Key takeaways
Redirecting Feedback is one move. Evidence, Anchor, Request.
The Camera Test applies. If a camera could not have captured it, do not say it.
An explicit request is not optional. Without a defined future behavior, the Rep is incomplete.
Never deliver Redirecting Feedback while activated. Composure is required.
Feedback is not complete when you say it. It is complete when the behavior changes.
The three moves
Redirecting Feedback has three parts. Skip any one and the Rep is incomplete.
Evidence. Name the specific, observable behavior. "You interrupted the client twice before they finished speaking."
Anchor. Connect the behavior to impact, results, or the standard. "That made it harder for them to explain the issue fully."
Request. Make the future behavior explicit. "Going forward, let them finish before responding."
Delivered together, in composure, close to the event. That is the whole move.
The Camera Test
The Camera Test is the guardrail on the Evidence move. If a camera pointed at the moment could not have captured what you are about to say, do not say it. This rules out.
Motive claims ("you did not care about the client")
Character claims ("you are unreliable")
Feelings you inferred ("you seemed dismissive")
Say what happened. Interrupting twice. Missing the deadline. Sending the email without the risk section. All Camera Test safe. See what is the camera test for feedback.
Redirecting versus Reinforcing Feedback
Redirecting Feedback. Names a behavior that needs to change. Ends with a Request.
Direct Reinforcing Feedback. Names a behavior you want to continue. Ends with Recognition.
Both use observable, specific language. Both are Reps. They are delivered at separate times, on separate behaviors. Do not sandwich one inside the other.
The four guardrails
Camera Test. Observable behavior only.
Explicit request required. No defined future behavior means no feedback happened.
Composure always. Never deliver while activated.
No mixed messaging. Do not combine with reinforcement. It softens the signal.
Common mistakes
Motive attribution instead of behavior naming.
Skipping the Request. Naming the problem without asking for the change.
Delivering hot. Words land as attack even if technically fine.
Sandwiching with compliments. Softens the signal.
Delivering once and never checking whether the behavior changed.
Frequently asked questions
What is redirecting feedback?
Redirecting Feedback is one of the four Reps of the LeaderReps Accountability System. A direct, composed conversation that names an observable behavior, explains its impact, and makes an explicit request for the future. Three moves. Evidence, Anchor, Request.
How is redirecting feedback different from reinforcing feedback?
Redirecting Feedback names a behavior that needs to change and ends with a Request. Reinforcing Feedback names a behavior you want to continue and ends with Recognition. Both use specific language. They are separate Reps, delivered at separate times, on separate behaviors.
What is the Camera Test?
The Camera Test is a guardrail on the Evidence part of Redirecting Feedback. If a camera pointed at the moment could not have captured what you are about to say, do not say it. It keeps feedback on inspectable behavior and out of motive attribution.
Why is an explicit request required in redirecting feedback?
Because feedback without a defined future behavior is just criticism. Your person walks away knowing what they did wrong but not what to do next time. Without a Request, the Rep is incomplete, and the behavior almost certainly repeats.
Should I use the feedback sandwich for redirecting feedback?
No. Sandwiching correction between compliments softens the signal and dilutes both moves. Recognition and Redirect are separate Reps. Run each clean, at separate times.
For the full framework, see The LeaderReps Accountability System. For the tactical playbook, see how to deliver redirecting feedback.