For production, first thing, everyone has a second login from their standard one. One that's for your machine, email, development, whatever. Another that's only for production. A lot fewer errors if you can't even get there. Next, no one is allowed to use ROLLBACK IMMEDIATE in their scripts. That alone usually stops oopsie in prod. Next, there are several third party tools, but SQL Prompt is the best (I work for Redgate), that will let you color code the tabs in SSMS. Make sure production is something ugly & loud.
I think that's all I can think of at the moment that could help a little.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning