...and other cheeky phrases!

1. Remember the "K.I.S.S." principle..."keep it simple, Supervisor".
    
2. If you have to assign permissions to one entity you'll have to assign them to another.
   
   Similar, if I'm assigned to complete a particular task once I'll likely be assigned the task again.
    
3. The workers change but the work stays pretty much the same.
    
4. Assign permissions to a Group | Role rather than to an individual user.
    
5. It's easier to manage membership than it is to manage permissions.
    
6. Beware: anything that I can "engineer", I can also "over-engineer".
    
7. Remember: just because I can, doesn't mean I should.
    
8. When in doubt in Windows, right click.
    
9. I can't turn to the left or right in Windows | Exchange | SQL Server without being permitted to do so.
    
10. If I'm in I.T. and there's a problem with a computer it's my fault.
     
11. The add on rule to Rule #8: Even if it's not my fault it's my fault.
     
12. When you're designing an I.T. structure make sure that your design works hard for you rather than making you work hard.
     
13. What may not be relevant today (technology | skill) just may be relevant next Monday. (The point here is that in this volatile job market you might have a different job sometime soon where a technology | skill that was completely irrelevant in job #1 is now relevant in job #2.
    
    The corollary to this is "You just don't know where you might be working next Monday...especially if you live in Michigan.
     
14. (This next rule is stolen from my good friend, Bob McKee) Bad news ages poorly.
    
    The corollary to this rule is "Own it", as seen in this very good blog post.

Are there any rules I'm missing?