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

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…