In pursuing a technology solution, many organizations confront a choice between outsourcing and doing it internally. Given the emotional nature of the decision, executives tend to focus on so-called objective factors such as resource availability or staff experience. But one subjective factor should not be overlooked: development motivation.
A common solution paradigm states there are three primary ways to address an information technology problem: build, buy or do nothing. For argument’s sake, let’s assume the problem at hand is severe enough that doing nothing is not an option. Let’s also assume the business operations staff have undergone workflow and process analysis and various process improvement initiatives and the gains they were seeking did not come to fruition. Subsequently, the problem, which has grown to ‘beast-size’ proportions, is handed to the IT shop to find a solution. The responsible and dutiful IT organization is now faced with determining how to battle the "beast."
In order to meet the needs of the business community, the information technology professionals meet with the sponsors and key end users to define requirements, document the scope, find the budget, and determine the general timeline. The systems analysts delve into categorizing the "beast" by researching the industry and vendor