The title may change as you grow. The work simply becomes more complex.

Save this as a reminder: leadership development is not one promotion. It is a progression in responsibility, perspective, and impact.

HLR™
Ideas that shape healthcare leadership.

The mistake is assuming excellence in one automatically makes you effective in the others.

A brilliant strategist who cannot execute creates plans.

A relentless operator without vision optimizes yesterday.

A culture builder without accountability creates comfort without performance.

A visionary who cannot bring people through change creates ideas without adoption.

Leadership maturity is the ability to know which role the moment requires—and move between them without losing the larger system.

Which of the five comes most naturally to you? And which one are you actively developing?

Save this for your next leadership reflection—or send it to someone stepping into a bigger role.

Healthcare Leadership Review™
Ideas That Shape Healthcare Leadership

#HealthcareLeadership #LeadershipDevelopment #HealthcareExecutives #SystemsThinking #OrganizationalLeadership

“Protect your people” is one of leadership’s most repeated pieces of advice.

It is also one of its most misunderstood.

Protection matters. When someone is unfairly blamed, publicly humiliated, disrespected, or caught in organizational politics they cannot reasonably navigate alone, leadership should show up. When a decision belongs to the leader, the leader should own it. When a team member has done good work and someone else takes the credit, the leader should correct the record.

People remember who stood beside them when doing so carried a cost.

But protecting people is not the same as protecting them from accountability.

Protect their dignity, not their immunity.

That distinction is harder to practice than it sounds.

Protection without accountability can become favoritism. Accountability without dignity can become fear.

Leadership requires enough judgment to know the difference.

Psychological Safety Is Not Immunity

Consider what happens when someone makes a significant mistake.

One manager immediately distances themselves:

“That wasn’t my decision.”

Another rushes to shield the employee from every consequence:

“Don’t worry. I’ll handle it.”

Neither response creates a healthy organization.

The first protects the leader at the employee’s expense. The second protects the employee at accountability’s expense.

There is a third response:

“We made a mistake. We are going to understand what happened, fix what needs to be fixed, and learn from it. I will not allow you to be publicly humiliated for it—but I will expect you to take responsibility for your part in it.”

That is protection with standards.

Amy Edmondson defined psychological safety as a shared belief that a team is safe for interpersonal risk-taking. In practice, that means people are more able to speak up, ask questions, admit uncertainty, raise concerns, and acknowledge mistakes.

Psychological safety is not a substitute for high standards.

It creates conditions in which candor, learning, and accountability can actually work—because people are more likely to surface problems before those problems become larger.

The goal is not to make accountability disappear.

It is to make truth-telling possible.

Healthcare Learned This Lesson Early

Healthcare offers one of the clearest illustrations of why this distinction matters.

In Amy Edmondson’s earlier research involving hospital nursing units, higher-performing teams appeared to report more medication errors. The counterintuitive finding did not necessarily mean those teams made more mistakes. It suggested that people in better-functioning units were more willing to acknowledge and discuss errors when they occurred.

That observation helped inform Edmondson’s later work on psychological safety, which she defined as a shared belief that a team is safe for interpersonal risk-taking.

In healthcare, that distinction carries consequences far beyond culture.

A clinician who can say, I made a mistake, I need help, or something here does not look right gives the organization information it can act on.

Silence removes that opportunity.

A culture that humiliates people for surfacing problems can teach them something much more dangerous:

Silence is safer than honesty.

This does not mean every error should be treated the same way.

An honest mistake made while exercising reasonable judgment is different from a capability gap. A capability gap is different from repeated negligence. Repeated negligence is different from reckless behavior or deliberate misconduct.

Good accountability recognizes those distinctions.

Healthcare’s concept of Just Culture offers an operational model for that balance. Rather than choosing between blame and a consequence-free environment, Just Culture asks organizations to examine both the system and the behavioral choices involved. Organizations remain responsible for the systems and conditions they create; individuals remain accountable for choices they could reasonably control.

The leadership translation is straightforward:

Protect the person’s dignity. Examine the system honestly. Hold people appropriately accountable for what they could reasonably control.

The standard should not be:

“Nothing bad happens when you make a mistake.”

It should be:

“You can tell us the truth about what happened, and we will respond fairly.”

That is a much more demanding culture to build.

Your Team Is Watching

Trust is easy to talk about when everything is working.

Its real test arrives when something breaks: a deadline is missed, a customer complains, a patient experience goes poorly, an executive is angry, or someone simply makes the wrong call.

People notice what leadership does next.

If the immediate response is to find someone to blame, employees learn that bad news should be managed before it travels upward.

If leaders rewrite their involvement in decisions once those decisions become unpopular, employees learn that ownership is conditional.

If initiative is celebrated when it succeeds but punished whenever reasonable judgment produces a bad outcome, people learn to wait for permission.

Organizations teach people what is safe through consequences, not slogans.

That does not mean a leader should defend everything their team does. Sometimes the employee is wrong. Sometimes criticism is justified. Sometimes a hard conversation is exactly what leadership requires.

The question is whether that conversation preserves the person’s dignity while addressing the behavior honestly.

Sometimes Protection Is the Hard Conversation

There is a version of leadership that confuses kindness with avoidance.

A manager sees a performance problem but wants to preserve the relationship, so the conversation gets postponed.

Then postponed again.

The employee assumes everything is fine.

Eventually, the problem becomes serious enough that what could have been developmental feedback becomes a consequential performance conversation.

That was not protection.

It was avoidance disguised as kindness.

Sometimes one of the most protective things a leader can do is tell someone something they do not particularly want to hear while there is still time to do something about it.

“I believe you are capable of better than this.
Here is where you are falling short.
Here is what needs to change.
And I am going to help you get there.”

Accountability delivered with dignity is not the enemy of psychological safety.

Done well, the two reinforce one another: people understand where the standards are, and they know that falling short does not automatically cost them their standing as a human being.

Trust Has Reciprocal Responsibilities

There is an obvious danger in talking about loyalty running both ways.

A bad manager can turn loyalty into a demand for silence.

Protect the team becomes don’t challenge me.

Have my back becomes hide what happened.

That is not loyalty.

It is coercion.

No employee owes a leader silence about unsafe behavior, misconduct, unethical decisions, patient-safety concerns, harassment, discrimination, or abuses of authority.

Loyalty does not supersede integrity.

In fact, sometimes the person willing to tell a leader an uncomfortable truth is demonstrating more commitment to the team than the person who quietly agrees.

Healthy reciprocity asks something different.

When a leader consistently advocates for people, gives them credit, owns decisions that belong to them, provides honest feedback, creates opportunities, and protects them from unfair treatment, team members carry responsibilities to the relationship too: honesty, good faith, accountability, and regard for the collective.

High-trust teams eventually move beyond asking:

“Will my manager protect me?”

They begin asking:

“How do we protect the integrity of this team?”

That is a more mature form of loyalty.

Protect Their Dignity

Perhaps the leadership principle was never really protect your people.

It was:

Protect their dignity.

Protect them from unnecessary humiliation.

Protect them from organizational politics they cannot reasonably navigate alone.

Protect them from blame for decisions they did not make.

Protect their ability to tell you uncomfortable truths.

Protect their opportunity to recover from honest mistakes.

Protect their right to receive credit for their work.

Protect them from abusive behavior.

But do not protect them from feedback.

Do not protect them from standards.

Do not protect them from responsibility.

Do not protect them from fair, proportionate accountability when their choices warrant it.

And do not confuse loyalty with pretending something did not happen.

The objective of leadership is not to create an environment where nobody experiences discomfort.

It is to create one where people can take risks, tell the truth, make mistakes, receive difficult feedback, take responsibility, improve—and still know they will be treated with dignity.

That is a stronger promise than:

“I’ve got your back.”

It says:

“I’ve got your back. And I expect you to have ours.”

That is how trust becomes culture.

Sources & Further Reading

Edmondson, Amy C. (1999). “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly, 44(2), 350–383.
Foundational research defining psychological safety as a shared belief that a team is safe for interpersonal risk-taking and examining its relationship with learning behavior.

Association of American Medical Colleges — “Amy Edmondson: Psychological safety is critically important in medicine.”
Used for historical context on Edmondson’s hospital medication-error research and the interpretation of differences in error reporting among nursing units.

Agency for Healthcare Research and Quality — Apply CUSP / Just Culture materials.
Used for the healthcare concept of shared accountability, including organizational responsibility for systems and individual accountability for behavioral choices.

AHRQ Patient Safety Network — “Culture of Safety.”
Used for healthcare-specific context on Just Culture, transparency, accountability, and organizational responses to safety events.

Editorial note: The leadership interpretations, examples, and conclusions in this article are Healthcare Leadership Review™ editorial analysis informed by established research on psychological safety and healthcare Just Culture.

Healthcare Leadership Review™
Ideas That Shape Healthcare Leadership

A project misses its deadline.

Someone gets blamed.

Turnover rises.

Recruiting is told to fill positions faster.

Employees stop speaking up.

Leadership schedules a workshop on psychological safety.

Customers complain about slow service.

Management tells employees to work faster.

Sales decline.

The sales team gets reorganized.

Organizations are remarkably good at responding to what they can see.

We are less disciplined about asking what produced it.

That distinction sits at the heart of systems thinking—and, increasingly, at the heart of good leadership.

Systems thinking examines how the parts of an organization influence one another—and how incentives, structure, information, authority, and consequences combine to shape behavior over time.

The practical shift is straightforward.

Instead of asking:

Who caused this?

Ask:

What made this outcome possible—or even likely?

Instead of:

How do we fix this problem?

Ask:

What happens elsewhere when we fix it?

And instead of:

Why aren’t our people performing?

Ask:

What conditions have we created in which they can perform well?

Those are harder questions.

They are also better ones.

The Problem Behind the Problem

Most organizational problems arrive disguised as isolated events.

A resignation.

A missed target.

A failed launch.

A difficult manager.

A disengaged team.

A customer complaint.

And sometimes the explanation really is local.

Someone made a poor decision.

A leader failed to lead.

An employee was wrong for the role.

Systems thinking should never become an intellectual excuse for avoiding individual accountability.

But neither should accountability become an excuse for avoiding the system.

Because when similar failures recur despite replacing the people involved, recurrence becomes information.

Imagine three managers occupying the same role over five years.

All three struggle with retention.

At some point, asking What’s wrong with these managers? becomes less useful than asking:

What is it about the role, workload, authority, incentives, expectations, structure, or culture that makes success so difficult?

The manager still matters.

But now we are looking at the whole picture.

That is the first discipline of systems thinking:

Do not confuse the most visible part of a problem with its cause.

Why the Obvious Fix Can Make the Problem Worse

Suppose a project is repeatedly late.

Leadership responds by asking for more reporting.

More status meetings.

More approvals.

More checkpoints.

The intention is reasonable: increase visibility and control.

But what if the additional reporting consumes the execution time the team is already short of?

What if more approval points slow decisions?

What if employees begin waiting for meetings rather than resolving issues themselves?

The intervention can appear sensible locally while making the larger system slower.

That is one of the central insights of systems thinking:

An action does not end where it is taken.

The first-order effect may be desirable.

The second-order effect may not be.

A cost reduction can create a service problem.

A productivity target can increase rework.

An approval designed to reduce risk can slow innovation.

A restructuring can solve today’s coordination problem and create tomorrow’s information problem.

The intervention worked.

And still made the organization worse.

Both can be true.

Think About a Bathtub

There is a simple way to understand this without turning systems thinking into an academic exercise.

Imagine a bathtub.

Water comes in through the faucet.

Water leaves through the drain.

If the tub keeps overflowing, you could spend all day mopping the floor.

That may be necessary in the moment.

But it is not much of a strategy.

Eventually you have to ask:

How quickly is water coming in?

How quickly is it leaving?

Is the drain blocked?

Did somebody turn the faucet higher?

Are we fixing the floor while ignoring what is filling the tub?

Organizations work like this more often than leaders realize.

Think about turnover.

People leave the organization.

Recruiting brings people in.

If departures continue to outpace hiring, leadership can demand greater recruiting productivity indefinitely.

But perhaps the real problem is not the speed at which people enter.

Perhaps it is the rate at which they leave.

Or the quality of onboarding.

Or manager capacity.

Or compensation.

Or the amount of time it takes to make an offer.

Or a job that has quietly become unsustainable.

Systems thinking encourages leaders to examine what is moving into and out of the problem—and what is influencing both.

Healthcare Makes This Especially Visible

A health system facing persistent vacancies may increase recruiter activity, add another sourcing tool, offer referral bonuses, or push harder on time-to-fill.

Those interventions may help.

But suppose the real constraint sits somewhere else.

Compensation has fallen behind the market.

Interview scheduling takes two weeks.

Hiring managers delay decisions.

Onboarding creates unnecessary friction.

The schedule candidates are being offered no longer fits the labor market.

Experienced clinicians are leaving faster than recruiters can replace them.

Recruiting harder may improve one part of the system while leaving the system itself unchanged.

The better question is not simply:

How do we hire more people?

It is:

What is producing the gap between the workforce we need and the workforce we can attract, hire, develop, and retain?

That changes the problem completely.

It also changes what leadership is responsible for.

Recruiting may own sourcing.

It does not own compensation strategy, managerial quality, workload, advancement opportunities, operational delays, or the experience employees have after they join.

When the same hiring objections and retention problems continue appearing, leaders should stop treating each vacancy as an isolated recruiting event.

The vacancy is the event.

The workforce model may be the system.

Organizations Don’t Run on Strategy Alone

We like to imagine organizations moving neatly from strategy to execution.

Reality is messier.

Strategy influences incentives.

Incentives shape behavior.

Behavior affects culture.

Culture affects what people feel safe saying.

That determines what information reaches leadership.

Information influences decisions.

Decisions shape execution.

Execution produces results.

And those results influence the next strategy.

The organization is constantly talking back to itself.

This is why smart people inside well-funded, well-intentioned organizations can repeatedly produce outcomes nobody wanted.

The components may be excellent.

The relationships between them may not be.

A world-class team inside a dysfunctional decision structure can look mediocre.

A capable employee working under conflicting incentives can look inconsistent.

A thoughtful manager operating with an impossible span of control can look ineffective.

Change the context and sometimes the behavior changes with it.

That does not mean people are powerless.

It means performance is rarely produced by people alone.

Systems Are Human

The language of systems thinking can sound mechanical.

Structures.

Flows.

Feedback.

Inputs.

Outputs.

But organizational systems are experienced by human beings.

A reporting structure influences who feels heard.

An incentive influences what someone prioritizes when objectives compete.

An approval process determines whether initiative feels worthwhile.

A performance-management system affects whether an employee experiments or plays safe.

A leader may never say:

Don’t take initiative.

But require seven approvals for every meaningful decision and the system communicates the message perfectly.

An organization may never say:

Don’t bring us bad news.

But punish the first person who surfaces a problem and people will learn.

Systems teach.

Usually without saying a word.

Watch What the System Rewards

If you want to understand an organization, do not begin with the values painted on the wall.

Watch what happens on Monday morning.

Who gets promoted?

Who gets heard?

What gets funded?

Which mistakes are tolerated?

Which ones become career-ending?

What happens when someone disagrees with a senior leader?

What happens when someone misses a target for the right reasons?

What happens when someone hits it for the wrong ones?

Organizations reveal their priorities through consequences.

A company can say collaboration matters while rewarding only individual performance.

It will get competition.

A company can say long-term thinking matters while evaluating leaders almost entirely on short-term results.

It will get short-term behavior.

A company can celebrate innovation while treating every failed experiment as evidence of poor judgment.

It will get caution.

People are remarkably good at learning unwritten rules.

Then leadership becomes frustrated when employees behave according to them.

Consider an organization that says collaboration matters while measuring every function independently.

Marketing is rewarded for lead volume.

Sales is rewarded for closing.

Operations is rewarded for efficiency.

Customer success is rewarded for retention.

Each team can optimize its own metric and still make the organization perform worse.

Marketing can produce leads sales considers poor quality.

Sales can close customers operations cannot serve efficiently.

Operations can optimize cost in ways that make the customer experience worse.

Customer success inherits the consequences.

And every function can plausibly argue that it did what leadership asked.

That is one of the uncomfortable lessons of systems thinking:

Rational behavior inside individual parts of an organization can produce irrational outcomes for the whole.

The solution is not another teamwork workshop.

Leaders have to examine the incentives, handoffs, information flows, and measures that make siloed behavior perfectly rational.

The Feedback Loop Leaders Don’t See

Now consider a manager who does not trust the team.

Oversight increases.

Employees learn that independent decisions carry risk, so they begin seeking more approval.

The manager sees fewer independent decisions.

That becomes evidence that the team cannot operate autonomously.

Oversight increases again.

Both the manager and the employees are participating in the pattern.

But the leadership insight is that the system has begun reinforcing the very behavior everyone says they want to eliminate.

Nobody necessarily intended to create dependency.

But the system did.

This is what a feedback loop looks like in organizational life.

Results do not simply appear and disappear.

They often return to influence the conditions that produced them.

That is why recurring problems deserve a different level of attention.

Why Quick Fixes Feel So Good

Symptoms are visible.

Systems usually are not.

The customer is angry today.

The project is late today.

The employee resigned today.

Revenue is down today.

Leaders are rewarded for acting.

So action feels responsible.

Announce something.

Reorganize something.

Hire someone.

Fire someone.

Launch an initiative.

Add a meeting.

Introduce another metric.

Sometimes decisive action is exactly what leadership requires.

Systems thinking is not an argument for endless diagnosis.

It is an argument for better diagnosis before repeated intervention.

Because when leaders respond to every recurring problem as though it were appearing for the first time, organizations become extremely busy without necessarily becoming better.

Before You Solve It, Map It

When a persistent problem appears, leaders should delay prescription long enough to understand what surrounds it.

Not indefinitely.

Long enough.

Ask what keeps producing the outcome.

Ask where work slows.

Ask what information people have when they make decisions.

Ask what they are rewarded for doing.

Ask what they are afraid of doing.

Ask where authority actually sits.

Ask what happens immediately after an intervention—and what happens six months later.

Ask who benefits from the current arrangement.

Ask who absorbs its hidden costs.

And perhaps the most revealing question:

If we changed none of the people involved, what would we need to change to produce a different outcome?

That question forces leadership away from personality and toward architecture.

It does not assume the person is innocent.

It simply asks whether replacing the person is enough.

Accountability Still Matters

There is a danger in taking systems thinking too far.

If everything is systemic, nobody is responsible.

That is not serious leadership.

People make choices.

Managers abuse authority.

Employees underperform.

Executives sometimes make poor decisions despite having good information and reasonable incentives.

A systems perspective should not eliminate accountability.

It should make accountability more precise.

There are two questions, not one:

What did the individual do?

And:

What conditions shaped, enabled, rewarded, tolerated, or failed to prevent it?

Leaders should be capable of asking both.

Sometimes the answer is to change the person.

Sometimes it is to change the system.

Often it is some combination of the two.

The system explains behavior. It does not automatically excuse it.

Leadership Is System Design

This leads to a more demanding definition of leadership.

Leadership isn’t merely getting people to perform. It is creating conditions in which good performance becomes more likely.

What information can people see?

What authority do they have?

What behavior gets rewarded?

What creates unnecessary friction?

What happens when someone makes an intelligent mistake?

How quickly can bad news travel upward?

Who can challenge whom?

How much autonomy exists at the edge of the organization?

What does the company measure?

What does it ignore?

These decisions form an invisible architecture around human behavior.

Senior leaders are designing that architecture whether they realize it or not.

Every incentive is design.

Every reporting line is design.

Every meeting is design.

Every approval threshold is design.

Every metric is design.

Every tolerated behavior is design.

Even doing nothing is design, because the existing system remains in place.

The higher a leader rises, therefore, the less the job can be about personally solving every problem.

The work increasingly becomes creating an organization capable of solving problems without waiting for the leader.

The Best System Does Not Remove Humanity

There is another trap.

Once leaders discover systems thinking, they can become obsessed with optimization.

Every inefficiency becomes something to eliminate.

Every variation becomes something to standardize.

Every behavior becomes something to measure.

But organizations are not machines.

They are communities of human beings trying to coordinate around a purpose.

Good systems do not remove judgment.

They make room for it.

They do not eliminate autonomy.

They support it.

They do not try to predict every exception.

They create enough clarity for people to navigate exceptions intelligently.

And they do not assume human beings exist to serve the system.

The system exists to help human beings accomplish something together that they could not accomplish alone.

That distinction matters.

An efficient system that exhausts its people is not a good system.

A profitable system that destroys trust is not a healthy system.

A fast system that consistently produces poor decisions is not high-performing.

Optimization without humanity eventually becomes another form of failure.

Change the Conditions

Perhaps this is the most useful leadership lesson in systems thinking.

When you want different behavior, do not only ask people to behave differently.

Change the conditions surrounding the behavior.

If you want candor, examine what happens to people who disagree.

If you want speed, examine where authority sits.

If you want collaboration, examine what gets rewarded.

If you want innovation, examine what happens when an intelligent experiment fails.

If you want accountability, examine whether ownership is actually clear.

If you want better decisions, examine how information moves.

If you want people to think like owners, examine whether they are trusted like owners.

Culture rarely changes because leadership announces a new culture.

Behavior changes when different behavior becomes possible, rational, and safe enough to repeat.

Repeated behavior eventually becomes culture.

The Question Behind the Question

The next time something goes wrong, there will be pressure to identify the problem quickly.

Sometimes you should.

But when the problem feels familiar, resist that instinct for a moment.

Look one level deeper.

The missed deadline may be the problem.

Or it may be telling you something.

The resignation may be the problem.

Or it may be telling you something.

The failed initiative.

The difficult meeting.

The customer complaint.

The declining engagement score.

The manager everyone struggles to work with.

Treat the event seriously.

Hold people accountable where accountability belongs.

Then ask:

What is this event revealing about the system around it?

Because the purpose of systems thinking is not to absolve people.

It is to see more clearly.

And perhaps that is ultimately what leadership requires.

Not having an answer for every problem.

Not finding someone to blame.

Not redesigning everything every time something goes wrong.

But developing the judgment to recognize the difference between an isolated failure and a recurring pattern.

Between a people problem and a context problem.

Between a symptom and a cause.

Between an intervention that makes us feel productive and one that actually changes what happens next.

Leaders do not merely solve problems inside organizations.

They shape the systems that make certain problems more—or less—likely to recur.

And when they finally intervene, they do not just ask:

How do we fix this?

They ask the harder question:

What do we need to change so that this problem becomes less likely to happen again?

That is the shift.

From managing incidents to understanding patterns.

From correcting behavior to examining conditions.

From repeatedly fixing problems—

to building better systems.

Sources & Further Reading

MIT xPRO — System Thinking. MIT’s professional-education materials examine systems as interconnected wholes, with attention to relationships among components, patterns, complexity, and the effects changes can have on overall system performance.

Berman, Adam. “Bringing a Systems Approach to Leadership.” MIT Sloan School of Management, November 18, 2020. A practitioner-oriented discussion of organizational context and the ways structures and systems influence behavior and culture.

Bansal, Tima, and Julian Birkinshaw. “Why You Need Systems Thinking Now.” Harvard Business Review, September–October 2025. Examines interdependence, secondary effects, and the unintended consequences that can emerge when leaders intervene in complex systems.

Senge, Peter M. The Fifth Discipline: The Art & Practice of the Learning Organization. Doubleday/Currency, 1990; revised edition, 2006. A foundational work connecting systems thinking with organizational learning, mental models, shared vision, and leadership.

Meadows, Donella H. Thinking in Systems: A Primer. Chelsea Green Publishing, 2008. A foundational introduction to feedback, delays, resilience, system behavior, and leverage points.

Sterman, John D. Business Dynamics: Systems Thinking and Modeling for a Complex World. McGraw-Hill, 2000. A comprehensive treatment of system dynamics, managerial decision-making, feedback, complexity, and unintended consequences.

Editorial Note

This article draws on established scholarship and current leadership thinking in systems analysis and organizational design. The workplace examples, healthcare application, interpretations, and leadership conclusions are HLR editorial analysis intended to make the discipline accessible to practicing leaders rather than reproduce a formal systems-dynamics curriculum.

HEALTHCARE LEADERSHIP REVIEW™

IDEAS THAT SHAPE LEADERSHIP

Upgrade your subscription

Healthcare professionals often treat networking as an event.

A conference.

A LinkedIn message.

A coffee.

A favor requested when a role opens, a referral source goes quiet, or a partnership suddenly becomes urgent.

That is too late.

In healthcare, many of the relationships that eventually produce growth are built long before they appear on a dashboard. A referral is the visible result of confidence. A difficult hire is often easier because familiarity existed before the requisition. A strategic partnership can look sudden from the outside even when it was built through months of shared context, introductions, problem-solving, and follow-through.

Healthcare growth is relational before it becomes transactional. And increasingly, it is operational before it becomes scalable. That distinction matters because healthcare is becoming more interconnected, not less. The work increasingly depends on coordinated relationships across providers, payers, schools, community organizations, technology partners, and talent markets.

Those are not networking activities. They are relationship systems.

A Healthcare Relationship Operating System is the set of routines, ownership structures, intelligence practices, and operating measures an organization uses to create, sustain, and activate trust at scale.

That difference changes how leaders build and manage relationships.

A CRM Full of Names Is Not a Relationship Strategy

Most organizations already have contacts. Sales has a CRM. Recruiting has candidate databases. Executives have LinkedIn networks. Physician liaisons have referral lists. Community-relations teams have partner directories. The problem is rarely the absence of names.

The problem is whether anyone understands the strength, relevance, ownership, and next action attached to those relationships.

An executive with 5,000 LinkedIn connections but no credible relationships with referral leaders, educational partners, community organizations, payer decision-makers, physician influencers, or future talent does not have a relationship advantage. They have a directory.

A relationship operating system asks a more useful set of questions:

• Who do we know?

• Who trusts us?

• Where have we created value?

• Where are we overdependent on one relationship?

• What information moves through the network?

• Which relationships connect directly to strategic priorities?

• And when an opportunity appears, can we move from conversation to action?

That is relational capacity. And like any other organizational capability, it can be built deliberately.

The Relationship Asset Model

I do not like reducing human relationships to scores. But organizations do need a disciplined way to understand whether strategically important relationships are healthy. Five dimensions are useful.

Relevance

Does the relationship connect to a current or emerging strategic priority? That might mean referral growth, market entry, a workforce shortage, payer strategy, community access, a new service line, or an operational need. Not every relationship needs to be commercially useful. But leaders should understand which ones matter to which problems.

Trust

Would the person take the call? Would they share early context? Would they put their reputation behind an introduction? Would they tell you the uncomfortable thing before it became public? Trust is the difference between having access to someone and actually having a relationship with them.

Reciprocity

Have you created value before asking for value? A relationship becomes fragile when every interaction contains an ask. Good networks are built through information, introductions, support, advocacy, and follow-through long before they become transactional.

Access

Does the relationship create meaningful proximity to a market, decision, community, talent pool, or source of information? Access is not status. A trusted nursing-program director may matter more to your workforce strategy than a hospital CEO. A local community leader may understand an access problem better than anyone in the executive suite.

Activation

Can the relationship move? Can both sides translate goodwill into an introduction, referral, hiring partnership, shared initiative, or problem-solving conversation when the moment arrives? That final dimension separates a relationship that feels warm from one capable of producing coordinated action.

The Trust-to-Transaction Ladder

One of the mistakes healthcare professionals make is trying to accelerate relationships past the stage they have actually earned. You meet someone at a conference. Two weeks later:

Can you introduce me to your CEO?

Send us referrals.

Consider this candidate.

Partner with us.

People feel the leap.

A healthier relationship progression looks more like this:

Visibility → Credibility → Trust → Collaboration → Transaction → Advocacy

Visibility

They know who you are. That may come from professional visibility, mutual contacts, events, shared communities, or repeated exposure.

Credibility

They understand what you know, what you do, and whether your judgment is useful. This is where thoughtful visibility matters. Not constant posting. Useful contribution.

Trust

They believe you will follow through and handle their reputation carefully. That matters enormously in healthcare because referrals, introductions, and recommendations carry reputational risk.

Collaboration

You have done something useful together. An introduction. A shared event. A working session. A candidate referral. A market insight. A community initiative. A problem solved.

Transaction

A referral, partnership, hire, contract, agreement, or project occurs. This is where most conventional business-development systems start measuring. The relationship began much earlier.

Advocacy

They bring your name up when you are not in the room. That is the real asset. A strong relationship does not merely respond when you ask. It creates opportunity before you know to ask.

The Network Is a Portfolio, Not a Funnel

Another mistake is treating every relationship as though it should produce the same outcome. It should not. Healthcare leaders need different relationship systems operating at different time horizons.

Revenue and Referral Relationships

Physicians. Discharge planners. Practice leaders. Employer groups. Payers. Community providers. These relationships may influence near-term patient flow, service-line growth, or business development. They require reliability. If a referral partner sends someone into a slow, confusing, or inconsistent process, relationship equity gets spent immediately.

Talent Relationships

Schools. Residencies. Program directors. Associations. Faculty. Career centers. Alumni. Former candidates. Former employees. These relationships may produce nothing today. That is exactly why they matter. The best talent systems are built before demand becomes urgent.

Strategic Growth Relationships

Health-system leaders. Vendors. Technology partners. Community organizations. Adjacent providers. Industry innovators. These relationships help organizations identify opportunities neither side could pursue alone.

Intelligence Relationships

Operators. Recruiters. Policy leaders. Journalists. Association leaders. Local executives. These relationships provide context. Sometimes the most useful market intelligence is not secret information. It is early interpretation from someone you trust.

Reputation and Community Relationships

Nonprofits. Workforce boards. Professional organizations. Civic leaders. Community groups. These relationships influence legitimacy, local understanding, access, and trust.

A healthy relationship portfolio contains all five. Overinvesting only in people who can produce immediate revenue creates a brittle network.

Building a Relational Operating System

1. Build a Relationship Intelligence Mapf

A relationship map should tell you more than who is in the database. For each strategically important relationship, leaders should know:

• Who owns the relationship internally?

