What Clinicians Get Wrong Moving to Administration
A co-authored dialogue on the translator role, the identity cost, and why clinical training leaves a wider gap than most expect.
Tracy Young is the co-founder and Chief Operating Officer of Essential Anesthesia Management and a practicing CRNA. He has been on every side of the clinical-executive translation question in this organization. We wrote our sections separately and edited each other's. The conversation was worth having in both directions at once.
The first formal feedback I received as a new executive came at a small, round, four-person table in the corner of a very typical executive office. Dark wood furniture, a desk and table both carrying stacks of papers and file folders, the printout of a PowerPoint deck for the upcoming board meeting laid out in front of the CEO and the COO. I had presented to the Executive Team from that deck the day before. I had walked into the meeting expecting we would talk about the substance of what I had presented. We did not, at least not in the way I expected.
The feedback was not about a decision I had made. It was not about the substance of the deck. It wasn’t about my expertise as the physician executive on the team. It was about how I was showing up in the room. The CEO told me, specifically and warmly, that I needed to slow down. That I needed to strip the technical expertise from my lexicon and my presentation style. That the rest of the senior team and the board needed the space and the time to ingest what I was sharing, sit with it, ask questions, and land on a good decision themselves. The COO did not say much, but she did not need to. She was nodding at the right beats, and I could read in the rhythm of her agreement that this was a conversation the two of them had decided was worth having before it got harder to have.
What I remember as clearly as the words themselves is the feeling of the conversation. This was not criticism. This was the first round of honest, direct feedback from someone who had decided, before I walked in, that the incorporation of it was critical to my success and growth as an executive, and that the same incorporation would bring benefits to the organization as a whole. The two were not in tension. They were the same investment, made twice. I had spent the twenty years before that conversation training to be the most prepared person in the room. The CEO was telling me, in the most generous way he knew how, that I had taken a job that called for a different skill set. A different way of showing up.
That conversation has stayed with me for the better part of a decade. Almost every time I have watched a clinician make the move into administration since, I have recognized a version of the same gap. The version I lived was about cadence and language. For someone else, it might be how meetings get run, or how decisions get framed, or how disagreement gets handled. The shape underneath each of these scenarios is the same. Clinical training rewards being the answer. Executive work, especially across a senior team, is about creating and holding the space that makes the answer-finding system work.
I’d argue that this is the single most important reframe a clinician moving into administration has to make, and the one most clinicians moving into administration miss for longer than they should. At the bedside, expertise is the asset. The patient in front of me benefits from the fact that the clinical team around them has read more, trained more, and seen more of this specific clinical scenario than almost anyone they will encounter on the worst day of their life. In the C-suite, expertise is one of fifteen things in the room, and rarely the most important one. The job is to lead a body of work in which I am the second, fifth, or tenth most expert voice about almost any given decision. The Chief Operating Officer knows the operations better than I do. The Chief Financial Officer knows the economics better than I do. The Chief Development Officer knows the pipeline better than I do. My job is to make sure the right clinical reality is in the room, in language the rest of the team can act on, before they make a decision that will live or die at the bedside.
When I have not done that well — and I have not done it well plenty of times — the failure mode is recognizable. I show up too prepared. I anchor the room early. I leave too little oxygen for the operators and finance leaders to bring their own constraints into the picture. The decision the room reaches is technically correct and operationally fragile at the same time. We end up implementing something the front-line clinicians cannot actually execute, and three months later we are doing the work over again from a worse starting place. Slowing down, stripping the lexicon, and making space turns out to be more than a presentation note. It is the actual mechanism by which a senior team makes good decisions together.
Once a clinician learns to stop showing up as the answer, the question that takes its place is a different one. Not “what should we do,” but “what is the room actually missing that I am uniquely positioned to bring.” The honest answer to that, in my experience, is rarely the technical knowledge the team assumed they were getting when they hired the clinician.
The job most clinicians think they are taking and the job they have actually taken are not the same job. Most assume the role is, at its core, the clinical voice in the C-suite. That description is not wrong. It is incomplete. The function of the job is the translator role, and the translator role is the load-bearing wall of the seat.
What I mean specifically is this: if I cannot carry a clinical concern to a non-clinical COO in language she can act on — meaning she understands the operational shape, the financial implication, the workforce signal, and the decision she is being asked to make — I have not done my job, no matter how well I have understood the clinical concern myself. Conversely, if I cannot bring an operational reality back to a clinical lead in language he can act on — meaning he understands why a contract distinction changes how the OR director feels about a six o’clock Friday case, or why a payer mix affects which staffing model is sustainable at his site — I have not done that job either. The clinical voice in the room does not stop at telling the truth about the clinical work. It keeps going, into making the truth usable to people who do not live inside that work day to day.
One of the clearest examples I can recall sat at the intersection of ability to pay and non-emergent but life-saving care. Cancer treatment, transplant work, the kinds of cases where insurance coverage shapes whether a patient has a path forward. For several rounds in that conversation I did not create enough space to hold the real question the organization was sitting on. The clinical team was carrying the moral injury of saying no, or watching the system say no on their behalf, to patients who did not have a financial path to long-term management of their care. The no-margin-no-mission line everyone in the room had already absorbed was real and unmoving. The conversation kept landing in one of those two corners and breaking against it.
The translator move I eventually learned was not to choose a corner. It was to hold the room long enough for the finance team and the clinical team to land somewhere together — a place where the conversation shifted from whether the organization could afford to say yes to how a conditional yes could be structured: what the program could commit to upfront, what the patient could demonstrate over time, and where the clinical and financial risk would sit between those two realities. The lead message to a patient could be options rather than a no, and patient autonomy could carry the weight of the decision. That message did not exist in the room before someone created the space for it. The seat I was in was the seat that was supposed to do that work.
The last one took me the longest to see clearly, and I think it is the one most clinicians moving into administration handle without ever putting language to it. It is the question of what to do with the clinical practice itself. I still pick up a few clinical shifts a month. I do that because the patient interactions ground me, because the teams I work alongside on those days are one of the strongest reminders I have of what we are building EAM around, and because the clinical specifics keep me current in a way that helps me lead the company. Those shifts are additive. They make me better at the executive work, not worse.
I have also watched clinicians in administrative roles hold onto a clinical practice for a different reason. The executive role feels uncomfortable. The clinical role feels familiar. The hours in clinic or in the OR become a way to recover the identity that the new seat is asking them to reshape. That is the protective version of the same arrangement, and it does not announce itself as protective at the time. It looks like commitment. It looks like staying connected to the work. The candid take on it usually requires someone outside the situation to label it, and the person hearing it named almost always pushes back the first time, because the protective version of the practice is doing real psychological work for the clinician holding onto it. What it is doing, specifically, is grieving. Or, in the language I tend to use, holding onto something the move into the executive seat carries a real fear of losing. Standing in the clinical hierarchy, the rhythm of being known by what your hands do, the patients themselves. Those losses are real, and they are not small. The protective version is the version that has not figured out how to live with the loss yet.
I am not arguing that clinicians in executive roles need to give up their practice. I am arguing that clinicians in executive roles need to be honest with themselves about which version they are running. I’m saying out loud that the job requires a certain amount of straddling the fence between the two worlds, but in a way that recognizes and capitalizes on that position. And I am arguing that the leaders who hold the development relationships inside those organizations — the CEOs, the co-founders, the senior executives who have made the transition and remember what it cost them — need to make it safe to have that conversation out loud, so that the protective version can become additive or fall away.
You and I came at this seat from opposite ends of the same problem. You built up through the firm — a clinician who became the operational executive, then a co-founder, then a partner who has been on every side of the clinical-executive translation conversation in this organization. I came in from outside it, after twenty years of clinical practice and fifteen of executive work in large health systems where the seats and the systems looked very different from the one we are running together now. The thing we agree on, before any of the rest, is that clinical training does not prepare a person for what these jobs actually ask. The other thing I have come to believe, watching it from both sides now, is that the transition does not happen alone. The CEO and COO at the table I described in the opening had decided, before I walked in, that the incorporation of their feedback mattered both to my growth and to the organization. The leaders who make these transitions possible are the ones who surround themselves with people who are better and brighter than they are. And then they do not stop there. They name the gap before it becomes a pattern, and they stay in the room after the feedback is given. The longer answer to all of this, and the part I am most curious to read, is the half you are about to write.
— David
---
David,
Reading your half, the phrase that kept coming back to me was your idea that clinicians are trained to become “the answer,” while leadership requires us to create the conditions where the best answers can emerge from the group. I think that is exactly right. And I think it explains why so many exceptional CRNAs, and clinicians more broadly, struggle when they first move into administrative leadership. The skill sets overlap far less than people assume.
My own journey from clinical CRNA to founder, business owner, and senior executive has been a slow evolution over more than 20 years. The honest truth is that the evolution is still happening. Daily.
As CRNAs, we talk about being lifelong learners clinically. We accept that mastery requires continuous development of knowledge, judgment, and technical skill. But many clinicians underestimate what the transition into administrative leadership requires, and that underestimation can make the transition far more difficult than it needs to be.
I think of the Dunning-Kruger curve, where early success can feel like mastery just before the floor falls out. Clinicians have lived this phenomenon during training, during early practice, and during the long arc of mastering a craft. We somehow fail to apply the same humility when moving into leadership. We assume that because we were excellent clinically, leadership will come naturally.
It usually does not.
One of the first things I noticed was the loss of the immediate feedback loop we get in clinical anesthesia. As a CRNA, I was used to making a decision and seeing the physiologic response in seconds or minutes. The work is tangible. The feedback is immediate. There is comfort in that. There is certainty in that. There is identity in that.
Leadership is much messier.
The other early lesson, after starting my own company and growing it, was that my personal ability to perform anesthesia became progressively less important to my success as an executive. That sounds strange to say out loud in a profession where clinical excellence is rightly revered, but it is true. The larger the company grew, the more the job became about building systems, developing people, creating alignment, and helping teams solve problems together. Scale is impossible without that network. No founder can be the answer to every problem and have it work.
The move from clinical CRNA to leader is really a move from personal execution to organizational execution. That transition is uncomfortable for clinicians because we were trained and rewarded for being individually excellent. Leadership rewards patience, communication, emotional control, long-term thinking, the ability to simplify complexity, and the ability to create buy-in instead of being correct.
That journey for me was slow, not linear, and not always graceful. I fought it at times. Then the weight of the role landed in a way I could not push back against, and I understood that leadership was not about having all the answers. It was about helping the organization become capable of finding better answers together.
I have watched incredibly smart CRNAs fail in leadership roles because they believed their clinical expertise alone would carry them. Clinical expertise gets you invited into the room. What determines whether you remain effective is your ability to build trust, align people, and translate complexity into action.
Your point about the translator role resonated with me because it may be the core function of clinicians in healthcare leadership. Clinicians often underestimate how little operational, financial, and organizational context exists outside their lane. Executives sometimes underestimate the realities and constraints of clinical care. Someone has to bridge that gap, and clinicians who learn systems thinking and the broader environment are uniquely positioned to do it.
As a COO, I have often translated in the opposite direction of the examples you described. I understand why a facility administrator is focused on subsidy structure, payer mix, staffing efficiency, or contract language. I understand why a CFO worries about labor expense growth or why operations is trying to standardize workflows. But if those realities reach clinicians without context, trust deteriorates quickly.
The clinician hears: “They only care about money.”
What they often do not see is that sustainability is what allows the mission to continue in the first place. Likewise, executives sometimes view clinician concerns as resistance or emotion, when in reality those clinicians are sending signals from the bedside that operators and finance leaders cannot see from conference rooms, spreadsheets, or board decks.
The clinical leaders who become effective are the ones who move fluidly between those worlds without losing credibility in either. That requires humility, because both sides will correct you regularly if you are listening honestly.
Early in my leadership journey, I struggled to build that bridge. Even now, the bridge-building is most of the work. Finding outcomes hospital administrators can support while also advocating for the success and stability of the clinical team is central to operational leadership.
When done well, that bridge creates stability. Stability in staffing. Stability in patient care. Stability in facility relationships. Stability in financial performance.
I have many examples from the early days of YPS Anesthesia where a department of CRNAs and physicians needed support, hospital administration was on a different page, and the department was at risk of fragmenting. The issue was financial in some cases, structural in others, relational or communication-based in others. Learning to find an outcome where everyone could move forward together has been one of the most gratifying parts of leadership, and one of the most important drivers of business success. Many organizations fail not because the clinicians are poor or the administrators unreasonable, but because no one translated between the two.
This is why the transition from clinical practice to administrative leadership requires more than ambition. It requires humility, curiosity, and the discipline to stop proving you are the smartest clinician in the room and start proving you can help the room make better decisions.
The goal is no longer to personally deliver the perfect anesthetic. The goal is to build the teams, systems, and cultures where excellent care happens reliably, repeatedly, at scale.
That is the real transition.
Not from clinician to administrator. From expert doer to builder of people, systems, and trust.
For those willing to make that transition, the impact extends far beyond any single room, any single case, or any single day in practice.
— Tracy
Tracy Young's version of this piece appears on his Substack at tracypyoung.substack.com.
Past the Door’s paid tier opens Monday, June 8. The first paid post lands Friday, June 12. Founder pricing — $6/month or $60/year — runs through July 7.





Oh boy, do I feel seen in this article. Well written.
Outstanding!!