Guide contents
On this page
Main flow · Process
Process
A sequence of activities that transforms inputs into outputs ready for handover.
Make the work visible, step by step
Describe activities in execution order. Connect each step to the people involved, decision points, acceptance conditions and exception handling. Explain when work returns to an earlier step. A successful main path alone does not explain how work proceeds during a disruption.
Build quality into the work
Metrics show speed, quality and resource use. Controls keep operations within acceptable boundaries. Impact analysis before approval and testing before production deployment are examples of controls built into work steps.
The process owner is accountable for the functioning of the whole process. Each participant is responsible for the work assigned to them.
Practical example
Change management steps
A change request is registered, impacts and risks are assessed, and the change is approved under agreed authority. An implementation plan is then prepared, the change is implemented and tested, deployed to production, and monitored. A post-implementation review captures lessons. Approval levels are organisational choices, not an ITIL model mandatory for everyone.
Include in your process description
- What are the work steps and their sequence?
- Who performs the work, who approves it, and who owns the whole process?
- Where is quality checked before work proceeds?
- How are interruptions, failures and rollback handled?
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.