Recently, I made a major change in my career.

I left a middle management role and moved back to a frontline nursing leadership role.

Some people might look at that kind of move and see it as a step backward. I don’t.

For me, it was the right move for a number of personal and professional reasons. But what surprised me most is how much I’ve learned in such a short period of time.

Many leaders follow a fairly predictable career path. They move from bedside or frontline practice into leadership, then continue moving further and further away from the daily work as their careers progress.

That distance can create perspective.

It can also create distortion.

Being back at the frontline has reminded me that certain leadership truths are much easier to understand when you are close enough to see how the work actually happens.

Here are five lessons I’ve learned.

1. The leadership-frontline gap is bigger than you think

Within my first few weeks, this became obvious.

There were initiatives that had supposedly been “rolled out” but were essentially invisible at the frontline. They hadn’t stuck. In some cases, staff barely knew they existed.

Even more revealing was what happened when frontline staff asked for clarification or support.

Sometimes the response was an email quoting a policy that didn’t quite make sense in practice.

Sometimes it was a promise to “take it up the chain.”

Sometimes it was a suggestion to form another workgroup, committee, or meeting to address a simple process question that probably could have been solved in a few hours by watching the work and talking to the people doing it.

This creates frustration.

It also incentivizes workaround culture.

When solving a problem locally is faster, clearer, and less bureaucratic than going through official channels, people will solve it locally. Sometimes that works. Sometimes it creates variation, risk, and confusion.

But the behavior makes sense.

At the root of this is a flaw in how we often approach change. We push too much from the top down and expect compliance at the point of care.

I’ve become even more convinced that many changes need to be built more from the bottom up.

That requires decentralized command. It requires empowering frontline leaders and staff to make decisions within clear guardrails, rather than trying to micromanage practice through increasingly precise and verbose policies.

2. You don’t improve patient care in a conference room

This is closely related, but it deserves its own point.

After only a short time back on the frontline, I can predict with surprising accuracy the leadership response to many operational questions.

“We’ll bring it to the next meeting.”

“Let’s gather the stakeholders.”

“We should schedule time to discuss that.”

Sometimes that is appropriate. Meetings are useful for coordination, decision-making, and alignment.

But you know what I almost never hear?

“Let me come see what that looks like.”

That should probably be one of our most common responses.

Meetings are comfortable territory for administrators. They feel productive. They create agendas, notes, action items, and the appearance of movement.

But meetings are often poor diagnostic tools for workflow problems.

Most people have difficulty translating lived experience into a clean verbal summary. And the people who understand the work most intimately are often not in the meeting at all, because they are busy taking care of patients.

If the problem is happening at the point of care, the first step should usually be to go there.

See the workflow.

Watch the friction.

Ask questions.

Listen to the people doing the work.

We need to replace the reflex of “let’s talk about it” with “let’s go see it.”

If spending meaningful time at the frontline feels burdensome to leaders, that is not just a scheduling problem. It is a culture problem.

3. Staff care, but not always about what leaders think they care about

I don’t mean this cynically.

Most frontline staff care deeply about doing good work. They care about their patients. They care about their teammates. They care about feeling competent and doing a job they can be proud of.

They also care about getting out on time, being able to take earned time off without guilt, having a manageable workload, enjoying the people they work with, and not ending every day feeling drained.

What many staff do not naturally care about are things like fiscal performance, strategic initiatives, quality dashboards, committee structures, or the priorities of senior leaders they barely know.

That does not mean those things are unimportant.

It means they are usually not motivating on their own.

Too often, leaders use organizational priorities as if they are self-evident reasons for change.

“We need to improve this metric.”

“This is part of the strategic plan.”

“This is a system priority.”

Those statements may be true, but they are rarely enough.

As leaders, one of our most important jobs is translation.

We have to translate the “what” and “how” of organizational priorities into a compelling “why” that makes sense to the people doing the work.

And to do that well, we first have to understand what actually matters to them.

Which brings us back to the first two points.

You cannot translate effectively from a distance.

4. The simplicity of the plan is one of the biggest predictors of success

One of the first projects I was assigned after returning to the frontline involved sharing an updated process for a certain type of patient visit.

After discussing it with our providers and administrative coordinator, we realized the actual change had only a few components.

