Skip to main content
Version: 2.0

Continuous Feedback

For two decades, I've seen engineering teams thrive and struggle, and one thing consistently separates the high-performing groups from the rest: a culture of ongoing feedback. It's not about eliminating performance reviews (those have their place!), but supplementing them with regular, informal conversations. As engineering managers, we often get bogged down in roadmaps, sprints, and technical details. But neglecting the human element – regularly checking in with our people – is a recipe for disengagement, frustration, and ultimately, lost talent.

This isn’t some fluffy “people skills” exercise. Regular feedback, when done right, is a force multiplier for productivity, innovation, and team cohesion. It allows you to course-correct quickly, unlock potential, and build trust – all crucial for navigating the constant change inherent in software development.

Why Traditional Performance Reviews Fall Short​

Let’s be honest: annual (or even bi-annual) performance reviews are often… stressful. They're retrospective, focused on documenting the past, and can feel like a judgment rather than a development opportunity. By the time that review rolls around, issues have often festered for months. Valuable coaching moments are lost, and individuals may feel blindsided by criticism.

Think of it like driving a car only looking in the rearview mirror. You’ll know where you were, but you’ll crash if that’s all you focus on. Regular feedback is like having real-time navigation - adjusting course as you drive.

What is Regular Feedback?​

It's more than just “checking in.” It's a consistent, ongoing dialogue characterized by:

  • Frequency: Regular, ideally weekly or bi-weekly, one-on-ones. Even short check-ins (“How are you feeling about the database refactor?”) count.
  • Specificity: Focus on specific behaviors or outcomes, not personality traits. Instead of "You need to be more proactive," try "I noticed you took the initiative to document the API changes - that was really helpful for the team."
  • Timeliness: Provide feedback close to the event. Don’t wait months to address something that happened last week.
  • Two-Way Communication: It's not a monologue. Create space for your team members to share their perspectives, challenges, and ideas.
  • Focus on Growth: Frame feedback as an opportunity for learning and development.

Practical Strategies for Implementing Regular Feedback​

Okay, great. But how do you actually do this without adding more meetings to an already overloaded schedule?

  1. Reimagine the One-on-One: The weekly one-on-one isn’t just a status update. Dedicate a significant portion of it to feedback – both giving and receiving. Start with a simple question: "What's one thing I can do to better support you this week?"
  2. "In-Moment" Feedback: Don't wait for the one-on-one. If you see something great (or something that needs addressing), offer quick feedback immediately. A quick Slack message ("Great job handling that production issue!") can go a long way.
  3. Leverage Tools (Wisely): Several tools can facilitate feedback collection. Services like feedback.fish, Vidhook, and Survicate offer ways to gather insights. There are many other options available, and the best choice depends on your team’s preferences. Remember, these tools are supplements, not replacements for genuine, human conversation. Pay attention to rate limits (like the one minute limit on Survicate) and ensure any tools are easy to use and don't feel like administrative overhead.
  4. Create a "Feedback-Friendly" Culture: Encourage your team to give each other feedback directly. Model vulnerability by asking for feedback yourself ("What could I have done differently in that meeting?").
  5. Focus on Strengths: While addressing areas for improvement is important, don’t neglect to acknowledge and celebrate successes. Positive reinforcement is incredibly powerful.

Implementing regular feedback isn’t always easy. Here are a few common challenges and how to address them:

  • “I don’t have time!” Prioritize. Investing 30 minutes a week in meaningful one-on-ones will pay dividends in productivity and morale.
  • “I’m uncomfortable giving negative feedback.” Practice. Start with small, specific observations. Focus on behavior, not personality. Remember that receiving feedback can also be challenging, even for experienced managers.
  • “My team member doesn’t seem receptive.” Create a safe space for dialogue. Ask open-ended questions. Listen actively. Try to understand their perspective before offering your own.

Conclusion​

Regular feedback isn't a magic bullet, but it’s a powerful tool for any engineering manager committed to building a high-performing, engaged team. It's about shifting from a reactive, assessment-focused approach to a proactive, development-focused one. By prioritizing regular, meaningful conversations, you unlock team potential and foster a culture of trust, transparency, and continuous improvement. It requires consistent effort, but the rewards are well worth it.