# How to get feedback on your management

**Feedback for managers** is most useful when the request is specific, the response feels safe, and the manager acts visibly afterward. Ask about behavior people have observed, not whether you are a good manager. Offer private ways to answer, receive examples without defending yourself, and close the loop. Candor grows from repeated experience, not from one promise that honesty is welcome.

        
## Why is manager feedback difficult?

        
A report evaluates risk before answering. You influence assignments, opportunities, recognition, and sometimes continued employment. Even a caring manager cannot remove that power by saying, “You can tell me anything.” People will consider your past reactions and the organization's habits before deciding how direct to be.

        
The question itself can create pressure. “Am I supporting you well?” invites reassurance. “What should I improve?” is broad and demands that the employee design your development. A specific prompt tied to shared work is easier: “During design reviews, when do I help the discussion, and when do I enter too soon?”

        
Feedback also carries emotional labor. Reports may worry that criticism will hurt you or trigger a long explanation. Your process should reduce that burden. Ask occasionally, make passing acceptable, and manage your reaction with someone who does not report to you.

        
## Which feedback routes should you offer?

        
| Route | Useful for | Manager responsibility |
| --- | --- | --- |
| 1 on 1 question | Context rich examples | Do not pressure an immediate answer |
| Written note | Time to think and precise wording | Protect privacy and respond calmly |
| Private collection | Patterns people hesitate to name | Do not search for authors |
| Peer observation | Meetings and shared decisions | Ask about behavior, not loyalty |
| Manager conversation | Context and recurring leadership choices | Compare with closer lived experience |

        
No route is complete. Direct conversation provides context but can suppress candor. Private collection can surface themes but removes detail. Use more than one route over time and be transparent about who will see the information and how it will be used.

        
## What questions produce useful answers?

        
Ask about a setting, behavior, and effect. “When we review an incident, what do I do that helps you speak clearly?” is answerable. “How is my leadership?” requires a summary judgment and often receives general praise. Narrow questions help memory and make change possible.

        
Balance strengths and friction. Ask what you should continue as well as what you should change. Strength questions are not there to protect your confidence. They identify behavior worth preserving while you experiment elsewhere. People may also find it easier to begin with a helpful example.

        
Invite feedforward when history feels risky: “In the next planning session, what could I do to help you own the decision?” A future focus can produce practical suggestions. Still leave room for past impact if the person wants to name it.

        
## How should you introduce the request?

        
Explain why you are asking and what will happen next. You might say, “I am reviewing how I enter technical decisions. I would value one example of when my involvement helped or reduced your ownership. You can answer now, later in writing, or not at all.” Choice makes the request more credible.

        
Acknowledge the power difference directly but briefly. Do not make a dramatic statement that requires reassurance. Say that you know candor can carry risk and that you will not connect disagreement with performance judgment. Then demonstrate that promise over time.

        
Do not ask during a performance conversation, after giving disappointing news, or while the person needs your decision. Their attention belongs to the immediate issue. Separate your development request from moments when they may feel obliged to please you.

        
## What should you do while receiving feedback?

        
Listen for the observed event and effect. Reflect what you heard: “When I rewrote the proposal in the meeting, you felt there was no longer room to own it.” Ask whether you understood. This is clarification, not agreement with every interpretation.

        
Control the urge to provide missing context. Your reason may matter later, but an immediate explanation often sounds like correction. Thank the person, note any question that needs thought, and say when you will return. A pause protects both learning and the relationship.

        
Do not reward only polished feedback. Someone may be nervous, indirect, or frustrated. Look for the information beneath the delivery while maintaining respectful boundaries. Reports should not need expert communication skills to describe the effect of your behavior.

        
## How can an engineering manager ask after a real event?

        
Suppose a production incident ends with a tense review. You facilitated quickly because time was short, but two engineers barely spoke. After the immediate work settles, ask each person what in your facilitation helped facts emerge and what narrowed discussion. Avoid asking whether the meeting was good.

        
One engineer may say your rapid questions felt like cross examination. Another may say the structure prevented speculation. Both can be true. Your task is not to average them. Consider what each person needed, which questions were necessary, and whether a slower opening could preserve rigor while improving access.

        
At the next review, state the purpose, allow a quiet minute to collect observations, and ask the service owner to begin. Later, ask whether the change affected participation. This creates a complete feedback loop: request, reflection, practice, and follow up.

        
## What if the feedback feels wrong?

        
Do not force yourself to agree immediately. Separate accuracy from usefulness. A claim such as “You never listen” may be literally false, yet it signals that a memorable experience of not being heard exists. Ask for an example if safe, then compare it with your notes and other observations.

        
Consider power and pattern. A single comment may identify a serious impact that others did not experience. Several similar comments may show a habit even if each example has complications. Your intention and constraints belong in the analysis, but they do not erase the other person's experience.

        
You may decide not to change. Explain only when useful: perhaps a security decision required authority that cannot be delegated. Even then, you might improve how you communicate the boundary. Receiving feedback does not mean granting every request. It means considering it honestly.

        
## How should anonymous feedback be handled?

        
Use private collection for themes, not investigation. Avoid guessing who wrote a phrase or changing behavior toward likely authors. If a comment lacks enough context to act on, name the theme and invite optional examples through a safe route. Accept that some ambiguity will remain.

        
Report back at a level that protects contributors. “Several people said I share my view before others have framed the decision” is enough. Do not quote distinctive wording that could identify someone. Explain the behavior you will test and when you will review it.

        
Private feedback loses value if employees see no response. It also loses safety if leaders demand raw comments or author identities. Set those boundaries before collecting anything. If confidentiality cannot be protected, say so clearly rather than promising it.

        
## How do you close the loop?

        
Summarize what you heard without turning it into a defense. Distinguish what you will change, what you will examine further, and what must remain because of role constraints. Keep the response concise. People should not have to process a long account of your learning.

        
Make the chosen action observable. If you heard that you interrupt solutions, say you will wait, reflect, and ask one question before advising in the next month of 1 on 1 meetings. The specificity lets people notice genuine effort without becoming your evaluators.

        
Return after practice. Ask whether the change helped and what still feels difficult. If you missed the behavior, acknowledge it. Closing the loop is not announcing perfect improvement. It is showing that speaking honestly can influence your choices.

        
## How often should you ask?

        
Use brief questions after relevant moments and a more deliberate review every few months. Too many requests can feel like a demand for reassurance or create constant observation. Match frequency to the behavior and the team's capacity.

        
Do not wait for a formal cycle if you suspect harm. If you interrupted someone publicly or reversed their decision without explanation, repair directly. Feedback processes should not delay basic accountability. Ask what impact the moment had after naming your own part.

        
Feedback for managers becomes candid when people experience respectful requests, calm reception, privacy, and visible action again and again. Your best invitation is your previous response. Build that record, and feedback becomes part of working together rather than a risky special event.

## Frequently asked questions

### How can managers get honest feedback?

Ask about specific behavior, offer private response routes, acknowledge the power difference, receive examples without debate, and show what changed afterward.

### What question should a manager ask first?

Ask, “What is one thing I do that makes your work easier, and one thing that makes it harder?” Then request an example only if the person is comfortable sharing.

### Should feedback for managers be anonymous?

Anonymous feedback can surface patterns, but it can be hard to interpret. Combine it with voluntary conversations and never pressure people to identify authors.

### What should a manager do with unfair feedback?

Pause, look for the experience behind the wording, compare other evidence, and choose whether a clarification, repair, or no change is appropriate.

### How often should managers ask for feedback?

Ask lightly after relevant moments and use a more deliberate process every few months. Avoid constant requests that make reports responsible for your reassurance.

Related: [manager self evaluation](https://isilta.com/blog/are-you-doing-well-as-a-manager/), [signs of a good manager](https://isilta.com/blog/which-signals-show-a-manager-is-effective/), [manager development plan](https://isilta.com/blog/what-to-do-after-a-manager-self-assessment/).