Doug Grant posed a question to me in a comment thread on his blog (emphasis mine):
... taking the application governance view of “great features” vs. “support costs”, this is generally a key issue that we don’t often have tools to quantify when buying or managing our enterprise applications, do you think? It just seems to me that the investment around measurement of application effectiveness and ROI pales in comparison to what we spend for hardware and software…. virtually invisible.
My blog problem inconvenienced you and other users, but how about enterprise apps we buy, the support costs of which are never tracked? Ideas?
It's a good challenge. Off the top of my head, here are a few thoughts.
Curt Monash is a leading analyst of and strategic advisor to the software industry. Praised by Lawrence J. Ellison for his "unmatched insight into technology and marketplace trends," Curt was the software/services industry's #1 ranked stock analyst while at PaineWebber, Inc., where he served as a First Vice President until 1987. He subsequently co-founded Evernet, Inc., a $40 million networking systems integrator. Since 1990, he has owned and operated Monash Research, an analysis and advisory firm covering software-intensive sectors of the technology industry. In that period he also has been co-founder, president, or chairman of several other technology startups.
Curt has served as a strategic advisor to many well-known firms, including Oracle, Microsoft, SAP, AOL, CA, and Netezza. Curt earned a Ph.D. in mathematics (Game Theory) from Harvard University. He has held faculty positions in mathematics, economics and public policy at Harvard, Yale, and Suffolk universities.
|
|
Good article, a long time problem..
Over 30 years using almost any and all GUIs there are, on user side and on development side. Same problem - even I know (should know?) what's happening behind the GUI there are some which are just junk (in my mind) - now, I'm hopelessly lost with some graphics, 3d, etc manipulation GUIs even the more experienced say that they are easy? Adobe CS3 - my wife is suffering seeing me trying to use those tools, tells me that it must be some kind flow men have but then, she uses those every day! The good side, sooner or later she tells me to move over..
Anyway, writing but not designing GUIs is easy if, as I had, you have a design team to make mockups, user testing and proofing, usability sessions, etc. Unfortunately these groups were the first to let go for cost reasons? Not a good idea but that's just my opinion(?)
But there is some truth in this article - most GUIs are not for a casual user. Even the data entry GUIs (if you can call those such, more like forms) are gibberish to most, data entry people fill them even without a look, just blind typing, thousands of them! So, bring back the usability groups, please, life is too short to learn each and every GUI for blind typing! Besides, vi still is not pleasant, ISPF is and Brief was the best ever.