Feed Forward: Why Looking Ahead Beats Looking Back for Team Performance

Why Traditional Feedback Fails

Let me describe a scene you have experienced. A manager sits down with a direct report for a "feedback conversation." The manager opens a document with notes from the past quarter. They go through what went wrong. The employee gets defensive. The manager gets frustrated. Both leave the meeting feeling worse than when they started.

This is the feedback ritual that plays out millions of times every year in tech companies around the world. And it is almost entirely useless.

Research backs this up. A meta-analysis published in the Journal of Applied Psychology found that one-third of all feedback interventions actually decreased performance. Not just failed to improve it — actively made it worse.

Why? Because traditional feedback has three fundamental problems:

Problem 1: It focuses on the past, which cannot be changed. Telling someone what they did wrong three months ago gives them no actionable path forward. They cannot undo the past. They can only feel bad about it.

Problem 2: It triggers defensiveness. Neuroscience research shows that critical feedback activates the amygdala — the brain's threat detection system. Once someone is in "fight or flight" mode, they cannot process constructive information. They are too busy protecting their ego.

Problem 3: It is filtered through the giver's biases. Feedback says as much about the giver as the receiver. Research on performance reviews shows that 62% of the variance in ratings reflects the rater's biases, not the ratee's performance. This is called the "idiosyncratic rater effect."

Enter Feed Forward

Marshall Goldsmith — the world's top executive coach, who has coached 200+ CEOs — developed Feed Forward as an alternative to traditional feedback.

The core idea is simple: instead of telling people what they did wrong in the past, give them suggestions for what they can do better in the future.

The shift from feedback to Feed Forward involves four changes:

The Feed Forward Process

Here is how a Feed Forward conversation works:

Step 1: The person picks one behavior they want to improve. Not a weakness someone else identified — a behavior they personally want to get better at.

Example: "I want to get better at communicating technical decisions to non-technical stakeholders."

Step 2: They ask a colleague (not necessarily their manager) for two specific suggestions for the future.

Example: "What are two things I could do in the future to communicate technical decisions more clearly to non-technical stakeholders?"

Step 3: The colleague provides two forward-looking suggestions. No references to the past. No judgment. Just ideas.

Example:

• "You could start each technical update with a one-sentence business impact summary before diving into the technical details."
• "You could create a one-page visual decision tree that shows options and trade-offs in simple terms."

Step 4: The person listens, takes notes, says "thank you," and moves on. No debate. No defense. Just gratitude and consideration.

That is it. No performance ratings. No documentation. No HR forms. Just a future-focused exchange of ideas.

Why Feed Forward Works Better Than Feedback

Goldsmith has run the Feed Forward exercise with over 50,000 people. He asks participants to try both feedback and Feed Forward and then rate their experience. The results are overwhelming:

• People prefer receiving Feed Forward over feedback by a ratio of greater than 10 to 1
• People find Feed Forward more useful for changing behavior
• Feed Forward conversations are faster (2-3 minutes vs. 30-60 minutes for feedback)
• Feed Forward produces less defensiveness and more openness to change

The reasons are psychological:

Reason 1: We can change the future but not the past. Feed Forward gives people actionable ideas for tomorrow. Feedback gives them regret about yesterday. The human brain is wired to engage more with what it can control.

Reason 2: Feed Forward is not personal. When someone says "here is what you did wrong," it feels like an attack on identity. When someone says "here is an idea for the future," it feels like a gift. Same information, different framing, completely different emotional response.

Reason 3: Anyone can give Feed Forward. You do not need to be someone's manager to give Feed Forward. A junior engineer can give Feed Forward to a CTO. A designer can give Feed Forward to an engineer. This democratizes improvement.

Reason 4: Feed Forward scales. You can get Feed Forward from ten people in 30 minutes. Getting feedback from ten people takes hours of scheduled meetings, and the emotional toll is enormous.

Implementing Feed Forward in Tech Teams

The Weekly Feed Forward Round

Replace your weekly one-on-one feedback conversations with a Feed Forward round. Here is how:

Format: 15 minutes in each one-on-one Frequency: Weekly or bi-weekly Structure:

