The belief is reasonable on its face: if you specify exactly what you need, every supplier bids on the same thing, and you get a genuine apples-to-apples comparison. The logic is tidy. The result is expensive. Exhaustive specifications block supplier innovation, lock buyers into legacy designs rather than better solutions, and raise sourcing costs by 8-15% — the premium for eliminating supplier creativity from the process.
Procurement teams default to specification-based sourcing because it feels safer. A 40-page technical specification with material grades, dimensional tolerances, and process requirements creates the illusion of control. What it actually creates is a smaller supplier pool. Suppliers who could deliver a better outcome using a different material, manufacturing method, or design are excluded before they can propose anything. The buyer pays for the spec, not for the result.
Why the myth has a valid origin
Specifications exist for good reasons. In regulated industries — aerospace, medical devices, pharmaceuticals — the specification is the compliance document. Changing it requires regulatory re-approval that costs more than any sourcing efficiency could recover. In replacement parts markets, the specification ensures interchangeability with existing equipment. If the new part does not fit, the savings are meaningless.
Specifications also prevent supplier gaming in categories where quality is hard to verify. A concrete supplier who reduces cement content to cut cost is delivering a different product, not a better one. The specification is the only thing standing between the buyer and substandard material. These are legitimate uses of specification-based requirements. The problem is not specifications themselves. The problem is applying specification-based logic to categories where it does not belong.
Where the myth breaks down: three scenarios that contradict it
Scenario 1: When supplier R&D exceeds buyer expertise. A procurement team specifying an industrial pump writes a specification based on the pump they bought last time. The specification describes the old pump's dimensions, materials, and performance curve. A supplier with a new magnetic drive design that eliminates the seal — the component that fails most often — cannot bid because the specification mandates a mechanical seal. The buyer gets a copy of the old pump at a slightly better price and misses a technology that would reduce maintenance costs by 40%.
Mandates mechanical seal. Excludes magnetic drive design. Locks in legacy failure mode. Suppliers compete on manufacturing efficiency, not design quality.
Requires 50,000-hour MTBF and 85% hydraulic efficiency. Supplier with magnetic drive beats mechanical seal on both metrics at 12% lower lifecycle cost.
Scenario 2: When specifications encode legacy cost structures. Specifications written years ago reflect the material prices and manufacturing economics of that era. A specification calling for a specific machined brass component made sense when brass was cheap and CNC time was expensive. Ten years later, injection-molded engineered polymer delivers the same strength at 60% lower cost. But the specification still says brass, so the buyer buys brass. A 2016 McKinsey study of industrial procurement found that 30-45% of active specifications in surveyed organizations had not been reviewed in over three years.
Scenario 3: When specifications are copied from supplier data sheets. The most common source of over-specification is the incumbent supplier's technical data sheet, transcribed into the RFP as a "neutral" requirement. The specification describes exactly what the incumbent already sells. Every competitor must design to that spec, which the incumbent meets by default. The buyer believes they are running a competitive process. They are running an incumbent-protection process dressed as competition.
The failure mode: over-specifying to compensate for weak evaluation capability
Organizations that lack the engineering capability to evaluate technical alternatives compensate by writing specifications that eliminate the need for technical evaluation. If the spec says "must be 316 stainless steel," the evaluator only needs to check a box. No judgment required. This is not a sourcing strategy. It is a capability deficiency dressed as rigor.
The cost of this pattern compounds. As specifications age, they diverge further from available technology. The evaluation team's capability to assess alternatives atrophies because they never practice. The procurement function becomes an order-placing function rather than a value-creation function. Breaking this cycle requires investing in the engineering capability to evaluate technical alternatives — or structuring requirements as outcomes and letting suppliers do the engineering.
What replaces it: a framework for choosing spec vs. outcome requirements
The decision between specification-based and outcome-based requirements is not ideological. It is situational. Four questions determine which approach to use:
- Is the specification safety-critical or regulated? If yes, use specification-based. Safety and compliance override cost.
- Is the item a replacement that must match existing systems? If yes, the specification is non-negotiable. Interchangeability is the primary function.
- Could multiple technical approaches achieve the same outcome? If yes, use outcome-based requirements. Do not pre-select the winner's technology.
- Has the category seen recent material or process innovation? If yes, specifications written more than two years ago are suspect. Review before issuing.
When outcome-based requirements are appropriate, define them in measurable terms: performance thresholds, service life, energy consumption, failure rate. Not "the pump shall have a mechanical seal" but "the pump shall achieve 50,000-hour mean time between failure." Let suppliers propose how.
What this means in practice
Audit your ten highest-spend active specifications. For each one, ask: when was this specification last reviewed by an engineer who was not the incumbent supplier? If the answer is more than three years, schedule a specification review. Bring in a second supplier or independent engineer to identify where the spec locks in legacy technology.
For your next sourcing event, try one outcome-based requirement. Pick a category where multiple technical approaches are viable. Write the requirement as a performance outcome, not a specification. Evaluate proposals against the outcome metric. Compare the result to your last specification-based event for the same category.
Train your evaluation team to assess technical alternatives. If your team cannot evaluate a supplier's alternative design without a specification to check against, the team is not evaluating. It is verifying compliance. Those are different skills. Invest in the first to stop paying for the second.
Frequently asked questions
Do outcome-based requirements work for all categories?
No. Safety-critical components, regulated products, and exact replacement parts require specification-based sourcing. The framework is for categories where the function matters more than the form — industrial equipment, packaging, logistics services, facility management, IT infrastructure, and MRO supplies where alternatives exist.
How do you prevent suppliers from gaming outcome requirements?
Define measurable acceptance criteria with pass/fail thresholds. "Must reduce energy consumption by 15% vs. current baseline" is testable. "Must be energy efficient" is not. Require suppliers to provide test data or third-party verification. Build a trial period into the contract with an exit clause if performance thresholds are not met.
Data sources
- McKinsey & Company, "Procurement 20/20: Supply Entrepreneurship in a Changing World," mckinsey.com, 2016.
- Chartered Institute of Procurement & Supply (CIPS), "Specification Writing Guide," cips.org, accessed July 5, 2026.
- Next Level Purchasing Association (NLPA), "Procurement Myths That Cost Companies Money," nextlevelpurchasing.com, accessed July 5, 2026.
- National Institute of Standards and Technology (NIST), "Performance-Based Specifications Guide," nist.gov, 2020.