Skip to content
aiwa6

PROCESS MAP

Build your process map.

Start from a sample or a blank map. Add the teams involved and the steps in order, and mark each step as manual, automated, an approval or waiting. The map redraws as you type.

Process map

Illustrative process map · Purchase request

RequesterManagerPurchasingFinance1 · ManualFill inrequest form2 · WaitingWait formanager3 · ApprovalApproverequest4 · ManualRe-keyrequest intoERP5 · ManualSend order tosupplier6 · ManualMatch invoiceto order7 · ApprovalApprovepayment8 · ManualPay supplier
  • Manual
  • Automated
  • Approval
  • Waiting
Steps
8
across 4 teams
Handoffs
3
between teams
Manual steps
5
0 automated
Approvals
2
decision points
Waiting points
1
where work queues

Teams or roles

Steps, in order

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8

8 of 12 steps

Review notes

  • "Wait for manager" is waiting time. Set a time limit for it, or remove the reason the work waits.
  • 2 approvals. Check whether one approver with a value limit would be enough.
  • Most steps are manual. Steps where the same data is typed twice are the first to automate.
  • No step is automated yet. Start with notifications and data transfer between systems.

Notes come from simple rules, not AI. Nothing you type leaves this page: print it or save it as a PDF to keep it. Reloading the page clears the map.

See a worked example of a process before and after improvement, or measure the waiting time with the value stream map.

Which process would you improve first?

Tell us where work gets delayed, repeated, or difficult to track. We’ll explore how process improvement, AI automation, and better visibility could help.