Skip to main content

Designing and Documenting a Process

Designing and documenting a process enables an organization to move from the initial level of the ITIL Process maturity Framework (PMF) through the repeatable level to the defined level.  To undertake this task without adequate resources can be quite daunting especially given the fact that it must
  • Identify needed changes to job descriptions
  • Develop and document work procedures
  • Identify work requirements
  • Establish the data to be collected and the format to report accomplishments
  • Document the necessary vocabulary to be utilized within the process
The following ten process design and improvement steps can be used to create an easy to use and repeatable approach to help move your organization from one level to the next.  The ten steps are grouped into four phases.  Each phase will produce a deliverable that serves as an input to the follow phase.
Phase: Requirements Definition.   Output: Requirements Definition Document.
1.   Determine the management’s vision and level of commitment
2.   Establish a project and form a project team
3.   Define process and identify customer requirements
Phase:  Process Analysis. Output: Gap Analysis Report
4.   Document “as is” process and baseline current performance
5.   Assess conformance to customer requirements
6.   Benchmark current performance
Phase: Process design and Implementation.  Output: Process Definition Document
     7.   Design or redesign process
     8.   Solicit feedback, fine-tune, and finalize the design
     9.   Implement new design
Phase: Continual Process improvement.  Output:  Maturity Assessments and Metrics
    10.  Assess performance and continually improve
Source:  The ITSM Process Design Guide

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem