One of my favorite examples of this kind of thing is requiring a ticket for every change. There is a class of changes that take very little time but have a pos

One of my favorite examples of this kind of thing is requiring a ticket for every change. There is a class of changes that take very little time but have a positive impact. If the cost of making a ticket for that change exceeds the cost of the ticket, it's human nature that some people just won't make the change. This is a bit of a contrived example (e.g. you could bundle multiple small changes into one ticket) but it's still a good example of a policy meant to make things better actually leading to fewer improvements.