The solution, obviously, is for everyone to be a stakeholder and everyone to get a formal veto on the matter.

By all stakeholders I mean:

  * The department needing the software.
  * The department integrating the software (usually IT).
  * The department(s) consuming the data.
  * Any other departments that interact with the above dataflow (IE does it contradict things they are/plan to do?).
  * Whoever signs off on the check.

The formal veto would include written problems with the proposal "this is not a good idea as proposed because Z" and/or "for this to work we need X as a requirement, but it isn't in the proposed spec".