This quote from quality guru Edwards Deming posits that undesirable results are a feature of a perfectly designed system, not a bug or human error. To improve outcomes, product leaders must analyze and redesign the underlying processes rather than blaming their teams.

Related Insights

A key principle of lean management is "Genba" (go and see). To truly improve a process, leaders must be physically present, observing and talking with the people who perform the tasks daily. Speculating from an office based on data alone leads to ineffective or out-of-touch changes.

The greatest performers, from athletes to companies, are not just the most talented; they are the best at getting better faster. An obsession with root-cause analysis and a non-defensive commitment to improvement is the key to reaching otherwise unachievable levels of success.

Exceptional people in flawed systems will produce subpar results. Before focusing on individual performance, leaders must ensure the underlying systems are reliable and resilient. As shown by the Southwest Airlines software meltdown, blaming employees for systemic failures masks the root cause and prevents meaningful improvement.

The conventional wisdom that you must sacrifice one of quality, price, or speed is flawed. High-performance teams reject this trade-off, understanding that improving quality is the primary lever. Higher quality reduces rework and defects, which naturally leads to lower long-term costs and faster delivery, creating a virtuous cycle.

Effective engineering leadership is like farming: growth isn't achieved by demanding it from the plants. Leaders should obsess over inputs—clear goals, sound strategy, team structure, and operational rigor—to create the conditions for great engineering to happen naturally.

In a truly product-led company, the product organization must accept ultimate accountability for business-wide challenges. Issues in sales, marketing, or customer success are not separate functional problems; they are reflections of the product's shortcomings, requiring product leaders to take ownership beyond their immediate domain.

Instead of stigmatizing failure, LEGO embeds a formal "After Action Review" (AAR) process into its culture, with reviews happening daily at some level. This structured debrief forces teams to analyze why a project failed and apply those specific learnings across the organization to prevent repeat mistakes.

Better products are a byproduct of a better team environment. A leader's primary job is not to work on the product, but to cultivate the people and the system they work in—improving their thinking, decision-making, and collaboration.

Menlo's culture operates on the principle that when mistakes happen, the system is at fault, not the individual. This approach removes fear and blame, encouraging the team to analyze and improve the processes that allowed the error to occur, fostering a culture of continuous improvement.

Leaders who complain their team isn't as good as them are misplacing blame. They are the ones who hired and trained those individuals. The team's failure is ultimately the leader's failure in either talent selection, skill development, or both, demanding radical ownership.