The Diagnosis Most Organizations Skip
What I do before I build anything
I was brought into an organization that had just completed a merger.
On paper, it was working. The org chart had been redrawn. The new leadership team had been announced. Town halls had been held. Culture decks had been updated with fresh language about shared values and unified vision.
And yet — something wasn't moving.
Managers were duplicating decisions. Teams that were supposed to collaborate were quietly routing around each other. A low-grade tension had settled into the organization that no one could name, so no one was addressing it.
They had hired me to design a leadership development program.
I told them I needed three weeks before I touched a single learning objective.
That pause — before the program, before the curriculum, before any intervention — is the work most organizations skip.
We have a design bias in organizational development. We move fast toward solutions. Someone surfaces a problem: engagement is down, a team is stuck, a leader is struggling. And almost immediately, the conversation shifts to what we should build. A workshop. A coaching program. A feedback framework. A retreat.
The instinct is understandable. Programs are visible. They signal action. They produce deliverables that can be reported upward.
But a program designed before a diagnosis is just a very expensive guess.
What I found in those three weeks wasn't a leadership gap.
It was a decision rights problem wearing a culture problem as a costume.
Two organizations had merged, but no one had mapped what actually changed underneath the org chart. The informal authority structures — who people actually went to when they needed a real answer — hadn't transferred. In one legacy organization, decisions had historically been made by a small group of senior individual contributors who held institutional knowledge no title had captured. In the other, authority flowed through hierarchy almost exclusively.
When those two systems merged, people defaulted to their original operating logic. Confusion wasn't a symptom of poor communication. It was a symptom of two incompatible decision architectures running simultaneously inside the same org chart.
No leadership program was going to fix that.
What fixed it was naming it — clearly, at the right level, with the data to back it up — and then designing a targeted intervention around decision rights, not development content.
This is what systems thinking actually looks like inside an organization.
Not a framework on a slide. Not a Cynefin diagram in a workshop. The real thing is slower and less elegant: sitting with what you're observing long enough to distinguish the symptom from the cause, and resisting the pressure to act before you understand.
Organizations under pressure — scaling fast, integrating acquisitions, navigating leadership transitions — are especially vulnerable to the program-first instinct. The urgency is real. The noise is loud. Stakeholders want to see movement.
But movement in the wrong direction compounds the problem.
A merger doesn't fail because the training was inadequate. It falters when no one maps the invisible architecture — the informal networks, the cultural load-bearing walls, the decision patterns — that didn't appear on either org chart and didn't survive the combination intact.
The organizations that integrate well aren't the ones with the most robust L&D calendar. They're the ones with someone who slowed down long enough to ask: what are we actually looking at here?
MIT research on organizational change consistently finds that transformations stall not from lack of effort but from misdiagnosis — leaders addressing the visible problem while the structural cause continues underneath. McKinsey's work on post-merger integration points to the same pattern: the organizations that capture value fastest are those that explicitly map cultural and operational incompatibilities before designing integration programs, not after.
The diagnostic phase isn't a delay. It's the work.
Three things that change when you lead with diagnosis:
1. You stop solving the stated problem and start solving the real one. The stated problem is almost never the problem. It's the place where the problem became visible. Diagnosis is the process of tracing backward from the symptom to the source — which requires a different set of questions than a needs assessment, and a different quality of listening than a stakeholder interview.
2. Your interventions get smaller and more precise. One of the counterintuitive outcomes of good diagnosis is that the intervention often shrinks. You need less when you know exactly where to apply pressure. Targeted beats comprehensive almost every time.
3. You earn the trust that makes the real work possible. Nothing builds credibility with senior leaders faster than demonstrating that you understand their business more deeply than they expected. Diagnosis done well is a form of partnership. It signals that you're not there to run a program — you're there to solve a problem.
The three weeks I spent before touching that leadership program changed everything about what we built.
More importantly, it changed what we didn't build — which saved the organization significant time, money, and the particular exhaustion that comes from doing a lot of work in the wrong direction.
The merger didn't need a better leadership curriculum.
It needed someone willing to look at what was actually there.
That's still the rarest thing I know how to offer.
