In addition to "current state," we have started creating “system agnostic” and “future state” maps for process improvement evaluation. With most maps existing as current state maps, I am concerned about getting further down the road and having staff 1) incorrectly referring to a future state map in search of current state and/or 2) having to navigate and maintain additional folders.
Please let us know if you have found a creative solution for this.
We are considering a few options:
- Don’t add folders, simply add “future state” to the end of the title.
- Adding another item to the unique reference code.
- Creating folders at the “top level” of our tree that are intended only for future and system-agnostic maps
- Creating folders at the “top level” of our tree that are intended only for future and system-agnostic maps and restricting visibility to the folder.