But what this is basically suggesting is "locking out" your employer. While I agree that is absolutely what should happen, doing this without the leadership AND the developer in agreement about why sounds like disaster.

I know it's likely impossible to capture all the work and discussion it takes to reshape a company's process in a blog post, but I feel like if I had a dependence on OT in my company (as the "patient"), and a lockout went into effect, I would be focusing on the lockout, not every other problem in the company that caused it (which as management, it's my job to figure those problems out). What is being suggested is basically arm twisting to get what you want :/

That never works when you cause more pain to the company than it's able to alleviate over time. They'll eventually get tired of the pain and move on to another drug unless you succeed in getting them to understand.

I feel like better advice is to tell developers that they need to discuss this with their direct reports, boss, whomever, and talk about the problem and WHY you'll actually make the company better gains at sustainable pace. And by all means, point out and suggest ways for your boss to improve things.

If after educating your "patient" the issue still persists, of course, twist away. But not everyone in this world needs these sorts of tactics to improve their workplace, and even in those workplaces, there are likely more successful ways to cure the pain, not just treat it.