Let Flow Be Your Teacher

A mentor once told me:

“If I had to teach Lean using only one concept, it would be flow. Make the work flow. Where it doesn’t, learn why—and make it flow better.”

The longer I work with manufacturing and operations teams, the more I agree with him.

Lean is often introduced in a classroom.

We explain value, waste, flow, pull, standard work, visual management, problem-solving, workplace organization, and continuous improvement. We introduce Japanese terms, draw diagrams, and share examples from industries that may look nothing like the participant’s operation. Each concept is valid.

But when we try to teach all of them in a few hours—or even a few days—the ideas can remain abstract and rarely transfer back to the manufacturing floor. People leave the training with a collection of tools but no clear idea where to begin.

Flow gives them a place to begin.

Start With a Simple Question

Can the work move from beginning to end without unnecessary interruption?

That question works whether the process makes a physical product, repairs equipment, fulfills an order, or responds to a customer request. Every process has something that needs to move.

It may be:

• Material

• Information

• A decision

• A customer request

• A technical drawing

• An approval

  
  

When that movement stops, there is something to learn. That stoppage may reveal missing information, unclear priorities, excess inventory, unreliable equipment, a quality defect, confusing business rules, poor workplace organization, or a decision that only one person is authorized to make.

In other words, following flow naturally leads us to nearly every other Lean principle.

You do not have to teach the entire Lean system before beginning. Start by watching the work move. Then pay attention to where it doesn’t.

Flow Makes Problems Visible

Most leaders begin by looking at results. They review revenue, cost, quality, output, on-time delivery, inventory, labor efficiency, or customer complaints. Those measures are important. They tell us whether the business is producing the outcome we expected. But they do not always tell us why.

When a result is off target, leaders often respond by asking for more effort.

Can we work overtime?

Can we expedite the order?

Can we add people?

Can we adjust the schedule?

These actions may temporarily protect the result, but they can also hide the process problem. Flow asks the leader to do something different.

Use the business result as a signal. Then go observe the process that creates it.

Where is the work waiting?

Where is it moving backward?

Where is it being handled more than once?

Where is someone searching for information?

Where is the team working around a rule, policy, or approval?

Where has the work stopped entirely?

You cannot answer those questions from a spreadsheet alone. You have to go see the work.

A Ten-Day Process With Six-Month Delays

A recent engagement involved a technical repair center with a 10-day turnaround target. The team was experienced. People cared about serving the customer. Everyone was busy. Yet product was choking at several points in the process.

Some repairs were waiting because billing information was missing. Others were complete but could not move because a customer had not approved the quote. Some had incorrect or incomplete shipping details. In several cases, product had been sitting in the process for more than six months.

The issue was not that technicians needed to work faster. The issue was that the work could not flow. Complex business rules made it difficult to know what should happen next. Important information was stored in different places. Ownership was unclear. Team members had to search, ask around, or wait for someone else to make a decision. The delays had become part of the normal operating environment.

By following the stopped work, we could see the actual problems.

We worked with the team to simplify the business rules and put the right information where people needed it. That allowed them to make decisions and move product forward without relying on repeated follow-up and individual heroics.

In the first week, the team moved over $250,000 of product out of the process. That result did not come from telling people to work harder. It came from helping the work flow.

What Can Flow Teach You

When you try to improve flow, the process begins teaching you what it needs. If material is waiting for an operator, you may learn about staffing, skill coverage, work balance, or standard work. If an operator is waiting for material, you may learn about scheduling, replenishment, supplier performance, or inventory rules. If completed work is waiting for approval, you may learn about decision rights, escalation, or unnecessary controls. If people are searching for information, you may learn about visual management, system design, or workplace organization. If defective work keeps returning to an earlier step, you may learn about quality at the source, process capability, or unclear requirements. If too much work has been released at once, you may learn about work-in-process, prioritization, pull, or capacity.

The concepts do not need to be taught as disconnected lessons. They emerge from a real problem the team can see. That changes the learning experience. Instead of asking people to remember a Lean tool and search for somewhere to apply it, we begin with stopped work and select the method that helps remove the impediment. The problem creates the need for the lesson.

The lesson has immediate context. And the team can see whether the change actually helped.

One Beaver Dam at a Time

I think about flow like canvassing a river.

You follow the water until you reach a beaver dam.

You do not stand at the riverbank and launch twenty improvement projects based on what you imagine might be happening upstream.

You go to the obstruction.

You study it.

You understand what is preventing the water from moving.

Then you remove or reduce the blockage.

Once the water begins moving again, you follow it to the next impediment.

That is the systematic and continuous nature of improvement.

Improving one point in the process does not mean the entire system is finished. It means the next constraint becomes easier to see.

The lesson continues.

This is also why flow can teach nearly the entire Lean system.

As you work to make the process move, you will encounter questions about quality, workload, information, inventory, equipment, standards, decisions, training, layout, and customer demand.

Flow connects them.

It gives leaders and teams a practical reason to learn each concept when it becomes relevant.

The Leader’s Role

The leader does not need to arrive at the process with the solution. The leader needs to arrive with curiosity.

1. Observe what is happening.

2. Ask where work routinely stops.

3. Ask the people doing the work:

   • what they are waiting for,

   • what information is missing.

   • which rules make the job harder.

4. Help them decide what to improve first.

The people closest to the process usually know where the friction is. They may not have the authority, resources, or cross-functional support to remove it. That is where leadership matters.

The leader’s role is not simply to demand better results. It is to help the team improve the process that produces those results.

A Simple Place to Start

When a business result is off target, resist the urge to solve it from the conference room.

Use the result as the signal, then follow the work.

• Observe the process.

• See where work stops.

• Understand why.

• Remove or reduce the impediment.

Then follow the flow until you find the next place to learn.

To request a case study showing how this approach has been applied in practice, or to schedule a conversation with Bareither Group Consulting, contact BGC.

That’s how you #improveLESS … and get better results.