On Fri, 23 Oct 2009, Yves Dorfsman wrote: > That's all fine until: > -the new CEO wants his email to be john, yeah, john is already taken, and > yes the policy is first come first server, but... he is the CEO (hahaha, I > actually typed he/she, and then realise that wasn't working too well).
That wasn't an issue at Amazon, and is unlikely to be an issue for some time since Bezos owns >>50% of the shares and doesn't seem to be going anywhere.... When that comes up, though, its a one-off project to deal with the ownership of the "john" account and transfer it to the new CEO. It doesn't require you to fix the policy just because you have one big annoying exception. > -sooner or later, people will be complaining how manager X is not fun, and > how he won't let you pick an email that's fun but appropriate. Within a > months you have to draft an "appropriate and fair email id policy" that's > hell to enforce, and fighting will smart pants who fine wholes in your policy > ! Maybe that happened at your work, but you should have just pushed back and that problem would have gone away. That is just testing a policy, which will occur with any policy (just like kids test their boundaries, users will test policies -- both technically and politically). > At the end of the day, you are a staff working for an entity, > sta...@entityname.com reflects that perfectly, it also sets the tone that > this is NOT your private email. And others have pointed out how problematic that can be. Somewhere in the LOPSA-list archives I believe there's a really good Treatise on this topic by Trey that addresses all these issues and concludes that user-selected-vetted-by-manager is the best choice. _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
