Guide contents
On this page
Guidance · Data & Documentation
Guiding documentation
Approved guidance and reference information that help a process operate consistently.
Guidance supports the right decision
Process descriptions, architecture principles, templates and lessons from previous implementations support the work. They are reused across process runs. The value of documentation depends on whether the right information can be found when it is needed.
Keeping information current is part of quality
Assign a document owner, approver, version number and review procedure. Distinguish current guidance from drafts and obsolete versions. For critical tasks, also plan access to instructions when the usual system is unavailable.
A guiding document explains how to act. A report from an individual process run may instead be an output.
Practical example
Cloud service implementation guidance
The cloud strategy sets out approved principles and suppliers. A reference architecture describes integration with the wider environment. Lessons from previous deployments help avoid known problems.
Include in your process description
- What guidance and templates are needed for the work?
- Where can the current version be found?
- Who approves and updates the document?
- How can instructions be accessed during an incident?
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.