Lead-Time Reduction, One-Piece Flow and Pull

The Scene Before the Storm

Picture this: A sprawling cylinder manufacturing facility in Australia. Pallets scattered across the floor like forgotten chess pieces. Work-in-progress inventory piled so high you couldn't see your colleague three stations away. Twenty days—that's how long customers waited for their orders.

the practitioner stood at the edge of the shop floor, clipboard in hand, watching chaos unfold in slow motion.

"We had waste everywhere," he'd later recall. "But the worst part? We didn't even know how to see it."

The numbers told a brutal story:

• 20+ days of customer lead time
• 20+ days of work-in-progress clogging the floor
• 17 accidents per 100 employees
• Disorganized work areas that felt more like obstacle courses than production lines

Sound familiar? Maybe your operation isn't manufacturing cylinders, but that suffocating feeling of inefficiency? That gnawing sense that there has to be a better way?

That's where this story begins.

The Seven Deadly Wastes Hiding in Plain Sight

1. Over Production — Releasing 20 days of work at once created mountains of inventory nobody could manage
2. Waiting Time — Assembly workers stood idle while machined components sat in queues elsewhere
3. Transport — Parts traveled labyrinthine routes across the factory floor
4. Inventory — Cash tied up in work-in-progress that added zero customer value
5. Motion — Workers bending, reaching, walking excessively due to poor workstation design
6. Defects — Problems buried under piles of inventory, discovered weeks after they occurred
7. Over Processing — Steps that customers never asked for and wouldn't pay for

The Cultural Shift Nobody Wanted to Talk About

Implementing lean required something far harder than buying whiteboards and floor tape. It required changing how people thought about work.

For operators, it meant:

