You have been meaning to give feedback to one of your team members for three weeks.
You have not done it yet.
The behaviour is real. The impact is real. The conversation is on your list. Every time you think about having it, something else takes priority, or you decide the timing is not right, or you tell yourself you will say something at the next 1:1 and then the 1:1 ends and you have not said it. The three weeks become six. The behaviour continues. Your private frustration grows. Eventually, you say something, and because the frustration has accumulated, the feedback comes out harder than you intended, the team member becomes defensive, the conversation ends without resolution, and you spend the rest of the week thinking about how you should have handled it better.
This is the most common pattern in feedback at growing Australian businesses. The manager is conscientious. The team is capable. The work matters. The system for giving feedback in a way that produces behaviour change rather than accumulated frustration is missing, and the cost shows up in every direction. Team members get blindsided in performance reviews by feedback they should have heard months ago. Managers carry private frustration that affects their relationships. Behaviours that could have been corrected easily get reinforced because they were never named. The business carries the operational cost of all of this, mostly invisibly, until someone leaves or underperforms in a way that becomes impossible to ignore.
Gallup research consistently shows that employees who receive meaningful feedback in the past week are dramatically more engaged than those who do not. The research is not telling us anything we do not already know. The gap is not in the awareness. It is in the practical method. Most managers were never taught how to give feedback. They learned by absorption from their own managers, which means most of them are repeating the patterns of managers who also never learned. The skill is missing because the structured method was never transferred.
This post is the practical framework for that method.
Why most feedback either gets avoided or lands badly
Before getting to the framework, it is worth being honest about why feedback is so consistently mishandled in growing businesses. The causes are structural and human, not personal.
Managers avoid feedback because the cost feels higher than the benefit. Giving difficult feedback is uncomfortable. The benefit is delayed and uncertain. The cost is immediate and felt. The rational calculation, in the moment, often says "I will do it next week." Next week, the same calculation produces the same outcome.
The feedback is vague. When the conversation finally happens, the manager says "you need to communicate better" or "your attention to detail could be stronger." The team member nods, agrees, and has no idea what specifically to do differently. The feedback produces no behaviour change because it was never specific enough to be actionable.
The feedback is delivered as personality. The manager describes the team member rather than describing the behaviour. "You are disorganised." "You are not strategic enough." The team member hears this as a judgement about who they are, not what they did. They become defensive. The feedback bounces off without changing anything.
The feedback is delivered too late. The behaviour happened six weeks ago. The conversation is happening now. The team member cannot remember the specific situation clearly. The connection between the behaviour and the impact has faded. The conversation produces vague agreement rather than concrete change.
The feedback is one-way. The manager talks. The team member listens. There is no exploration of context, no question about what the team member was navigating, no openness to information the manager does not have. The conversation is a verdict, not a dialogue. The team member complies but does not internalise.
The feedback is never followed up. The conversation happens. The team member commits to changing. Nothing further is said about it. Three months later, the behaviour has either changed or not changed, but the manager does not know which, because they have not checked. The feedback was an event rather than the start of a learning loop.
Fix these six failure modes and feedback starts to do what it is supposed to do.
What feedback is actually for
Before the framework, a quick clarification on purpose. Feedback is not about making the manager feel better. It is not about establishing authority. It is not about creating a paper trail for a future termination.
Feedback is about producing behaviour change in the team member, in a way that helps them perform better and grow professionally. That is the test. Every feedback conversation should be evaluated against it. If the conversation did not produce a clear path to behaviour change, the feedback failed, regardless of how well the manager felt they delivered it.
This matters because it changes the orientation. The manager is not the protagonist of the feedback conversation. The team member is. The manager's job is to give the team member the information and the support they need to change. Everything else is secondary.
The 6-part framework for feedback that produces behaviour change
This is the framework I use at ThinkSwift when I work with managers who want to get better at the most important conversations they have. It is built for the specific situation where the relationship matters, the behaviour matters, and the goal is to produce change rather than to vent or to comply with a performance management process.
Part 1. Give the feedback close to the event
The single most important move is to deliver feedback close to when the behaviour happened. Not in the moment, usually. The moment is rarely the right time. But within days, not weeks.
The principle. Feedback is most effective when both parties can clearly remember the specific situation. Once the memory fades, the conversation becomes abstract, and abstract feedback does not produce concrete change.
A practical rule. If you find yourself thinking about a feedback conversation more than once, the conversation is overdue. The fact that you are thinking about it is the signal. Schedule the conversation in the next forty-eight hours. Not next week. Not at the next 1:1. Within forty-eight hours.
This is the discipline that breaks the avoidance loop. The longer feedback waits, the harder it becomes to deliver. The harder it becomes to deliver, the longer it waits. The cycle ends when you commit to a rule that overrides the in-the-moment calculation. Forty-eight hours, no exceptions.
Part 2. Use the Situation-Behaviour-Impact structure
The most important structural move is to use a consistent framework that separates objective observation from interpretation. The Situation-Behaviour-Impact model is the cleanest tool for this.
The structure has three parts.
Situation. When and where did this happen? Be specific. "In the client meeting on Tuesday." "During the project handover last week." "In the engineering standup this morning." The situation grounds the feedback in a specific event that both parties can remember.
Behaviour. What specifically did the person do? Describe observable behaviour, not interpretation. "You interrupted the client three times before they had finished explaining the brief." Not "you were dismissive." Not "you were not listening." The specific observable action, in language the team member cannot reasonably dispute.
Impact. What was the consequence of the behaviour? On the work, on the team, on the client, on you. "The client became visibly frustrated and pulled back from the conversation. We did not get the full brief, and I had to follow up by email to fill in the gaps." Concrete consequence, named directly.
That is the entire structure. Three sentences. Maybe four. Delivered calmly, with a tone that says "I am sharing this because I want you to know," not "I am sharing this because you are in trouble."
The reason this structure works is that it is hard to disagree with. The team member can argue with "you are dismissive." They cannot easily argue with "you interrupted the client three times." The conversation moves from contested judgement to shared observation, and shared observation is the foundation that behaviour change can be built on.
This is also the structure that works for positive feedback. "In the client meeting on Tuesday, you asked a clarifying question that surfaced a requirement we had missed in the original brief. As a result, the proposal we wrote was substantially more aligned with what the client actually needed, and they signed faster." Same structure. Different content. Same effectiveness.
Part 3. Make the feedback a dialogue, not a delivery
After you have delivered the Situation-Behaviour-Impact, stop talking and ask a question.
"What is your perspective on what happened?"
"What were you trying to do?"
"What did you notice about how that went?"
The question is what turns the feedback from a verdict into a conversation. It opens space for the team member to provide context you do not have, to share their interpretation of what happened, to surface constraints or considerations that affected their behaviour.
Sometimes this changes the conversation entirely. The team member shares something you did not know, and the situation is more nuanced than your original framing. You adjust. The feedback becomes a joint problem-solving conversation rather than a one-way correction.
Sometimes the team member confirms your read of the situation, and the conversation moves quickly to what to do differently next time.
Either way, the dialogue produces better outcomes than the monologue. The team member feels heard, which means they are more likely to internalise the feedback rather than just comply with it. The manager learns context they did not have, which produces better-calibrated feedback going forward.
The mistake most managers make is to skip this step. They deliver the SBI and immediately move to "and so going forward, I would like you to..." The team member never gets to speak. The conversation feels procedural. The behaviour change, if it happens at all, is reluctant compliance rather than genuine adjustment.
The pause to ask a question is two minutes of conversation. The return on those two minutes is dramatically better feedback outcomes.
Part 4. Agree on what specifically will change
The fourth move is to land the conversation on a specific, agreed change in behaviour. Not a vague commitment. A concrete action.
"Going forward, in client meetings, you will let the client finish their full thought before responding, even if you think you know where they are going. We will check in on this after the next two client meetings."
That is concrete enough to be actionable, specific enough to be observable, and time-bounded enough that both parties know when to check in.
The version to avoid. "Going forward, you will work on being a better listener." This is the version most feedback conversations end on. It commits to nothing, produces nothing, and leaves both parties with the sense that something has been agreed when in fact nothing has been agreed.
The discipline is to keep the conversation going until there is a specific change agreed. If the team member cannot articulate the specific change, the manager helps. If the manager cannot articulate it, the conversation is not ready to end. Push through to the concrete commitment, or the feedback will not produce the behaviour change it was supposed to.
Part 5. Follow up explicitly
The fifth move is to close the loop. Feedback without follow-up is feedback that decays.
In the days and weeks after the feedback conversation, the manager actively watches for the behaviour. When the team member demonstrates the new behaviour, the manager acknowledges it specifically. "In the meeting just now, I noticed you let the client finish their full thought before responding. That worked well." This is positive SBI, delivered close to the event, and it reinforces the change in a way that purely procedural follow-up cannot.
When the team member reverts to the old behaviour, the manager gives feedback again, immediately and specifically, using the same structure. "In the meeting just now, when the client started talking about budget, you interrupted to clarify a point. The same pattern we discussed last week. Let us talk about what made that happen."
Either way, the follow-up is what makes the original feedback land. Without it, the feedback was a single moment that the team member can choose to act on or not. With it, the feedback becomes a learning loop that produces sustained change.
A practical mechanism. In your own notes, after every significant feedback conversation, capture what was discussed, what was agreed, and a date to check in. The check-in does not need to be a separate meeting. It can be a brief comment in the next 1:1 or a quick conversation in the moment. The discipline is that the check-in happens, not that it is formally scheduled.
Part 6. Make feedback regular, not exceptional
The final move is the cultural one. If feedback is rare, every feedback conversation is high-stakes. The team member sees the manager request a quiet word and immediately assumes something is wrong. The conversation starts with elevated stress on both sides, which makes it harder to land well.
The fix is to make feedback frequent enough that it is no longer exceptional. Brief positive feedback in the flow of normal work. Brief constructive feedback close to the event. Specific recognition in team meetings. Direct, calm conversations about behaviour and impact, often enough that they are part of the texture of the working relationship rather than a deviation from it.
When feedback is regular, the difficult conversations become much easier. The team member is not surprised when the manager wants to discuss something. The structure is familiar. The relationship has been built on a pattern of honest, specific, calm feedback in both directions, so the harder conversations sit on a foundation of trust that has been established through dozens of smaller exchanges.
This is the long-term work. The framework above produces individual feedback conversations that land well. The cultural work produces a team where feedback is part of how the team operates, not a special event that everyone dreads.
What this looks like in practice
A practical example. Imagine a team member is consistently arriving late to internal meetings, by five to ten minutes. The behaviour is producing friction on the team. You have been thinking about saying something for two weeks.
With the framework above.
- Day one of the new approach: schedule a brief 1:1 within forty-eight hours of the next instance. Not a formal meeting. A fifteen-minute conversation.
- The conversation: "In our planning meeting on Tuesday, you arrived at ten past, eight minutes after we started. The same pattern happened in last Thursday's standup and Monday's review. The impact is that the team has to recap when you arrive, which means we lose ten to fifteen minutes of collective time each week. What is your perspective on what is happening?"
- The team member explains. Maybe they are coming from another meeting that consistently runs over. Maybe they have a personal commitment in the mornings. Maybe they had not realised the pattern was visible.
- You work together to agree the specific change. Maybe they move the preceding meeting. Maybe the standup moves by ten minutes. Maybe they commit to being on time and giving notice if they cannot.
- Follow up. In the next two weeks, you actively notice whether the change happens. You acknowledge it when it does. You raise it immediately if it does not.
This is dramatically more effective than the standard pattern of avoiding the conversation for six weeks, then mentioning it in a performance review as "punctuality could be better," then being confused about why nothing has changed by the next review.
The bigger picture
Giving feedback well is the most important skill a people manager has. It is also the most consistently undertaught. Most managers are doing the job they learned by watching their own managers, and most of those managers were doing the job they learned the same way. The result is a generational pattern of feedback being either avoided or delivered badly, with significant operational cost that nobody quite measures.
The six-part framework above is not complicated. It is also not the default. The default is to wait too long, deliver too vaguely, talk too much, agree to too little, and follow up too rarely.
Deliver close to the event. Use Situation-Behaviour-Impact. Make it a dialogue. Agree on specific change. Follow up explicitly. Make feedback regular.
Done consistently, this is the discipline that turns feedback from one of the most avoided conversations in management into one of the most effective. The team gets better. The team members feel respected. The manager carries less private frustration. The business gets the compounding benefit of a team that is continuously improving because the information they need to improve is being given to them in a way they can actually use.
The conversations are not always easy. The team member will sometimes push back. You will sometimes get it wrong and have to acknowledge that. The skill is built through practice, and the practice gets easier the more you do it. But the framework above takes the conversation from "I have been dreading this for weeks" to "I have a structure that works and a method I trust." That shift is the difference between feedback as an avoided burden and feedback as one of the most valuable tools you have as a leader.
The work pays back in every direction. Better performance. Stronger relationships. Less of the silent operational drag that comes from accumulated unspoken frustrations. The team members who get clear, specific, kind feedback are the team members who stay, grow, and become the people you can rely on as the business gets bigger. Skip this discipline, and you build a team that does not know what they are doing well or what they need to change. Build it, and you build a team that gets measurably better at the work, conversation by conversation, year over year.
That is what good feedback actually looks like in a growing business. Not performance reviews. Not annual conversations. Hundreds of small, specific, structured, respectful exchanges that compound into a team that genuinely keeps getting better.