• What shared problem or strategic priority connects the organizations?

• When was the last meaningful interaction?

• What is the next value-creating action?

• How strong is the trust?

• What introductions are available in both directions?

• Is the relationship dependent on a single person?

That final question matters more than most organizations realize. A company may say: “We have a great relationship with that health system.” What it actually means is: “Our VP knows their COO.” That is not organizational relationship strength. That is single-thread risk.

If either executive leaves, the relationship may disappear. Mature partnerships become multithreaded. Executive to executive. Operations to operations. Clinical to clinical. Recruiting to workforce development. Finance to finance. The relationship survives because the organizations know each other—not merely two individuals.

2. Analyze Referral Friction

When referrals decline, leaders often assume the relationship has weakened. Sometimes it has. Sometimes the relationship is fine and the operating system is failing it. A trusted referral source may stop sending patients because:

• Response times are slow

• Access is confusing

• Capacity is inconsistent

• Updates disappear

• Eligibility is difficult to understand

• Handoffs are weak

• Families complain

• Nobody closes the loop

That creates a critical distinction:

Relationships open the door. Operational reliability keeps it open.

A declining referral relationship should be investigated through two lenses at once: relationship confidence and service performance. A business-development team cannot outreach its way out of an access problem. And an operations team should not assume every lost referral is simply a service failure. Leaders need to know which system is breaking.

When referral volume falls, do not begin only with:

Which partner stopped sending?

Ask:

At what point in the referral journey does confidence break?

That turns referral management from relationship maintenance into operational diagnosis. And it keeps organizations from asking business-development teams to compensate for service problems they do not control.

3. Build Partnerships Around Shared Problems

Healthcare is full of conversations that end with: “We should find a way to partner.” That is not a strategy. A partnership becomes strategic when both sides can define:

• A shared problem

• A complementary capability

• A measurable outcome

• An owner on each side

• A first experiment

The better opening question is:

What problem can neither organization solve as well alone?

Maybe it is a workforce gap. A maternal-health access problem. A rural referral issue. A patient-navigation challenge. A clinical-training shortage. A chronic-disease population falling between care settings.

The Administration for Community Living describes community care hubs as organizations that centralize administrative and operational infrastructure across healthcare and community partners, including contracting, payment operations, referral management, service delivery, technology, data collection, and reporting. That is partnership as operating infrastructure. Not networking.

4. Build Talent Before Requisitions Open

Healthcare organizations should stop pretending recruiting begins with an approved requisition. By then, the clock is already running. The more durable workforce strategies begin upstream.

Nursing programs. Allied-health schools. Residencies. Community colleges. Career centers. High schools. Professional associations. Internal employees pursuing advancement. Former employees. Former candidates.

The American Hospital Association has highlighted these kinds of build-the-pipeline strategies as hospitals confront persistent workforce shortages. One concrete example is Jefferson Health’s collaboration with the School District of Philadelphia and Esperanza College, which provides students with 1,000 hours of classroom instruction and hands-on training at Jefferson Einstein Philadelphia Hospital for in-demand entry-level healthcare jobs. That is not simply recruiting. It is labor-market infrastructure.

And it changes the recruiter’s role. Instead of asking:

Who can we find this month?

The organization begins asking:

• Who knows us before they enter the market?

• Which future clinicians have already experienced our organization?

• Where are our education relationships strongest?

• Which specialties have no pipeline at all?

• What internal talent could be developed instead of replaced?

A talent pipeline is not a list of résumés. It is a community of people who understand your organization before either side urgently needs the other.

5. Turn Market Intelligence Into Relationship Action

Business development is partly information advantage. Healthcare leaders are constantly absorbing signals:

A new ambulatory site. A leadership transition. A health-system acquisition. A workforce shortage. A payer-policy change. A technology investment. A new service line. A market expansion.

But information has little value if it never changes behavior. The useful question is:

What relationship action does this signal create?

A new service line may mean reconnecting with clinical and operational leadership before staffing or referral needs become public. A workforce shortage may mean deepening relationships with schools and professional associations before recruiting demand peaks. A technology initiative may create openings with clinical-adoption, change-management, workforce, and governance leaders—not merely IT.

Deloitte’s 2026 U.S. health care outlook identifies three strategic imperatives: improving digital consumer experiences, scaling generative and agentic AI, and joining forces with other industries. Deloitte reports that about 80% of surveyed executives view collaborations with other industries as a C-suite or board priority, while 63% expect strategic partnerships and joint ventures to become a higher priority in 2026.

Technology changes the market. Relationships tell you where the market is moving before the org chart catches up.

6. Compound Credibility

Visibility is not the same as constant promotion. The goal is not to stay in everyone’s feed. The goal is to create repeated evidence that you are informed, reliable, useful, and thoughtful about other people’s interests. That may mean:

• Sending a relevant article with one sentence explaining why it matters

• Making an introduction with no immediate benefit to yourself

• Congratulating someone on a meaningful promotion

• Sharing a concise market observation

• Hosting a small conversation around a problem leaders actually care about

• Following up after an event with something useful instead of “Great meeting you.”

The standard is simple:

Would this interaction make someone more willing to trust me with their reputation, patient, candidate, colleague, or opportunity?

If yes, credibility is compounding. If every interaction contains an ask, it probably is not.

The Operating Cadence

None of this works if relationship management happens only when someone remembers. The cadence should be simple enough to use and consistent enough to matter.

Weekly — Relationship Pulse

Five purposeful reconnections; one valuable introduction; five meaningful engagements; one market scan; capture one relationship insight. Purpose: Keep trust, reciprocity, and intelligence active

Monthly — Network Review

Review priority relationships; revive dormant high-value connections; add contacts tied to market shifts; attend or host one relevant gathering. Purpose: Prevent relationship drift and rebalance the portfolio

Quarterly — Relationship Operating Review

Audit the relationship map, referral friction, talent pipelines, partnership gaps, and single-thread risk; select 10 relationships to deepen. Purpose: Align relationship infrastructure with strategy

The word purposeful matters. “Checking in” is rarely useful on its own. There should be a reason. Context. Insight. Congratulations. A resource. An introduction. A shared problem.

Measure What Matters

The danger of turning relationships into an operating discipline is creating another dashboard full of meaningless activity metrics. Do not measure coffee meetings. Measure outcomes.

Depending on the function, useful indicators might include:

• Referral-source retention

• Referral conversion

• Time from referral to response

• Partner-generated opportunities

• School and residency relationships

• Quality and retention of hires by talent source

• Strategic introductions made and received

• Percentage of priority partnerships with multiple cross-organizational relationships

• The number of meaningful opportunities discovered before they became public

Metrics should tell leaders whether the network is becoming more useful and resilient. Not whether everyone was busy.

The Leadership Question

The biggest risk in healthcare relationship strategy may be that organizations assume they own relationships they have never actually institutionalized. A physician liaison leaves. A recruiter changes companies. A CEO retires. A partnership executive gets promoted. And suddenly a relationship everyone thought belonged to the organization turns out to have belonged to one person.

That should concern leaders. Because relationship capital is real. So is relationship concentration risk.

The leadership task is not to turn every human connection into corporate property. It is to build enough organizational trust, shared value, and cross-functional connection that strategic relationships can survive normal leadership and workforce transitions. That is what makes the network an asset rather than a collection of personal favors.

The Real Operating System

Your network should not be something you remember when you need a job, a referral, a candidate, or a partnership. It should already be there. Alive. Useful. Reciprocal. Connected to the work.

Healthcare growth is relational before it becomes transactional. But relationships alone are not enough. The organization still has to respond. Deliver. Follow through. Make the hire. Serve the patient. Execute the partnership.

Relationships create access. Operations determine what happens after the door opens.

The leaders who understand both will build something more durable than a large network: an organization that knows how to create trust before it needs to spend it. That may be one of healthcare’s most underestimated growth capabilities.

Sources & Research Notes

HFMA — Value-Based Care Adoption

HFMA reports that participation in value-based care and shared-risk arrangements among hospitals, health systems, and health plans reached 45.2% in 2023.

American Hospital Association — Workforce Pipelines

The American Hospital Association has highlighted health-system partnerships with education providers and internal workforce-development strategies as ways to build more durable nursing and healthcare talent pipelines.

Administration for Community Living — Community Care Hubs

The Administration for Community Living describes community care hubs as organizations that centralize administrative and operational infrastructure across healthcare and community partners, including contracting, payment operations, referral management, service delivery, technology, data collection, and reporting.

Jefferson Health Workforce Development Program

The Jefferson Workforce Development Program, developed with the School District of Philadelphia and Esperanza College, provides students with 1,000 hours of classroom instruction and hands-on training at Jefferson Einstein Philadelphia Hospital for in-demand entry-level healthcare roles.

Deloitte — 2026 U.S. Health Care Outlook

Deloitte’s 2026 U.S. health care outlook identifies three strategies: improving digital consumer experiences, scaling generative and agentic AI, and joining forces with other industries. Deloitte reports that about 80% of surveyed executives viewed collaborations with other industries as a C-suite or board priority, while 63% expected strategic partnerships and joint ventures to become a higher priority in 2026.

Editorial Note

The Healthcare Relationship Operating System, Relationship Asset Model, Trust-to-Transaction Ladder, Network Portfolio framework, and operating cadence presented here are HLR editorial frameworks informed by the cited healthcare evidence and the author’s professional experience. They are intended as management tools rather than validated clinical or academic models.

Free insights to keep you informed.
Paid insights to take you deeper.

The juice is worth the squeeze. 🍋

#hlr

The passing of Hayden Panettiere made me think about a movie I hadn’t thought deeply about in a while.

Remember the Titans.

My favorite movie growing up. And, strangely enough, one of my earliest lessons in leadership. I didn’t know that at the time.

I was a kid watching football, conflict, friendship, and one hell of a soundtrack. And I absolutely loved Sheryl Yoast.

Hayden played her with this certainty that seemed completely unaware she was supposed to be intimidated.

• She was a child in rooms full of grown men.

• She knew football.

• She had opinions.

• She spoke her mind.

• She didn’t ask permission to be there.

• She just belonged.

I admired that then. I understand it differently now.

Because beneath the football, Remember the Titans was asking a much bigger question:

