• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Feedback as Dialogue

Purpose and Strategic Importance

Feedback as Dialogue is the practice of treating feedback exchange as a two-way, ongoing conversation rather than a periodic top-down evaluation. When feedback is only given by leaders to team members, it creates asymmetry that limits learning, distorts relationships, and suppresses the honest communication that organisations need to function well. Leaders who invite, receive, and act on feedback from those they lead create the conditions for genuine mutual improvement.

This practice is foundational to a feedback culture. If the leader does not invite feedback on their own behaviour, team members cannot feel genuinely safe giving it. If the leader does not act on feedback, team members stop providing it. The practice requires leaders to go first, stay curious, and demonstrate that feedback is genuinely wanted — not tolerated.


Description of the Practice

  • Leaders actively solicit feedback on their own behaviour and leadership, not just from their own managers.
  • Feedback is received with curiosity rather than defensiveness: questions before explanations.
  • Leaders close the feedback loop: "You told me — here's what I've done with it."
  • Team members are coached on how to give useful, specific feedback — not just asked to provide it.
  • Feedback flows in multiple directions: leader to team, team to leader, peer to peer.

How to Practise It (Playbook)

1. Getting Started

  • Ask for feedback from your team directly: "What's one thing I do that makes your work harder? What's one thing I could do better?"
  • Receive it without immediately defending, contextualising, or discounting.
  • Follow up: "I heard that I — I've tried [Y] in response. Has it helped?"
  • Name when you are acting on feedback, so the person knows their input made a difference.

2. Scaling and Maturing

  • Build feedback into team rituals: end-of-project reviews, retrospectives, peer conversations.
  • Use 360 feedback processes periodically to gather structured, broad input on leadership behaviour.
  • Coach team members on feedback frameworks (SBI, COIN) so that the quality of feedback given improves alongside the culture.
  • Make asking for feedback a visible leadership behaviour — others will adopt what leaders model.

3. Team Behaviours to Encourage

  • Team members give feedback to each other as naturally as they give it upward.
  • Feedback is timely — shared close to the relevant event, not stored for formal reviews.
  • People ask for feedback proactively rather than waiting to receive it.
  • Feedback conversations are calm and curious, not charged or defensive.

4. Watch Out For…

  • Leaders who ask for feedback but respond in ways that punish honesty.
  • Feedback systems that create data but no change — teams stop contributing to processes that lead nowhere.
  • Feedback that flows only top-down, maintaining the leader as the sole arbiter of performance.
  • Treating 360 feedback as a compliance event rather than a genuine learning input.

5. Signals of Success

  • Leaders receive meaningful, specific feedback from their teams — not polished reassurance.
  • Visible changes in leader behaviour follow from feedback received.
  • Team members give each other feedback without the leader needing to prompt or facilitate.
  • Feedback exchange is described as a normal, valued part of how the team works.
  • The quality and specificity of feedback improves over time as the practice matures.
Associated Standards
  • Leaders create conditions where people feel safe to speak and challenge
  • Leaders model curiosity and continuous learning visibly
  • Leaders create regular space for reflection and learning

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering