If you’re starting out on a process mapping journey, then sooner or later (ideally sooner), you’re going to encounter the phrase “the as-is process“. It takes the basic understanding of a process map one step further.
If your process mapping endeavours are to drive real change, then it is important that you understand exactly what is an as-is process map and why they matter in the world of mapping and process improvement.
So, What Do We Mean By An As-Is Process?
An as-is process map reflects exactly how a process is performed today. If you monitored and noted how someone actually executed a particular job or task, then that would be the as-is process.
Whether it is good, bad or indifferent, an as-is map needs to show the current way of working in all of its glory. It should show all process steps, all instances of rework (where steps have to be performed again due to errors), any instances of variation (where the ‘same’ process is performed different ways. In short if a step is carried out, it needs to be in your process maps.
What Other Types Of Process Mapping Are There?
The main alternative to an as-is process mapping is a to-be process map. As the name suggests, a to-be map depicts how a process will look in the future rather than how it works today.
To-be process maps normally come about for one of two reasons:
- There is no existing process meaning one needs to be created from scratch.
- Process improvement work is resulting in a new, better way of working.
Regardless of the driver, a to-be process is all about ensuring the new process makes sense and is understood ahead of any go-live. It enables readers of the process map to ensure that the new process will work as planned and make any adjustments before it becomes part of day-to-day working.
The other type of process map that we sometimes encounter is what we call a ‘should be‘ map. In fact, when people have documented their own processes, I would say it is the most common, and arguably the most dangerous type of map. We’ll explain more about the risks involved in documenting your own processes in a future article.
Again, the clue is in the name. A should-be map reflects how people expect a business process to be performed but doesn’t actually reflect the reality. It can create risks as people assume that it reflects the as-is process, and subsequently base decisions on that way of working.
Why As-Is Process Mapping Is Critical For Change
Whatever type of change project you’re undertaking, it seems fundamental that you understand exactly what it is you are changing. If you’re focusing on incorrect ways of working, then any process analysis is going to be somewhat flawed. Imagine a process automation project that is based on incorrect information. The likelihood is that any process variation or workarounds could be missed in the design, with manual intervention being required in the ‘automated’ way of working.
An as-is map provides clarity around how your business processes truly operates It is your blueprint for change and success.
TL;DR What Is An As-Is Process Map?
An “as-is process map” is a visual representation of how a specific process is currently performed, capturing all its steps, rework instances, and variations. This map is crucial for understanding the existing way of working and serves as a foundation for process improvement. It contrasts with a “to-be process map,” which depicts how a process will look in the future, often created when there’s no existing process or during process improvement efforts. Another type, the “should-be map,” reflects how people expect a process to be performed but may not align with reality and can lead to flawed decision-making. As-is process mapping is critical for any change project, ensuring a clear understanding of the current state of business processes and providing a basis for effective change.