What happens when people who have been taught to see each other as different are suddenly asked to succeed together?

I didn’t have words like diversity, equity, and inclusion when I first watched it. I certainly didn’t understand organizational culture. I hadn’t studied human resources. I didn’t have a degree or professional certification behind my name. I hadn’t sat inside workplaces and watched how hiring decisions get made, how talent gets developed, how culture gets built, or how easily good people can become invisible inside organizations.

All of that came later. But the foundation was already being built.

Before DEI Was an Acronym

Human Resources was where I began formally studying people and organizations. I studied it. Earned the degree. Earned the certification.

And perhaps because of that foundation, I sometimes struggle with what has happened to the conversation around DEI. We have turned something profoundly human into corporate vocabulary.

• Initiatives.

• Metrics.

• Committees.

• Training.

• Statements.

• Representation targets.

Some of those things matter. But none of them, by themselves, create belonging.

That’s one reason Remember the Titans still resonates with me. The film places Black and white players on the same newly integrated football team and then spends much of its story showing that proximity alone does not create trust.

Diversity put them in the same room. It didn’t make them a team. That required something harder.

• They had to confront what they believed about one another.

• They had to listen.

• They had to fight.

• They had to become uncomfortable.

• They had to discover each other’s humanity.

• Eventually, they had to trust someone they had been taught not to trust.

Tell me that isn’t a workplace lesson.

HR didn’t teach me to care about DEI. HR gave me the language for something my life had already taught me to recognize.

My Starting Line Wasn’t My Mother’s

My relationship with these ideas is personal, too. My mother grew up in Belize. I grew up in the United States with privileges and opportunities she did not have.

One generation. Same family. Very different starting lines.

I’ve never believed acknowledging that diminishes what I’ve worked for. It gives me perspective on the conditions that made some of that work possible.

Privilege doesn’t erase effort. It asks us to be honest about the conditions under which effort takes place.

That distinction matters enormously when we talk about work. Because organizations love the language of merit.

• Hire the best person.

• Promote the strongest performer.

• Reward the people who work hardest.

Those principles sound perfectly fair. Until you begin asking harder questions.

• Who had access to the opportunity in the first place?

• Who knew the unwritten rules?

• Who had someone advocating for them when they weren’t in the room?

• Whose potential was recognized before there was proof?

• Who received grace after a mistake?

• Who could afford to take the opportunity that paid less today but opened doors tomorrow?

• Who could take a professional risk without failure becoming a financial crisis?

• Who entered corporate America already understanding its language?

• And who had to learn all of that while simultaneously proving they deserved to be there?

That’s where equity becomes more complicated than equality.

Equality says everyone gets the same starting gun. Equity asks whether they were standing at the same starting line when it fired.

My family taught me that difference long before HR gave me terminology for it.

The Workplace Is a Team, Too

There is a moment in almost every organization’s DEI journey when diversity becomes arithmetic.

• How many women?

• How many people of color?

• How many people from underrepresented backgrounds?

Representation matters. It matters enormously. But representation is the beginning of the conversation, not evidence that the work is finished.

You can recruit a remarkably diverse workforce and still build a culture where everyone who succeeds learns to behave, speak, and lead exactly like the people who were already there.

That isn’t inclusion. That’s assimilation. And there is a difference.

Real inclusion asks something much more difficult of leaders: Can someone enter this organization, remain recognizably themselves, and still be trusted with influence?

• Can they disagree?

• Can they challenge prevailing thinking?

• Can they make a mistake without that mistake becoming evidence about everyone who looks like them?

• Can they be ambitious without being labeled difficult?

• Can they be quiet without being overlooked?

• Can they speak with an accent?

• Can they come from somewhere unfamiliar?

• Can they have a different cultural reference point?

• Can they be the only person like themselves in the room and still feel the same certainty Sheryl Yoast seemed to have on that football field: I belong here.

That’s the standard. Not attendance. Belonging.

But inclusion does not mean nobody has to adapt. Teams require norms. Professions require standards. Working with other human beings requires compromise.

The harder question is whether those expectations are genuinely connected to excellent performance—or whether they are inherited preferences for how the people who historically held influence happened to speak, dress, lead, and behave.

Because sometimes we call something a standard when it is simply familiarity.

Recruiting Made the Responsibility Real

My career eventually took me from studying HR to recruiting healthcare talent nationally. And that changed my relationship with these ideas. They became less theoretical.

When you are responsible for identifying, screening, and presenting healthcare talent across different markets and communities, questions about access and opportunity are no longer confined to a textbook, policy, or annual initiative. They appear in the work. Every day.

• Who gets found?

• Who gets screened in?

• Which requirements are genuinely necessary?

• Whose experience is considered transferable?

• Whose career path is considered unconventional?

• Who gets described as having potential?

• Who gets dismissed because their résumé does not look like the person who held the job before them?

• Which candidate gets labeled a “culture fit”—and what do we actually mean when we say it?

Those decisions matter because they happen before many candidates ever meet the hiring team. Recruiters are part of the system through which opportunity moves. That means we have responsibility, too.

The Recruiter Is Part of the System

Recruiters cannot create an inclusive organization by themselves. Neither can HR. Neither can a DEI initiative. Hiring is a shared system, and responsibility travels through it.

Recruiters influence where organizations look for talent, how broadly they search, how requirements are interpreted, who advances through screening, and what information reaches the hiring team. Hiring managers determine how that talent is received, evaluated, and ultimately selected. Leadership shapes the conditions surrounding both.

That means diversity in hiring requires more than expanding the top of the funnel. It requires discipline throughout the process.

• Are job requirements genuinely connected to performance—or are we carrying forward credentials and preferences because that’s what we’ve always hired?

• Are candidates being evaluated against consistent criteria?

• Are we sourcing beyond the networks that repeatedly produce the same kinds of candidates?

• Are accommodations accessible?

• Are we examining where candidates fall out of the process?

• Are compensation practices equitable?

• Are hiring teams equipped to recognize bias without becoming afraid to exercise legitimate professional judgment?

• Are we distinguishing culture contribution from the much more comfortable idea of culture fit?

• And when a recruiter notices a pattern, are they empowered to say something?

Because recruiters occupy a consequential position in the hiring process. We are often the first human gate between interest and opportunity. That should make us thoughtful about the gate.

It does not mean lowering standards. It means being rigorous about which standards actually predict someone’s ability to succeed.

In healthcare, that responsibility carries additional weight. We recruit into organizations serving communities that are themselves extraordinarily diverse—across race, ethnicity, language, geography, socioeconomic background, age, disability, gender, education, and lived experience.

The goal is not demographic arithmetic for its own sake. The goal is to make sure qualified talent is not unnecessarily filtered out before an organization ever has the opportunity to recognize it.

As a national healthcare recruiter, that remains a priority in how I approach the work. Not because every candidate slate should satisfy some predetermined demographic formula. Not because standards should disappear. And not because the best-qualified candidate should ever be displaced to satisfy an initiative.

But because “we hired the best person” only means something if we were serious about where we looked, who received consideration, and how we decided what “best” meant.

That is a recruiting responsibility. It is a hiring-team responsibility. And ultimately, it is a leadership responsibility.

HR Sits at the Intersection of People and Power

My earlier studies in HR gave me another way to understand why this matters. Human Resources sits at an extraordinary intersection of people and power. HR doesn’t merely administer employment. It helps construct the systems through which opportunity moves.

• Who gets recruited.

• Which qualifications become requirements.

• How compensation is structured.

• Whose performance gets recognized.

• Who receives development.

• Who enters succession planning.

• Who gets promoted.

• What leadership potential looks like.

• Which behaviors get labeled “executive presence.”

• Who gets another opportunity after getting something wrong.

Whether we acknowledge it or not, every one of those systems can widen opportunity—or quietly reproduce the advantages already present.

And bias does not require a deliberately biased person at every decision point. It can become embedded in criteria, processes, traditions, and definitions of “fit” that everyone involved experiences as normal.

That is why DEI cannot simply belong to HR. But HR cannot pretend it has no responsibility for it either. Neither can recruiting. Neither can the hiring team. And neither can leadership.

Culture isn’t what an organization writes on its website. Culture is the accumulation of thousands of decisions about whose voice matters.

• Who gets invited.

• Who gets interrupted.

• Who gets sponsored.

• Who gets challenged.

• Who gets protected.

• Who gets another chance.

• Who gets promoted.

• Who gets believed.

Every workplace eventually reveals who it believes belongs there. The employees already know.

What a Football Movie Understood

Remember the Titans is a dramatized film inspired by the 1971 football season at T.C. Williams High School in Alexandria, Virginia. It is not a documentary account of school integration, and I don’t treat it as one.

I view it as something else: a story that reached me before I had the language to explain what I was seeing.

Within that story, integration didn’t magically solve anything. Proximity created conflict before it created understanding. People said the wrong things. People resisted. People were angry. Some changed faster than others.

And leadership wasn’t about pretending those differences didn’t exist. It was about refusing to allow those differences to determine whose humanity mattered.

That distinction feels especially important now. Because somewhere along the way, DEI became a political argument when, inside a workplace, many of the fundamental questions are remarkably practical:

• Are we finding talent everywhere it exists?

• Are we removing barriers that have nothing to do with someone’s ability to do the work?

• Are we evaluating people fairly?

• Are we creating conditions where different people can do exceptional work together?

• Are our leaders capable of leading people whose lives don’t look like theirs?

• And are people given a genuine opportunity to belong?

Those shouldn’t be radical questions. They are leadership questions. They are business questions. And for someone whose career began with HR and now lives much closer to the front line of healthcare hiring, they are impossible for me to separate from the work.

What Stayed With Me

And eventually, this brings me back to Hayden. I didn’t know her. I don’t want the familiarity of having watched someone on a screen to pretend otherwise. What I knew was a character.

A little girl standing on a football sideline, surrounded largely by grown men, completely certain that she had every right to understand the game, have an opinion, and occupy the space. I loved Sheryl for that.

Years later, Hayden would describe Remember the Titans as her favorite movie to film and speak warmly about what that period of her life meant to her. There is something especially poignant about knowing that now.

