Overengineering

Overengineering (or over-engineering)^[1] is the act of designing a product or providing a solution to a problem that is complicated in a way that provides no value or could have been designed to be simpler.^[2]

It is generally criticized in terms of value engineering as wasteful of resources such as materials, time and money. NASA listed excessive features as one of the top 10 risks of failure for development projects,^[3] and Mercedes-Benz developed and removed 600 non-essential features from their cars due to malfunctions, lack of usability and customer complaints.^[4]

As a design philosophy, it is the opposite of the minimalist ethos of "less is more" (or: “worse is better”) and a disobedience of the KISS principle.

Characteristics[edit]

Overengineering is often identified with design choices that increase safety, add functionality, or overcome a perceived design flaw that most users would not notice or would accept.

It can be hard to avoid when safety or performance is critical (e.g. in aerospace vehicles and luxury road vehicles), or when extremely broad functionality is required (e.g. diagnostic and medical tools, power users of products).

Overengineering often occurs in high-end products and specialized markets.

A product may be overbuilt – with performance far in excess of expected normal operation such as a city car with top speed of 300 km/h, or a home video recorder with a lifespan of 100 years. Such products may be more expensive, bulkier, and heavier than necessary.

A product may be overcomplicated – with functions that are not necessary, and reduce the usability of the product by overwhelming users which is sometimes called feature fatigue. ^{[5] [6]}

Sometimes overengineering occurs over time in the form of feature creep.

Overengineering can decrease the productivity of a development team because even though the team produces product, the value realized might be less than if the team was producing only what the user needs and wants.

Overengineering can consist of premature optimization, potentially to the detriment of the project due to diminishing returns on time and effort invested in the design process.

Cultural references[edit]

A story about very precise engineering is given in the 1858 story The Deacon's Masterpiece or, the Wonderful "One-hoss Shay": A Logical Story by Oliver Wendell Holmes Sr., which tells of a carriage (one-horse shay)

That was built in such a logical way
It ran a hundred years to a day,
And then,
...
went to pieces all at once, --
All at once, and nothing first, --
Just as bubbles do when they burst.

Because it had been engineered so that no single piece failed first – no piece was over-engineered relative to the others, and they thus all collapsed at the same time.

A similar quote by Ferdinand Porsche claimed "the perfect race car crosses the finish line in first place and immediately falls into pieces."^{[citation needed]}

Examples[edit]

German Second World War weapons, like the famous Tiger I tank or Panther tank, have been listed as examples of over-engineering^[7] in comparison to their Soviet rivals such as the T-34. German arms allegedly used expensive materials and excessively labour intensive production processes, limiting production and making them hard to repair when they broke down in the field.

Another example is Juicero, a wi-fi "smart" juicing press. After its release, Bloomberg News published a story that showed that the juice packs could be squeezed by hand faster than the press, and that hand-squeezing produced juice that was near-indistinguishable in quality and quantity from the output of the machine, which cost $400 even after a price reduction.^[8]

In 2024, former technical director and chair of Network Rail High Speed Andrew McNaughton stated to the Transport Committee that HS2 was overengineered in respect of bridge foundations and masts.^[9]

See also[edit]

• Technical debt
• Feature creep
• You aren't gonna need it
• Planned obsolescence
• skyTran
• Useless machine
• Writing in space
• Design by committee

References[edit]

External links[edit]

• "Code Simplicity ", Code Simplicity: The Science of Software Development Book, O'Reilly Media, Max Kanat-Alexander, March 2012
• "Stop Over-Engineering!", Software Development magazine, Joshua Kerievsky, April 2002
• "Overengineering: How much is too much?", EDN magazine, Paul Rako, January 2008