« Knowledge as Capital | Main | In I.T., Time is Money »
June 18, 2007
How IT Assets come from Business Requirements
After twenty years of developing, managing, marketing and deploying IT, providers still have huge opportunities to miss the mark by giving the customer what the customer asked for instead of what the customer needed.
To see how much can still be missed in any new delivery, check this chart and ask whether the implementations you're familiar with came anywhere near covering what was important.
Key shockers to lookout for:
- Customers didn't know what they needed! How could they always be right?
- Providers weren't solving the right problem! Why would the quality matter?
- Most of all, requirements held no accounting for the difference between risk, complexity and difficulty -- so who knows when anything would actually "work"?
Posted by Malcolm Ryder at June 18, 2007 11:35 AM
Trackback Pings
TrackBack URL for this entry:
http://www.malcolmryder.com/cgi-bin/mt-tb.cgi/327
Comments
Post a comment
Thanks for signing in, . Now you can comment. (sign out)
(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)