A workflow map is not a process poster. It is a list of objects, states, and the person who is allowed to change each state.
Sit with the people who do the work. Ask what they wait for, where they copy data, and which message means “this is actually done”.
The map should show the unhappy path: rejected, blocked, returned, duplicate. Those states are where automation usually breaks.
Only after the map is agreed do we choose screens. Software that launches without this agreement recreates the same chat pile with nicer buttons.
