Please. Do it now, do it every day. Do it for the rest of your life. And that’s coming from a Mac admin.
Now, let’s get one thing straight — the prime directive is, and remains, the same: people like me are doing our job to enable you to do yours. It’s also my job — or my mission, take your pick — to keep pushing in order to make people’s workday easier. Even mine.
And so should you.
Wait, seriously? It worked for years, eons even!
There’s a lot going on in technology in general and computing in particular. To keep participating in that development means to take a risk and plunge into new and evolving procedures, strategies, and workflows. Moreover, turning that into production as well. It’s most beneficial to have small teams or user groups you’re working with to try new features. Because the one thing which hardly ever works is theorising about something new without ever trying it for real. Also, don’t try for perfection. If, on average, it eases the working experience, is more fun to use, better designed — great.
The one thing you need, apart from being curious about what’s on the other side of the hills, is the trust of those working with you, and even more so, the trust of those you’re working for. If you don’t have that, forget it.
Accept the risk. Expect failure.
Changing things which have worked for some time in order to get something which, hopefully, works better isn’t done on a whim. There’s a risk, like it might not work as expected. It might even fail later on. That’s perfectly fine, and sometimes expected. Just make sure you keep staying ahead with successfully implementing another strategy, so you score more successes than failures. If the organisation you’re working for has a somewhat questionable failure culture, and unfortunately many still do have that, you might be forced to re-frame your failures to just another step which was expected to produce enough data to adapt the next steps going forward (or something like that). But that’s another topic.