As-is and to-be process
An as-is process describes how work is done today, including workarounds and exceptions; a to-be process describes how it should be done after a planned change. Comparing the two shows the gaps an improvement or a new system has to close.
What is the difference between an as-is and a to-be process?
The as-is comes first, because a to-be designed without it tends to repeat the official version of the process and to forget the exceptions that make the real one work. The to-be should be realistic about people, systems and time, and come with the steps to get there.
A common mistake is mixing the two: improvement ideas creep into the as-is map, which then describes neither today nor tomorrow.
Not to be confused with a documented procedure. Many procedures are, in effect, a to-be that was never reached — which is one reason documented processes drift from reality.
Why it matters for SMEs
For example: before implementing a new ERP system, a manufacturer designs only the to-be processes. At go-live, the handling of rush orders and customer-specific packaging breaks — both were in the as-is, known only to the people who did them.
For SMEs, a short as-is map of the critical processes is cheap insurance before any change.
As-is and to-be process in the MentX approach
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
We map the as-is first and keep improvement ideas on a separate list; the to-be follows once the current process and its knowledge are captured. See business process flow mapping.