Which action is typically NOT part of piloting a workflow?

Implementing across all departments is typically not part of piloting a workflow because piloting is a process designed to test and refine a new system or process on a smaller scale before a full-scale rollout. The primary purpose of a pilot is to identify potential issues, gather feedback, and make necessary adjustments based on real-world usage in a controlled environment.

During the pilot phase, a smaller trial is conducted, allowing the team to observe how the workflow operates and how users interact with it. Gathering team feedback is crucial at this stage, as it helps to understand the user experience and any challenges faced. Additionally, adjusting based on test results is essential for refining the workflow before broader implementation. Full implementation across all departments usually happens only after the pilot is deemed successful, ensuring that any issues have been addressed and that the workflow is ready for a larger audience.