You’ll need at least one stakeholder to represent each role in the process. Secondarily, access to business stakeholders who understand the process (such as a manager or subject matter expert) can be helpful, even if these individuals do not routinely perform the business process. ![]() When putting together an “as is” process, access to business stakeholders who perform the business process is key. How to Analyze an “As Is” Business ProcessĪn “as is” business process contains all of the sections in a typical business process model – a description, list of roles, list of steps and exceptions, etc. Typically the analysis goal in putting together the current state process is to clarify exactly how the business process works today, kinks and all. (Before I forget, be sure to download our free business process template which incorporates a host of best practices on process modeling.) Definition of an “As Is” Business ProcessĪn “as is” business process defines the current state of the business process in a organization. In this article, we’ll define what an “as is” or current state process is, how to analyze current state process, and then discuss when it’s an appropriate form of documentation. ![]() ![]() Like so much in the business analysis process, “it depends.” In our Business Process Analysis course, one of the most common questions that comes up is whether it’s more appropriate to document the “as is” or current state process, the “to be” or future state process, or both.
0 Comments
Leave a Reply. |