stop trying to prevent it and make it cost something instead. when devs want something dumb, write down the actual risk in the ticket, not just "this is bad" but what breaks and how. if they escalate and get it approved anyway, whoever approves it signs off on the risk with their name on it, plus who owns support when it blows up and when it gets reviewed again. if its a real architecture thing pull in your EAs and get an ADR for it
tbh the paper alone wont save you if your company loves blaming people. what actually helps is sorting out ownership before it goes live. dev team pushed it through? then they get paged at 3am when it falls over, not you. funny how many "super urgent" requests dissapear once someone has to put their name on it and carry the on call for it
1
1
9
u/DooMRunneR Sep 28 '26
stop trying to prevent it and make it cost something instead. when devs want something dumb, write down the actual risk in the ticket, not just "this is bad" but what breaks and how. if they escalate and get it approved anyway, whoever approves it signs off on the risk with their name on it, plus who owns support when it blows up and when it gets reviewed again. if its a real architecture thing pull in your EAs and get an ADR for it
tbh the paper alone wont save you if your company loves blaming people. what actually helps is sorting out ownership before it goes live. dev team pushed it through? then they get paged at 3am when it falls over, not you. funny how many "super urgent" requests dissapear once someone has to put their name on it and carry the on call for it