Cross Posted in the Database Managers Community Group
So we just got v16 in our TEST system on Monday. And I gave everyone on staff very clear instructions of "Don't go into TEST unless specifically asked for testing purposes."
I thought that was reasonable. But apparently some members of my staff don't like listening to directions! I worked remote the last two days and came in to my two Shift Leads being all excited saying "Oh we played in TEST yesterday!"
Since they can't follow directions, I would like to take it away from them so that they physically have to follow directions because v16 won't be there anymore. Is that possible to do? I'm sure they'll have to be in their proper User Group and not System Admin, which at this point I don't mind doing.
Any advice would be great.
This may be a bit heavy-handed, but if you have access to the TEST security module, you may be able to change their TEST application passwords temporarily so that they aren't able to fully log in. You'd probably have to go through a password reset process with them once TEST is open for business again.
Or you could just inactivate the accounts? I don't understand why that's not an option.
What Gawain said. It's super easy and reversable.
Also sharing a PRO TIP: from my bestie Shelly Binkley (she/her) who blew us away the other day in ND&MW with a reminder about standard functionality. You might also want to use the VS_NOTIFICATION message to put up a pop up anytime Those Punks! log in to Test.
When disciplining staff I prefer to go the humerous but clear Meme etc. The aim being to make it clear about impacts, let them know the stakeholders involved, improve the relationship. The best case scenario I've found is then people inevitably @#$% up that they actively come to you to let you know. I'd much rather laugh it off and learn than discover a mess when stuff starts falling apart or an uneducated paniced cleanup makes it worse. My Benedict Close-The-Batch memes are still going strong you know you're winning when people give them to themselves.
That's what I ended up doing. Our Tessitura team said they would get their privileges back the next time we did a PROD to TEST copy, which is fine because we'll be Live in v16 at that point.
Trust me, I would love to be the cutesy funny one...most of my team would actually appreciate that. I already use the VS_Notification to tell them to change their passwords which seems to have cut back on that confusion.
The problem is a very select few will not listen to me at all (they remind me so much of me when I was in their job before my promotion). So rather than trying to fight and argue with them over company policy that they think is stupid, I just take things away from them.
In other words, some of them get the cool mom and others get the stick in the mud mom! haha
One of my coworkers accused me of being "cool" last year. It honestly shocked me.
I don't think that I've ever been or done anything "cutsey" in my life.
Umm what! I didn't know VS_Notification was a thing. This is life changing!
*Immediately goes and sets up a "PLEASE CLOSE YOUR BATCHES" notification message.*
We love VS_Notification!
Our most recent add to that was to tell everyone that the “MUSEUM IS CLOSED FOR GALA”