As a kid, I thought I admired Sheryl’s confidence. I’m not sure I understood what I was actually seeing. She belonged. Or perhaps more importantly: She behaved as though belonging was never hers to request.

There is something powerful about that. Especially when so much of organizational life is spent watching talented people calculate whether they are permitted to be fully themselves in a particular room.

Hayden’s passing made me return to a movie I loved before I understood why I loved it. And in returning to it, I realized something.

• Remember the Titans gave me an early story about difference.

• My family gave me perspective on different starting lines.

• My early studies in HR gave me language for what I had already begun to understand.

• My career in healthcare recruiting gave me responsibility for putting some of those ideas into practice.

That’s why DEI matters to me. Not because three letters appeared in an HR textbook. Not because a company created an initiative. And not because everyone should become the same or arrive at the same outcome.

It matters because talent is everywhere. Opportunity isn’t. Belonging isn’t. And organizations make choices every day that either narrow or widen the distance between them.

• Diversity asks who made the team.

• Equity asks whether everyone had a fair opportunity to show what they could do.

• Inclusion asks whether people can contribute fully without first becoming more like everyone already there.

• Belonging is what happens when they no longer have to wonder whether the team was built for someone like them.

And leadership? Leadership creates the conditions that determine whether any of those things are true.

Twenty-six years after I first watched that little girl walk confidently onto a football field, I understand the lesson differently. Sometimes the things we love as children stay with us for reasons we don’t understand until much later.

Thank you, Hayden, for bringing Sheryl to life.

I thought she was teaching me something about confidence. It took me a few decades to realize she was teaching me something about belonging.

Sources & Research Notes

1. Hayden Panettiere and Remember the Titans. Hayden Panettiere portrayed Sheryl Yoast in Disney’s Remember the Titans, released in 2000. The film became one of her notable early roles.

2. Historical context. Remember the Titans is a dramatized story inspired by the 1971 football season at T.C. Williams High School in Alexandria, Virginia. The film takes creative liberties with the history surrounding school integration and is used in this essay as a personal and cultural reference rather than as documentary evidence.

3. Hayden on the film. In a 2023 retrospective interview with Entertainment Tonight, Panettiere described Remember the Titans as her favorite movie to film and spoke warmly about wishing she could return to that period of her life.

Editorial Note

This essay uses Remember the Titans as a personal and cultural lens through which to explore opportunity, diversity, equity, inclusion, belonging, recruiting, and leadership. The film is a dramatization and should not be treated as a complete historical account of school integration in Alexandria.

The interpretations of workplace inclusion, recruiting responsibility, organizational systems, and leadership expressed here are the author’s editorial analysis.

HEALTHCARE LEADERSHIP REVIEW™
IDEAS THAT SHAPE LEADERSHIP

“As long as you’re dancing, you can break the rules.
Sometimes breaking the rules is just extending the rules.
Sometimes there are no rules.”

It comes from her poem Three Things to Remember, later included in A Thousand Mornings and Devotions. Oliver spent a career noticing what most of us hurry past. She won the Pulitzer Prize for American Primitive in 1984 and the National Book Award for New and Selected Poems in 1992, but the enduring power of her work came from something less measurable: an ability to make the obvious feel newly discovered. (The Pulitzer Prizes⁠)

Those three lines are ostensibly about dancing.

They are also an unusually good description of leadership.

Because every organization eventually develops rules.

Some are written down: approval processes, reporting structures, budgets, job descriptions, brand guidelines, operating procedures.

Others are invisible.

This is how we do things here.

That isn’t your department.

We tried that before.

Leadership wouldn’t go for it.

People at your level don’t make that decision.

The longer an organization exists, the harder it becomes to distinguish between a principle and a habit.

And that distinction matters.

A principle protects something important.

A habit merely preserves something familiar.

Weak leadership treats the two as interchangeable.

Strong leadership knows the difference.

First, Learn the Dance

Oliver’s first line contains an important qualification that is easy to miss.

As long as you’re dancing, you can break the rules.

Not standing on the sidelines.

Not criticizing everyone who came before you.

Not ignoring constraints because discipline feels inconvenient.

Dancing.

There is competence implied in the metaphor.

Before great musicians improvise, they learn scales. Before great architects challenge convention, they understand structure. Before exceptional leaders redesign an organization, they understand why it works the way it does.

The most dangerous rule-breaker is often the person who doesn’t understand the rule.

The most valuable one is the person who understands it so completely that they can see where it has stopped serving its purpose.

This is why experience and rebellion are not opposites.

At their best, they are partners.

Mastery gives you the judgment to know which conventions are load-bearing and which are merely historical residue.

Some Rules Were Once Good Ideas

Organizations rarely create bureaucracy because somebody wakes up wanting to make everyone’s life harder.

Most rules begin as solutions.

A mistake happens, so another approval is added.

A client complains, so another process is introduced.

Someone overspends, so another layer of authorization appears.

A project fails, so another meeting enters the calendar.

Individually, each decision may be perfectly rational.

Collectively, they can create an organization incapable of moving.

The problem is that organizations are very good at remembering the rule and surprisingly bad at remembering the reason for it.

Years later, someone asks:

Why do we do this?

And the answer is:

Because that’s the process.

That sentence should terrify leaders.

It means the organization has stopped thinking.

Sometimes Breaking the Rule Extends It

Oliver’s second observation is more interesting than simple rebellion:

Sometimes breaking the rules is just extending the rules.

That is how genuine innovation often works.

The breakthrough doesn’t necessarily destroy the underlying principle. It finds a better expression of it.

A company obsessed with customer service might abandon a cumbersome customer-service procedure precisely because the procedure has begun making service worse.

A leader committed to accountability might eliminate layers of approvals because ownership becomes clearer when fewer people are pretending to own the decision.

A creative team might violate brand conventions because preserving the spirit of the brand requires occasionally surprising the people who have become accustomed to it.

The surface rule changes.

The deeper principle survives.

Sometimes it becomes stronger.

This is one of the most important distinctions in leadership:

Consistency of principle does not require consistency of method.

Methods should evolve.

Principles should tell us why.

The Rule Is Not the Mission

Eventually, every successful organization faces the same danger.

The systems that helped create its success become sacred.

What once enabled progress begins preventing it.

The company starts protecting the machine instead of protecting the mission.

Kodak is remembered not because it failed to understand photography, but because organizations can become deeply invested in the economic architecture that made them successful. Blockbuster’s problem wasn’t that nobody understood convenience. Entire industries have watched newcomers violate conventions that incumbents had mistaken for laws.

The pattern repeats because success creates its own mythology.

We did this.

It worked.

Therefore this must be the way.

But yesterday’s advantage can become tomorrow’s constraint.

Leadership requires asking a more uncomfortable question:

If we were building this organization today, knowing everything we know now, would we still design it this way?

Sometimes the answer will be yes.

Often it won’t.

And Sometimes There Are No Rules

Oliver saves the most unsettling idea for last.

Sometimes there are no rules.

Leadership education rarely prepares people for this.

We love frameworks.

Five steps.

Seven principles.

The playbook.

The operating model.

The best practice.

They give uncertainty the appearance of order.

But eventually every serious leader reaches territory where precedent becomes unreliable.

There is no case study for your exact company, your exact people, your exact market, your exact moment.

There is no spreadsheet capable of removing ambiguity from a genuinely difficult decision.

There is no leadership book that can tell you exactly when to persist and when to quit, when to protect someone and when to challenge them, when to move quickly and when to wait.

At some point, the framework ends.

Judgment begins.

That is where leadership becomes less like engineering and more like dancing.

You listen.

You notice.

You respond.

You adjust.

You trust the principles you’ve spent years developing.

And then you move.

The Best Leaders Aren’t Rebels

There is a fashionable version of leadership that celebrates disruption for its own sake.

Break things.

Ignore convention.

Move faster.

Be contrarian.

But breaking rules isn’t inherently courageous.

Sometimes it’s just reckless.

The goal isn’t to become the person who always says no to convention.

The goal is to become the person capable of determining whether convention still deserves a yes.

That requires something harder than rebellion:

judgment.

The mature leader can hold two ideas simultaneously.

Rules matter.

And rules are not sacred.

Structure creates freedom.

And too much structure destroys it.

Experience deserves respect.

And experience can become a prison.

The question is never simply:

Should we follow the rules?

The better questions are:

What is this rule protecting?

Does it still protect it?

What would happen if we removed it?

Are we preserving a principle—or preserving a habit?

And if nobody had written the rule yet, what would we choose to do?

Keep Dancing

Mary Oliver spent much of her life walking through woods, fields and shorelines, paying extraordinary attention to ordinary things. Her poetry repeatedly returned to nature, wonder and the question of how a human being ought to inhabit a life. The Poetry Foundation describes her work as rooted in close observation of the natural world and in the limits of human consciousness and language. (Poetry Foundation⁠)

Perhaps that’s why her three lines land so differently from the usual celebration of rule-breaking.

She doesn’t tell us to burn the rulebook.

She tells us to dance.

There is movement in that.

Responsiveness.

Awareness.

The willingness to change direction without losing rhythm.

Maybe that is the leadership lesson.

Learn the rules.

Understand why they exist.

Respect the principles underneath them.

Then pay attention closely enough to recognize the moment when obedience stops being wisdom.

Because sometimes leadership means following the rule.

Sometimes it means extending it.

And sometimes the most important thing a leader can recognize is that the rule everyone is afraid to break was never really a rule at all.

Keep dancing.

Careers, ideas, partnerships, and possibilities often move through conversation. Reach back. Reconnect. Ask the question.

One conversation can change the direction of everything.

Join 36K+ healthcare executives, operators, and leaders reading HLR™ — the industry-leading newsletter on healthcare and leadership.

#Leadership #HealthcareLeadership #ExecutiveLeadership #HLR

Ask a health system CFO what the organization spends on salaries, and you will get an answer within minutes.

Ask what the organization spent last year on turnover, and you will usually get silence.

Not because the number is small.

Because it has never been calculated.

Turnover in healthcare is treated as weather—something that happens to organizations rather than something organizations produce. It is discussed in percentages, managed by HR, and lamented in workforce meetings.

It is almost never treated as what it actually is: one of the largest controllable costs in the enterprise, sitting invisibly across a dozen budget lines, owned by no one.

