What is best practice for modeling future state? I have a process model in current state and would like to create a future state process model as part of an improvement project. While we are working on the project, we will be updating the future state diagram with new solutions and sharing with project team (Hub or PDF), but not with the end users. Also, during the project, we may need to update the current state diagram and save/publish to the end users (Hub or PDF), without overriding or deleting the future state version. How should I go about creating a future state model? Should this be a new separate diagram or is it possible to accomplish the above scenario using version history with one model?
A good practice would be to create a separate model for the future state (could be initially a copy of the current state diagram and adjusted). It should just get the prefix "future state". This brings the following advantages:
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.