How to Ask for Leadership Feedback You Can Actually Use

You ask how you are doing and hear, “Great work. Keep it up.” The answer is pleasant, but it gives you little to practice before the next project. Useful leadership feedback starts with a specific moment, an observable behavior, and someone who saw its effect. Ask what helped, what made the work harder, and what they would suggest for a similar situation. Then choose one change and return to it after you have practiced. This makes feedback part of the work itself, instead of a broad judgment you receive only during a performance review.

Choose a moment the other person actually observed

Pick a recent situation where your leadership affected the work: a planning discussion, a handoff, a disagreement, a coaching conversation, or a decision under time pressure. The example gives both of you something concrete to examine. “How did I handle the discussion about the launch risk?” is more answerable than “Am I a good leader?”

Choose the person for their view of that situation. Your manager can comment on whether your recommendation addressed the wider priority. A project partner can tell you whether your update clarified the next step. A direct report can describe how your intervention affected their ability to own the work. No single perspective captures everything.

The Center for Creative Leadership’s guidance on learning agility recommends seeking feedback, asking clarifying questions, and resisting an immediate defensive response. The practical exercise in this article builds on that principle: make the request specific enough to learn from, then give yourself room to consider the answer before deciding what to change.

Ask about behavior and effect

A useful question points to what you did and how it landed. Avoid asking the other person to diagnose your personality or predict whether you deserve promotion. Those questions are broad, and they can pull the discussion away from the evidence they actually have.

Try one of these prompts after a relevant moment. Use only the prompt that fits; sending a colleague a long questionnaire can make a small request feel like another assignment.

• After a meeting: “When the group disagreed, what did I do that helped us make progress? Where did I make the discussion harder?”
• After a recommendation: “Was the tradeoff clear enough to make a decision? Which part needed more context?”
• After a handoff: “What did you still have to work out after I handed this over?”
• After coaching: “Which part of our conversation helped you choose a next step? Where did I take over too much?”
• After a difficult week: “What did you need from me that you did not get?”
• Before another attempt: “What is one change you would suggest when I handle this again?”

If the answer is a label, ask for an example. “I should be more decisive” could mean you failed to name an owner, reopened a settled choice, or waited too long for additional information. “Which moment made you feel we needed a clearer decision?” helps you identify the action behind the label.

Make the request easy to answer honestly

Give the other person a choice of timing and format. A short message can work: “I am practicing how I lead planning discussions. Could you give me a brief read on yesterday’s meeting, especially how I handled the scope disagreement? Written feedback or a few minutes after our next check-in would both help.”

Explain the purpose without asking for reassurance. “I am trying to improve this behavior” gives a clearer invitation than “I hope I did not handle that badly.” Avoid adding a long account of what you intended before they speak. It can steer them toward confirming your explanation rather than describing their experience.

When you manage the person, acknowledge that the request can feel different because you evaluate their work. Offer an established feedback channel if your organization has one, and do not pressure them for an immediate critique. Do not promise anonymity you cannot provide. Your later response matters as much as the wording of the invitation.

Receive the answer before explaining yourself

Listen for the example, the effect, and the suggested change. If you feel the urge to defend the decision, write down the context you want to add and first check that you understand. “You needed me to name the owner before the meeting ended, and without that you were unsure who should follow up. Is that right?”

Clarifying a factual error is reasonable. The aim is not to agree with every interpretation. It is to understand what the other person experienced before deciding whether the feedback fits. If necessary, say, “I want to think about that and come back to you,” rather than arguing yourself out of hearing it.

Thank them for the concrete information. You do not need to declare that the feedback has transformed your leadership or promise a complete change overnight. A measured response is more credible: “That example helps. I will try closing the next planning discussion with the owner and next step, then check whether it was clearer.”

Turn the feedback into one observable practice

Use a small record to translate the conversation into action. The example below is fictional; adapt the structure to a behavior you genuinely want to improve.

• Situation: The planning meeting ended with two unresolved handoffs.
• Feedback: A teammate could not tell who was responsible for the next step.
• Behavior to practice: Close each decision with an owner, next action, and date.
• Next opportunity: The next two weekly planning meetings.
• Observer: The teammate who raised the issue.
• Follow-up question: “Was ownership clearer this time? Where was it still ambiguous?”

Choose a behavior within your control. “Make everyone feel confident” is difficult to practice directly. “Ask the owner to restate the next step before we close” is specific. You can observe whether you did it and ask whether it helped.

Keep the number of active changes manageable. If you hear several useful points, select the one most relevant to the work ahead. Save the others for later discussion. Trying to adjust every part of your communication at once can make it difficult to tell which change made a difference.

Work through conflicting or vague feedback

Two colleagues can give different advice because they experienced different situations. One wants more context; another wants a faster recommendation. Before deciding that one is wrong, compare the audience, decision, and timing. A specialist reviewing an implementation may need detail that a sponsor approving the direction does not.

Ask what the reader needed to do with your message. You may discover a practical solution: start with the recommendation and decision needed, then provide supporting detail below it. The goal is to understand the requirements behind the preferences, rather than average two conflicting opinions into a compromise nobody needs.

Be careful with feedback that cannot be tied to behavior, such as “You are not leadership material” or “You need more presence.” Ask which observed action led to that view and what effective behavior would look like. If the person cannot provide an example, treat it as an unresolved judgment rather than a complete development plan. Repeated unfair or discriminatory treatment deserves appropriate organizational support; collecting more feedback is not a substitute for addressing it.

Close the loop and keep the learning

After practicing, return to the original example: “I have been ending the planning discussion with confirmed owners. Has that made the handoffs clearer?” This gives your colleague a narrow question to answer and shows that their effort led somewhere. If the change did not help, revise it together.

Record what you heard, what you tried, and what happened. Keep the difference between the colleague’s words and your own interpretation clear. A private note about your learning should not turn into a file of judgments about the colleague. Follow your employer’s rules for storing work information.

Bloomly can hold your reflection with the relevant Role so that a later development conversation starts from a real example. A useful entry might say, “Practiced closing decisions with owners in two planning meetings; a project partner said the second handoff was clearer. Still need to confirm dates before ending.” That preserves progress without pretending the skill is finished.

Ask for a specific view of a specific moment. Listen for the behavior and its effect, choose one change, and ask again after you have practiced. You will not receive perfect feedback every time, and you do not have to adopt every suggestion. What you can build is a repeatable habit of learning from the people who experience your leadership. The strongest evidence of growth is the change you can explain and the difference someone else can observe.