In this article
- New manager feedback begins with inherited context
- Choose an issue that matters to the work
- Open with observation and curiosity
- A hypothetical first-month conversation
- Agree a small, observable change
- Receive correction without losing the thread
- Build a pattern, not a dramatic first impression
- Explain what is changing from the previous approach
Harvard Business Review discusses the risks of early feedback in a new leadership role. The practical preparation below focuses on your first few conversations.
New manager feedback begins with inherited context
Learn what the employee was previously asked to do. A process you dislike may reflect an earlier instruction, a customer requirement or a constraint that nobody has explained yet.
Ask how the current approach developed. Review the relevant documents and speak with the people who own the requirement when appropriate.
This is especially important when you inherit an experienced team. Expertise may sit with people whose methods differ from yours.
Context is not a reason to avoid a clear safety or conduct issue. Follow the proper procedure when immediate action is required. For ordinary performance concerns, checking the facts improves the conversation.
Choose an issue that matters to the work
Your first feedback should concern a meaningful behaviour or outcome, rather than a campaign to make the team resemble your previous workplace.
Ask: What consequence does this create? What standard applies? What change would help?
If the answer is only “I prefer it this way,” consider whether a request, discussion or experiment is more appropriate than corrective feedback.
Choose a recent, specific example. An inherited reputation such as “She is difficult” is not enough. You need your own understanding of the relevant behaviour and context.
Avoid saving several concerns for one large introductory confrontation. A focused conversation gives both people a better chance to understand and act.
Open with observation and curiosity
A useful opening can be direct and provisional: “I noticed the customer update did not include a confirmed owner for the next action. I would like to understand how that update is prepared.”
Then explain why it matters: “Without an owner, the service team was unsure who should follow up.”
Ask for the employee’s account before proposing a solution. You may learn that the template has no owner field or that responsibility changes after the meeting.
Do not weaken a clear requirement with excessive apology. Respectful language can still be plain: “We need the next action and owner to be visible.”
Likewise, avoid announcing that your way is the professional way. The issue should be understandable without accepting your status as proof.
A hypothetical first-month conversation
Imagine a newly appointed team leader finds that weekly reports contain different date ranges. Her initial reaction is that the team is careless.
She asks a senior analyst how the reports are compiled. The analyst explains that two systems export on different cycles and the previous manager accepted the mismatch.
The new leader explains the comparison problem and asks the analyst to propose a workable convention. They agree to label each reporting period clearly while investigating whether the cycles can be aligned.
The feedback still addresses a real issue. Learning the context prevents the manager from blaming employees for a process they inherited.
This hypothetical is a scenario for practice, not a factual account of Peak Belt’s founder or a client.
Agree a small, observable change
Make the next action specific enough to review. “Improve your reporting” is broad. “Label the reporting period on the first page and flag any mismatch before distribution” is clearer.
Ask what support or decision is needed from you. A new manager should not demand a change while leaving an obsolete template or conflicting instruction in place.
Set a review point that matches the work. If the report is monthly, an immediate daily check-in may add little value.
Explain whether the change is a trial or a permanent requirement. Employees should not have to infer whether they can suggest adjustments after trying it.
Receive correction without losing the thread
If the employee points out that your observation is inaccurate, check it. A factual correction is useful information, not an attack on your authority.
You can say: “Thank you; I missed that instruction. Let us separate what was required then from what we need going forward.”
If disagreement concerns the standard, explain the reason and where your authority begins and ends. Consult the appropriate owner if necessary.
Do not retaliate through tone, assignment or exclusion. A new manager establishes expectations partly through how they respond when someone challenges their interpretation.
Build a pattern, not a dramatic first impression
Regular, proportionate conversations are more sustainable than one performance designed to establish toughness. Notice good work with the same specificity used for correction.
Ask the team how they prefer routine feedback, while being clear that urgent issues may need immediate discussion. Preferences inform the process; they do not remove legitimate accountability.
Peak Belt’s first-time-manager mistakes guide and performance-feedback guide provide broader context. Explore TrueNorth for related leadership practice.
Explain what is changing from the previous approach
When a new standard differs from the old one, name the change and its reason. Employees should not be criticised for following an instruction that was valid before you arrived. Set a clear effective point, provide the necessary tools and explain how questions will be handled. This makes the transition accountable without rewriting the team's history.
Before your first feedback conversation, write the observation, the work consequence and one question about context. If you cannot complete those three lines, investigate before delivering a judgement.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.