• Stopping the line when problems occurred (terrifying for anyone who'd been trained to keep production moving at all costs)
• Owning their workspace and machines through Total Productive Maintenance
• Speaking up about inefficiencies instead of working around them

For supervisors, it meant:

• Managing by value stream instead of by department
• Conducting daily "15 x 15" stand-up meetings focused on abnormal conditions
• Auditing standard work instead of firefighting

For leadership, it meant:

• Visiting the shop floor—actually visiting it, not walking through quickly
• Asking questions instead of issuing commands
• Accepting that the best ideas would come from the people doing the work

the practitioner arranged site visits to the originating manufacturer plants. He sent managers to lean conferences. He built a small library of books and made reading part of the job.

"We applied a learn-by-doing approach," he noted. "You can't read your way to lean. You have to practice."

Change #1: Crushing Batch Sizes

Before: Work released to the floor in 20-day batches After: Work released in 5-day batches

This single change—releasing smaller amounts more frequently—immediately reduced the tidal wave of inventory flooding the floor. Suddenly, problems became visible. When something went wrong, you found out in days, not weeks.

Change #2: Aligning Component Production

The machining cells for rods, barrels, and heads each operated on their own schedules. Final assembly waited for whichever component arrived last—sometimes for days.

The team restructured work so that components for each cylinder arrived at assembly together. Less waiting. Faster flow.

Change #3: Creating "Talking" Workspaces

Every cell got its own tracking board showing:

• Quality — First-time-through rates collected at final assembly
• Cost — Pieces per day, productivity trends
• Delivery — Lead time tracking, order status
• Safety — Near-misses, hazards identified

But the real genius was making these boards the center of daily team discussions. Every morning, operators gathered for brief stand-ups. They reviewed yesterday's performance, identified today's priorities, and flagged problems before they cascaded.

Change #4: Standard Work That Actually Worked

"Standard work" gets a bad reputation as bureaucratic documentation nobody reads. the practitioner's team flipped this.

They created visual layouts showing exactly how each process should flow—decision points, quality checks, timing requirements. These weren't filed in binders. They were mounted at each workstation, laminated and visible.

More importantly, supervisors audited standard work weekly. Not to catch people doing things wrong, but to verify the standard was achievable and to identify improvement opportunities.

Change #5: Total Productive Maintenance

Machines don't break down randomly. They send signals—strange noises, minor vibrations, slowly declining performance. But when operators are disconnected from their equipment, these signals go unnoticed until catastrophic failure.

The team allocated specific machines to specific operators. Responsibility breeds ownership. Operators began conducting daily checks, cleaning critical components, and catching problems early.

Before-and-after photos showed the transformation: grimy, neglected motors became clean, well-maintained equipment you could be proud of.

Key engineering insight

Somewhere in year two, something shifted.

Continuous improvement suggestions started flowing. Not from management mandates, but from operators who genuinely wanted to make their work easier.

The team established a "Lean Thinking CI Suggestion Scheme"—critically, this was not positioned as cost reduction. Management knew that framing it that way would kill engagement faster than anything.

Instead, suggestions focused on:

• Making work easier and safer
• Reducing frustration and wasted effort
• Improving quality for customers

Workers began bringing ideas to daily stand-ups. Small experiments proliferated. Some failed. Many succeeded. The accumulation of dozens of tiny improvements created momentum that no single initiative could have achieved.

The Results: Numbers That Matter

After three years of sustained effort, the transformation became undeniable:

Read that last number again. 35% spare capacity.

The same team, in the same building, with largely the same equipment, now had room to grow by more than a third—without adding a single employee or square foot of space.

What This Means for You

You might not run a cylinder manufacturing plant. But the principles that transformed the practitioner's operation apply everywhere work gets done.

Principle 1: You Can't Improve What You Can't See

Before implementing any changes, map your current process honestly. Follow a single order, project, or customer request from start to finish. Document every handoff, every delay, every moment the work sits waiting.

Most organizations discover that actual value-adding work constitutes a shockingly small percentage of total time. The rest? Waiting, moving, reworking, searching for information.

Your action: Pick one recurring process this week. Follow it physically through your organization. Time how long it actually takes versus how long it should take.

Principle 2: Batch Size Is the Hidden Killer

Whether you're processing invoices, writing code, or manufacturing widgets—smaller batches mean faster flow, earlier feedback, and less accumulated waste.

Your action: Identify one place where you batch work. Cut that batch size in half. Observe what happens.

Principle 3: Visual Management Changes Behavior

When performance is visible to everyone, people naturally adjust. This isn't about surveillance—it's about shared awareness that enables collective problem-solving.

Your action: Create one simple visual display that shows your team's key metric in real-time. It could be as simple as a whiteboard tracking daily completions.

Principle 4: Tools Don't Transform—Thinking Does

The factory didn't change because of whiteboards and floor markings. It changed because people started thinking differently about their work.

• "What is the customer actually paying for?"
• "Why does this step exist?"
• "What would make this easier?"

Your action: Ask your team one of these questions in your next meeting. Then actually listen.

Principle 5: Perfection Is the Compass, Not the Destination

the practitioner's team titled their forward vision "Pursuit of Perfection"—not "Achievement of Perfection."

The goal isn't to reach some final state where everything is optimized. The goal is continuous movement toward better. Every improvement reveals the next opportunity. There is no end.

Your action: Commit to one small improvement this week. Next week, commit to another. The compound effect will astonish you.

The Question That Changes Everything

Here's what I want you to consider:

If a high-mix, low-volume manufacturing operation—one of the most complex production environments imaginable—can slash lead times by 85% and eliminate workplace injuries entirely...

What's possible in your work?

Not theoretically. Not someday. This quarter.

The tools exist. The principles are proven. The only variable is whether you'll begin.

Where Are You in Your Journey?

I'd love to hear from you:

• Have you attempted a lean transformation? What worked? What didn't?
• What's the biggest source of waste in your current operation? Sometimes naming it is the first step to defeating it.
• What's stopping you from starting? Fear? Resources? Skepticism?

Drop your thoughts in the comments. Let's learn from each other the same way the practitioner's team learned—by doing, experimenting, and sharing what we discover.

If this story resonated with you, share it with someone in your network who's struggling with operational chaos. Sometimes the most valuable gift is showing someone that a better way is possible—and providing a roadmap to get there.

Failure trigger and engineering context

Then came the order that nearly broke them.

A major retailer wanted 10,000 units. Tight deadline. Big opportunity.

the practitioner did what seemed logical: he pushed harder. Every station worked at maximum speed. Parts flew from department to department.

The result?

• 300 minutes to complete a single batch (when it should have taken 30)
• Defects everywhere—wrong components, missing parts, sloppy assembly
• the practitioner found problems so late in the process that fixing them meant dismantling finished products
• Workers blaming each other while inventory piled up between stations

One evening, I found the practitioner staring at a whiteboard covered in production numbers.

"We're doing everything right," he said. "Why is everything wrong?"

I pointed to the pile of half-finished products between his stations.

"See that? That's not inventory. That's time. Money. Problems waiting to happen."

That pile was his chocolate conveyor belt—and it was accelerating toward disaster.

The Computer Assembly Example

Imagine you're building computers. Three departments:

• Department A: Builds the base unit (10 minutes each)
• Department B: Installs the monitor (10 minutes each)
• Department C: Tests the system (10 minutes each)

The Batch Approach (What the practitioner Was Doing):

Department A builds all 10 computers first: 100 minutes Then Department B does all 10: 100 minutes Then Department C tests all 10: 100 minutes

Total time: 300 minutes

But here's the killer detail—what happens when Department C finds a problem?

They find it in all 10 units.

The defect from Department A has now multiplied. You've got 10 broken computers instead of 1. You've wasted hours. And you've got three departments pointing fingers at each other.

The One-Piece Flow Approach:

Build one computer completely before starting the next.

Department A finishes unit 1: 10 minutes Department B immediately takes it: 10 minutes Department C tests it: 10 minutes

First finished computer: 30 minutes (vs. 300 for the first one in batch mode)

And here's the magic: if there's a defect, you catch it immediately. One unit affected. Problem solved before it multiplies.

Key engineering insight

I introduced the practitioner to a concept called Takt Time—the heartbeat of efficient operations.

Takt Time = Available Work Time ÷ Customer Demand

It's elegantly simple. If you have 8 hours of work time and need to produce 1,000 units:

8 hours × 60 minutes × 60 seconds = 28,800 seconds

28,800 ÷ 1,000 = 28.8 seconds per unit

That's your rhythm. Your pace. The drumbeat everyone marches to.

the practitioner stared at the calculation. "So we need one finished unit every 29 seconds?"

"Exactly. Not ten units every five minutes. Not zero units for three minutes, then a rush of twenty. One. Every. Twenty-nine. Seconds."

His eyes widened. "That means we can't have piles between stations. There's no time for piles."

Exactly.

. One-Piece Flow: The End of the Pile

We eliminated the queues between stations. Instead of dumping finished work into holding areas, each station handed off directly to the next.

The immediate change: problems became visible instantly.

When something went wrong at Station A, Station B knew within seconds—not hours. They could fix it together, in real-time.

the practitioner's favorite quote from this phase: "We used to bury our mistakes in piles. Now we can't hide them—so we fix them."

. Pull System: Work Only When Needed

Traditional systems push work forward: "I'm done with this, so here it comes, ready or not."

Lean systems pull work forward: "I'm ready for the next piece—please send it."

The difference is profound.

In a push system, every station works at maximum speed regardless of downstream capacity. Result: bottlenecks, backlogs, chaos.

In a pull system, work only moves when the next station signals they're ready. Result: smooth flow, no piles, visible problems.

We implemented this using Kanban—a Japanese term meaning "signal."

the practitioner's version was simple: colored squares on workstations. An empty square meant "send me work." A full square meant "wait."

No computers needed. No complex software. Just visual clarity.

. Physical Layout: Stop Walking, Start Working

I asked the practitioner to track how far his workers walked each day.

The answer was staggering: 170 meters per task cycle.

His workers were spending more energy traveling between stations than actually building products.

We redesigned the floor into a U-shaped cell—stations arranged in a horseshoe where workers could hand off directly to each other.

New walking distance: 90 meters.

That's 100 kilometers less walking per year. Per worker.

"We didn't hire more people," the practitioner told me later. "We just stopped wasting the people we had."

. Visual Controls: If You Can't See It, You Can't Fix It

Walk into most businesses and try to figure out what's happening. Is this pile normal? Is that machine behind? Is anyone winning?

You can't tell.

Lean operations make status visible at a glance.

the practitioner installed:

• Color-coded flags at each station (green = on track, yellow = falling behind, red = stopped)
• Daily production boards showing target vs. actual output
• Safety calendars tracking days since last incident

The psychology of this is powerful. When problems are visible, people fix them. When successes are visible, people sustain them.

One worker told me: "Before, I never knew if I was doing well. Now I can see it. And honestly? I want to keep that board green."

. Workload Balancing: No Heroes, No Victims

In the practitioner's old system, some workers were overwhelmed while others waited.

The Registration desk took 15 minutes per task. Prep took only 4 minutes. The Evaluation step took 6 minutes.

Takt time was 12 minutes.

See the problem?

Registration couldn't keep up (15 > 12), so they became a bottleneck. Prep finished too fast (4 < 12), so workers sat idle waiting.

The fix: redistribute the work.

We moved some tasks from Registration to Prep. New breakdown:

• Registration: 12 minutes ✓
• Prep: 7 minutes
• Pre-visit: 5 minutes
• Evaluation: 6 minutes

Everyone now worked within Takt time. No bottlenecks. No idle time. No heroes burning out while others watched.

. FIFO: First In, First Out

The final piece: ensuring the oldest work gets processed first.

Why does this matter?

In the practitioner's old system, urgent orders jumped the queue. "Important" customers got prioritized. New work got cherry-picked because it was easier.

Result: some orders sat for weeks. Customers waited endlessly. Problems aged and multiplied.

FIFO (First In, First Out) enforces discipline: the first item into the queue is the first item processed. Period.

We marked maximum queue lengths on the floor with tape. When a queue hit its limit, the upstream station stopped producing until space opened.

"It felt unnatural at first," the practitioner admitted. "Stopping work seemed wrong. But we were stopping to prevent problems, not create them."

The Results: What Changed

Ninety days after implementing these principles, the practitioner shared his numbers:

But the number that mattered most to the practitioner?

Zero overtime for the first time in four years.

"We're not working harder," he said. "We're just not working stupid anymore."

Your Chocolate Factory

Here's what I want you to understand:

You have a chocolate factory moment happening right now.

Maybe it's:

• Your inbox, where emails pile up because you batch-process them twice a day (instead of touching each one once)
• Your project workflow, where tasks get handed off in chunks that create bottlenecks
• Your team meetings, where problems stay invisible until they explode
• Your customer service queue, where first-come-first-served has been replaced by "whoever yells loudest"

The principles that saved the practitioner can save you:

1. Flow over batch. Handle one thing completely before starting the next.
2. Pull over push. Work only when the next step is ready for it.
3. Visual over hidden. Make status obvious at a glance.
4. Balance over heroics. Distribute work so no one drowns while others wait.
5. FIFO over chaos. Oldest first. No exceptions.

The Hardest Part (And Why Most People Fail)

I'll be honest with you.

This looks simple on paper. It's hard in practice.

Not because the concepts are complex. They're not.

It's hard because it requires you to:

• Stop rewarding speed and start rewarding rhythm
• Accept visible problems instead of hiding them in queues
• Trust the system instead of heroic individual effort
• Change physical spaces that have "always been this way"
• Confront the reality that your current chaos is self-created

the practitioner's biggest obstacle wasn't his workers or his equipment.

It was his own belief that busyness equals productivity.

Breaking that belief—watching him actually stop a line rather than create a pile—was the hardest battle we fought.

What the practitioner Would Do Differently

Remember the practitioner at the chocolate factory?

If she'd understood Lean, here's what would have changed:

1. She'd have set a Takt time with her supervisor: "How many chocolates per minute do we actually need?"
2. She'd have created a pull signal: "Don't send more until I'm ready."
3. She'd have made problems visible: "Hey, the pace just changed—something's wrong upstream."
4. She'd have balanced the work: "Ethel and I should each handle half, not compete for the same pile."

Instead of stuffing chocolates into her hat, she'd have calmly controlled the flow.

And she probably wouldn't have quit.

Your Move

Look around your workspace tomorrow.

Find your pile.

That stack of "pending" items. That backlog of requests. That holding area that's somehow become permanent.

Then ask yourself:

"What would happen if I processed these one at a time, in order, only when I'm truly ready for the next?"

Start small. One workflow. One process. One day.

The chocolates will stop piling up.

And you—like the practitioner, like the practitioner could have been—will finally catch your breath.

What's your chocolate factory moment? What pile has been driving you crazy?

Drop a comment below. I read every single one—and sometimes, talking through it is the first step to fixing it.