The presence of duplicate or overlapping capacities, roles, processes, or systems within or between organizations that perform the same function without coordination, leading to inefficient use of resources or conflicting actions; distinct from intentional redundancy established for resilience or backup.

Principle

Redundancy lowers marginal efficiency by duplicating effort and fixed costs; however, intentional redundancy can increase resilience to shocks, so the net effect depends on whether duplication is coordinated and justified by contingency value.

Demonstration

Illustrative scenario: Situation — Two procurement units within a ministry independently negotiate separate contracts for identical IT services. Recognition — Contracts contain similar deliverables at different prices and no consolidated supplier management. Action — Both units execute their contracts and maintain separate vendor relationships. Consequence — The ministry pays higher aggregate costs, loses volume discounts, and faces inconsistent technical standards across units.

Misapplication

Error: labeling any two units doing similar work as harmful redundancy. Mistake: ignoring whether duplicates are deliberate backups, temporary contingencies, or part of a staged transition; this conflation misguides remedy design.

Consequence

Consequences include higher operating costs, reduced bargaining power, inconsistent service quality, and potential inter-unit conflict; but where failure tolerance matters, redundancy can preserve function during disruption.

Reversal

In contexts where continuity is critical (infrastructure, emergency services) or where capacity buffers are needed, redundancy is a deliberate design choice that trades efficiency for reliability; coordinated redundancy (shared standards, pooled procurement) retains resilience while limiting waste.

Boundary

Clearly within: two uncoordinated units maintaining the same capability with separate budgets and outputs. Boundary case: duplicated capacity with formal backup roles and scheduled failover. Clearly outside: designed backup systems with documented failover procedures and cost‑benefit justification.

Semantic Tension

Efficiency ↔ Resilience: reducing redundancy improves short‑term efficiency but can decrease the system's ability to withstand shocks; increasing redundancy preserves function at the cost of higher baseline expenditure.

Synthesis

Functional redundancy should be evaluated as a tradeoff: wasteful duplication arises when overlapping capacities lack coordination or contingency value; effective design preserves redundancy only where its marginal resilience benefit exceeds its efficiency cost and is governed accordingly.