Policies:
Policies are guiding principles that are intended to influence decisions and actions across an organisation and govern the implementation of its processes.
Procedures:
Procedures define the specific steps necessary to perform activities in a process. They document the way activities are to be performed to facilitate consistent conformance with organisational requirements and to support quality and consistency.
Process owner:
The process owner is responsible for designing the processes necessary to achieve the objectives of transforming inputs into outputs. The process owner is responsible for the creation, update and approval of documents to support the process. Many process owners are supported by a process improvement team.
Processes:
Processes are related activities or actions that are taken to produce a specific service, product or desired result.
Root Cause Analysis (RCA):
Root cause analysis is a collective term that describes a wide range of approaches, tools, and techniques used to uncover causes of problems.
Swimlane
A swimlane is a visual element used in process flow diagrams, or flowcharts that visually distinguishes job sharing and responsibilities for sub-processes of a business process. Swimlanes may be arranged either horizontally or vertically.
Work Instructions:
Work Instructions are a form of procedure and are generally recognised as a subset of procedures.
Overview of Process Management
A process is usually defined as a set of interrelated or interacting activities that transform input into outputs. One Process Modeling Tool is known as the SIPOC Diagram. It gets its name from its five components:
SIPOC Diagram
(Supplier-Input-Process-Output-Customer)
Inputs to a process are most likely to be outputs from other processes. A ‘supplier' is not necessarily a company but may be even be a co-worker. For example, a ‘supplier' in the ‘Placement of an Advertisement in the Press' process would be the head of the Requesting Unit.
It should also be noted that within an organisation the ‘customer' may not necessarily reward the ‘supplier' with something tangible.
After undergoing the process, the input should have greater value as an output. In this example, an advertisement giving notification of a vacancy in a centre, department or unit; a new diploma or degree being offered or requesting a service to fill a need such as procuring reagents for a lab.
A second Process Modeling Tool which can be used is the Deming Cycle or PDCA (Plan→Do→Check→Act).

The 'Facilitating the Documentation of Procedures' Process Map will be reviewed against this Process Modeling Tool.
Plan
The Senior Specialist meets with representatives of the centre, department or unit to plan this process. The objective of this process of ‘Facilitating the Documentation of Procedures' is to develop procedures that are formatted in the official UTT template for procedures. These procedures should have information in each section based on the guidance given in the template. The steps from the Senior Specialist's swimlane to the Quality Representative's swimlane indicate how this objective will be accomplished.
Do
All the Position Holders (Senior Specialist; centre, department or unit; Administrative Assistant; Head of Department; Document Control Administrator and Quality Representative) identified in the titles of the swimlanes will perform their respective tasks. Data (for example, length of time for centre, department or unit to submit draft procedure to Senior Specialist and length of time the Senior Specialist takes to provide guidance to centre, department or unit) can be collected and processed.
Check
Any data collected can be processed and analysed to check on the performance of the process. This analysis can also include checks against stated objectives and variability, consistency and trends which may be developing.
Act
Action can then be taken based on the review of the findings. The process may remain unchanged or may be improved by implementing the process with these revisions.
There are three main types of processes
Processes should be designed to add value for the end-user and should not include unnecessary activities. The outcome of a well-designed process is increased effectiveness (value for the end-user) and increased efficiency (less costs for the organisation).
|
Symbol |
Name |
Description |
|
|
Start/End |
Represents the start or stop points in a process. |
|
|
Process step |
Represents a process step or task. This is the most commonly used symbol. |
|
|
Decision |
Represents a decision point or a branch in the process where usually there are two options (Yes/No, Pass/Fail). |
|
|
Arrows |
Indicate the direction/flow of the process. |
|
|
Off-Page Connector |
Used to connect a process to another page. |
|
|
Subroutine |
Represents a formally defined process or a series of steps documented elsewhere. |
|
|
Input/Output |
Represents the inputs in or outputs from a process. |
|
|
Document |
Represents a process step that produces a document. |
|
|
Multi-documents |
Represents a process step that produces several documents. |
|
|
Connector |
Used to connect one point in the process map to another to avoid drawing flow lines all over and crossing each other. They are usually labelled for easy reference. |
|
|
Stored Data |
Represents a process step that stores data. |
COMPARISON OF POLICIES, PROCESSES AND PROCEDURES
|
The distinctions commonly drawn between Policies, Processes, and Procedures can be subtle, however, there are characteristics that help discern Policy from Processes and Procedure. They are: |
||
|
Policies |
Processes |
Procedures |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reference: Tristan Boutros and Tim Purdie (2014). The Process Improvement Handbook (Version 1.0)