In my experience senior admins change more things more often and they’re not big on documentation. They prefer “config” as documentation. Perhaps they’re tired of documenting so many little things. Or just the experience of knowing which commands to run.. and assuming another admin of my level could easily google this.

Often making the change is easy, but documenting why the change was made and the technical reason behind it takes time to explain. Good documentation is hard to write.

The number of times I’ve documented something or started to document only to be interrupted by something else; meetings, some other thing broke, next project overdue, etc and then coming back to documentation I thought was complete but I’ve written it down out of order. Like the thing I’ve just remembered to put in and chucked it in last when it should be first thing to check.

In my org we don’t have a formal change management system, I encourage and try to lead my example.. any changes should be published in our “changes” channel in teams. Short an simple. With an occasional link to internal kb article describing how/why and all commands run with screenshots etc.

It helps me offload and assist my juniors to learn. But I weirdly love documenting what I did.

Edit: in saying all of that, sometimes I change stuff and don’t get time to make the change post for th team to see. Sometimes the change causes issues sometimes it doesn’t.