How to give a senior executive feedback they can use
Give a senior executive feedback by describing an observed behavior, explaining its work consequence, and stating the change you expect. Invite correction of your facts before settling the follow-up. Check that the executive understands the expectation without requiring agreement with every interpretation you offered.
Usable executive feedback is information about a specific work behavior and the expected adjustment that a leader can examine and act on. This is a practical definition. Its fairness foundation includes Colquitt’s 2001 distinction between procedural, interpersonal, and informational justice. That study does not originate or validate the conversation method below; it helps separate respectful treatment and adequate explanation from agreement about an outcome.
Replace the adjective before scheduling the conversation
Composite scene: You are at home writing notes for an executive’s review. The page says “defensive,” “territorial,” and “needs to collaborate.” You can remember several uncomfortable meetings. You cannot yet describe what the executive should do differently at the next one.
Do that preparation first. Choose an observable example and identify the work consequence. “You rejected the handoff” may still be too broad. “You reassigned the launch task during the meeting without confirming the receiving team’s capacity” describes a behavior the executive can recognize, dispute, or explain.
Avoid diagnosing what produced it. A refusal to accept your account may mean a factual error, a different interpretation, or disagreement about the role. Examine those possibilities before concluding that the person’s reaction demonstrates an enduring trait.
For a formal performance process, involve HR and employment counsel. The proposed approach here is general leadership preparation, not an assessment of legal adequacy or a substitute for required employment procedures.
Decide what kind of feedback you are giving
Separate three conversations that are easily combined. You may need to correct one action, clarify a recurring role expectation, or address a documented pattern with employment consequences. Say which conversation this is and prepare at the appropriate level.
If an executive made a reasonable choice under an unclear instruction, the first task may be to clarify the instruction. If the instruction was clear and the behavior recurs, examine the actual pattern. Do not turn one surprising event into a global claim about character.
Likewise, avoid offering something as optional advice when it is a requirement of the role. “You might want to consider” can obscure an expectation you intend to enforce. State the expectation plainly, with the proper authority and professional review where needed.
Use performance expectation resetting when the underlying standard has never been clear. The feedback conversation should apply a standard the executive can understand.
The observation, consequence, and expectation method
1. Select one defensible example
Write what you observed, when it happened, and which parts come from another person’s account. Where the source is indirect, verify it appropriately before presenting it as a finding. Keep private employee details restricted to the legitimate purpose.
Choose an example that illustrates the behavior you need to address. Avoid building a long catalogue merely to make disagreement difficult. Several weak examples do not repair an unsupported central assertion. If the material facts are still uncertain, investigate through the correct route before delivering a conclusion.
2. Explain the consequence at work
Identify what changed because of the behavior. In a hypothetical handoff dispute, the reassignment may have left two managers believing the other owned the launch. Confirm that consequence with the relevant work record rather than assuming it from the tension in the meeting.
Separate the observed consequence from a forecast. “The approval was delayed” differs from “the team will lose trust in you.” The latter is an interpretation requiring its own support. You can ask about effects without turning a concern into an established psychological fact.
3. State the expected behavior
Describe the next comparable action. For the handoff example: “Before changing an owner in the meeting, confirm capacity with the receiving manager and state who has accepted responsibility.”
Make the instruction proportionate to the role. Avoid requiring the executive to seek your approval for every ordinary decision because one handoff failed. If you are changing decision authority, discuss that change explicitly through the appropriate process rather than hiding it inside feedback about communication style.
4. Invite correction without abandoning the standard
Ask, “Which part of the event or consequence have I described incorrectly?” Listen to the answer. An executive may identify a relevant instruction or constraint you omitted. Correct your account where the evidence supports doing so.
Then distinguish the standard from the disputed interpretation. The parties may disagree about intent while agreeing that future ownership changes require an acknowledged handoff. If the expectation itself is disputed, resolve who can set it and why it belongs to the role.
5. Define the follow-up example
Choose a real upcoming situation where the expected behavior can be observed. Agree what evidence will be reviewed and when. Avoid a promise to monitor the person’s attitude generally.
If the concern forms part of a formal employment process, have HR and counsel guide documentation and follow-up. Where the conversation remains ordinary coaching, keep the record specific enough to prevent later disagreement about what was requested.
Exact words for a difficult exchange
Use proposed wording such as:
In [specific situation], I observed [behavior]. The work consequence was [verified effect]. In the next comparable situation, I expect [observable action]. Tell me what I have missed or described inaccurately. We may interpret parts of the event differently, but we need a clear expectation for the work. Please explain that expectation in your own words, and we will review [example] at [checkpoint].
If the executive says, “You are calling me uncollaborative,” return to the actual behavior: “I am asking for an acknowledged handoff before responsibility changes. If that instruction creates another problem, explain the problem so we can address it.”
If they say the relevant manager had already agreed privately, ask for an appropriate verification. Do not demand disclosure of unrelated private communications. Once the fact is established, decide whether the problem concerns the behavior itself or how the decision was made visible to others.
Make room for disagreement without rewarding evasion
Edmondson’s 1999 research defines team psychological safety around interpersonal risk. It gives a reason to inspect whether an executive can point out a factual error in your feedback. It does not mean the executive can avoid an established role requirement simply by disagreeing with it.
State what is open. The account of an event may be open to correction. The means of meeting an expectation may be open to discussion. Some conduct standards may already be required. Explain those distinctions instead of making the whole conversation feel like a test of whether the executive agrees with you.
If the person requests time to consider the feedback, decide what is reasonable for the situation. Set a clear return point. Avoid demanding an immediate emotional response that tells you little about the person’s later behavior.
Avoid turning a work issue into a relationship contest
Jehn’s 1995 research distinguishes task disagreement from relationship conflict. It also shows why broad claims that conflict is always useful are unwarranted. Applied here, examine whether discussion remains about the work or becomes an argument over loyalty and personal standing.
If the executive challenges your own contribution, consider the relevant facts. A CEO may have issued inconsistent directions. Acknowledging that does not prevent you setting a clear instruction now. It can improve the accuracy of the conversation without resolving every historical grievance.
Industrial/organizational psychology, the psychology of work and organizations, supplies these distinctions. The proposed method is not a personality test, and disagreement during feedback does not establish a diagnosis or a stable deficit in the executive.
Use a concrete follow-up rather than a verdict on attitude
Return to the hypothetical launch handoff. At the next planning meeting, inspect whether the receiving manager accepted responsibility and understood the required work. If the handoff occurred, acknowledge the specific improvement.
If it did not occur, ask what prevented it. The answer may identify capacity, missing authority, or a repeated refusal to follow the instruction. Those possibilities require different responses. Do not report all three as “still defensive.”
If the executive followed the instruction but the launch still failed, review the other causes. A completed communication behavior is not proof that every part of the operating plan was sound. Preserve the distinction between the feedback target and the wider business result.
Repair feedback that was too broad
If you previously used a label, correct it directly. Say, “My earlier wording was too broad. Here is the behavior I need to discuss.” Then supply the example and expectation rather than asking the executive to forget the prior conversation.
If the record contains an inaccurate claim, involve the proper owner in correcting it. Do not leave a vague adverse statement in place while giving a more careful explanation privately. Ask HR or counsel about records with employment consequences.
A repair should also identify what remains valid. You may withdraw an unsupported motive claim while retaining a verified instruction about handoffs. That gives the person an accurate account of both the correction and the responsibility still attached to their role.
Close on an action both parties can identify
Before ending, ask the executive what they understand the next requirement to be. Correct any difference between their account and yours. Confirm what remains disputed and what information will resolve it.
You do not need a declaration that the conversation felt good. You need a specific expectation, a fair opportunity to correct the record, and a follow-up tied to actual work. That gives the executive something usable and gives you a defensible basis for the next management decision.
Related reading: How to build an executive team that can disagree and deliver, What to say when your own behavior has damaged team trust, How to rebuild trust between departments that blame each other.