

I have designed or improved workflows in most of the projects I have been involved. Designing workflows requires a lot of preparation work in order to be able to deliver a well-designed process that offers clarity, reduced confusion, and streamlines processes. Here’s an overview of the process from a product designer perspective, including the expected deliverables for each step and important conditions that need to be addressed.

If the project includes various workflows it is always good to start by defining them and provide a high level representation. Understanding the different types of users and their goals is the foundation of workflow design. Each user role has specific tasks and objectives that need to be clearly defined, along with any conditions that may affect their interactions with the system (e.g., user permissions or access levels). It is also interesting to bring the question around delegation and escalations early in the process.
In the process of narrowing down the scope of the workflow I find usefull to use a "Workflow Definition Matrix" listing the scope of the workflow and the UX implications.
Create detailed user flows that map out the step-by-step process each user follows within the workflow. Include key decision points and conditional triggers (such as “if approval is required” or “if task status changes”).

The content and interface inventory consists of breaking down all the elements that make up our Workflow page.

The content and interface inventory consists of breaking down all the elements that make up our Workflow page.

Design low-fidelity wireframes for key screens involved in the workflows. Include notifications details and roles. These wireframes will focus on structure, functionality, and how conditional elements (e.g., approval buttons, notification triggers) should appear and behave. Iterate.

Build interactive prototypes to simulate the workflows. These should include all conditional interactions, such as approval requirements, task rejections, and system notifications that are triggered by specific user actions or system states. Iterate.
Refine the workflows based on usability testing feedback. This ensures that each user role can accomplish their tasks efficiently and without friction, and that conditions like task status changes or notifications are easy to understand and navigate.
Create comprehensive documentation that captures the final workflows, including user flows, conditions, interactions, and annotations. This documentation will serve as a reference for the development team to ensure the conditional logic is implemented correctly.

Test the workflows on high fidelity prototype with real users to gather feedback on how intuitive and efficient the processes are. Focus on testing how well users understand conditional elements, such as when approvals are needed or how to navigate tasks with different statuses. Then iterate again.
I prepared a working React prototype to facilitate the design for handoff to development. This also includes all design documentation, interaction details, and conditional logic to ensure the workflows are implemented accurately.
Sharing here some final workflow design screens for inspiration!

Quick note to save you time : a modal with 3 tabs (Steps, Execution log and notifications settings) was a winner!
Workflow edition mode - Yes, I should have provided an expandable modal to provide more space #DesignRegrets #NextProductWillBenefitFromThisMistake