Reception needed to hand out a new questionnaire at check-in.

Clinical staff needed to use a new flowsheet in the EMR and capture the questionnaire into the appropriate fields.

Clinical staff needed to learn one new procedure that could be taught in about 15 minutes, while we also verified technique for another procedure they were already doing.

Providers needed to use a new EMR toolset to document the encounter.

That was basically it.

In the clinical setting, implementing this required a few well-planned conversations, some focused teaching, and intentional follow-up. Less than two hours of actual work.

The official plan was much bigger.

There needed to be a “kickoff meeting” to discuss the “new process” and “strategize” the implementation. Scheduling that meeting took weeks because everyone’s calendar was packed.

Meanwhile, we rolled out the process.

Two months later, the leadership team offered a date for the kickoff meeting.

It was already done.

This may sound like I am just criticizing meetings again, but the real point is more subtle.

The change itself was simple. We were substituting a few forms and tools within an existing workflow. It did not need a complicated strategy or a detailed rollout plan. It needed prompt action and focused follow-up at the point of care.

When planning a change, look for the shortest responsible path.

Do not create complexity just to make the work feel official.

This is not only about efficiency. It is also about packaging.

When leaders overbuild a simple change, staff notice. It creates eye rolls. It makes the change feel bigger, heavier, and more annoying than it needs to be.

Sometimes the best implementation message is:

“This is a simple update. Here’s what’s changing. Here’s why it matters. Here’s how we’ll support you.”

Not every change needs a campaign.

Some changes just need clarity, follow-through, and proximity to the work.

5. Visibility and presence matter more than leaders realize

One of the most surprising parts of returning to the frontline has been realizing how infrequently staff interact with leaders outside their immediate area.

That surprised me partly because I have been on the other side.

I know how much effort many leaders put into staying visible, staying connected, advocating for staff, and making thoughtful decisions behind the scenes.

But the frontline often does not see that.

More than once, I have watched a leader arrive for a meeting or a brief check-in, have a conversation, leave, and then heard staff ask:

“Who was that?”

That is hard to hear, especially when the person is someone I know, respect, and have worked beside. In many cases, these are leaders who advocate fiercely for staff in rooms those staff will never enter.

But from the frontline perspective, that advocacy is invisible.

And if people do not know you, they are less likely to trust you.

This becomes especially important during change.

When leaders show up to communicate a major initiative, staff are not only evaluating the message. They are evaluating the messenger.

Do they know this person?

Do they trust them?

Do they believe this person understands their work?

Do they think this person will still be around after the announcement?

If the answer is no, skepticism is predictable.

This is not about blaming individual leaders. Many leaders are overloaded with responsibilities that do not add much value to their core leadership mandate. In ambulatory care, the challenge is even harder because sites are often geographically distributed.

But the difficulty does not make presence optional.

It makes it more important.

Leaders need to treat visibility as real work, not extra work.

That means scheduling it.

Protecting it.

Measuring it, perhaps.

And taking personal responsibility when too much time has passed since they were meaningfully present with the people they lead.

The further away you are from the frontline, the more intentional your presence has to become.

So what?

When I first started making these observations, I found them difficult to swallow.

The reality stings a little.

Many leaders work hard. They care about staff. They want to stay connected to the work. They want to make good decisions. They want to support patient care.

But good intentions do not automatically translate across distance.

Everything looks different from different altitudes.

From an airplane, a mansion can look like a tiny model. From the ground, it is large, detailed, and complex. Both views are real. They are just incomplete without each other.

That is what returning to the frontline has reminded me.

Leaders need both altitude and proximity.

We need meetings, but we also need observation.

We need strategy, but we also need simplicity.

We need organizational priorities, but we also need translation.

We need to advocate for staff behind closed doors, but we also need to be known by the people we are advocating for.

If you are in leadership, it may be worth asking yourself:

When was the last time I spent meaningful time at the frontline?

Not a quick walk-through.

Not a scheduled appearance.

Not a meeting in a conference room near the unit.

Real time.

Watching the work.

Asking questions.

Understanding friction.

Getting to know the people.

Because if the people you lead do not know you, do not see you, and do not believe you understand their reality, they are much less likely to follow you when the work gets hard.

And in healthcare, the work is almost always hard.