Every Workflow Is a Values Statement

People often think culture lives in mission statements, strategic plans, or the words hanging on the wall in a conference room. I don't think that's where culture lives at all.

Culture lives in workflows.

Every workflow is a values statement.

The steps we require people to take, the approvals we demand, the forms we make them complete, the phone calls we ask them to make, and the barriers we place between them and the help they need all communicate what we truly value. 

Not what we say we value. What we actually value.

A workflow that requires a patient to call three different departments to access care tells them convenience was not the priority.  A workflow that requires a transgender person to repeatedly explain their identity to multiple staff members tells them dignity was not built into the process.  A workflow that prioritizes compliance but ignores patient experience sends a clear message about what matters most.

Systems speak.

Patients hear them. Staff hear them. Communities hear them.

The question isn't whether our workflows communicate values. They do. The question is whether they communicate the values we claim to hold.

In healthcare, we often talk about health equity, patient-centered care, access, belonging, and dignity. Those are important conversations. But values become real only when they are operationalized.

If we say we value access, why does it take six weeks to get an appointment?

If we say we value equity, why are some patients forced to navigate more barriers than others?

If we say we value people, why are our staff spending hours fighting systems instead of serving patients?

These are not philosophical questions. They are operational questions.

Some of the most powerful equity work doesn't happen in a boardroom. It happens when someone asks a simple question:

"Why are we doing it this way?"

That question has the power to uncover invisible barriers, unnecessary complexity, and workflows that have drifted away from the organization's mission.

Every form should have a purpose.

Every step should create value.

Every handoff should be intentional.

Every barrier should be justified.

And every workflow should be examined through the lens of the people experiencing it.

Operational leaders have a unique responsibility. We don't just manage processes. We design the conditions in which people experience care, access services, and do their work. Every decision about a workflow is ultimately a decision about whose time, dignity, and experience we value.

That's why I believe operations is one of the most powerful tools for advancing equity.

Not because workflows are exciting.

But because workflows become lived experiences.

Patients do not experience mission statements.

They experience appointment scheduling.

They experience check-in processes.

They experience referral pathways.

They experience pharmacy pickups.

They experience whether the system made their life easier or harder.

The same is true for staff.

Employees experience culture through hiring processes, onboarding workflows, communication channels, approvals, and decision-making structures. Long before someone reads an employee handbook, they have already learned the organization's values through its systems.

So the next time you're reviewing a policy, redesigning a process, or building a new program, ask yourself:

What values are embedded in this workflow?

Because every workflow is a values statement.

The only question is whether it's telling the story you intended to tell.