There’s a scene you’ve encountered before:
A patient is crashing. The room tenses. A physician gives an order. A nurse hesitates, then questions it. The exchange is quick, stressful, and just sharp enough to make everyone else go quiet for a moment.
If you’ve watched ER, The Pitt, or any medical drama, you’ve seen a version of it. Raised voices. Personalities clashing. Someone storms out. The patient becomes the backdrop.
In real life, it looks different. Quieter. Less theatrical. But the stakes are higher, and the consequences linger longer.
What happens next in that moment, whether the nurse speaks again, whether the physician listens, whether the team recalibrates or fractures, is where culture lives. And increasingly, that moment traces back to a relationship that most patients will never see: the one between the chief medical officer and the chief nursing officer.
How We Got Here
The CMO and CNO roles didn’t grow up together. They arrived at the same place from very different paths.
The modern CMO role took shape as medicine itself became more organized, more measured, more accountable. Years ago, the job was often about translation. The medical staff spoke one language, administration another. The CMO stood in the middle, the bridgebuilder, keeping the peace.
Then came To Err Is Human. Everything shifted. Safety was no longer assumed. It had to be engineered, measured, defended. The CMO was no longer a liaison. The CMO became responsible.
Responsible for outcomes. Responsible for engagement. Responsible for making physicians part of a system that increasingly demanded accountability and standardization.
The CNO’s evolution was less abrupt but just as significant. Nursing has always been the operational backbone of the hospital. That never changed. What changed was recognition. As hospitals grew more complex and as staffing, throughput, and patient experience became existential issues, the CNO moved from operational oversight to strategic leadership.
Different histories. Different instincts. Same destination. The CNO and CMO are the chief clinical officers sitting at the table with the CEO. Both roles now sit at the intersection of quality, safety, experience, and cost. And neither can succeed alone.
The Dyad Is Not a Concept. It’s a Relationship.
We sometimes speak about the “dyad” as if it’s a structure. It isn’t. It’s a relationship that either works or doesn’t.
Amanda Shrout, a CNO within LifeBridge Health, said it plainly when I asked her to describe the partnership:
“The ability to rely on one another … when handling difficult situations, when collaboration is needed, when challenges arise.”
Reliance is a strong word. It implies vulnerability. It means there are moments when one leader cannot make the decision alone.
She went on to describe something that often gets overlooked:
“It starts from a place of mutual respect … understanding of the swim lanes and when they intersect … and the ability to see what the other needs.”
That last part matters more than most of us admit.
Not just knowing your role. Not just respecting the other role. But actively trying to see what the other person needs to succeed.
That is where most dyads either take hold — or quietly fall apart.
Alignment Is Necessary. Tension Is Inevitable.
There’s a tendency, especially among new leaders, to equate alignment with agreement. That’s a mistake.
The best CMO-CNO partnerships don’t eliminate tension. They make it useful.
Shrout captured that balance well:
“The alignment is crucial … especially for quality and patient safety … The tension is bound to exist … we are coming at this work from different professional backgrounds.”
Of course we are. Physicians are trained to move quickly, decide despite uncertainty, and own outcomes. Nurses are trained to anticipate, monitor, and coordinate across time. Physicians often focus on the problem in front of them. Nurses see the ripple effects before they happen.
Neither is wrong. But without alignment, those differences become friction. With alignment, they become perspective.
And perspective is what complex systems require.
Where It Breaks Down First
If you want to find the earliest signs of a struggling dyad, don’t look at dashboards. Listen to the units. You’ll hear it in small things.
Pages that go unanswered.
Orders that are technically correct but operationally unrealistic.
Assumptions that “someone else is handling it.”
Shrout didn’t hesitate when asked what physician leaders often miss:
“How important it is that nurses get responses in a timely fashion … Physicians understand that, but the work gets in the way.”
That’s not a character flaw. It’s a system failure.
We tend to treat communication as a professionalism issue. Sometimes it is. More often, it’s structural. Competing priorities. Poor escalation pathways. Tools that don’t match the pace of care.
The dyad must own that. Not just expectations, but design.
Because culture follows structure far more reliably than it follows intention.
What High-Performing Teams Actually Do
Ask what separates strong teams from struggling ones, and you might expect something complex. You won’t get it.
“Transparency. The ability to disagree and come to a collaborative solution.”
That’s it.
Not perfection. Not harmony. Transparency.
It sounds simple until you try to operationalize it. Transparency requires psychological safety, and psychological safety requires leaders who can tolerate discomfort without shutting it down.
We have data to support this. Studies in BMJ Quality & Safety and similar journals have linked open communication and team safety directly to patient outcomes. But most of us don’t need the literature. We’ve all seen the alternative.
Silence is expensive.
When the Dyad Scales
The real test of a dyad is not how the two leaders interact. It’s whether that interaction changes the system.
At Sinai Hospital, a structured approach to multidisciplinary service lines has done exactly that:
“We’ve launched our Quarterly Service Lines… bringing together physicians, APPs, nursing, and a full multidisciplinary team … recognized for improvements in quality, safety, and throughput.”
That didn’t happen by accident. It happened because alignment at the top was translated into structure across the organization. Regular forums. Shared data. Collective ownership.
The dyad stopped being a relationship and became a model.
Shared Accountability Gets Real Fast
It’s easy to talk about shared accountability in theory. It gets much harder when metrics are on the line.
Take sepsis. Everyone knows the drill. Early recognition. Timely antibiotics. Fluid resuscitation. Documentation. But none of it works unless both sides execute.
“Achieving the SEP-1 bundle relies on both the physician and the nurses … we each need to understand our responsibilities and how we rely on each other.”
There is no partial credit. The dyad must make that explicit. Who owns what? Where do the handoffs occur? What happens when something slips?
And just as importantly, how success is shared.
The Quiet Shift in Hierarchy
Something else is happening, slowly but unmistakably.
The hierarchy is flattening.
“We’re moving to a much flatter structure of mutual respect … nurses need trusted partners in our physician colleagues.”
This isn’t about culture for culture’s sake. It’s about safety.
In high-reliability systems, the person closest to the problem has a voice. If that voice is suppressed, the system fails. The dyad sets the tone. Not in policy, but in behavior.
Who gets heard. Who gets dismissed. Who gets backed up.
People notice.
When Things Go Sideways
The most revealing moments are the hardest ones. A patient deteriorates. A plan isn’t clear. Multiple teams converge. Everyone is moving, but not always in the same direction.
This is where communication either saves the situation — or complicates it.
“Unspoken expectations … we assume the other one is doing something … This is why closed-loop communication is essential.”
Closed-loop communication is not elegant. It’s repetitive. It can feel unnecessary — until it isn’t. Say it. Hear it back. Confirm it happened.
Simple. Not optional.
Conflict Isn’t the Problem
Leaders often worry about conflict between physicians and nurses. They shouldn’t.
The absence of conflict is usually a sign of disengagement, not alignment.
“We have to be open to feedback and compromise … there is gray in leadership and in healthcare.”
That gray space is where leadership lives.
Physicians tend to want clarity. Nursing leaders often operate within constraints that resist clean answers. The dyad must bridge that gap. Not by forcing agreement, but by staying in the conversation long enough to reach something workable.
Practical Advice That Actually Works
When I asked what advice she would give a new CMO, Shrout didn’t offer theory. She offered behavior:
“Consistently seek input … invite the CNO to the table … publicly support the CNO… facilitate relationship building.”
None of that is complicated. All of it requires intention. Especially the public support.
Alignment that happens behind closed doors but disappears in front of others isn’t alignment. It’s negotiation. People watch what leaders do far more than what they say.
What Comes Next
The next decade won’t make this easier.
Staffing pressures will continue. Financial margins will tighten. Technology will promise solutions that don’t always fit the workflow.
“We need to remain aligned … whether implementing new technology, changing care models, or redesigning care — we need to move forward together.”
That’s the throughline.
Together.
Amanda Shrout’s leadership reflects that mindset. Amanda Shrout built her foundation in the emergency department, where teamwork is immediate and unforgiving. That perspective carries forward. Direct. Practical. Focused on what works.
Final Thought
Patients never meet the dyad. They don’t know the titles. They don’t see the meetings. They don’t hear the conversations that shape decisions.
But they feel the results. They feel it in how quickly someone responds. In whether the team seems coordinated or scattered.
In whether care feels intentional or improvised.
The CMO and CNO set that tone.
Not with a memo. Not with a metric.
With a relationship.
And like any relationship, it takes work.