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

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

What Is A Service Offering?

The ITIL4 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 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.               Note: Goods may not always be provided for every Service Offe

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 the