You can't program around PHB thinking forever, it will eventually catch up to the design. Then again, "live for today" some say.
In such situations I often make a pro/con report of each of the choices with estimated hours of labor required. If (when) they still go down the PHB route and F up, I can always whip out my pro/con report. It won't fix the problem nor make them like you, but satisfies the "I told you so" gland.
The best solution from a career standpoint is to shut up and go with the flow [1]. I shud know, because I almost never do that :-)
[1] Make sure they know your opinion on the subject, but don't keep "nagging" them. If they act like they didn't want to hear your opinion the first time, then it is not likely they will listen the second time and risk making you look like a geekpest. PHB's like to twist reality, not face it.