Uses and Misuses of Price's Law or Pareto Principle

The notion that a five percent to 10 percent reduction in force at a large organization might be "productivity-neutral" or even "productivity-positive" rests on the premise that large organizations eventually suffer from organizational entropy or “slack.”

In massive corporations, the individual contribution of an individual is notoriously difficult to measure, if it can be measured at all.

The Pareto Principle (80/20 rule) suggests that 80 percent of the value is produced by 20 percent of the employees. If this holds true, a 10-percent layoff that misses the "vital 20 percent" would, mathematically, have a negligible impact on total output.

Price's Law likewise suggests that half of organizational output is created by just 10 percent of workers.

But the idea can be carried too far. In other words, Pareto might suggest  where value is concentrated, but it does not tell us what parts of the value chain, in what quantities, we can try to remove.

In other words, complex products often require many value chain contributions whose contributions are outside the “80 percent of value” attribution, but are still essential for product success. 

The logic of eliminating most of the other value chain elements outside the “80 percent of value” only works only when inputs are independent and optional. That is rarely, if ever, the case for most products. 

For example, a particular  product ships only if every step is completed. So even low-value steps are non-optional constraints. 

Also, some value chain operations represent option value or risk reduction. They might not show up in the completed product, but might instead provide protection against product failure. 

Quality assurance efforts, regulatory compliance or maintenance might not be direct value creators, but might be necessary to deliver a final product. 

So many functions might be structurally necessary but individually have low marginal impact. And even that does not help address the question of staffing levels to support such processes. 

Were that not the case, competitive markets would force firms toward the Pareto-suggestion of minimal staffing. And we do not see that. 

Study / Source	Domain	Key Finding	Implication for Workforce
Pareto principle overview	Operations / Engineering	80% of outcomes driven by ~20% of causes	Output concentration is real
Pareto in supply chains (Slimstock)	Supply chain	20% of products drive most revenue	Inventory focus is uneven
Lean operations Pareto usage	Manufacturing	Majority of defects from small set of causes	Useful for prioritization
Juran Pareto analysis guide	Quality management	“Vital few and useful many” distinction	Many low-impact roles still necessary
IMD Pareto analysis strategy article	Strategy	Pareto helps focus leadership effort, not eliminate complexity	Tool for prioritization, not simplification
Value chain simulation research (VCS)	Manufacturing systems	Output depends on interdependent processes across cost, quality, delivery	System requires multiple linked roles
Pareto distribution empirical study (arXiv)	Economics/statistics	Heavy-tailed distributions common in real systems	Inequality of contribution is structural, not eliminative

That noted, Pareto does make sense for:

• Prioritizing improvements (fix top 20 percent of defects)

• Sales focus (top 20 percent of customers or products)

• Time allocation (focus on high-leverage activities)

Still, Pareto notwithstanding, large organizations might often be less productive than imagined because of:

• Social Loafing: In large groups, individuals often work less hard than they would alone because their lack of effort is easily hidden by the group's overall performance

• Bureaucratic Friction: Beyond a certain size, organizations require "coordinators for the coordinators." Removing a layer of these roles can actually speed up decision-making, allowing the remaining staff to be more productive because they spend less time in meetings.

So when an organization has excess personnel, it can often absorb a reduction in force without losing core output, effectively "trimming the fat" to improve the output-per-employee ratio.

Study / Source	Key Focus	Source Link
Love & Nohria (2005)	Reducing Slack: Found that downsizing improves performance specifically when the firm has "excessive" resources (high slack).	Read at ResearchGate
Cascio, Young, & Morris (1997)	Financial Consequences: A landmark study showing that layoffs alone rarely boost ROA, but asset restructuring combined with cuts does.	Read at ResearchGate
Guthrie & Datta (2008)	Industry Context: Demonstrates that the negative impact of layoffs is significantly higher in "knowledge-intensive" (R&D) industries.	Read at ResearchGate
McKinsey & Company	The Productivity Imperative: Analyzes how technology and "de-layering" (removing management tiers) can boost service-sector productivity.	Download PDF (McKinsey)
Zyglidopoulos (2005)	Corporate Reputation: Examines how the market and stakeholders perceive downsizing as a signal of "efficiency-seeking" behavior.	Read at ResearchGate

The caveats are several.

Guthrie and Datta warn that in organizations with high innovation requirements, a 10-percent cut can remove critical "intangible assets" whose loss will not be seen until later. 

The Cascio study suggests that many firms fail to see long-term productivity growth after layoffs because they lose the ability to innovate

In other words, if the ideal is “cutting fat but not muscle,” the danger is “cutting some muscle as well.”.

If “productivity” is defined as total output divided by total input, then a smaller denominator “automatically” raises productivity, assuming output remains the same. 

The argument is that many large firms have enough "operational slack" (excess resources) that a five-percent to 10-percent  cut acts as a "forcing function," requiring the remaining staff to automate or abandon low-value tasks.

Large organizations are complex, so it might not be easy to determine how much, and where, to make layoffs. If one assumes every existing function actually is essential, then an “across the board” approach actually makes some sense.

The organization keeps the function, but possibly operates more efficiently.