A Lesson Worth Remembering

A few years ago, I worked with a patient recovering from a stroke.

He was 75 years old. A widower. The kind of person who had spent most of his life taking care of himself and expected to keep doing so.

He lived alone in the same house he had occupied for years. He wasn't particularly active, but he kept busy. He mowed his own lawn. Tinkered with his car when something wasn't running quite right. Ate more like a typical American than his physician probably preferred. The routines weren't glamorous, but they were his.

His daughter and son-in-law lived nearby. They were devoted to him, but like many families, they were balancing careers, school activities, and the constant demands of raising three children.

Then everything changed.

A stroke interrupted the life he had built and the independence he valued. As he began to recover, the family focused on the next step. They wanted him admitted to an inpatient rehabilitation facility (IRF).

From their perspective, the reasoning seemed simple. More therapy meant a better chance of recovery. More rehabilitation meant a better chance of returning home.

More care HAD to be better than less care, which was an understandable conclusion.

The challenge was that the admission coordinator's assessment told a different story. An IRF is designed for patients who can tolerate intensive therapy, typically three hours per day, five days per week. Based on his assessment at the time, there was significant concern that he would not be able to safely tolerate that level of activity.

The recommendation was for a different level of care.

The family experienced a denial.

The admission coordinator saw a mismatch.

The policy applied a standard.

Three distinct points of view, yet none fully explained the why. Recovery after a stroke is rarely a straight line. Endurance has limits. Healing demands more of the body than many people realize. Its purpose was to determine the environment in which recovery was most likely to succeed.

The same is true of many healthcare policies. They often show up at the moment they prevent something.

A transfer that cannot occur.

A treatment that must wait.

A process that requires another step.

A standard that limits available options.

We experience the restriction without seeing the risk the policy was designed to address.

We don't see the patient harmed by a missed medication during a transition of care.

We don't see the countless situations that convinced healthcare organizations, regulators, and clinicians that a consistent standard was necessary.

The people most affected by a policy rarely see the experiences that led to its creation.

To the family, the policy felt like a denial. A barrier standing between a loved one and what appeared to be a better path forward.

To the admission coordinator, the policy may have felt routine. One of many assessments completed in the course of helping patients find the most appropriate level of care.

Neither perspective revealed the story behind the decision.

Policies are often experienced as barriers, but they are rarely created for that purpose.

Behind every policy is a reason.

Sometimes that reason is a patient.

Medication reconciliation is an example.

Today, it is a familiar process performed countless times each day across healthcare settings. Yet medication reconciliation did not appear because someone wanted to create more documentation. It developed as healthcare organizations sought to reduce preventable harm associated with communication failures, medication discrepancies, and transitions of care.

EMTALA offers another example.

The law was enacted because patients seeking emergency treatment were sometimes turned away, transferred, or denied care based on their ability to pay or insurance status. The regulation itself reads like a legal requirement. The story behind it is about access to emergency care when people are at their most vulnerable.

Policies can't carry those stories with them. What remains are the requirements. The lesson that inspired them is often forgotten.

Medication reconciliation. EMTALA. Admission criteria for inpatient rehabilitation.

On paper, they look very different.

Yet they share something in common. Each exists because a risk was recognized that needed to be addressed.

Most of us encounter these policies long after those lessons have been learned.

We experience them as requirements.

As restrictions.

As paperwork.

And that's where perspective matters.

The easiest way to view a policy is to ask:

What is this preventing me from doing?

A more useful question is:

What is this trying to protect?

For this patient, the answer was not immediately obvious.

The family saw a loved one who needed rehabilitation.

The assessment saw a patient whose recovery remained fragile.

The policy recognized a reality both perspectives had to consider: not every patient benefits from the same level of care at the same point in recovery.

Sometimes the correct path is not the most aggressive one.

Policies cannot be written for one patient, nor can they account for every unique circumstance.

They must work for everyone. To accomplish that, they have to be objectively standardized and consistently applied.

But the very qualities that make a policy effective are often the same qualities that make it feel impersonal.

A policy cannot change based on who is asking. It cannot be applied differently depending on how compelling a story may be.

If it could, consistency would disappear.

Fairness would become subjective and trust in the process would eventually erode.

Policies are designed to create clarity and consistency.

The stories behind policies are deeply human.

The language used to write them often isn't.

That presents a challenge for leaders:

How to connect the objective, standard policy to the story behind it.

People rarely connect with objective policy language.

They connect with meaning.

A policy can tell someone what to do, explain the requirement, and define the standard.

But the policy does not explain why the policy matters.

Helping people understand the why changes how the policy is experienced.

The requirement remains. The process remains. The standard remains.

What changes is the understanding.

The conversation shifts from:

"Why are we required to do this?"

to

"Who does this protect?"

And that is often where frustration begins to soften because understanding has a way of changing perception.

I don't remember every detail of that patient's recovery.

I do remember the tension, though.

A family wanting what they believed was best. Clinicians recommending what they believed was safest. A policy sitting uncomfortably in the space between them.

At first glance, the policy seemed to be limiting an opportunity.

Looking closer, it was attempting to protect the very patient at the center of the decision.

That's true of more policies than we often realize. We experience the restriction, but we rarely see the risk. We read the requirement, but we rarely hear the story. We encounter the standard, but we rarely meet the people whose experiences made that standard necessary.

That's why understanding matters.

Not because every policy is perfect.

And not because every requirement deserves blind acceptance.

But because understanding helps us see beyond the language.

Beyond the barrier.

To the protection.

When a policy reads cold, it's often because the people it was designed to protect are no longer visible.

Sometimes that person is a future patient.

Sometimes it's a family facing circumstances we never witnessed.

Sometimes it's the patient sitting directly in front of us.

The policy is rarely the whole story.

Somewhere behind it is a lesson worth remembering.