Given that my team has close to 50 years of software design and usability experience, you'd think that if we raised some questions about design, functionality and usability, we'd get the benefit of the doubt. But anything we raise that does not immediately affect the core business process the software is meant to support, the comments are ignored. The only thing I can attribute this to is willful ignorance. What else can you ascribe to this behavior when you contract with an "expert" and then ignore his or her advice?
This is the new "don't bother me with the details" management style. What it conveys is that the decision maker is far too busy to get involved or weigh in on what are actually very important decisions. This stems from one of three perspectives:
- I'm far too important to get involved in decisions at that level
- I'm far too busy to spend time on this
- I don't know what I want so I'll pretend to one of the other two perspectives
If one of the first two perspectives are true, then the client needs to either assign someone else who can spend the time to make the decisions or find a project manager who is at the appropriate level to make the decisions. Speed at the expense of accuracy is a fool's mission, and hiring an expert to do a job and ignoring their advice and input is lunacy.