The moment a coachee looks at their 360 data and says, with real conviction, that the people who rated them are wrong, is one of the most instructive moments in any coaching engagement. How you handle the next ten minutes determines whether the coaching becomes useful.
The moment a coachee disputes their 360 data is one of the most instructive in the engagement. How the next ten minutes are handled often determines the rest.
The 360 debrief is, in my experience of executive coaching, the session where the coaching either opens or closes. In every other session of the engagement, the coach and coachee are working with material that the coachee has selected, framed, and brought. In the 360 debrief, for the first time, the material comes from somewhere else. It arrives with a specificity and a multiplicity that self-report cannot simulate, and it occasionally carries the particular quality of data that is both entirely accurate and entirely unwelcome. How the coach and coachee navigate the thirty minutes following the delivery of that data is, in my experience, more consequential for the outcome of the engagement than any other single conversation in the process.
The engagement I am describing was with the CHRO of a mid-sized financial services firm, appointed eighteen months earlier into the role. She was, by most measurable indicators, performing effectively: the function was well-organised, the leadership team trusted her judgment, and her business partnering relationships had improved measurably since her appointment. The 360 had been commissioned as part of a broader executive team development process, and she had entered the debrief session, by her own account, without particular anxiety about what it would contain. The data contained a pattern that twelve of her seventeen raters had, in different ways and with different specific examples, described: that she was not visible as a strategic thinker in cross-functional leadership conversations. That she was perceived as technically excellent and operationally dependable, but not as someone who shaped the broader business direction in the forums where direction was being set.
The Disagreement
When I presented the pattern, she was quiet for a moment, and then said, with a directness I respected, that the people who had rated her this way did not have sufficient proximity to her work to rate it fairly. That the cross-functional forums referenced in the feedback were not the contexts in which real strategic conversations happened in her organisation. That the data was, in her assessment, A FUNCTION OF VISIBILITY rather than a function of capability. She did not become angry or defensive in any performative sense. She offered a well-organised counter-argument, calmly and precisely, in the way that a technically competent senior professional presents a case they believe in.
This is one of the most common and one of the most instructive moments in executive coaching practice, and I want to be precise about what I mean by instructive, because the instruction is not straightforward. When a coachee disputes their 360 data, the instinctive response of many coaches is to find a way to resolve the dispute, either by validating the data and asking the coachee to sit with it, or by finding aspects of the counter-argument that can be integrated into the debrief without entirely dismissing either the data or the coachee’s perspective. Both of these responses, however gracefully executed, make the same fundamental error: they treat the disagreement as a PROBLEM TO BE RESOLVED rather than as data to be explored.
The disagreement itself is one of the most diagnostic moments in the coaching engagement. What the coachee is doing when they dispute the 360, the specific framing they choose, the particular counter-argument they construct, the emotional quality of the disagreement, all of this reveals something important about how they are relating to their own development, their professional identity, and the feedback process itself. Resolving the dispute quickly closes that window. Staying in it, with genuine curiosity and without an agenda to prove or disprove the original data, opens it.
“When a coachee disputes their 360 data, the most useful thing I can do is not defend the data. It is to become genuinely curious about what the dispute is protecting.”
RK, Founder & Principal Consultant, ProventusHRWhat I Did Not Do
I did not defend the data. This is perhaps the most critical thing I did not do, and it requires some explanation because the instinct to defend the data is very strong in this moment. The data has been carefully gathered. The process has been rigorously explained. Twelve people arrived at this pattern independently. It is objectively compelling evidence. But engaging with the data as something to be defended is to engage with the coachee’s counter-argument as something to be refuted, and refutation is the one response that most reliably converts a coaching conversation into a debate, with the coach and coachee on opposite sides of a factual dispute that neither can definitively resolve.
I also did not over-validate the counter-argument. The instinct to meet resistance with empathy, to say “I hear you, and I understand why this feels inaccurate to you,” is well-intentioned and, in many coaching moments, exactly right. In this particular moment, it would have been a way of bypassing the productive discomfort that the data had created, rather than allowing that discomfort to do its work. The coachee needed to sit in the tension of the data, not to be helped out of it.
What I did instead was offer a single question, and then stay in the silence that followed it. The question was: “What would need to be true for twelve separate people, across four different levels and three different functions, to arrive independently at this specific description of your strategic presence?”
The Turn
The question worked because it sidestepped the accuracy debate entirely. Whether the data was objectively right, whether the raters had sufficient proximity to rate fairly, was in fact an unanswerable question in the room. What was answerable was a more productive one: what is the CONSISTENT PERCEPTION that twelve independent observers share, regardless of the mechanism through which they arrived at it, and what does that perception tell us about the leader’s current impact?
She was quiet for some time. And then she said something I did not expect: “I think I may have been managing my strategic thinking privately. Doing the work in my head and then presenting the conclusions, rather than bringing the thinking process into the room.”
This was a disclosure of extraordinary value. Not because it confirmed the 360 data, which it did, but because it was self-generated: she had arrived at a specific, behavioural, and immediately actionable insight through her own process, rather than having it delivered to her by me or by the raters. The coaching for the remainder of the session, and across the subsequent months of the engagement, was anchored in this insight. The development focus became specific and precise: not “be more strategic” in the vague and frustrating way that most strategic leadership feedback is framed, but “bring the thinking process into the room, make the reasoning visible, invite others into the analysis before the conclusion is formed.” The 360 data at the end of the engagement showed a consistent shift in this specific dimension across nine of the twelve original raters who had described the original pattern.
What to Do and What Not to Do
For coaches navigating this moment, the following distinctions are practically useful. First, distinguish between the DATA and the PATTERN. Individual data points can legitimately be questioned, contextualised, or attributed to specific relationship dynamics. When twelve people describe the same pattern in different words and with different examples, the pattern is no longer a data point. It is a signal about something real in the leader’s professional impact, regardless of whether it reflects the leader’s intention or their internal experience of themselves.
Second, recognise that the disagreement has an emotional structure, and that the emotion is information about what is at stake. The CHRO in this account was not merely disputing a factual claim. She was experiencing a genuine dissonance between her internal self-concept, in which she was a capable strategic thinker, and an external account of her impact that challenged that self-concept directly. That dissonance is not comfortable. It is also, handled well, the most productive condition in which genuine developmental insight can occur. The coach’s role is not to resolve the dissonance quickly but to create a container safe enough to sit in it.
Third, use questions that move from the data’s accuracy to the data’s signal. “Regardless of whether these raters are right, what does this consistent perception tell us about impact?” is a question that does not require the coachee to concede that their counter-argument was wrong. It invites them to move to a more generative level of the conversation without losing face, and without the coach having to win a factual argument they cannot definitively win.
The broader principle that this specific situation illustrates is one of the most important in executive coaching practice: THE COACHEE’S RELATIONSHIP TO THE DATA is always more diagnostically rich than the data itself. A coachee who receives difficult 360 feedback with equanimity and immediate acceptance is in some sense less interesting, developmentally, than one who disputes it vigorously. The dispute tells you what is at stake. And what is at stake is always, at its root, a piece of identity that is engaged in the coaching process whether the coachee wishes it to be or not.
“The coachee who disputes their 360 data most vigorously is often the one who makes the most significant change during the engagement. The dispute tells you where the important work is. It is not a barrier to the coaching. It is the first step of it.”
RK, Founder & Principal Consultant, ProventusHRResearch Reference
Atwater, L. and Yammarino, F. (1992). “Does Self-Other Agreement on Leadership Perceptions Moderate the Validity of Leadership and Performance Predictions?” Personnel Psychology, 45(1). Research consistently shows that the discrepancy between self-ratings and other ratings is one of the strongest predictors of specific developmental areas where coaching will produce the most significant change. Leaders who overrate themselves relative to stakeholders in a specific competency area show the greatest improvement in that area when coaching is designed to address the discrepancy rather than to validate the coachee’s self-perception.
The ProventusHR Perspective
The 360 debrief at ProventusHR is not a report-reading session. It is a designed coaching conversation in which the data is a starting point, not a destination. Our debrief protocol specifically anticipates the disagreement moment and treats it as a productive element of the process rather than a complication to be managed. Coaches are prepared to hold the tension of the dispute with genuine curiosity, to use the specific questions described in this field note when the moment warrants it, and to distinguish between a coachee who is processing difficult data and one who is fundamentally refusing the developmental position. These are different situations that warrant different responses, and the skill to distinguish them is a function of experience, presence, and the quality of the coach’s relationship with uncertainty. The 360 debrief, done well, is one of the richest developmental conversations available in the coaching engagement. Done poorly, it closes the room before the coaching has had a chance to begin.
About the Author
Founder Director, ProventusHR · MGSCC Master Coach · NDA Alumnus
Founder of ProventusHR and principal architect of ExperienceLearning and REEL|Life. 25+ years across leadership advisory, executive coaching, and experiential design across 14 industries. 9x Brandon Hall HCM Excellence Award winner (2022 to 2025).
Full Profile ›Every engagement begins with a discovery conversation. No templates, no generic programmes; only work that fits the context, the culture, and the people involved.
Start a Discovery Conversation