Managing
To build a feedback culture, make feedback expected, specific, frequent and acted on. In practice that means leaders ask for feedback before they give it, feedback gets a fixed slot in the week rather than waiting for reviews, everyone uses one simple shape for it, and people can see work change because of it. The last part matters most: feedback that never changes anything teaches people to stop giving it.
Most attempts to build a feedback culture start with training people to give feedback. It is the wrong end. Teams rarely lack people willing to give feedback; they lack a reason to believe it is safe and worth it. Someone who gave honest feedback last year and saw nothing change, or saw it held against them, will not do it again however good the workshop was.
A feedback culture is not a skill. It is a system with four parts, and it fails at its weakest one.
| Part | What it looks like when it works | What it looks like when it fails |
|---|---|---|
| Giving it straight | Feedback names a specific behaviour and its effect, soon after it happened. | Vague praise, hints, or criticism saved up for the annual review. |
| Taking it well | People ask follow-up questions and say thank you, including the boss. | Defensiveness, explanations, or a cold week afterwards. |
| Giving it often | Feedback happens weekly, in normal meetings, about normal work. | Feedback is an event that people brace for. |
| Acting on it | You can point to work and habits that changed because of feedback. | The same comments, year after year, with nothing different. |
Diagnose before you fix. A team that gives feedback well but never acts on it needs a different intervention from one where feedback simply never happens. If you are not sure which part is weakest, the free feedback culture check scores all four in about three minutes.
The fastest signal that feedback is safe is the most senior person in the room asking for it and responding well. Not any feedback for me?, which always gets silence, but a specific question: What is one thing I did in that meeting that made it harder to disagree with me? Then thank the person, do not explain yourself, and change something visible. That one exchange does more than a policy.
People avoid feedback partly because they do not know how to phrase it. Give them one simple structure and use it everywhere. The SBI model works well: the situation (when and where), the behaviour (what the person did, observably), the impact (what it caused). In Tuesday's client call, when you answered the pricing question before I could, the client stopped asking us questions. That is feedback. You need to be less dominant is a judgement.
Feedback that depends on someone finding the right moment does not happen. Put it in the calendar. Three rhythms that work:
The bigger and rarer feedback is, the more it hurts and the less it helps. A comment the day after a presentation is a coaching note. The same comment in a review six months later feels like an ambush. Aim for many small pieces of feedback about specific work, mostly delivered within a week.
Receiving feedback is the neglected half. Give people three moves: ask one clarifying question, say thank you, and decide later whether to act. They do not have to agree on the spot. Separating hearing feedback from accepting it takes most of the heat out of the conversation.
This is the step that decides whether the culture survives. When feedback leads to a change, say so: Several of you said our stand-ups ran long, so from next week they end at fifteen minutes. People keep giving feedback only when they can see it working.
Run a short survey every quarter on the four parts above, share the results with the team, and pick the weakest one to work on. A rising score is the evidence people need that this is not another initiative that will fade.
People do not stop giving feedback because it is hard. They stop because nothing happened last time.
The after-action review is one of the oldest and most copied feedback rituals. After an exercise or operation, the team answers four questions: what was supposed to happen, what actually happened, why there was a difference, and what we will do next time. Rank is set aside for the discussion. It works because it is routine, it is about the event rather than the person, and it always ends in a change.
Ed Catmull describes in Creativity, Inc. how Pixar's Braintrust, a group of experienced filmmakers, reviews films in progress and gives candid notes to the director. The important design choice is that the Braintrust has no authority: the director decides what to do with the notes. Removing the power to command made it easier for people to be honest, and easier for the director to listen.
Both examples share a design you can copy at team level with no budget or software. One rule: every Friday, each person gives one teammate one piece of SBI feedback, in writing, about something from that week, and the manager goes first. It takes ten minutes. After a month, spend fifteen minutes asking the team which habits have changed because of it. If nobody can name one, the problem is step six, not the ritual.
For the giving side in more depth, see how to give constructive feedback at work and Kim Scott's radical candor. If you want to draft a difficult piece of feedback before you deliver it, the free feedback builder walks you through it.
Expect the first signs in four to six weeks if the rhythms are kept, mainly more feedback flowing upwards and problems surfacing earlier. A lasting change usually takes two or three quarters, because people wait to see whether the first piece of honest feedback is punished. The quickest way to undo the work is a single senior person reacting badly in public. The quickest way to speed it up is a senior person visibly changing something because of what they heard.
Tour De Force runs this as live, experiential training for teams worldwide, online and in person. Talk to us, or play The Weekly Challenge from our gamified learning apps to see the method in ten minutes.
Questions
A feedback culture is one where giving and asking for feedback is expected, routine and safe, in every direction, and where feedback reliably leads to change. It has four parts: feedback is given straight, taken well, given often and acted on. A team is only as strong as its weakest part.
Start with leaders asking for specific feedback and responding well. Agree one simple shape for feedback such as Situation, Behaviour, Impact. Give it fixed slots in one-to-ones and meetings, keep it small and frequent, teach people how to receive it, and visibly close the loop when feedback leads to a change.
The US Army's after-action review, where teams ask what was supposed to happen, what happened, why, and what to do next time; and Pixar's Braintrust, where experienced filmmakers give candid notes that the director is free to act on or not. At team level, a weekly habit of one specific piece of feedback per person works well.
Usually because feedback does not lead to visible change, or because someone was punished for being honest. Training people to give feedback cannot fix either. Other common causes are relying on anonymous channels, feedback flowing only downwards, and saving feedback for annual reviews.
Ask the team short, specific questions each quarter about the four parts: whether feedback is specific, whether it is received well, how often it happens and whether it changes anything. Compare the manager's answers with the team's. The free Tour De Force feedback culture check does this in twelve questions.
Keep reading
Twelve questions on whether feedback gets given straight, taken well, given often, and acted on.
GuideSituation, behaviour, impact: the simplest shape for feedback that lands.
GuideCare personally, challenge directly, and where the model gets misused.
Get in touch
Book a 30-minute discovery call and we'll shape an experiential programme around your goals.
Book a discovery call →