1. The team member shares one behavior they want to improve this week (2 minutes)
2. The manager offers 2 Feed Forward suggestions (3 minutes)
3. The team member shares one behavior they think the manager could improve (2 minutes)
4. The team member offers 2 Feed Forward suggestions to the manager (3 minutes)
5. Both agree on one small experiment to try this week (5 minutes)

Notice the reciprocity. Feed Forward is not top-down. The manager asks for Feed Forward too. This builds trust and models the behavior.

The Sprint Retrospective Feed Forward

Replace the "what went wrong" section of your sprint retro with a Feed Forward section:

Instead of: "What went wrong this sprint?" Ask: "What is one thing we could do differently next sprint to improve?"

Instead of: "Who dropped the ball?" Ask: "What suggestion does anyone have for how we can handle similar situations better next time?"

Instead of: "Why did we miss the deadline?" Ask: "If we face a similar timeline pressure next sprint, what two things could we do to increase our chances of hitting the target?"

The Code Review Feed Forward

Code reviews are a natural place for Feed Forward. Instead of only pointing out what is wrong with the code, add forward-looking suggestions:

Traditional code review comment: "This function is too complex. It has a cyclomatic complexity of 15."

Feed Forward code review comment: "For functions like this in the future, you might try extracting the validation logic into a separate function and using early returns — it would bring the complexity down and make it easier for others to review."

Same information. But the second version gives the developer a specific, actionable technique they can use in all future code, not just this PR.

The Peer Feed Forward Exchange

Once a quarter, run a Peer Feed Forward Exchange:

1. Each team member writes down one behavior they want to improve
2. They pair up with three different colleagues (5 minutes each)
3. In each pair, they share their behavior and receive two Feed Forward suggestions
4. After all three conversations, they write down the top 3 suggestions they plan to try
5. They share their top 3 with the team (optional but powerful)

This exercise takes 30 minutes and generates more actionable improvement ideas than a quarterly performance review.

Feed Forward for Technical Leadership

Feed Forward is especially powerful for technical leaders — CTOs, VPs of Engineering, Tech Leads — because they rarely receive honest feedback. The higher you go, the less truthful people are with you.

Areas where technical leaders benefit most from Feed Forward:

• Communication: "What could I do to communicate our technical strategy more clearly?"
• Decision-making: "What could I do to make architecture decisions that the team feels more bought into?"
• Delegation: "What could I do to delegate more effectively so I am not a bottleneck?"
• Meetings: "What could I do to make our team meetings more productive?"
• Hiring: "What could I do in interviews to better assess candidates' real capabilities?"

The key: Ask for Feed Forward from people at every level, not just your peers. Your most junior engineer often has the most valuable perspective on your leadership — because they experience it most directly.

Common Objections to Feed Forward

Objection: "But sometimes people need to hear what they did wrong."

True. Feed Forward does not replace accountability. If someone made a serious mistake, address it directly. But for ongoing development and improvement — which is 90% of what feedback conversations are about — Feed Forward is more effective.

Objection: "This sounds too soft. Our culture is direct."

Feed Forward is not soft. It is specific, actionable, and forward-looking. "In the future, try X" is more direct than "in the past, you failed at Y" — because it tells people exactly what to do, not just what they did wrong.

Objection: "People will just avoid addressing real issues."

The opposite happens. Because Feed Forward feels safer, people are more willing to address real issues. It is easier to say "here is a suggestion for improvement" than "here is what is wrong with you." The same issues get surfaced — with less defensiveness and more action.

How Hyperion Consulting Uses Feed Forward

At Hyperion Consulting, we integrate Feed Forward into our leadership coaching and team development programs. We help technical leaders build Feed Forward cultures where continuous improvement is the norm, not the exception.

Our coaching approach focuses on:

• Identifying the 1-2 behaviors that will have the biggest impact on your leadership effectiveness
• Building a Feed Forward network of trusted colleagues who provide ongoing suggestions
• Creating team rituals that embed Feed Forward into daily workflows
• Measuring behavior change over time — not just satisfaction scores

Ready to replace broken feedback with Feed Forward? Book a free consultation to discuss how we can help your team.