Who This Is For, and Who It Isn't For

CEO wanted to talk. He sincerely wanted to address the issues his organization was facing. We spent almost two hours on a diagnostic conversation, working through where his last four transformations had gotten stuck and why the fifth one already looked like it might be in trouble. He asked sharp questions. He pushed back in useful ways. Then we reached the part of the conversation about what actually needed to change, and he told me his employees were the problem. “Our people are just really resistant to change.”

It turns out, they weren’t. He had described the real constraint himself, an hour earlier, without recognizing it. Decisions were routed through committees that hadn’t been redesigned in a decade, sign-off chains were built for a company half the current size, incentives rewarded finishing on schedule over finishing well. Some part of him already knew this. But designating the system as the actual constraint would have meant admitting his own design choices were part of it, and blaming the people in front of him was the easier conclusion to reach. Plus, it meant they had to change and he didn’t.

I didn’t argue with him. Two hours of conversation isn’t enough data to settle a question like that, for him or for me. So I suggested something more useful than a debate: he and a few of his key leaders complete the Organizational Adaptability Pulse Check on my site, independently, and we would review the results together.

They did. The data didn’t reveal what he expected. People weren’t where the organization was actually breaking down. Governance and infrastructure was. Capability building was. The profile pointed at precisely the pattern I’d started to suspect an hour into that first conversation, without either of us calling it out yet.

To his credit, he looked at his own data and conceded he might have been wrong. He wanted to understand why. That’s what moved us into the full Adaptive Capability Diagnostic, not to confirm what the Pulse Check had already suggested, but to find the actual mechanism underneath it.

We found it in the decision flow. Approval chains and standing committees that should have been dismantled years earlier were still routing every meaningful decision through people and steps that no longer matched how the organization needed to operate. Layered on top of that were real capability gaps, not a training problem so much as capability that had never been built in the first place. Between the two, transformations weren’t just slowing down. Some of them were failing outright, and the people closest to the work were absorbing the blame for outcomes the structure had already made close to inevitable.

Who I actually work with

The leaders I work with know something has to change. That’s the baseline, not what sets them apart. What actually sets them apart is what they’re willing to do next: concede the problem might be their people, but stay genuinely open to the more common answer, that once they look honestly, it’s the organization.

Blaming employee resistance without data is lazy, and I’m not interested in confirming a leader’s assumptions for them. I’m interested in finding out what’s actually true, even when that takes longer than a two-hour conversation. Often, when there’s real employee resistance, it isn’t the disease. It’s a symptom of something else: structural debt, built up from years of transformations layered on top of each other without anyone going back to clear out what no longer works.

They recognize a specific pattern beyond that one conversation: a project gets its sign-off, gets its post-mortem, and changes nothing about how the organization actually operates six months later. They have spent hundreds of thousands or even millions of euros or dollars on outside consultants, more than once, and watched every bit of that capability walk out the door the day the engagement ended, which means the next transformation starts from zero again. The consultants gained more valuable experience but the organization didn’t build any additional capability. They launch initiatives reactively, after something has already broken, instead of sensing the shift before it becomes a crisis.

Who this work isn’t for

It isn’t for leadership that wants to blame people without first proving or disproving that hypothesis, and without understanding what’s actually underneath it. It also isn’t for leaders who know something has to change but who, when it comes down to it, would rather protect the status quo than do anything differently. Knowing something is wrong and being willing to act on what you find are two different commitments. This work is only effective for the second one.

Why the distinction matters more than it sounds like it should

Diagnosing “people” and diagnosing “the organization” lead to two entirely different engagements. If you treat a structural constraint as a people problem, the intervention becomes a communications plan, a training rollout, maybe a new set of values printed on a poster. The exhaustion doesn’t move, because nothing that was actually broken got touched. Six months later, the same cycle resurfaces under a different initiative name, and it gets read as more evidence that the people are the problem, which was never true to begin with.

The CEO from that call was not a bad leader. He was a leader who had built a set of governance decisions years earlier that made sense at the time, decisions that had turned into the actual bottleneck without anyone flagging them as such. Recognizing that wasn’t an indictment. It was the starting point of an engagement that actually changed something, once he was willing to look.

The line I keep saying

The problem might be your people. But it’s almost always the organization.

That’s not a rhetorical flourish. It’s the filter I use before I take on any engagement. Sometimes that filter ends a conversation after two hours. This time, it didn’t. What started as one diagnostic call turned into a Pulse Check, then a full Adaptive Capability Diagnostic, then a client who was willing to redesign the decision flow that had been running his company for years.

If this is where you are right now, unsure whether it’s your people or your organization, start with the free Organizational Adaptability Pulse Check: https://www.kellybrogdongeyer.com/pulse-check.

If you already suspect the answer and want to go straight to the why behind it, let’s have that conversation.