Good Operations Are Never Finished

A process can be standardized. That does not mean we are finished.

In fact, standardization is where something important begins. Once people begin using a new process, the operation starts teaching us things.

• Sometimes the process works exactly as expected.

• Sometimes it does not.

• Technology behaves differently in the real world than it did during testing.

• A step that looked simple on paper creates friction in practice.

• Someone discovers that the training did not quite prepare them for what they are seeing.

• A customer responds differently than expected.

And sometimes what looks like resistance is actually someone telling us that something is not working.

This is where learning becomes part of the operating system.

Learning Is More Than Training

Organizations often think about learning as a class, a training session, or an updated SOP. Those things matter. But learning is not the same as receiving information.

People learn differently.

• Some are visual.

• Some are auditory.

• Some need to physically do the work before the new process becomes familiar.

Leaders sometimes expect a light-switch change. The training happens, the new SOP is distributed, and tomorrow everyone executes the new process exactly as designed.

That may happen.

But it is not something I would count on.

Change requires time. And the bigger the change, the bigger amount of time needed.

Change requires people to understand what is changing, what they are being asked to give up, and what they are expected to do differently.

It also requires leaders to listen. Set the goal. Set the expectation. Then give people enough room to make the change while paying attention to who needs help along the way.

One Person + One Person + One Person is the organization.

Individual learning becomes organizational learning when we bring those experiences together.

Go See What the Operation Is Teaching You

When someone says, "This isn't working," I go back to the Three Actuals.

• Go to the Actual Place.

• Be with the Actual People.

• Observe the Actual Process.

Then determine what you are really seeing.

• Maybe the new process has a legitimate problem.

• Maybe the technology is not behaving as expected.

• Maybe there is a gap in the training.

• Maybe the expectation was not clear.

• Maybe someone has the resources they need and has simply decided not to perform.

Those are very different situations.

The mistake is deciding which one you have before you go see.

This is why leaders need to stay close enough to the operation to observe what is actually happening.

People will respect what you inspect.

Inspection is not about looking over someone's shoulder waiting for them to make a mistake.

It is about demonstrating that the standard matters.

It is about being present.

It is about listening.

And it is about learning what the operation is telling you.

Learning Becomes Communication

Learning that stays with one person is not organizational learning.

• If one person discovers a better way to perform a repetitive task, the organization should benefit from that discovery.

• If someone identifies a problem with a system, that knowledge should not disappear into a help-desk ticket.

• If a new standard creates an unintended consequence, the answer should not be for everyone to quietly create their own workaround.

The learning needs to move into actions.

That is where communication becomes part of the operating system. Communication is not simply telling people what changed. It is listening to what they are experiencing, sharing what has been learned, clarifying expectations, and making the appropriate adjustment.

• Sometimes the standard needs to change.

• Sometimes the training needs to change.

• Sometimes the technology needs to change.

• Sometimes the person simply needs additional support.

• Sometimes the expectation needs to be reinforced.

The point is not to change everything every time someone raises an issue. The point is to create an operation that can learn without losing its discipline. That is the difference between constant change and thoughtful improvement.

And Now We Loop

This brings us back to the beginning of this series.

The purpose of an operating system is not to create a perfect process that never changes.

The purpose is to create a system that can respond intelligently when the operation, the people, the technology, or the customer changes.

That is why this series has never really been a straight line.

• Diagnose taught us to see the actual operation.

• Design taught us to be intentional.

• Prove taught us not to assume.

• Standardize taught us to make what works repeatable.

• Learn teaches us that the standard itself can teach us something.

• Communicate makes that learning organizational.

And now we go again.

Diagnose. Because…

• The operation has changed.

• The people have changed.

• The technology has changed.

• The customers have changed.

• The business has changed.

That is not a failure of the operating system.

That is the operating system working.

Good operations are never finished.

The strongest operations have improvement built into the work and into the culture. They observe, learn, communicate, adapt, and improve.

Then they do it again.

That is where it sticks.

When thoughtful improvement becomes the oxygen the operation breathes.

The operating system is alive.

And when it is working as it should, it serves the goals of the leaders, supports the people doing the work, and ultimately serves the customer.