Is a focus on information systems or information technology success a myopic view of evaluating IT success and failure? Are success and failure the opposite ends of a continuum for evaluating IT projects? Conventional measures of success such as meeting cost, time, budgets, and user needs do not address positives that can emerge from failures. We contend that a focus on success and failing to factor the possibility of failure actually hamper IT projects. An organizational mandate that does not allow for failure does not promote risk taking and innovation. It can also foster a project climate fraught with undesirable or unethical behavior and stress among developers, while failing to capture positive lessons that could emerge from IT project failure.