“The Piece,” in One Piece Flow

The Envelope Game

A simple exercise makes this concept click for almost anyone. Take twenty pieces of paper, twenty envelopes, and twenty stamps. Fold all twenty papers first, then stuff all twenty envelopes, then seal all twenty, then stamp all twenty. That is batching, and it takes noticeably longer than the alternative: fold one paper, stuff it, seal it, stamp it, and move to the next, one complete envelope at a time.

This is where people usually get confused. Folding twenty papers in a row feels like focusing on one thing, doesn’t it? That confusion is exactly the point worth untangling, because it reveals the real question underneath one-piece flow: what actually counts as “the piece”?

The Real Pain: Thinking You’re Doing One Piece Flow When You’re Not

The real pain is believing you are already practicing one-piece flow simply because you are repeating the same action over and over, when you are actually still batching at a higher level. Folding twenty papers in sequence is focus on a task, but it is not focus on the actual deliverable.

That false confidence is dangerous precisely because it feels like discipline. Teams and individuals convince themselves they are already doing the efficient thing, which removes any motivation to look closer at what is actually slowing them down.

The Failure Pattern: Confusing a Step With the Piece

The failure pattern is mistaking any single repeated action for “the piece” itself, when the real piece is the complete, finished unit of value someone else is actually waiting on. In the envelope game, the piece was never a folded paper. It was a finished, sealed, stamped envelope ready to mail.

This same confusion shows up constantly in real work. Researching a set of drawings feels like meaningful, focused progress, but if the actual deliverable is a fully reviewed, double-checked, and transmitted submittal, research alone is just one step of a much larger piece still waiting to be completed.

A few signs tend to show up when a team has confused a single step with the actual piece, and they are worth checking honestly:

• Work in progress is measured by activity completed, like drawings reviewed or inspections done, rather than by fully finished deliverables ready to hand off.
• Similar sub-steps across multiple tasks get grouped together and done all at once, even when each task’s true completion is what actually matters.
• Nobody has clearly defined what “finished” specifically means for the task at hand before starting on it.

This Isn’t Intuitive, and That’s Okay

None of this is obvious, and it is worth being honest about that. Nearly every stage of life quietly teaches the opposite lesson: batching similar steps together feels efficient, and it gets reinforced in school, in early jobs, and in how most processes get taught by default.

Doing one thing at a time, all the way to completion, before moving to the next, runs against that lifetime of conditioning. Struggling to see it clearly at first is not a personal failing, it is just genuinely counterintuitive.

Gang Forms and the Missing Envelope

Here is the same question applied directly to construction. Building gang forms involves several steps: shaking out materials, assembling components on strongbacks, sheathing the forms, cleaning and oiling the face, and getting everything ready for rigging. Batching means doing step one across all four forms, then step two across all four, and so on, which means no single form is actually ready to use until every form has passed through every step.

Doing one form completely, all five steps, start to finish, before moving to the next, means that first form is ready for quality control and use far sooner. The same logic applies to submittals: researching drawings, reviewing the submittal, getting a second set of eyes, and transmitting it. Batching means researching all four submittals first, then reviewing all four, then double-checking all four, which delays every single one of them reaching a truly finished state. Processing one submittal completely before starting the next gets that first one out the door, reviewed and ready, far faster.

Why It Matters: The Customer Waits Four Times Longer

This matters because whoever is downstream, a client, an inspector, the next trade, another department, is waiting specifically for a finished piece, not partial progress on several pieces at once. In the envelope game, the first finished, mailable envelope arrives roughly four times faster under one-piece flow than it does under batching.

An exterior inspection and consulting company learned this directly. Their team was running two hours behind daily and twenty to forty reports backlogged, because they treated the inspection and the follow-up report as two separate batched tasks, doing several inspections first and pushing every report to later in the day. The fix was recognizing that the real piece was never just “an inspection,” it was a completed inspection and report together. Once they finished each inspection and its report before moving to the next site, they went from three or four inspections a day to five, and their entire backlog disappeared.

Teach the Framework: Ask What Needs to Be Finished

The core diagnostic question is simple: what actually needs to be complete before this is genuinely ready for whoever is next in line? A hospital’s piece is not a patient who has been seen, it is a patient who has been seen, diagnosed, and treated. A car manufacturer’s piece is not a partially assembled vehicle, it is a finished car. A construction company’s piece, at the largest scale, is a finished building, but at a smaller scale, it might be one completed submittal, one completed inspection report, or one completed form ready for concrete.

Getting this definition right matters more than the general instinct to “focus.” Focusing intensely on the wrong-sized piece, a single sub-step instead of the true deliverable, still produces the slower, batched outcome, just disguised as diligence.

A few practical questions help correctly identify the real piece before organizing any workflow:

• What does the person or team downstream actually need in hand before they can do anything useful with it?
• Is progress being measured by individual steps completed, or by fully finished deliverables ready to hand off?
• Would grouping similar sub-steps together across multiple tasks actually delay every single one of them reaching a truly finished state?

Turning This Into Daily Practice

Before starting any batch of similar work, whether it is submittals, inspections, forms, or reports, take a moment to explicitly define what “finished” means for one single unit. That definition becomes the actual piece that should flow through the process one at a time.

Watch specifically for the tempting shortcut of grouping similar sub-steps together, research all the drawings, make all the calls, draft all the reports, since that instinct is exactly what quietly turns a genuine one-piece flow effort back into disguised batching.

Connecting It Back to Building People, Not Just Projects

None of this happens automatically, since batching feels efficient and gets reinforced everywhere outside of deliberate Lean training. Teaching teams to correctly identify the real, finished piece in their own work is exactly the kind of practical skill that shortens durations and reduces backlogs without requiring anyone to work harder.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how to correctly apply one-piece flow instead of just relabeling batching as focus.

The Challenge

So here is the challenge worth carrying into your next task list: before organizing your day around a batch of similar work, stop and ask exactly what needs to be finished for one single piece to be genuinely done. As Jason put it plainly, “What is the piece that we want to flow?” On we go.

FAQ

What’s the difference between batching and one-piece flow?

Batching means completing the same step across multiple items before moving to the next step, like folding twenty papers before stuffing any envelopes. One-piece flow means fully completing one item, through every step, before starting the next, which consistently finishes faster overall.

Why does folding twenty papers in a row feel like focus if it’s actually batching?

Repeating the same physical action does feel like concentrated effort, but the real question is what the finished, useful deliverable actually is. In the envelope example, a folded paper is not the deliverable, a sealed, stamped, mailable envelope is, and batching delays that true deliverable significantly.

How does this apply to something like construction submittals?

If the true piece is a fully researched, reviewed, double-checked, and transmitted submittal, batching the research step across several submittals before reviewing any of them delays every single one from reaching that finished state. Processing one submittal completely before starting the next gets that first one out the door far sooner.

Why did the inspection company’s fix work so well?

They had been treating an inspection and its written report as two separate, batchable tasks, doing several inspections and pushing all the reports to later in the day. Once they recognized the real piece was the completed inspection and report together, finishing each one before moving to the next site, their backlog disappeared entirely.

How can someone correctly identify “the piece” in their own work?

Ask specifically what the next person in line, a customer, an inspector, another department, actually needs in hand before they can use it. That fully finished, ready-to-hand-off unit, not any single sub-step along the way, is the real piece that should move through the process one at a time.