Outcome specification, also known as Outcome-based specification (OBS), is a method of describing what a solution (equipment, goods, or services) must achieve or the performance it must deliver for its stakeholders. In essence, it focuses on the results required rather than the specific methods or inputs used to achieve them.
Based on the provided reference:
Outcome-based specifications (or “OBS”) describe the function or performance that a solution (equipment, goods, or services) must fulfil for the stakeholders; in other words, what the solution should do.
This means an outcome specification clearly defines the desired end state, the functions the solution must perform, or the level of performance required from the perspective of those who will benefit from or use it.
Why Use Outcome Specification?
Focusing on outcomes rather than specific technical details can offer several advantages:
- Flexibility and Innovation: It allows solution providers to propose the most efficient or innovative ways to achieve the desired outcome, rather than being constrained by prescriptive methods.
- Clearer Focus: Ensures that the solution directly addresses the actual needs and goals of the stakeholders.
- Performance Measurement: Makes it easier to measure the success of a solution based on tangible results and performance metrics.
- Risk Transfer: Often shifts the responsibility for how to achieve the outcome to the supplier or provider, who typically has expertise in their domain.
Outcome vs. Traditional Specifications
Here's a simple comparison:
| Feature | Traditional (Prescriptive) Specification | Outcome (Performance/Function) Specification |
|---|---|---|
| Focus | How to build or provide the solution (inputs, methods, design) | What the solution must achieve (results, performance, function) |
| Question Asked | "Build this exact thing?" or "Follow these steps?" | "Achieve this result?" or "Perform these functions?" |
| Example | "Use a size 12 bolt made of stainless steel." | "Ensure the connection can withstand 500 kg of force." |
Practical Examples
-
Instead of: "Provide weekly status reports via email."
-
Outcome Spec: "Ensure stakeholders have access to up-to-date project progress information." (This could potentially be met by email, a dashboard, a shared document, etc.)
-
Instead of: "Install three specific types of sensors in the room."
-
Outcome Spec: "Maintain room temperature within 20-22°C and monitor air quality according to industry standards."
Outcome specification is a powerful tool for defining requirements in a way that encourages efficiency, innovation, and a clear focus on achieving desired results for stakeholders.
