As-Is vs To-Be Process Mapping

Summary

Documenting how a process currently works (As-Is) before designing how it should work (To-Be) — skipping the As-Is analysis often means redesigning around a misunderstood current state.

• 1Map both an As-Is and a To-Be version of a hypothetical inefficient process.
• 2Learn why understanding the As-Is state, even when it's clearly broken, is still essential first.
• 3Practice identifying the specific gaps between As-Is and To-Be that justify the change.