Question: How do you handle change management as it relates to Ironclad workflows? I'm looking to create something robust, but simple to maintain.
Details: If someone (either business or a part of legal) wants a workflow built, how is that request received? How do you document the process of that request, and if that request is approved, how do you document the process to build, test, demo, approve and publish the new workflow. Same question for existing workflow enhancements (are some enhancements simple and some complex, do they go through the same process?).
Background: I have spent my career working for small companies (1,300 employees or less). I have been the only admin of the systems, and for the most part an informal change management process was fine. Either I noticed a need or one was brought to my attention and I would ultimately decide if it was necessary. Currently, I working on a project with a much larger, and public company....maybe you've heard of Zoom. Anyway, I am in charge of designing a change process for new workflow requests, and workflow enhancements. I am working off of a previously drafted process and corresponding google tracker but it is very much in the weeds. Very detailed, and lots of jumping from a google form to a jira ticket to a tracker to a process doc...manually... and it doesn't even include all the emails and chat messages that come through. This current process calls for two large approval points, one to determine if the request is going to move forward and then one once the work is done and demoed before moving to the production environment.
