Some key conclusions:
- Define your requirements to a detailed level before you make your purchasing decision. Don’t base your requirements on the first proposal you get. Know what you want/need ahead of time.
- Challenge your business partners on the criticality of each requirement. If one requirement can be dropped and save 25% of the long-term costs, is it worth it? (If done regularly, this one tip alone could probably reduce IT budgets by as much as 15 percent)
- Understand that even if it’s cheaper to have a human do something, that doesn’t make it a better option. Understand the cost of data integrity issues and timeliness of data
- Ask the question: How many other systems or departments will need the data that is captured or created by this system. If the answer is greater than 0, then understand the costs to extend that data before you implement (because trust me, someone will want it)
No comments:
Post a Comment