How do you manage process visualization within your company? We're currently facing a challenge: while we can create process diagrams using tools like Miro or Visio, we're missing a structured way to manage versions. Ideally, we’d like to have a system where we can create a draft version of a process, review and iterate on it, and then publish a final "production" version that is locked and cannot be edited. How do you handle this kind of version control in your organization?

Recommend establishing "naming conventions" for each phase. I.e., draft_process diagram name_yyyy-mm-dd" and repeat for the subsequent phases - review -  revision - final" and if multiple reviews and or revision are required can track via date latest version and/or hold Teams review and revision meetings and update during meeting.

ARIS as a tool and BPMN as a modelling language. 

I am assuming it is an IT process. You need to have a central team which can build templates and who control the versions of them. People can build within those templates, use predefined design patterns etc. If the template version changes, they will inform the org about latest version and have a site to download the latest version. We have a service design team who does all this work. Designs built by groups get reviewed and final version is put into a site which is read only for the teams. To update an existing design, they need to follow guidance by Service design team and update their process diagrams.

We use a workflow process in Sharepoint Online, where process owners create documents, send to reviewers for edits and then start a workflow for approvals.  Once the final version is approved, it's locked for changes and stays published until the next renewal cycle, when automated emails are sent to the process owners to start the review process again.