This post is part two of a series where we discuss the Problem Management process and how to put one together. In the previous post, I presented some design elements for consideration. In this follow-up post, I will illustrate the design activities further with the following, additional elements.
Problem Management Process Requirements
Problem Management Process Flow
Problem Management RCA Form
The first document contains a list of sample process requirements. The purpose of the requirement document is to capture all considerations that need to be factored into the process design. You will need to decide what activities or requirements will be considered a critical part of the Problem Management process. For example, if row #12 “Categorize the root causes to facilitate further analysis” is important to your organization, make sure that particular requirement is documented, so your process design will incorporate a method of categorizing the root causes.
What can you do if you need some extra help on knowing what to look for in designing your Problem Management process? I would suggest using the following documents as your starting point:
- ITIL: Problem Management in the Service Operation manual, section 4.4.
- COBIT 5: Enabling process DSS03 – Manage Problems
- ISO/IEC 20000: Problem Management in Section 8.2
By using ISO/IEC 20000 as the base, I have derived some sample requirements for your reference. As you can see from the document, the sample requirements outlined in the document are pretty rudimentary and generic. You need to tailor your version of the document with the actual requirements from your organization. Do not select a particular requirement just because it looks good on paper or in theory. Craft or select the requirements to include in your process design only when they make sense for your organization. Also, if you plan to implement a tool or have an existing tool that will be used to support the Problem Management process, the tool-specific considerations should be captured in the requirement document as well.
The second document contains a sample process flow. The process flow shows who is doing what and during what stage of the Problem Management process. Once you have determined what your requirements are for the process, the process flow attempts to match and support the process requirements.
The third document is a sample data entry form for the root cause analysis exercise. The form illustrates what data you may want to captured with the process, and they should be consistent with the requirements you have captured from working with your organization. The data you want to capture from the process should also be consistent with the support from the tools you plan to use with the process. Normally, we don’t want to have the tool’s capability drive the process design decisions. If you have an existing ITSM tool that you would like to use for the Problem Management process, now it is the time to factor the tools into the design and make sure the design can be supported by the tools.
In part three of the post, we will combine everything we have done and produce one final process design document. The process design document will include not only the requirements, the flow, and the roles, but also other information pertinent to the process such as the policy statement, a RACI chart, and the process metrics. The final process design document can then be used as the foundation to implement the actual Problem Management process within your organization.
You must be logged in to post a comment.