That invisibility is not an accounting quirk.

It is a leadership choice.

And it is becoming an expensive one.

The number no one budgets for

The 2026 NSI National Health Care Retention & RN Staffing Report—drawn from 527 hospitals across 40 states—puts the average cost of a single RN departure at $60,090.

The average hospital loses $5.19 million a year to RN turnover alone. Larger systems lose between $4.2 million and $6.2 million per facility.

National RN turnover rose again this year, to 17.6 percent. Nearly a third of hospitals report vacancy rates above 10 percent. The average hospital carries 43 unfilled RN positions at any given moment, and filling one takes 56 to 102 days.

Physicians are more expensive still. Recruitment costs alone average over $150,000 per physician and can exceed $500,000 for hard-to-fill specialties. While the search proceeds, a vacant physician position forgoes an estimated $300,000 to $800,000 in monthly gross billings, depending on specialty. Research published in the Annals of Internal Medicine estimates burnout-driven physician turnover and reduced clinical hours cost the U.S. system roughly $4.6 billion annually.

Now do the arithmetic most boards never see.

A 350-bed hospital with 1,000 RNs at national-average turnover loses roughly 176 nurses a year. At $60,090 each, that is more than $10 million—before counting a single physician, therapist, technologist, or the contingent labor purchased to bridge every gap.

Ten million dollars is not a rounding error.

It is a service line.

It is a margin.

In many hospitals operating at 1–3 percent margins, it is the difference between investing and retrenching.

Yet in most organizations, no executive owns that number. No budget line contains it. No variance report flags it.

The most expensive recurring cost in healthcare operations does not appear on the balance sheet it quietly destroys.

Why the cost hides

Turnover cost hides because it fragments.

Recruitment advertising sits in one budget. Sign-on bonuses in another. Agency and travel labor in a third. Overtime in a fourth. Orientation and preceptor time are absorbed into productive hours. Lost revenue from an unfilled surgical position never appears as a cost at all—it appears as volume that “softened.”

Each fragment looks tolerable.

Assembled, they describe a system paying a premium to stand still.

The travel-labor era made this visible for a moment. When contingent labor spend exploded, boards finally saw workforce instability as a financial event, because it arrived as one enormous invoice. Systems responded—and contract labor has fallen substantially from its peak.

But here is the uncomfortable truth of the post-travel-nurse era: many organizations treated the invoice as the problem.

The invoice was the symptom.

The turnover that generated it remains. National RN turnover went up this year, not down. The system did not get healthier. The bill just got redistributed—back into the fragments where no one totals it.

Turnover is not one cost. It is four.

Executives who want to manage turnover economically need to see its full structure. The cost of a departure arrives in four distinct layers.

Layer one: the transaction. Advertising, sourcing, recruiter time, interviewing, sign-on incentives, credentialing, relocation. This is the layer most cost studies capture, and it is the smallest.

Layer two: the bridge. Every vacancy must be covered—by overtime, by float pools, by agency staff at premium multiples, or by closed beds and delayed procedures. The bridge is where turnover converts into both cost and lost revenue simultaneously. It is also where the exhaustion that produces the next departure is manufactured.

Layer three: the ramp. A new nurse is not a replacement on day one. Productivity, unit knowledge, and clinical fluency take months to rebuild. Preceptors slow down to teach. Teams recalibrate. Studies of physician turnover consistently find that disrupted referral relationships and patient panels take a year or more to recover.

Layer four: the spiral. This is the layer no spreadsheet captures and the one leaders most need to understand. Turnover causes turnover. Each departure raises workload on those who remain, weakens team cohesion, and normalizes leaving. Research links higher nursing turnover and unstable staffing to worse patient outcomes—including, in multiple studies, elevated mortality. Quality events then generate their own costs: extended stays, litigation exposure, reputational harm, and the departure of clinicians who did not enter the profession to deliver care they cannot be proud of.

The four layers explain why per-departure cost estimates, however striking, systematically understate the truth. They price the transaction and part of the bridge. The ramp and the spiral—the layers that compound—go unmeasured.

What gets unmeasured gets unmanaged.

The highest-yield asset most systems underinvest in

Here is where the economics become genuinely interesting—and genuinely hopeful.

NSI’s data shows that each one-point reduction in RN turnover saves the average hospital roughly $295,000 per year.

Recurring. Compounding. Every year the improvement holds.

Now consider where the leverage concentrates. First-year nurses turn over at 22.3 percent—well above the overall rate—and early-tenure departures account for nearly a third of all RN turnover. The organization successfully found these people, competed for them, won them, credentialed them, and trained them.

Then lost them before the investment returned anything.

This is the closest thing healthcare has to a free lunch. The most expensive turnover in the system is also the most preventable, because its drivers are known and largely internal: weak onboarding, absent manager connection, unrealistic early workloads, and the gap between the job that was described and the job that exists.

A hospital that cut only its first-year losses in half would recover millions annually—without recruiting a single additional candidate.

Compare the yields. A retention program that reduces system turnover by two points returns $590,000 per hospital per year against a program cost that is typically a fraction of that. Few capital projects in healthcare clear their hurdle rate so easily.

Yet watch where the money actually goes. Recruitment budgets grow. Sign-on bonuses escalate—paying a premium to acquire commitment the organization then fails to keep. Retention investment, meanwhile, must fight for funding as a “soft” initiative.

The market is pricing these assets exactly backward.

Retention is a financial strategy. Treat it like one.

If turnover is a financial event, retention must be governed with financial discipline. That implies five moves.

1. Build the turnover P&L. One number, owned at the executive level: fully loaded annual turnover cost, by role, by unit, by tenure band. Include the transaction, the bridge, and a defensible estimate of the ramp. Present it beside the labor budget every quarter. The purpose is not precision. It is visibility. A cost that appears in the room gets managed; a cost that fragments does not.

2. Price the spiral into decisions. When a unit runs chronically short, the apparent savings of the unfilled position are an illusion; the organization is paying in overtime, agency premiums, quality risk, and the accelerating departures of those who remain. Staffing decisions should be evaluated against the full four-layer cost, not the payroll line alone.

3. Redirect acquisition premium into retention yield. Every dollar of sign-on bonus is a confession that the organization must pay people to overlook something. Some of that spend is unavoidable in scarce markets. But a portion of it—shifted into first-year support, preceptor capacity, manager development, and schedule design—buys commitment instead of renting it.

4. Hold operations, not HR, accountable for the number. Turnover concentrates where management is weak, workloads are unsustainable, and schedules are hostile to life outside work. Those are operating conditions. The executive scorecard should show retention by department and by manager, and leaders should answer for it the way they answer for quality and cost—because it is both.

5. Invest where tenure is shortest. The first year is where the money is. Structured onboarding, deliberate manager connection in the first 90 days, honest job previews, and protected early workloads are not culture programs. They are the highest-ROI capital deployment available to most health systems today.

The heart of the matter

It would be easy to read this argument as cold—people reduced to replacement costs.

It is the opposite.

The financial case and the human case for retention are the same case.

Every $60,090 departure began as something smaller: a schedule that made family life impossible. A manager who never made rounds. A new nurse who spent her first months overwhelmed and unseen. A physician who concluded, quietly, that the organization would never fix what it knew was broken.

The dollars are simply the ledger’s way of recording accumulated human disappointment.

That is why the turnover balance sheet matters. Not because people are costs—but because until organizations count the cost of losing people, they will keep underinvesting in the conditions that make people stay.

Healthcare has spent a decade asking its workforce to be resilient.

The more productive question was always the reverse:

What would it cost us to build an organization people don’t have to be resilient to survive?

The answer, it turns out, is far less than what we are paying now.

We are already spending the money.

We are just spending it on leaving.

Sources and research notes

• NSI Nursing Solutions, 2026 National Health Care Retention & RN Staffing Report (527 hospitals, 40 states): $60,090 average cost per RN departure; $5.19M average annual hospital loss; 17.6% national RN turnover; 8.6% vacancy rate; 43 average unfilled RN FTEs; 56–102 day recruitment window; $295,000 saved per 1-point turnover reduction; 22.3% first-year RN turnover.

• AMN Healthcare (2025) and related analyses of physician recruitment costs ($150,000+ average; up to $500,000+ by specialty) and vacancy-period gross billings ($300,000–$800,000/month by specialty).

• Han, S., et al., “Estimating the Attributable Cost of Physician Burnout in the United States,” Annals of Internal Medicine (~$4.6B annual system cost).

• Press Ganey nursing workforce analyses on early-tenure turnover concentration.

• Peer-reviewed literature linking nurse staffing instability and turnover to patient outcomes, including NEJM (Needleman et al., staffing and inpatient mortality) and subsequent longitudinal studies.

• Kaufman Hall National Hospital Flash Report series on labor expense and contract labor trends.

Physical therapists occupy a particular blind spot in this analysis. While PT turnover runs lower nationally—15.2 percent versus 17.6 percent for RNs—the per-departure cost rivals nursing at $61,000 to $70,300. In outpatient clinics, where a single therapist may carry 20–30 active patients, each departure creates both an immediate revenue hole (lost billable hours during the 6–12 week recruitment window) and downstream loss as patients follow their familiar clinician elsewhere. A 20-therapist outpatient clinic at national-average turnover loses three PTs annually—$183,000 to $210,900 in direct turnover cost, plus an equivalent loss in patient continuity and referral relationships that take months to rebuild.

Comprehend Health analysis (2026) on physical therapist turnover: $61,000–$70,300 average cost per PT departure; 15.2% national PT turnover rate; cost breakdown includes $33,000 lost revenue during 6-week vacancy, $20,200 recruiting expenses, $7,200 temporary staffing premiums, $5,200 onboarding and ramp-up time.

Editorial note: Cost figures are survey-based estimates and vary by market, role, and methodology. They are used here to illustrate order of magnitude, not to price any individual organization’s experience.

IDEAS THAT SHAPE LEADERSHIP

By Julia Weingartner
Founder & Editor-in-Chief, Healthcare Leadership Review™

There was genuinely a point in my career when I stopped updating my résumé.

Not because I had stopped growing. Not because I had become complacent. And certainly not because résumés no longer mattered.

I simply did not need mine in the same way anymore.

