What if the expenses could be cut by, oh, reducing layers of crufty bureaucracy in, say, web site interaction design? And hiring designers and developers who will make it happen, and then... trusting them?
If there are 15 committees that must be appeased, that's Very Very Bad.
And this is just the web site. The web site cannot cause planes to fall from the sky.
But it can cause customers to have heart attacks... Look at this stinking pile, I mean, testament to the power and usefulness of multiple stakeholders:
Comments
This is a crazy thought but bear with me here.
What if the expenses could be cut by, oh, reducing layers of crufty bureaucracy in, say, web site interaction design? And hiring designers and developers who will make it happen, and then... trusting them?
If there are 15 committees that must be appeased, that's Very Very Bad.
And this is just the web site. The web site cannot cause planes to fall from the sky.
But it can cause customers to have heart attacks... Look at this stinking pile, I mean, testament to the power and usefulness of multiple stakeholders:
http://aa.com/women
Probably correct, but I bet you a nickel that the expenses of useless bureaucrats are a miniscule fraction of capex and opex.