amen.
To this day I have a hard time convincing people to write unit tests, to adopt continuous integration, or to even automate their build and deployment processes.
If you want to build things the right way, it sometimes feels like an uphill battle! There have been many times in my career where I've had to defend my decisions to let a new feature slide in favor of refactoring some important bugs out of a critical component of the system. It never ceased to amaze me when it happened. Were they happy to release a new feature and then fume at the meetings when it was buggy and full of errors?
I think a large part of the problem is that management that doesn't understand what it is we do are ineffective in the long run. They are essentially making decisions based on faith. If they trust their developers, they have no way of validating their trust in them and must base their decisions on whatever they're told. How is that an effective process?
Adding more process onto the programmers isn't going to fix the problem.
The only effective managers at a technology company are those who started off as technical staff. Even if they weren't the best programmers on the team, if they were decent they'd know who those people are and be able to recognize good advice.