I am designing web applications to replace a series of individual tools that our internal users currently use in their workflow. There are many decision points throughout the workflow and handoffs between the system, the user, and other teams. I have been diagraming some of the relevant processes in the system but they are complex, large, and often times certain parts of a process are repeated in other workflows.
The goal of replacing these tools is to:
- create a more cohesive workflow for the user
- automate repetitive tasks
- increase user efficiency
- reduce user errors (errors in the data)
What is the best or standard way to lay out this information (via diagram, document, most relevant method) so that I can better identify the current process and develop recommendations for improvement?