On an assembly line for household appliances, 10 operators assembled motors for downstream production. Demand was high, but output consistently fell short—and many motors failed final inspection, requiring weekend overtime to catch up.
|
ADVERTISEMENT |
Managers tried the usual fixes. Push the operators, tweak the workstations, reduce wasted motion. For a day or two, it looked like progress. But by Friday, the numbers told the same story.
One afternoon, I asked the line boss, “Why do you think the line keeps falling behind?”
She shrugged. “Honestly? Some of the guys just... slow it down. Makes overtime worth it.”
The truth was unmistakable. Defective motors repaired on Saturdays at time-and-a-half pay often made up the week’s shortfall. The system rewarded defects. The constraint wasn’t the workers or the machines; it was a policy contradiction.
A system that unintentionally rewards defects
This is exactly the kind of insight upon which Eliyahu Goldratt built his book The Goal (North River, 1992): Local improvements rarely solve systemwide problems.
Lean tools exposed waste, but optimizing one step only moved the bottleneck downstream. The theory of constraints (TOC), Goldratt’s framework, identifies the true constraint—the handful of factors that ultimately determine throughput. But knowing the constraint isn’t enough if policies, incentives, or assumptions reinforce it.
Here’s where TRIZ comes in
The motor line presented a classic contradiction. Management wanted higher production, but the incentive system encouraged the opposite behavior. Lean and TOC identified the bottleneck, but resolving it required looking beyond traditional improvement tools.
TRIZ (a Russian acronym for “theory of inventive problem solving”), developed by Genrich Altshuller, teaches how to resolve contradictions directly instead of compromising or working around them.
Applied to the motor line, TRIZ led to a simple but powerful approach: Restructure pay and production expectations so that weekday output was rewarded, while overtime repairs no longer created a shortcut. The contradiction—high production vs. guaranteed overtime income—was resolved by redesigning the system, not by asking workers to try harder. Once this alignment occurred, output stabilized and defects dropped.
The beauty of TRIZ is that the same logic applies far beyond manufacturing. Consider American urban “stroads.” They try to be highways and city streets at the same time. Fast, but unsafe. Safe, but slow. The same contradiction principle applies; conflicting goals exist in the same system space. TRIZ encourages separating functions—protected pedestrian zones, dedicated cycling lanes, limited-access traffic corridors—just as we separated incentives from output on the assembly line. Speed and safety now coexist.
Organizations face similar contradictions every day. Executives want lower inventory but higher service levels. Operations teams are asked to increase throughput without adding staff. Quality leaders are expected to reduce variation while accelerating innovation. Many of these objectives seem mutually exclusive. But compromise isn’t always the answer.
Combining lean, TOC, and TRIZ provides a more powerful approach. Lean exposes waste. TOC highlights the few factors that limit system performance. TRIZ provides structured ways to resolve contradictions that make difficult problems seem unsolvable. Together, they move improvement beyond incremental fixes toward systemic solutions.
The motor line story demonstrates a universal lesson: The biggest obstacles to improvement are often policies, incentives, and assumptions quietly shaping system behavior.
When progress stalls, the most powerful question a leader can ask is not, “How do we work around this bottleneck?” It’s, “What contradiction in our system design is creating the problem?”

Comments
Lean, TOC, TRIZ
This sentence "Restructure pay and production expectations so that weekday output was rewarded, while overtime repairs no longer created a shortcut." seems unnecessarily vague. HOW did the pay and productions expectations change? Were the workers paid a piece rate? According to my training in lean, a piece rate is counter intuitive. If they were paid a piece rate how much was it and did it really make up the difference of 4 or 5 hours of overtime pay?
Awaiting your response,
Steve
Lean TOC & TRIZ: Restructure pay and production expectations?
That’s a helpful question, Steve. Thank you for pushing for more clarity.
In the article, I compressed what was actually a broader shift in how performance and incentives were aligned. This was not a move to a traditional piece-rate system; as you noted, that approach can introduce its own issues in a lean environment.
The changes focused on removing the unintended incentive to shift output into overtime:
Weekday expectations were clarified at the team level, with visible daily targets so that completing work in regular hours became the norm. The advantage of weekend rework was reduced or eliminated, primarily by tying performance recognition (and where applicable, variable pay) to first-pass yield and weekday completion rather than total repaired volume.
In other words, the system began to reward right-first-time output during regular hours, instead of volume recovered later through overtime.
The exact compensation mechanics can vary by organization (as I'm sure you're aware), which is why I kept that portion at a higher level. The central point is that once the contradiction was removed - a system asking for throughput while rewarding delay and defects - the behaviors and results shifted quickly.
Add new comment