Leadership Development for Feedback: Helping Managers Have Better Conversations
Leadership development for feedback is the practical work of helping managers notice what is happening, discuss it clearly and agree a useful next step without making the conversation feel like a verdict on someone’s character. It is not a script to memorise. It is a repeatable capability: preparing well, being specific, listening properly and adapting the conversation to the person and situation.
When feedback is treated as an occasional formal event, it often arrives too late and carries too much weight. When leaders develop the skill to make feedback part of normal working life, people have more opportunity to adjust, ask for support and understand what good work looks like.
A useful feedback-development focus helps managers:
- turn vague concerns into observable examples
- hold a two-way conversation rather than deliver a judgement
- distinguish a one-off mistake from a pattern that needs attention
- agree ownership, support and a realistic follow-up point
- adapt their approach without lowering the standard
That sounds straightforward. In practice, it asks leaders to manage their own assumptions, time pressure and discomfort as well as the conversation in front of them.
Feedback is a leadership capability, not a difficult-conversation emergency service
Many managers first receive feedback training when something has gone wrong: a team member is missing deadlines, two colleagues are in conflict, or a review is approaching. Those situations matter, but leadership development for feedback should start earlier. The aim is to build the habits that prevent routine issues from becoming formal problems.
A capable leader can move between several kinds of feedback. They can recognise work that should continue, point out a change that is needed, ask someone to reflect on their own performance and raise a concern before it hardens into resentment. None of those conversations needs the same tone. What they share is clarity and respect.
The distinction is worth making because feedback is often confused with criticism. Criticism can leave a person trying to work out whether they themselves are the problem. Useful feedback keeps the focus on work, behaviour, decisions and their effects. It gives enough detail for someone to understand what happened, while leaving room for their account of the situation.
For example, “You are not committed to the team” is a broad interpretation. “In the last two handovers, the information needed for the next shift was missing, and colleagues had to chase it” gives the person something concrete to respond to. The latter may still be uncomfortable, but it is possible to discuss and improve.
This is why feedback development is bigger than teaching a model with a memorable acronym. A model can help a manager organise their thoughts. It cannot replace judgement about timing, context, workload, working relationships or the support someone may need. Leaders need practice in making those calls.
Build the conditions before asking managers to be more candid
A manager cannot create a healthy feedback culture alone. People learn from what happens after they speak up. If feedback is met with defensiveness, public embarrassment or no meaningful follow-through, the team quickly learns to stay quiet.
Leadership development therefore needs to address the environment around the conversation. Senior leaders can make their expectations visible by asking for feedback on their own decisions, acknowledging it without retaliation and explaining what they will do next. HR and L&D can make feedback part of manager support rather than a remedial programme reserved for people in difficulty.
It also helps to separate developmental feedback from every other workplace process. A conversation about how a presentation landed is not automatically a performance-management event. Nor should a manager promise that an informal conversation will never inform a broader pattern. The honest position is simpler: this conversation is about understanding the work, improving it where needed and being clear about what happens next.
Managers often avoid feedback because they fear triggering an emotional reaction. Emotion is not proof that the conversation failed. It may signal surprise, frustration, disappointment or a need for more time to think. The leader’s job is not to remove emotion; it is to stay steady, listen and avoid turning discomfort into an argument.
That requires a different kind of preparation. Before a meeting, a manager should be able to answer four questions:
- What did I directly observe or receive reliable evidence about?
- Why does it matter to the work, team or customer?
- What perspective might I be missing?
- What change, support or decision would make this conversation useful?
These questions slow down the impulse to label someone. They also make it less likely that a manager will save up several unrelated frustrations and unload them at once.
The conversation should create shared understanding, not just deliver a message
Feedback becomes more useful when the manager treats it as an exchange of information. The leader still has a responsibility to name the concern or expectation plainly. But they also need to find out what the other person saw, intended and was working with.
A simple structure works well:
- Set the purpose and name the specific moment or pattern.
- Describe the effect without exaggerating it.
- Invite the person’s view and listen for relevant context.
- Discuss the standard or outcome that is needed.
- Agree one or two actions, support needed and a time to review progress.
The order matters. Beginning with a long explanation can make the manager sound as though the decision has already been made. Asking only open questions can obscure the issue the leader is responsible for addressing. Good feedback holds both parts: a clear observation and genuine curiosity.
Better questions are particularly useful once the manager has named the issue. “What made that handover difficult?” invites context. “What would help you complete it consistently next time?” turns towards action. “How will we know this is improving?” makes the agreement testable without turning it into a threat.
Leaders who want to strengthen this part of their practice can use the ideas in Asking Better Questions in Leadership & Coaching. The purpose is not to make every conversation feel coached. It is to replace assumptions with questions that help both people understand the work.
A concrete example: moving from frustration to an agreed change
Consider a manager, Priya, who is concerned about Jordan’s contributions in weekly project meetings. Jordan regularly arrives with updates that are too broad for the group to make a decision. Priya has become increasingly frustrated because meetings run over and actions are left unclear.
An unhelpful version might sound like this: “You need to prepare properly. Your updates are always vague and it is holding everyone back.” Priya may be trying to solve a genuine problem, but the wording combines judgement, absolutes and an unclear request. Jordan may focus on defending their effort rather than examining the meetings.
A stronger approach is more precise: “I want to talk about the last two project meetings. When you gave the status update, we did not have the delivery date or the decision you needed from the group. We used extra time clarifying both, and we left without a clear owner for the risk. How did you see those meetings?”
Jordan explains that the information is coming from two teams late on Monday, shortly before the meeting. Priya now has a fuller picture. The standard does not disappear, but the response can be more useful. They agree that Jordan will circulate a short pre-meeting update by Friday, flag missing information early and state the decision needed at the start of each agenda item. Priya will help unblock access to one of the teams providing the information. They will review the next two meetings together.
This is leadership development for feedback in action. Priya did not soften the point until it became meaningless. She avoided guessing at Jordan’s motivation, learned about a practical constraint and made the next step specific. Jordan leaves with accountability and support rather than a general sense of having failed.
Adapt the approach without turning people into categories
Different people may prefer different amounts of detail, time to process or opportunities to talk through an issue. A manager who notices those differences can make feedback easier to hear and act on. That does not mean lowering expectations for some people or deciding that a profile explains everything about them.
Personality insight can be a useful hypothesis for preparing a conversation, especially when a manager and employee have different communication preferences. It can prompt questions such as whether the person is likely to value advance notice, written detail, a chance to discuss options, or a direct statement of the expected outcome. The conversation itself should confirm what works; it should not be governed by a label.
That approach is central to Effective Feedback: How to Give Performance Feedback That Works, which explores how leaders can tailor their communication while keeping the message fair and clear.
Adaptation also includes choosing the right setting. Private, timely feedback is usually better for a concern about an individual’s work. A team conversation may be right when the issue is a shared process or expectation. Public recognition can be motivating for some people and uncomfortable for others, so a manager should know the person well enough to check rather than assume.
The constant is the standard. The route to helping someone meet it may vary.
Give managers practice on the work they actually face
Managers rarely struggle because they cannot define feedback. They struggle when they have to do it between a deadline, an unexpected absence and their own workload. Development needs to fit that reality.
A practical programme can focus on live situations, with appropriate confidentiality. Managers might bring a forthcoming conversation, separate facts from interpretations, practise the opening aloud and consider likely responses. A peer can challenge a vague statement or ask what evidence supports it. A coach can notice when the manager slips into rescuing, lecturing or avoiding the issue.
Short practice cycles are more useful than a one-off session followed by silence. The manager tries a new approach, reflects on what happened, gets help with the next conversation and gradually builds confidence. This can sit alongside existing one-to-ones, project reviews and team meetings rather than becoming another large initiative that busy managers cannot sustain.
For organisations where time is already tight, the development design matters as much as the content. Managing When Overwhelmed: Leadership Tips for Busy Managers offers a helpful starting point for thinking about leadership work that must happen alongside delivery, not after it.
A manager’s development plan does not need to cover every feedback challenge at once. One leader may need to become more direct about standards. Another may need to stop jumping to solutions before they understand the issue. A third may need to follow up consistently. Selecting one behaviour, applying it repeatedly and reviewing the result is more manageable than asking for a total personality change.
Make follow-up part of the feedback, not an optional extra
The credibility of feedback is often decided after the conversation. If a manager never returns to the agreed action, people may conclude that the issue was not really important. If they follow up only to look for failure, feedback begins to feel punitive.
A useful follow-up asks what has changed, what remains difficult and whether the agreed support has happened. It should recognise progress honestly. It should also name what is still below the required standard. This is how a conversation becomes a learning loop rather than a one-time intervention.
For teams, it can help to build light routines around this. At the end of a project, managers can ask what should be repeated, stopped or adjusted next time. In one-to-ones, they can ask what feedback the employee has for them. Before a high-stakes meeting, they can clarify the decisions and contributions expected. These routines make feedback more ordinary, which reduces the pressure when a harder conversation is needed.
Organisations can also look for patterns without treating individuals as data points. Are managers consistently avoiding timely conversations? Do teams lack a shared definition of a good handover? Are expectations changing without being communicated? Those questions may reveal a system problem that individual feedback alone cannot solve.
Know where feedback development has limits
Better feedback will not fix an unmanageable workload, an unclear strategy, poor resourcing or a decision that has not been made. It cannot make a leader’s subjective impression objective simply because it is delivered politely. Where the concern involves conduct, formal performance processes, legal risk or employee wellbeing, managers should use the appropriate internal support and procedures.
There is also a limit to what a single manager can observe. Feedback should not rely on rumour, selectively remembered incidents or a personality-based assumption. When the evidence is incomplete, the leader can say what they have noticed, ask for context and avoid claiming certainty they do not have.
For HR and L&D, the wider task is to give managers enough shared language and practical support to handle everyday conversations responsibly. Assessment insight and private coaching can help selected people prepare for the work in front of them, but they are aids to reflection, not substitutes for managerial judgement. MyTeamBuilder’s HR and L&D approach shows how wider understanding and selected coaching can be combined without assuming everyone needs identical support.
The best test is simple: after feedback, does the person understand what happened, why it matters, what they can do next and where they can get help? If not, the answer is rarely a harsher message. It is usually better preparation, a clearer conversation or a more realistic agreement.
If the aim is to help managers make feedback a normal, useful part of leadership rather than a dreaded event, Take the next step with MyTeamBuilder to explore a practical route from shared insight to better conversations.