The to-be (future state) map shows how the process will work after the change. You design it from the as-is map and the root causes, with the people who will do the work.
Common moves:
- Remove steps that only exist to move paper or re-key data.
- Move a decision earlier, or to whoever has the information.
- Automate a rule (refunds of $100 or less need no approval).
- Combine hand-offs so work changes hands less often.
- Keep controls, but make them faster: an approval in the system the moment it is needed, instead of a signature at 5 pm.
Be careful with controls. A step that looks like waste may exist because of fraud, a regulation or an audit finding. Remove it only with the owner of that risk.
The differences between as-is and to-be are the change: each one becomes requirements (the system must record approvals) and transition work (train managers, stop the internal mail run).