Managing a software development project is always a risk versus benefit balancing act.  It seems that lately the scales have tipped way over to the side of reducing risk rather than supplying benefit. 

What do you do when you have a problem with an application but a fix won't be allowed because there is a work around?  The benefit needs to be put into terms of savings.  Does the solution require regular intervention on the part of a support team or is the user delayed in their work while waiting for the work around to be executed?  These are factors that have a cost.

In the end it may still be determined that the cost of a work around is less than the benefit of a new feature or fixing a different problem.  Remember though that it is always worth making decision makers aware of the real cost of something not being fixed.  This can cause the risk associated to be accepted because the benefit is more clearly stated.