The Work Healthcare Keeps Adding Without Taking Anything Away

A health navigator is trying to help someone find the right local support. They may have access to a resource directory, a spreadsheet, notes from previous conversations, or a list of organizations they have learned to trust over time. They may also carry an enormous amount of knowledge in their own head: I think this provider accepts that insurance. That organization works with younger children. This program may have openings. I know someone there, let me call.

That knowledge is valuable. It reflects experience, relationships, judgment, and years spent understanding how the local system actually works.

But it also raises an important question: How much of their job should depend on remembering the system themselves?

At Living with SHAPE, we believe this question points to a much larger issue in healthcare. Organizations continue to add documentation, coordination, technology, follow-up, navigation, and new responsibilities to already complex roles, while much of the older work remains underneath.

Over time, healthcare professionals become responsible not only for doing their jobs, but also for compensating for fragmented information, disconnected resources, difficult workflows, and systems that depend on human memory to hold them together.

The problem is not always that healthcare needs more people doing more work.

Sometimes the system needs to carry more of the work itself.

Healthcare Professionals Carry More Than Their Job Description

Much of healthcare depends on work that rarely appears in a formal job description.

Experienced staff know whom to call when a process stalls. They remember which resource is actually useful, where information is hidden, which department responds fastest, and which workaround makes a difficult workflow manageable. They know the difference between how a process is supposed to work and how it works in practice.

This kind of knowledge is often what keeps healthcare moving.

The problem is not that people have expertise. Expertise is essential. The problem is when basic system reliability depends on individual people remembering everything the system itself has failed to organize.

When important knowledge lives primarily in someone’s memory, the organization becomes dependent on that person being available. New employees have to rebuild the same mental map. Staff turnover takes operational knowledge out the door. Different employees may solve the same problem in different ways simply because each person has learned a different path through the organization.

That creates hidden work, and hidden work consumes capacity.

Navigation Makes the Hidden Work Easy to See

Health navigation is one of the clearest examples. A directory can tell a navigator that resources exist. It may provide organization names, contact information, addresses, and basic descriptions. But knowing that something exists is only the beginning.

The navigator may still need to determine whether a resource fits the person’s actual circumstances. Does it serve their age group? Accept their insurance? Offer the needed service? Provide support in the right language? Serve their ZIP code? Have eligibility requirements? Work for someone with this particular combination of needs?

When those questions cannot be answered easily by the infrastructure, the navigator performs the filtering manually.

They search. They compare. They remember. They call. They interpret. They piece together information from multiple places.

The directory stores information. The person does the intelligence work.

This is closely connected to the burden we explored in Healthcare Friction Is Data. Repeated searching, calling, interpreting, and working around systems are not only inconveniences. They can reveal where the infrastructure is asking people to compensate for what it does not yet do well.

For patients, that friction can make healthcare harder to use. For employees, it becomes workload.

Experience Should Be Valuable, Not Required for the System to Work

There is real value in an experienced navigator knowing the community. They may understand local relationships, recognize subtle differences between programs, know which questions to ask, and understand what someone means even when the situation does not fit neatly into a category.

That is exactly the kind of expertise healthcare should protect.

But there is a difference between using experience to improve the quality of support and requiring experience to compensate for missing infrastructure.

A newer employee should not need years of accumulated memory before they can provide consistent navigation. A clinician should not need to know which hidden spreadsheet contains the most current resources. A care coordinator should not have to depend on personal relationships simply to discover what services are available.

Human expertise should strengthen the system. It should not be required to make the system functional.

When essential knowledge is better organized, experienced staff can use their judgment where it actually matters instead of spending so much of their attention retrieving basic information.

Better Tools Should Reduce the Search Work

The opportunity is not simply adding another technology platform. Healthcare already has plenty of tools. The question is whether a tool actually removes work.

Imagine a staff-facing navigation tool that allows someone to enter the circumstances that matter for the person in front of them and narrow available local resources accordingly. Instead of manually scanning a large directory, the navigator can quickly identify a smaller set of relevant possibilities.

The infrastructure handles more of the searching, filtering, organizing, matching, and information retrieval. The navigator can spend more time understanding what the person needs, explaining meaningful differences between options, exercising judgment, building trust, and helping someone decide what should happen next.

That is a fundamentally different use of technology. The goal is not to replace the navigator. It is to make the navigator’s expertise more valuable by removing work that never needed to consume so much human attention in the first place.

This is the same principle behind AI Should Make Healthcare More Human, Not Give Patients Another Door to Navigate. Technology creates meaningful capacity when it quietly reduces unnecessary work around care rather than simply creating another interaction people have to manage.

Better Infrastructure Can Make Quality More Consistent

When useful knowledge lives primarily in individual employees, the experience can vary depending on who happens to be working.

One navigator may know a local provider well. Another may never have heard of it. One employee may have recently learned that a program changed its eligibility requirements. Another may still be working from older information.