Hear me out.

Early in my career, I always kept an updated résumé and LinkedIn profile. My first boss gave me a piece of advice that stayed with me: keep track of every project you complete. So I did. As I took on new assignments, learned new skills, and produced new results, I documented them. Each experience became another line on my résumé and another part of the story I could tell about my career.

Then, at some point, something shifted.

My track record began speaking before I entered the room. My network knew what I could do. Former colleagues, clients, and leaders could speak to the quality of my work. Opportunities increasingly came through relationships, referrals, and reputation rather than applications.

That did not happen because I found the perfect résumé template. It did not happen because I memorized the perfect answers to the most common interview questions. It happened because, early in my career, I said yes—a lot.

Say Yes Before You Feel Ready

Early in your career, say yes to as many meaningful opportunities as you can.

Yes, I would love to cross-train with the sales department.

Yes, I am interested in learning about marketing and branding.

Yes, I will write a newsletter profiling a rising star.

Yes, I will take on the celebrity client, even though I am new and have no experience in the entertainment industry.

Yes, I will work with the global client that is struggling to find someone who understands the cultural nuances of the role.

Yes, I will present in front of new hires, even though I hate speaking in front of groups.

Most of these opportunities had little to do with my formal education or previous experience. That was precisely why they mattered.

Every yes stretched my range. Together, those experiences gave me capabilities I could not have predicted I would need: business development, sourcing, client management, market analysis, public speaking, cultural intelligence, writing, marketing, and personal branding.

Saying yes did not mean agreeing to everything without boundaries or discernment. It meant recognizing when an opportunity could expand me—and refusing to let inexperience make the decision on my behalf.

I did not always know how I would do the thing when I accepted it. I trusted that I could learn.

That trust became one of the most important forms of interview preparation I ever had.

Follow the Market, Not Just Your Job Description

Saying yes was only part of the strategy. I also learned to follow the market.

When the pandemic transformed recruiting, I knew the approaches that had worked when I entered the industry in 2014 would no longer be enough. The market had changed. Talent was harder to find, harder to reach, and often reconsidering what work meant altogether. I sharpened my sourcing skills because the moment required it.

When I stepped into a staffing role with heavy business-development and market-insight responsibilities, I responded by studying trends, following the data, and writing articles. I wanted to understand not only where the market was, but where it was going.

And when I realized how important marketing and branding were to recruiting, I became more intentional about how I showed up.

Recruiting is not only about identifying qualified people. It is also about trust. If you can build a reputation as someone people genuinely want to work with, it becomes much easier to recruit on behalf of the people and organizations you represent. You are no longer simply filling a position. You are inviting someone into a relationship, and your credibility becomes part of the offer.

Following the market taught me not to define myself too narrowly by a title. A job description tells you what the role requires today. The market gives you clues about what you will need tomorrow.

How I Walked Into Every New Opportunity

The opportunities mattered, but so did the way I entered them. I showed up to nearly every new challenge headfirst, carrying four qualities with me.

1. Authenticity and transparency

I never wanted to win an opportunity by pretending to be someone I was not.

If I lacked experience, I was honest about it. If I did not know something, I said so—and then explained how I would learn it. I trusted that the right employer, client, or leader would value self-awareness, integrity, and potential more than a perfectly polished performance.

Being myself closed nearly every interview I had.

I take enormous pride in that because authenticity is deeply important to me. I want to work in environments where I can be fully myself and where other people are given that same freedom. No one should have to flatten their personality, hide their perspective, or erase the nuances of who they are to be seen as capable.

Authenticity does not mean arriving unprepared. Transparency does not mean disclosing every detail of your life. It means that the person in the interview is the same person who will arrive to do the work.

2. Curiosity coupled with a hunger for challenges

I did not need to enter every opportunity already knowing exactly what to do. I needed to be willing to ask thoughtful questions, understand the real problem, and figure out what the situation required.

The assignments that interested me most were often the ones that made me wonder, Can I actually do this?

Curiosity helped me learn. Challenge gave that curiosity somewhere to go.

Over time, I stopped seeing a lack of familiarity as proof that I did not belong. I began to see it as an invitation to expand.

3. Sheer enthusiasm and positivity

I brought genuine enthusiasm to the possibility of doing meaningful work, learning something unfamiliar, and contributing wherever I could.

Not performative enthusiasm. Not the kind of positivity that denies difficulty or insists that every situation is perfect. I mean the kind of energy that says: this may be hard, but there is something here worth attempting—and I am excited to see what we can make of it.

4. The willingness to be taught

Being teachable requires a particular kind of confidence: enough self-awareness to know your weaker areas, enough conviction to know where you are strong, and enough humility to understand that neither is permanent.

I was never afraid to say, “I don’t know—but teach me. I want to know.”

That sentence did not make me less capable. It showed that I was honest about the limits of my knowledge and serious about expanding them. Pretending to know everything might protect your ego for a moment, but it prevents the very growth that could change your career.

Knowing your strengths matters because you should understand the value you already bring. Knowing your weaker areas matters because self-awareness keeps you from confusing confidence with completeness. Being teachable connects the two. It allows you to contribute from where you are strong while remaining open to what someone else can show you.

The people who taught me did more than help me complete an assignment. They expanded the way I thought, and their lessons became resources I carried into every role that followed.

Those four qualities became my interview strategy long before I realized I had one.

I did not enter interviews trying to deliver a flawless performance. I entered ready to have an honest conversation about what I had done, what I was still learning, what energized me, and how I could help.

I never aced interviews by becoming the person I thought they wanted. I aced them by becoming more confident in the value of who I already was.

Getting the Job Was Only the Beginning

Of course, authenticity may help close an interview, but it cannot do the work for you. Once I had the job, four things mattered most.

1. Solving problems no one thought to solve

I did not want to wait for someone to identify every problem and hand me a set of instructions. I learned to look beneath the obvious assignment and ask better questions.

What are we missing? Where are people getting stuck? What have we accepted as normal simply because no one has stopped to challenge it?

I genuinely enjoyed difficult assignments. Challenges gave me an opportunity to think differently, test my abilities, and create value beyond the boundaries of my job description. Some of my most important contributions came from recognizing a problem before anyone formally asked me to solve it.

2. Cross-collaborating like my career depended on it

Because, in many ways, it did.

The best results rarely belonged to one person or one department. They came from people across recruiting, sales, marketing, operations, leadership, and client services sharing information and working toward a unified mission.

Cross-collaboration taught me that protecting your small piece of the work can limit the larger result. When people understand the mission, share what they know, and see how their responsibilities connect, the work becomes more cohesive—and far more effective.

For me, collaboration was never networking for the sake of visibility. It was about building enough trust to solve problems together.

3. Being resourceful

Resourcefulness became one of the most valuable abilities I carried from role to role.

Sometimes it meant drawing on knowledge, relationships, or experiences I had developed in previous jobs. Sometimes it meant knowing exactly who to call. Other times, there was no ready-made answer and no expert waiting in my back pocket. All I had was the determination to investigate, experiment, and figure it out.

I learned that not having the answer is rarely the real limitation. The greater limitation is believing you cannot move forward until someone gives it to you.

Resourcefulness is the ability to look at what you have—even when it seems insufficient—and create momentum from it.

4. Celebrating the small wins

This may sound less consequential than solving a major problem or landing a major client, but celebrating small wins had an impact far greater than most people realize.

A difficult market can make even talented teams question whether their work is making a difference. Recognizing progress—a promising conversation, a creative solution, a breakthrough with a client, or simply a teammate who refused to give up—reminded everyone that we were still moving.

Celebration was not about lowering the standard or pretending the larger challenge had disappeared. It was about protecting the team’s energy long enough to meet that challenge.

There is an important difference between a team fighting itself and a team fighting the problem together.

During the hardest seasons, I wanted the dynamic to be us against the market, not me against you. Celebrating small wins reinforced that unity. It reminded us that we shared the challenge, the mission, and ultimately the result.

The Best Interview Answers Are Collected, Not Invented

By the time I entered an interview, I was not searching for adjectives to describe myself. I had experiences that demonstrated who I was.

I could talk about the problems I had solved, the teams I had brought together, the resources I had found, the markets I had adapted to, and the momentum I had helped create when conditions were working against us.

That is the difference between telling someone you are capable and giving them evidence they can believe.

Yes, prepare for the interview. Research the company. Understand the role. Know your numbers, your projects, and your results. Practice explaining your experiences clearly. Keep track of what you accomplish—my first boss was absolutely right about that.

But do not confuse rehearsing with becoming.

The strongest interview answers are not manufactured the night before. They are collected over the course of a career. They are built every time you accept an opportunity that stretches you, learn a skill the market is beginning to demand, solve a problem that was not neatly assigned to you, collaborate across a boundary, use what you have to create what you need, or help a team remember that progress still counts.

Your résumé should document that story. Your interview should bring it to life. Your reputation should confirm it after you leave the room.

There may come a point when your track record and network begin doing much of the talking for you. That is a privilege, but it is not an accident. It is the compounded result of your work, your relationships, your willingness to evolve, and the way you made people feel while doing difficult things together.

The goal is not to become someone who never needs a résumé.

The goal is to build a career too rich to be contained by one.

The Takeaway

You begin preparing for your next interview long before you know it has been scheduled. Every meaningful opportunity you accept, unfamiliar skill you learn, difficult problem you solve, relationship you nurture, and small win you celebrate becomes part of the evidence you will one day bring into the room.

Say yes before you feel completely ready. Follow the market beyond the boundaries of your job description. Know your strengths, be honest about your weaker areas, and remain teachable enough to say, “I don’t know—but teach me. I want to know.” Lead with authenticity, curiosity, enthusiasm, and the willingness to figure things out.

Then let your work support your words.

The goal of an interview is not to perform the version of yourself you believe someone else wants. It is to communicate, with clarity and evidence, the value of the person and professional you have already worked to become.

• 550+ clinics nationwide

• 25 states

• Clinician-founded & clinician-led

• USA TODAY Top Workplace (multiple consecutive years)

• Mentorship, residency & leadership pathways

• Confidential introductions

• Referral bonus available

Seeking to get ahead in your PT career? Let’s connect.

📩 juliawconsulting@outlook.com