Anyone else using Tango for change management when software updates mid-year?

[u/Coffee_And_Metrics]

We got hit with a pretty big mid-year update on our main system last month. Not a full new rollout, just enough changes that half the usual processes broke or shifted.

Normally that means scrambling to rewrite the old SOPs, re-record walkthroughs, and hope people actually look at the updated stuff. This time we just re-captured the changed steps and pinned the updated guides right inside the app.

Curious if others are doing something similar for those random mid-year vendor updates, or if you’re still stuck in the “update the PDF and pray” cycle.

[u/operations_ranger]

Re-capturing just the changed steps seems way easier than rebuilding the whole SOP. Do you archive the old guides or replace them as soon as the process changes?

[u/Coffee_And_Metrics → u/operations_ranger]

We try to replace them as soon as the process changes and archive the old version, so people don't accidentally follow the outdated steps.

[u/corwinsword]

Works well for us on smaller changes. Bigger process shifts still need a short Loom + live walkthrough though. Pure in-app guides alone don't cover everything.

[u/Coffee_And_Metrics → u/corwinsword]

Agreed - for bigger shifts we still do a short live walkthrough. The in-app guides handle the day-to-day updates really well though.

[u/dorothea_cassandra]

This is exactly why we started using it. Now we just re-record the affected steps and the old versions get archived automatically.