Complexity Cost

Count what variety costs: every option multiplies parts, setups, tests and stock — make variety earn its keep.

Time45 min
FormatSmall group
StageToolkit

Complexity Cost: what it is and why it works

Complexity Cost makes visible what product variety costs beyond the direct cost of each variant. Every additional option, part number, supplier or process multiplies activities: engineering maintenance of drawings and bills of materials, purchasing and supplier management, setups and changeovers, inventory and obsolescence, test procedures, service parts and documentation. The method defines complexity units for the product family, such as active part numbers, options, suppliers and processes, plots cost or overhead against them, identifies where cost jumps, and lists variants whose volumes cannot carry their share. Those variants are then pruned, consolidated or re-priced.

The method works because standard costing spreads overhead evenly by labor or machine hours, so low-volume variants look almost as cheap as high-volume ones while consuming a disproportionate share of support activities. The catalog grows by addition because each new variant looks profitable on its own, and nobody owns the cumulative effect. Anderson's work on managing the cost of complexity framed variety as something to be priced and managed rather than accepted. Activity-Based Costing supplies the cost-per-activity data the method needs, while Standardization and Modularization provide the design routes that keep external variety for customers while reducing internal complexity.

What you need

Sales volume and revenue by variant or configuration over at least a year
Count of active part numbers, options, suppliers and processes by product family
Overhead and support costs, ideally broken down by activity
Direct cost and price by variant
Customer and market input on which options customers actually value

What you get

Complexity units defined and counted for the product family
A chart of cost or overhead against complexity, with the threshold where cost jumps
A list of low-volume variants with their full complexity cost
Decisions per variant: keep, consolidate, re-price, move to order-specific pricing or drop
A rule for approving new variants with their complexity cost included

When to use it

When the catalog grew by addition and is never pruned.

How to do it, step by step

Define complexity units: active part numbers, options, suppliers, processes.
Plot unit cost or overhead against complexity for the product family.
Identify the complexity threshold where cost jumps.
List variants below minimum volume with their full complexity cost.
Prune or re-price the variants that cannot carry their complexity.

Worked example: Pruning an industrial fan range

Illustrative scenario — figures are realistic but not from a real company.

A manufacturer of industrial centrifugal fans offered its mid-range line in about 1,200 sellable configurations built from 3,400 active part numbers. Revenue was flat, while engineering change requests, stock write-offs and changeovers kept rising.

The team defined four complexity units: active part numbers, configurations sold in the last year, suppliers and distinct paint and coating processes.
Using activity costs, they estimated a yearly cost to maintain an active part number, covering engineering, purchasing, inventory and data upkeep, and a cost per changeover in the fabrication cell.
Of the 1,200 configurations, about 470 had sold fewer than three units a year. Together they brought about 5% of revenue but carried roughly 1,300 unique part numbers and most of the special coatings.
Sales and engineering reviewed the tail: 280 configurations were dropped in favor of the nearest standard, 120 kept at a new engineered-to-order price, and 70 kept as they served strategic customers.

Result. Active part numbers fell by about 900 over a year, changeovers in fabrication dropped noticeably, and slow-moving inventory was written down once rather than every year. Revenue lost from dropped configurations was small, as most customers accepted the standard alternative. A new-variant approval rule now includes the part-number and changeover cost.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

Judging variants by standard margin, which hides their support cost.Use activity-based data to attribute engineering, purchasing, inventory and changeover costs to variants.
Cutting variants that customers buy as part of a package.Check customer buying patterns before pruning, and offer the nearest standard alternative.
Pruning once and letting variety grow back.Add an approval rule for new variants that includes their complexity cost and a minimum volume.
Reducing external choice when internal complexity was the real issue.Use modular design and late differentiation to keep customer options while reducing internal part numbers.

Frequently asked questions

What is complexity cost in manufacturing?

It is the cost created by variety itself: additional part numbers, options, suppliers and processes that increase engineering, purchasing, inventory, setups, quality control, documentation and service activities. These costs mostly sit in overhead, so they are often invisible in standard product costs, even though they grow with the number of variants rather than with volume.

How do you measure the cost of product variety?

Define complexity units, such as active part numbers or configurations, and link support costs to them using activity-based costing. Compare overhead or unit cost across product families or periods with different complexity levels. Then attribute the complexity cost to low-volume variants to see which ones carry their full cost and which do not.

What is the difference between complexity reduction and SKU rationalization?

SKU rationalization focuses on pruning the list of sellable items. Complexity reduction is broader: it also targets internal part numbers, suppliers, processes and design variety, often using modularization and standardization so the customer-facing range can stay wide while internal complexity falls.

Origin

Complexity cost — product variety economics (Anderson, "Managing the Cost of Complexity", 1997).

Used in these playbooks

Complexity pruning quarter 1 quarter

One quarter to cut what variety costs: measure complexity, standardize parts, modularize the platform and delete the functions nobody misses.

Related methods

More in “Toolkit”

Cross-cutting methods: curves, complexity, quality and estimating tools.