Guide contents
On this page
Main flow · Outcome / Value
Outcome and value
The benefit or change for which the process exists.
Value is created for the recipient
Identify who benefits from the process: customers, staff, another team or the organisation as a whole. Describe the intended change, for example in service availability, security or ease of working. The number of completed documents alone does not demonstrate a benefit.
Outcomes often take time to appear
Agree a baseline, target, evaluation date and person responsible for collecting information. Other changes may also affect the result, so do not automatically attribute it to a single process. Outcome information provides the basis for strategic feedback.
A new monitoring solution is an output. Faster incident detection is the intended outcome.
Practical example
The benefit of security training
Training materials, a delivered session and attendance records are outputs. The intended outcome is that staff recognise threats more effectively and make safer decisions. This can be assessed through changes in skills and reporting behaviour. An increase in reports may also indicate better detection.
Include in your process description
- Who receives the value?
- What behaviour or situation changes?
- How will you know that the change occurred?
- When is the outcome evaluated, and who reviews the results?
Connections to other components
Based on the Generic Process Model materials. Questions and practical guidance have been structured for reading on the web. Sources and clarifications.