When the Data Points at the Person Who Hired You
The diagnostic implicates leadership. The person who hired you is sitting across from you. What happens in the next twenty-four hours will define the engagement more than anything that came before it.
There is a moment in almost every serious engagement when the work stops being abstract. The diagnostic is complete. The pattern is clear. And the thing generating the friction \u2014 a behavior that has become load-bearing, a structural decision that served a different organization, a blind spot that has gone unnamed long enough to calcify \u2014 traces back, unmistakably, to the person sitting across from you. The person who called you in. The person who is paying for this.
What you do in the next twenty-four hours will define the engagement more than anything that came before it.
This is not a comfortable moment. It was not designed to be. But it is also not the crisis it can feel like in the hours between when you see the finding and when you have to deliver it. The practitioner who learns to move through this moment with clarity and care \u2014 not despite the discomfort but through it \u2014 is the one whose clients actually change.
What the data is doing
Before thinking about delivery, it is worth understanding what the finding actually means.
When the diagnostic implicates leadership, it is almost never saying that the leader is a poor executive or a difficult person. It is saying that something specific is producing friction at a cost the organization is paying whether or not it can see the invoice. A meeting culture that has trained people to arrive with answers rather than questions. A decision made three years ago about reporting structure that made sense then and is quietly strangling coordination now. A pattern of response to bad news that has taught the people below a certain level to edit before they speak. The data is not a verdict. It is a location. It tells you where the source of the problem is. What to do about it is a separate question \u2014 and one the leader is considerably better positioned to answer than the practitioner is.
This distinction matters enormously for how the finding lands. A practitioner who walks into that conversation carrying the data as an indictment will produce defensiveness. A practitioner who walks in carrying it as a discovery \u2014 something the two of you are looking at together \u2014 creates the conditions for something more useful.
The finding did not come to punish the leader. It came to give them something they did not have before: an accurate picture of what is happening and why. That is a gift, even when it does not feel like one on delivery.
What the leader is about to experience
Empathy is not optional in this moment. It is methodologically required.
Amy Edmondson's foundational research on psychological safety establishes that people assess interpersonal risk before deciding whether to speak, act, or engage honestly \u2014 and that this calculus is driven primarily by what they observe happening to others who tried. The leader receiving a difficult finding is no different. They are running the same calculation, in real time, about what it will cost them to accept what they are hearing. The practitioner who understands this is not just being kind. They are managing the conditions under which honest engagement becomes possible.
The person receiving this finding hired you because something felt wrong and they wanted to understand it. They were willing to invite scrutiny into their organization \u2014 which is not a small thing. And now they are about to hear that the thing that felt wrong has their fingerprints on it. Whatever their initial reaction \u2014 a reframe that repositions the data, a silence that goes half a beat too long, an agreement that arrives too quickly to be real \u2014 it is coming from somewhere genuine. They are processing something that is genuinely hard to process.
Most leaders move through a predictable sequence when a finding like this lands. The first response is protective. A leader who built a high-performing team over seven years and is now hearing that her communication style has been quietly suppressing dissent is not going to absorb that in thirty seconds. A founder who has made every significant decision in the organization's history and is now looking at data suggesting that his certainty has become the organization's ceiling is going to need more than a moment. This is not resistance. It is the entirely human response of someone whose self-image is in contact with information that challenges it.
The practitioner who mistakes this for obstruction and pushes harder will lose the room. The practitioner who recognizes it as processing and holds the space will find that the leader almost always arrives, on their own, at something closer to acceptance than the initial response suggested.
Let them move through it. Your job in that moment is not to win the argument. It is to stay present, stay warm, and trust that the data can hold its own weight without you defending it.
How to deliver it
There is no script for this conversation that works across every leader and every finding. But there are principles that hold.
Lead with what you observed, not what you concluded. The finding is a pattern in the data. Present it as such \u2014 specifically, concretely, with the evidence visible. "Here is what the instrument surfaced across your senior team" is a different sentence than "here is what I think you have been doing wrong," and it produces a different conversation. The data is neutral. Let it be neutral.
Name the cost before the cause. Before the leader can hear what is driving the friction, they need to understand what the friction is costing. A team that has learned not to surface problems until they are unavoidable. A decision-making process that has slowed because the people with the best information have stopped volunteering it. Talent that has started looking elsewhere without saying why. Name these specifically, in terms the leader already cares about, before you introduce what is generating them. The cost grounds the conversation in organizational reality rather than personal evaluation. It also reminds both of you why you are in the room.
Connect the finding to the leader's own stated goals. In the intake conversation, a client tells you what they are trying to build \u2014 a senior team that can operate without them in the room, a culture where performance conversations happen before problems compound, an organization that can sustain the growth that is coming in the next eighteen months. They tell you what they are trying to protect \u2014 the quality that made the first twenty people want to stay, the trust they built with a board that has been patient, the reputation for execution that opened the doors they are now walking through. They tell you what they want the organization to look like. The finding is not in opposition to any of that. It is in the way of it. Framing it that way transforms the conversation from an evaluation into a problem-solving session \u2014 which is the only kind of conversation that produces change.
Give them a moment before you offer a path forward. The instinct, when delivering difficult news, is to move quickly to solutions \u2014 to soften the landing with what comes next. Resist it. The leader needs to absorb the finding before they can meaningfully engage with what to do about it. A pause, however uncomfortable, is more respectful than a pivot.
What this moment is actually for
The practitioners who do this work well share a particular quality. They are not detached. They are not clinical. They care \u2014 genuinely, visibly \u2014 about what happens to the leader and to the organization after they leave the room. That care is not separate from the rigor of the finding. It is what makes the rigor bearable.
Edmondson's more recent work makes a related point: psychological safety is not about comfort. It is about the conditions under which people can engage honestly with difficult information without the engagement becoming the threat. The practitioner's job is to create those conditions in the room \u2014 not by softening what the data says, but by making it safe enough for the leader to hear it without shutting down.
A leader who feels that the practitioner is genuinely on their side \u2014 not colluding with them, not softening the data, but invested in what happens next \u2014 is a leader who can hear hard things. That relationship is built or lost in exactly this kind of moment.
The data pointed at the person who hired you. That means you are exactly where the work needs you to be. The question now is whether you can deliver what you found in a way that leaves them more capable, more clear, and more willing to act than they were before you walked in.
That is the standard. It is a high one. It is also the only one worth holding.
Psychological Safety and Learning Behavior in Work Teams
Administrative Science Quarterly — Administrative Science Quarterly, 1999
High-trust leadership teams make decisions 2x faster and implement them 3x more successfully. — PwC
What People Get Wrong About Psychological Safety
Harvard Business Review — Harvard Business Review, 2025
91% of HR leaders say people analytics is critical. Fewer than 35% can act on it. — Deloitte
Seeing this pattern in your organization?
The diagnostic identifies which institutional state is generating the friction — and what to do about it.
Take the Diagnostic →