Those differences are understandable. No person can hold an entire changing healthcare and community ecosystem in their head.

Better infrastructure can make more of that knowledge available across the team.

That can strengthen consistency without eliminating human judgment. It can improve onboarding because new staff begin with a stronger foundation. It can reduce the impact of turnover because organizational knowledge does not disappear when experienced employees leave. It can also make resource discovery easier when the local landscape changes. This matters beyond navigation.

Healthcare organizations contain countless examples of knowledge that has become attached to individuals rather than embedded in systems: special workflows, workarounds, contacts, spreadsheets, process knowledge, and informal ways of getting things done.

When that knowledge becomes easier to organize and share, the organization becomes less dependent on individual memory and more capable as a whole.

Capacity Matters Most Where There Is Less of It

This problem becomes even more important in communities and organizations with limited workforce capacity.

Not every healthcare system has large navigation teams, extensive administrative support, abundant provider networks, or specialists dedicated to every part of the patient journey. In smaller communities, a relatively small number of people may carry enormous responsibility.

That makes every hour of human attention more important.

The answer cannot simply be asking those employees to become faster at searching, more knowledgeable about every resource, or better at holding fragmented systems together.

“Do more with less” is not a sustainable capacity strategy.

Better infrastructure can help a smaller team use the capacity it already has more effectively by reducing the amount of effort required to locate, organize, and interpret information.

The goal is not extracting more productivity from people. It is preventing avoidable work from consuming the limited human capacity already available.

The Deeper Question Is What Work Actually Requires a Human

The most useful workforce question may not be, How do we get more work done?

It may be: What work actually requires a human being?

Healthcare unquestionably needs people for judgment, empathy, context, relationships, trust, interpretation, and difficult decisions. Those are not secondary qualities. They are some of the most important capabilities healthcare has.

But many healthcare professionals also spend substantial time searching for information, checking multiple systems, repeating data entry, tracking down resources, recreating lists, manually routing information, and compensating for gaps between tools.

Those activities may be necessary today. That does not mean they should remain necessary.

A useful way to look at healthcare administrative burden is to separate the work that depends on human capability from work that exists because the infrastructure around humans is incomplete.

Better design gives capacity back by moving more of the second category into the system.

A Practical Leadership Practice: The Capacity Reclamation Check

Choose one role in your organization and look closely at what that person has to do to perform their job well. Do not begin with the official workflow. Look at the real work.

Ask:

• What does this person have to remember that the system could know?

• What do they repeatedly search for?

• What information do they manually compare or filter?

• What do they have to reconnect because systems do not communicate?

• What workarounds have become part of the normal process?

• What knowledge would be lost if this employee left tomorrow?

Then separate those tasks into two categories.

The first category is work that genuinely benefits from human judgment, relationships, context, or interpretation.

The second is work that exists because information is fragmented, difficult to retrieve, poorly organized, or trapped in individual memory.

That second category is where capacity may already be waiting to be reclaimed. The objective is not to automate everything on the list. It is to identify where better infrastructure could carry more of the routine cognitive and administrative load so people can focus their attention where human capability creates the greatest value.

Regenerative Psychology™ and Workforce Capacity

Regenerative Psychology™ asks whether the systems surrounding people strengthen human capacity or continually consume it.

When organizations depend on employees to remember, search, compensate, reconnect, and work around fragmented systems, valuable attention gets spent maintaining the infrastructure rather than performing the work people are uniquely equipped to do.

A regenerative approach asks a different question: What can the system carry so people can spend more of themselves on the work only people can do?

That does not diminish expertise. It protects it. Better infrastructure should make skilled people more capable, not make them unnecessary.

Stop Adding Work Without Examining What Can Disappear

Healthcare professionals have become remarkably good at making complicated systems work.

That adaptability is a strength. Experienced people notice gaps, create solutions, remember exceptions, build relationships, and keep care moving when the formal process is not enough.

But healthcare should be careful not to build organizations that depend indefinitely on that adaptability.

Every new responsibility deserves a companion question: What work can now disappear?

If a new technology is introduced, what searching, repetition, or manual coordination does it eliminate?

If a new process is created, what older process is no longer necessary?

If better information becomes available, what no longer has to live in someone’s memory?

If the answer is consistently “nothing,” then healthcare may be adding capability while continuing to consume the same human capacity underneath it.

The next opportunity is not simply asking people to become faster, more experienced, or more efficient at navigating complexity.

It is building systems that carry more of that complexity themselves. So the people inside healthcare can spend more of their attention on judgment, connection, trust, and care.

For healthcare leaders, a useful place to begin is one role and two questions: What does this person have to remember, search for, or manually connect just to do their job well?

And: Which of those things could the system already know for them?

That may be where meaningful workforce capacity is already waiting to be reclaimed.