ISO 20000: Getting the Right Start on Your Process Implementation
ISO 20000 or ITIL process implementation can seem like a very daunting task.
In a previous article, I gave you an overview of a ground-breaking approach, the Process Prototyping Implementation Methodology, which can allow you to achieve ISO 20000 certification in just 18 months.
Let me remind you of the four stages of the process-based methodology:
This stage has two tasks and one milestone.
So, here you are, all ready to get going on your process implementation.
First task at hand? Find out what's already been done by performing a document inventory and review.
Before getting too far ahead of yourself and jumping right into process mapping, make sure that you read and acknowledge the work that has been done in the past by the organization.
The existing documentation may not be perfect, but it is extremely rare that organizations do not have anything documented on a process.
The aim here is to perform a quick organizational archaeology search in order to find the different pieces of the process you are addressing.
Once the documentation has been collected, you should review the content to get a feel of the process.
This Inventory and Review task has two major benefits: first, it saves a lot of time and money by building on work that has already been done.
Second, it shows respect for the organization by saying that what was done in the past is not obsolete, that you don't need to start from scratch and use sanitized best practices in which the organization will not recognize itself.
Task 1: Document Inventory and Review- what you should do:
The objective of this task is to document a draft process based on existing and best practices.
The objective is not to document an encyclopaedia.
When documenting a process prototype, remember that less is more.
Document the process objective, scope, performance indicators, flow chart of activities (without the activity descriptions), interfaces with other processes and reference to best practice or standard requirements.
By definition, the process prototype will be far from perfect; and will be conceptual in nature.
That is exactly what is required at this point in time.
The prototype will serve as the basis for initiating discussion with the other resources involved in the process building stage.
Task 2: Process Prototype Building -what you should do:
This is the methodology's first milestone that is called the Orientation Meeting.
The objective of this meeting is to review and sculpt the prototype to include the owner's vision and expectations of the future process.
It is also a great opportunity to communicate the standards requirements for this particular process.
If the prototype is off, this is the right time to readjust.
When many different groups are involved in the process, for instance the Security group in the case of incident management process, I recommend meeting with group representatives one on one in this phase.
Key resources must be involved early to ensure that they can express their vision and expectations.
By doing this, the process team obtains the buy-in from the process owner and other key resources on the high-level elements of the process.
This enables the process team to move a lot faster by not getting entangled in philosophical discussions about the process later on.
...
and there you go! You're all done with Stage 1 of the Process Prototyping Implementation Methodology for your ISO 20000 implementation project.
In a previous article, I gave you an overview of a ground-breaking approach, the Process Prototyping Implementation Methodology, which can allow you to achieve ISO 20000 certification in just 18 months.
Let me remind you of the four stages of the process-based methodology:
- Process Prototyping
- Process Building
- Process Implementation
- Process Tuning
This stage has two tasks and one milestone.
So, here you are, all ready to get going on your process implementation.
First task at hand? Find out what's already been done by performing a document inventory and review.
Before getting too far ahead of yourself and jumping right into process mapping, make sure that you read and acknowledge the work that has been done in the past by the organization.
The existing documentation may not be perfect, but it is extremely rare that organizations do not have anything documented on a process.
The aim here is to perform a quick organizational archaeology search in order to find the different pieces of the process you are addressing.
Once the documentation has been collected, you should review the content to get a feel of the process.
This Inventory and Review task has two major benefits: first, it saves a lot of time and money by building on work that has already been done.
Second, it shows respect for the organization by saying that what was done in the past is not obsolete, that you don't need to start from scratch and use sanitized best practices in which the organization will not recognize itself.
Task 1: Document Inventory and Review- what you should do:
- Collect all existing formal or informal documentation related to the process (including forms, procedures, policies, audit reports, maturity assessment, etc.
). - Store collected documents.
- Read and review collected information, including the best practice or standard on which the process will be based (ISO 20000, etc.
).
The objective of this task is to document a draft process based on existing and best practices.
The objective is not to document an encyclopaedia.
When documenting a process prototype, remember that less is more.
Document the process objective, scope, performance indicators, flow chart of activities (without the activity descriptions), interfaces with other processes and reference to best practice or standard requirements.
By definition, the process prototype will be far from perfect; and will be conceptual in nature.
That is exactly what is required at this point in time.
The prototype will serve as the basis for initiating discussion with the other resources involved in the process building stage.
Task 2: Process Prototype Building -what you should do:
- Prepare a high-level flowchart of the process.
- Ensure all the requirements are addressed.
- Prepare questions.
- Prepare propositions, solutions, best practices, guidance, ideas...
This is the methodology's first milestone that is called the Orientation Meeting.
The objective of this meeting is to review and sculpt the prototype to include the owner's vision and expectations of the future process.
It is also a great opportunity to communicate the standards requirements for this particular process.
If the prototype is off, this is the right time to readjust.
When many different groups are involved in the process, for instance the Security group in the case of incident management process, I recommend meeting with group representatives one on one in this phase.
Key resources must be involved early to ensure that they can express their vision and expectations.
By doing this, the process team obtains the buy-in from the process owner and other key resources on the high-level elements of the process.
This enables the process team to move a lot faster by not getting entangled in philosophical discussions about the process later on.
...
and there you go! You're all done with Stage 1 of the Process Prototyping Implementation Methodology for your ISO 20000 implementation project.
Source...