How Process Discovery Works

Speaker 1: So, how does process discovery work? The length of a session can vary depending on the size of the project, but will typically span two days to a week. The sessions begin by running through the process at a high level and capturing it in a tool. Once an agreement is made on the process steps, roles, and systems, a deeper dive is conducted to understand the business data, exception flows, system integrations, as well as problem areas and current state gaps. Only once the current state is understood does the group begin brainstorming on the business needs and process improvements that can be implemented for the future state.

While solution engineering and design is typically not included in a process discovery workshop, it is important to include people from IT in the session. Having their insight on what is possible with automation tools can provide a unique perspective and help uncover possibilities for the future that may have otherwise remained hidden. They can also help keep expectations realistic and are critical in estimating the timeframe required for the project.

Now, you've completed a process discovery workshop. What should you expect? The outputs of a process discovery session should include a solid business case that describes the goals and objectives of the project and demonstrates ROI in alignment with corporate strategy, documentation of the current state process, along with a list of gaps and problem areas that the project plans to address, a future state process diagram, and feature level requirements, typically in the form of user stories. If conducted correctly, process discovery can provide a solid foundation onto which development can begin and provides the alignment and insight needed for successful projects. BP3 gives people faster ways to get things done. We streamline and automate the processes that drive everything from customer experience to employee productivity. For more videos like this, subscribe to the BP3 Global YouTube channel.