Skip to main content

Process Maturity – Documenting the “As Is” Process

There are many challenges to defining and documenting a process for ongoing continual improvement and to ensure process maturity is in alignment with the overall business strategy and outcomes.  One such challenge is to be able to document the “As Is” process.

When documenting the “As Is” process caution must be taken not to accept the existing documentation, or flowcharts provided as the true baseline of what is really being done.  What are the current activities and procedures that are being used and what is the step by step workflow that participants and stakeholders are actually performing?  The actual is what really needs to be captured. 

The complexity of this challenge is exasperated by the fact that frequently when determining and “As Is” state for immature processes the assessor or process design engineer will discover that there is not one single process that is being followed but in fact many?  What then?

Non adherence to process is generally due to little or no governance, training, tools and a variety of cultural reasons.  The fact remains that we must document the actual.  The actual documentation of the “As Is” state when just starting out might require that you document several process flows.   

A recent initiative to document such a process for a national service provider in central US ended up taking months.  You cannot imagine the war room discussions that took place in the workshops to ascertain the current way they followed a specific process.  As is frequently the case, this organization had originally rated this process internally as a level three maturity. The documentation and assessment report that followed was a real eye opener to the business sponsors and IT staff for how out of control the service management processes really were.  They discovered they had not one but eight different processes and varied procedures, lots of redundant data, lack of control, frustrated staff, no visibility to business outcomes or cost… and the list goes on. This effort paid off because it helped to establish sponsorship and further commitment to improvement.  Information is an amazing thing!

Some helpful tips for getting started when attempting to improve process maturity:
  • Establish a project and define both the customer and process requirements and be sure you have the appropriate project team.
  • Document the “As Is” (remember this the actual) and baseline current performance to the requirements that you have previously agreed upon. Benchmark current performance.
  • Once you have the Gap Analysis Report you can design or redesign the new process, solicit feedback and fine tune before implementing the new process.
  • Realize a process is never perfect.  The most critical element is to ensure that you have a measurement system in place for ongoing monitoring and reporting that enables future improvement that can adapt to the dynamic nature of the business outcomes that this process is supporting.

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...