Which Lean Principle Should You Follow?

Which Lean Principle Do We Follow When They Conflict?

Here is a scenario that does not get talked about enough in Lean construction circles. You are designing an invoice process. If you add a specific communication step, it honors the trade partner, demonstrates transparency, and goes the extra mile in your service. If you skip that step, you eliminate over-processing, reduce administrative burden, and keep the system moving faster. Both of those choices are defensible under Lean principles. Both of them have a Lean principle that says “yes.” And they are pointing in opposite directions.

Which one do you follow? Most Lean training programs do not give you a good answer to that question, because most of them present the principles as a clean, harmonious framework where everything points the same way. In the field in the actual decisions of a real project, a real accounting department, or a real PM trying to choose between two legitimate good ideas, the principles will occasionally conflict. Acknowledging that honestly, and having a framework for resolving it, is what separates teams that can actually implement Lean from teams that can recite it.

The Invoice Story That Made It Clear

The CFO of Elevate Construction brought a question about an invoice process. There was a step in the process that could go one of two ways. Including the step would require extra time and effort from the accounting team, it bordered on over-processing, which Lean categorizes as one of the nine wastes. But the step also communicated more transparently with the client and demonstrated an extra level of care and respect. Skipping it would be leaner from an administration standpoint. Including it would be more respectful from a relationship standpoint.

Both the waste-elimination principle and the respect-for-people principle are genuine Lean principles. Neither is wrong as a principle. They are just pointing in different directions in this specific situation. And the question which one do you follow is a question that cannot be answered by consulting a list of principles, because the list contains both of them.

Lean Principles Do Conflict

Before getting to the resolution, it is worth saying this clearly: Lean principles can and do conflict with each other. Some people in the Lean community would push back on that statement, arguing that when principles seem to conflict, someone is misapplying one of them. That may sometimes be true. But it is not always true, and pretending it is always true is how practitioners end up with no honest framework for navigating the real decisions that arise in real work.

Here is a clear example. Paul Akers built a manufacturing company famous for its Lean discipline. When he began working with Japanese business partners, they required that his product labels be measured and placed to the nearest millimeter, precise, consistent, perfect. Following that standard is, in one reading, an expression of strive for perfection and respect for the customer. In another reading, it is over-processing, unnecessary precision that adds time and effort without meaningfully changing the outcome. Both readings are legitimate. Both are grounded in genuine Lean thinking. And they conflict.

The six Lean principles that Elevate Construction teaches, respect for people, nature, and resources; stability and standardization; one-piece process and progress flow; flowing together on Takt time and pull; total participation with visual systems; and quality and continuous improvement, are all real and all important. But they are not always in agreement with each other in every specific situation. Accepting that reality is not a weakness in the framework. It is an honest description of how principles work when applied to complex, real-world decisions.

The Theory of Constraints as the Resolution Tool

When two legitimate principles conflict, the resolution framework comes from Eliyahu Goldratt’s Theory of Constraints. In any system, there is always one limiting factor, the constraint that is doing more than anything else to hold back the system’s overall performance. Every improvement effort directed at something other than the constraint produces local gains that do not improve the whole. Only improving the constraint improves the system.

Applied to conflicting Lean principles, the question becomes: which principle, if violated, creates the most limiting constraint on the outcome? Not which principle sounds most important in the abstract. Which specific violation, in this specific situation, will do the most damage to the system, the people, and the work?

In the invoice story: if adding the extra process step creates so much administrative burden that the team cannot actually serve the client effectively, if the over-processing cascades into the team falling behind on other work, missing deadlines, or reducing the overall quality of service, then the waste elimination principle is the one that protects the constraint. The over-processing is the more limiting factor. Follow the principle that removes it.

But if skipping the step means the client receives less transparency, feels less respected, and the relationship is genuinely harmed in a way that limits the business’s ability to serve and retain clients, if the disrespect is the more limiting factor, then the respect-for-people principle wins. Follow that one.

The decision is not about which principle sounds nobler. It is about which violation causes the most damage to the system, to the people, and to the mission.

How to Apply This on a Project Site

Construction is full of exactly these situations, and naming the resolution framework makes them faster and cleaner to navigate. A few examples of where this pattern shows up regularly:

A superintendent wants to give every trade partner a perfectly detailed zone briefing before they enter each new zone. Thorough communication respects the trades and protects quality. But if the briefing process adds two hours to the mobilization of every zone and the project is already behind its Takt time, the over-processing may be the more limiting constraint right now. A shorter, more targeted briefing that still honors the trade and moves the production system is the right answer, not because communication does not matter, but because at this moment, the limiting factor is speed of deployment, not depth of briefing.

A field engineer wants to walk every single control line in a new zone before releasing any work to trade partners. That is thorough, careful, and respectful of quality. If the zone’s layout is straightforward and the control lines have already been established by previous phases, the most limiting factor is not quality risk, it is the time the field engineer is consuming that could be spent on a zone where the layout risk is actually high. The stability and standardization principle says the established system should be trusted in low-risk situations so that attention can flow to the high-risk ones.

A PE wants to add a coordination review step to every RFI before it goes out. In some contexts, that prevents errors and serves the designer well. In a project that is generating 30 RFIs a week during a critical phase, adding that step to every single one may create a processing bottleneck that slows the information flow the field depends on. The limiting factor analysis says: add the review step to the RFIs where the risk of error is highest, and streamline the rest.

Warning Signs That the Conflict Is Not Being Resolved Well

When teams do not have a framework for navigating principle conflicts, a predictable pattern emerges. Watch for these signals:

• Decisions oscillate between principles with no consistent logic, sometimes maximizing respect for people, sometimes maximizing waste elimination based on whoever is in the room or what the last training session emphasized.
• The team defaults to the principle that is easiest to apply in any given moment rather than the one that most limits the constraint.
• Debates about which principle to follow consume meeting time without a resolution framework, creating the same analysis-paralysis that the principles were supposed to prevent.
• Leaders feel they have to violate one principle to honor another and carry guilt about the trade-off rather than understanding it as a rational, constraint-based decision.

The resolution is always the same: identify which violation which specific deviation from which specific principle creates the most limiting constraint on the system. That is the principle to honor in this specific situation. The other principle is still valid. It will be the governing principle in a different situation where its violation would be the more limiting constraint.

Both Principles Remain Valid

One more thing worth saying directly. Using the Theory of Constraints to choose between conflicting principles does not mean abandoning the principle that loses in any given situation. It means recognizing that in this situation, at this moment, with these specific conditions, one violation is more damaging than the other. In a different situation, the answer may be reversed.

The goal is not to rank the principles permanently. The goal is to have a decision framework that produces clear, defensible choices when principles conflict, choices grounded in the honest question of where the system is most constrained, not in preference, habit, or whoever argued most convincingly in the last meeting. We are building people who build things. Part of building those people is giving them the thinking tools to navigate real decisions, not just the inspiration to value all six principles in the abstract. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow and develop the decision-making discipline that makes Lean principles work in practice, not just in training.

A Challenge for Builders

Find a decision you are currently avoiding on your project because two legitimate principles seem to be in conflict. Name both principles explicitly. Then ask one question: which violation, if I fail to honor this principle here creates the most limiting constraint on the outcome? The answer to that question is the principle to follow. Make the call. Move forward. The system needs you to decide, not to debate.

As the Stoic philosopher Marcus Aurelius wrote, “The impediment to action advances action. What stands in the way becomes the way.”

On we go.

Frequently Asked Questions

Can Lean principles actually conflict with each other, or does it always mean someone is misapplying one?

They can genuinely conflict. Waste elimination and respect for people, strive for perfection and avoid over-processing, these are real Lean principles that point in opposite directions in specific situations. Acknowledging that honestly is what makes the framework usable in real-world decisions rather than just inspirational in training rooms.

What is the Theory of Constraints resolution when Lean principles conflict?

Identify which violation creates the most limiting constraint on the system, the people, and the outcome. The principle whose violation does more damage to the system is the one to honor in that specific situation. This is not about ranking the principles permanently, it is about applying constraint-based thinking to each specific decision.

Does choosing one principle over another mean abandoning the other?

No. The other principle remains valid and may well be the governing principle in a different situation. The constraint-based resolution is situational, not permanent. In a different context with different conditions, the limiting factor analysis may produce the opposite answer and both answers can be correct in their respective situations.