Source Note: This is a Foundation Essay from The Long Game. It draws on five specific examples from my time as Trim Shift Leader at GM’s Lansing Grand River (LGR) and Lansing Delta Township (LDT) assembly plants — the same city, the same company, in many cases the same people, twenty years apart. The contrasts are not hypothetical. They happened. I was there.
___________________________________________________________________________
Twenty years is long enough to forget why you built something. Long enough to keep the shape of a thing while hollowing out everything that made it work. I know this because I watched it happen. Twice, in the same city, with many of the same people.
In the early 2000s, at GM’s Lansing Grand River Assembly Plant, we built a standardized work system from scratch. Not because someone told us to. Because it was the foundational act of deploying frontline intelligence — the thing that made everything else possible.
Here is what that looked like.
Every team leader — every one of them — wrote their own job element sheets. By hand. They would go to the station, study the work, practice it, time it. Then they would take photographs of the parts, the positions, the sequences. They would print those photographs, cut them out, paste them onto the sheets. Tedious? Dramatically. Imprecise in places? Of course. But here is what mattered: when a team leader finished writing a job element sheet, the work lived in their head and in their hands. They owned the method. And because they owned it, they used it. They trained their people from it. They certified their people against it. They improved it when something better emerged. The document was not a bureaucratic artifact filed in a binder. It was the current best method, owned and continuously refined by the person closest to the work.
If there were two hundred stations on my line, there were thousands of job element sheets — because the content changed with every car line, every option mix. As a shift leader, part of my job was to read and sign every single one. That discipline existed because the system was alive. It breathed. It was the team leader’s instrument.
Fast forward twenty years. I arrived at Lansing Delta Township — same city, same company, in many cases the same people — and found something that looked identical from a distance. Standardized work binders on the floor. Job element sheets at every station. All the right words in all the right places.
But something fundamental had changed.
The sheets were computer-generated.
So I asked the obvious question: who wrote them? Well, there is a pilot team that reviews them. Who enters the data? Before long, the trail led exactly where I feared it would. Industrial engineers — or their functional equivalent — were writing the standardized work. A centralized group, removed from the floor, creating documents that the floor was expected to follow.
This is not a small difference. This is a civilizational difference.
When a team leader writes the job element sheet, they own the method. When someone else writes it and hands it to them, they are handed a procedure. The document looks the same. The binder looks the same. The station looks the same. But ownership has been transferred from the person doing the work to the person designing the system. We had, in the span of twenty years, returned to exactly what we started from — Taylorism — while maintaining the entire liturgical apparatus of lean. The vestments were worn. The hymns were sung. The congregation had no idea the theology had changed.
That is why I call it The Handmaid’s Tale. It looks like standardized work. It performs the rituals of standardized work. But the intent — ownership on the floor, intelligence deployed at the point of action — has been quietly, efficiently, irreversibly removed.
• • •
The second example is subtler, but if anything more profound.
At LGR, a basic first step for any operator at any station was this: look at the manifest of the vehicle coming toward you. Get a good sense of what you are about to build. Then, when you pick up the part, inspect it. Here are the specific defects you should look for. Then install it.
Read. Inspect. Install. Simple. Foundational. The operator was not just a pair of hands attaching components. They were a quality gate. They understood the relationship between the part, its condition, and its impact on the line. The job element sheet codified this — it told you which parts went where, the min-maxes, how to pick them up, and critically, what to look for before you installed them.
Twenty years later at LDT, those sheets were gone. The manifest-reading step? Gone. The inspection step? Gone.
The logic was impeccable. We pay the supplier to ensure quality. We pay the sequencing center to sequence correctly. Why should we pay our people to duplicate that effort?
Efficient. Absolutely efficient.
And absolutely devastating.
What had been removed was not redundancy. What had been removed was the operator’s relationship to the part. Their understanding of what good looks like. Their role as the last line of intelligence before a component disappeared into a vehicle that a customer would drive home. The floor had been reduced from an intelligent system to a logistics exercise — parts flowing to positions, hands attaching them, no cognition required or expected.
• • •
The third example involves a million-dollar decision that, on paper, looked like exactly the kind of investment a serious organization makes in quality.
We were launching a new vehicle model, and the persistent problem with the previous generation had been electrical defects — improper connections, bent prongs, modules not properly grounded. These defects were found at the end of the line, which meant the car had to be parked in the repair area, diagnosed, and fixed. And anyone who has worked in an assembly plant knows the real cost of an electrical defect. The diagnosis itself is usually straightforward — you read the error code. The agony is the disassembly. You strip layers of vehicle interior to reach where the defect lives, fix it, and then put everything back together. And here is the thing that no efficiency model captures: a car that is assembled right the first time and a car that is disassembled and reassembled are not the same car. The parts are interchangeable in theory. In practice, the customer is not getting a pristine vehicle. They are getting a vehicle that has been operated on.
So a decision was made: install a million-dollar diagnostic inspection system at the end of the trim shop. Plug into different aspects of the vehicle, run diagnostics, flag error codes. Catch the defects before the vehicle moves to chassis. Stop the line, fix it right there.
Logical. Expensive. And operationally catastrophic.
The system was installed at the end of the trim shop — a location with almost no footprint for stopping vehicles, diagnosing them, and repairing them. It sat in the buffer between trim and chassis. If you were aggressive enough with it — if you actually stopped every vehicle the system flagged — you would drain chassis of work and shut down the other half of the plant. Within the first few months, the reality became clear: it was infeasible. But telling the emperor he has no clothes is not how these things work. So instead, the theater continued. The system ran. It flagged. And quietly, nothing much happened with the flags.
Meanwhile, what actually solved the problem was what always solves it. The team members gained comfort and facility with the new product. They figured out the nuances. The electrical defects reduced — slowly, naturally, through repetition and learning and the accumulated intelligence of people who build cars every day. The million-dollar system did not teach anyone anything. It did not build capability. It consumed attention and resources that could have been directed at the other critical quality issues screaming for help. And worse — far worse — it reframed the quality problem as a detection problem. When defects were found, the response was to trace them back to the point of cause and discipline the person who made the wrong connection.
Efficient at detecting defects. Efficient at alienating the people who built the car. Six months into the launch of the new program, the million-dollar system was quietly ripped out. No announcement. No postmortem. People simply agreed, without saying so, that it did not do what it was supposed to do. And it disappeared. The Handmaid’s Tale again — the appearance of a quality system, performing the rituals of quality improvement, while the actual mechanism — frontline learning and ownership — was not only ignored but actively undermined.
• • •
The fourth example may be the most instructive of all, because it involves the very act of training itself.
Again, a new vehicle model. A decision was made — correctly, in principle — that people needed to be trained and certified on the new work content. They needed to develop the mental and muscle memory required to perform the steps of the job properly before the launch.
Here is how it is supposed to work. The pilot team — the group doing development work with the new vehicle — pulls in the team leader from each area. They work together. They write the standardized work for the five or six stations in that team leader’s zone. The team leader takes ownership of those documents, brings them back to the floor, trains and certifies their people, and then improves the documents as a living practice. The knowledge flows from development through the team leader into the team. The team leader is the bridge.
Here is what actually happened. People with almost no experience were pulled into the pilot team. Engineers essentially cut and pasted standardized work from the previous model with some modifications. And then — this is where it becomes theater — that data was fed into a computerized virtual training system. A picture of the vehicle appeared on a screen. The trainee would touch points on the picture to simulate tightening this fastener, turning this bolt, clicking this connector. The system tracked whether the trainee got the sequence right, whether they remembered which parts went where.
The quality control of this system was so poor that the pictures were often wrong. The sequences were wrong. The parts were wrong. Operators looked at it and said what any intelligent person would say: why are we doing this? I know how to build this car. I will figure it out.
But the theater continued. Everyone went through the system. Everyone was certified by the system. And the real training happened the way it always happens — on the floor, through repetition, through defects, through feedback, through the slow accumulation of knowledge that comes from actually building the product with your hands. The standardized work people actually used to ensure quality bore little resemblance to what was on the paper or what was in the virtual training. The system certified. The floor trained. Two parallel universes, one visible to management, the other actually producing cars.
So much theater. For such little value.
• • •
Four examples. Four different facets of the same inversion. The first stripped ownership of the method from the team leader’s hands. The second stripped the operator’s relationship to the part. The third replaced frontline learning with a surveillance system. The fourth replaced the team leader’s role as trainer with virtual certification theater.
But the fifth example is the one that named the thing. And to understand it, you first have to understand what a team actually is.
• • •
A team is not an org chart designation. It is not a name on a whiteboard or a set of stations grouped for administrative convenience. A team is a social organism. It forms the way all human bonds form — through proximity, repetition, and the small accumulated acts of sharing a life together.
Here is what a team looks like when it is real. These are people who know each other. They talk about their kids’ football games while they work. They argue about what happened with their girlfriends the previous evening. They horse around. They bring food for each other — someone’s wife made too much biryani, someone else brought tamales, someone shows up with a sheet cake because it is their daughter’s birthday. During breaks, they eat together. They celebrate things together. They grieve things together. They share the ordinary texture of their lives in the minutes between the work, and because of that sharing, they become people to each other. Not headcounts. Not labor units. People.
And on the line, that social fabric is what makes everything else work. They help each other out. When someone falls behind, the person next to them steps in without being asked — not because a procedure says to, but because that is what you do for someone you know. They watch each other’s quality. They flag problems for each other. They teach each other tricks they have figured out. The team leader is the glue — the person who holds that social construct together, who knows each member’s strengths and struggles, who creates the conditions for the group to function as something greater than a collection of individuals.
In that social construct, the work happens. In that social construct, frontline intelligence is deployed. And it blooms. Not because someone mandated it. Because the human conditions for it exist — trust, familiarity, mutual obligation, pride in shared effort. The team is the soil. Everything else is what grows in it.
Now. Here is what happened.
The model year was running long in the tooth. The new vehicle was coming, but not yet. In the meantime, market demand required more volume — not enough for a business case to add a third shift, but enough that something had to give. So the plant did what plants do under pressure: it increased operating hours by staggering shifts, splitting breaks, stretching the schedule. On paper, this maximized utilization of the asset. In practice, it destroyed the most fundamental unit of lean.
The team.
By staggering start times and break schedules, team members who were nominally part of the same team never overlapped long enough to be together. They did not start work at the same time. They did not take breaks at the same time. Extra relief people were added to the line so that each person could take their half hour individually — one at a time, rotating off and rotating back. So a break was no longer a team gathering. It was a solitary half hour. One person sitting alone with a cell phone, watching a YouTube video, eating whatever food they had brought — by themselves. Then clamoring back to the line so the next person could be relieved. No conversation. No human contact. The food stopped being shared because there was no one to share it with. The stories stopped being told because there was no one to tell them to.
And on top of that, the plant had issued bone-conducting headphones — the kind that sit on your cheekbone and let you listen to whatever you want while you work. So now every team member was in their own acoustic world. They did not talk to each other while they worked because they were listening to their own music, their own podcasts, their own silence. They did not talk during breaks because they took breaks alone. They were, in every meaningful sense, strangers who happened to work adjacent stations and share a team leader’s name on a whiteboard.
Teams of strangers. Building cars together. Going home without ever having spoken.
And then one day, a team member looked at me and said: Venki, what team?
That was the moment this phrase — The Handmaid’s Tale — crystallized in my mind. Because here was a plant that had team leaders, team boards, team meetings on the schedule, team metrics on the wall. Every artifact of the team concept was present and accounted for. And the team itself did not exist. The humans who were supposed to constitute it had been rendered invisible to each other by scheduling optimization and consumer electronics. The most foundational element of lean — people who know each other, work together, solve problems together, hold each other accountable, and take pride in what they build together — had been dissolved. Not by malice. By efficiency.
• • •
Five examples. Five layers of the same erosion.
Ownership of method, removed. Relationship to the part, severed. Quality reframed as detection instead of learning. Training reduced to certification theater. And finally, the team itself — the irreducible human unit on which every other element depends — dissolved into a collection of isolated individuals wearing headphones.
None of these changes happened because someone decided to abandon lean. Every one of them made perfect sense to the leaders who approved them — leaders who had not been present when the original systems were built and therefore did not understand why those systems existed. They saw inefficiency where there was investment. They saw redundancy where there was resilience. They saw manual processes where they imagined digital precision. They optimized for cost where the original architects had optimized for capability.
This is how the return to Taylorism happens. Not through a dramatic policy reversal. Not through a boardroom decision. It happens through a thousand small, reasonable, well-intentioned efficiency improvements, each one removing a thin layer of frontline ownership until one day you look at the floor and realize that what you have is not a lean system. It is a traditional system wearing lean’s clothes.
And it does not help that in a unionized environment, the union exists to fight Taylorist management. Even when the management is not consciously Taylorist, the union will fight it as though it is. Because historically, that is what management has always been. So the adversarial dynamic reinforces itself — management optimizes, the union resists, and the possibility of genuine collaboration around frontline intelligence disappears into the gap between them.
What I found when I returned to Lansing for my Walden Pond years was a Handmaid’s Tale. The rituals of lean, performed faithfully. The substance of lean, gone. Not because anyone killed it. Because the foundational understanding of deploying frontline intelligence no longer existed in the leaders who ran the system. Without that understanding, every decision defaults to the Taylorist model — tell them what to do, check whether they did it, discipline them when they did not. It is the gravitational pull of industrial management. Without continuous, conscious effort to resist it, you always fall back.
So my question to everyone who finds themselves at different stages of lean — in any industry, at any scale — is simple:
Do you have the artifacts of lean? Or do you have lean?
Do you have the binders, the boards, the metrics, the certifications, the team names on the whiteboard? Or do you have deployed frontline intelligence — people who own their methods, understand their parts, learn from their defects, train their own, and know each other’s names?
• • •
And if the answer is uncomfortable — if you recognize your own floor in these examples — then the harder question follows: how do you go back? How do you restore the foundation?
I have been vexing with this for a long time. Decades now. And the question I keep circling is whether Western companies made a fundamental mistake in adopting lean — not because lean is wrong, but because they never fully understood the foundation that needed to be established first. The degree of effort and intention required to abolish the Taylorist way of thinking was massively underestimated. And since it was never abolished, lean was layered on top of it. The topsoil looked different. The bedrock never changed. And over time, as the examples above illustrate, the bedrock reasserted itself.
Does lean work in situations like that? My answer is it absolutely does. I do not have a better system to replace it with. I do not think one exists. But I have come to believe that before you can put lean back in — genuinely, with deployed frontline intelligence as its foundation and not its decoration — you have to first build something that was never built the first time around. A foundation. A different understanding of what labor is, what the floor is capable of, and what the relationship between the people who design the system and the people who operate it must look like.
That foundation will take years to build. It requires leaders who understand that frontline intelligence is not a tool to be deployed when convenient and withdrawn when the spreadsheet demands it. It is the operating system itself. Everything else — the standardized work, the quality systems, the training, the teams — runs on top of it. Without it, you get theater. You get a Handmaid’s Tale.
This is what I have been writing about. This is what Already Paid For is about. Not lean as a methodology. Lean as a commitment — to the intelligence, dignity, and capability of every person on the floor. Until that commitment is foundational, not decorative, we will keep building Handmaid’s Tales and wondering why the results do not follow.
The vestments were worn. The hymns were sung. The theology had regressed to the mean. Taylorism.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit thelonggameforall.substack.com
