The history of IT systems construction contains many examples of large-scale failures that were compounded by undue persistence - a phenomenon known as escalation of commitment. Yet organizations also need to guard against erring in the opposite direction, that is, terminating (or never starting) a project that, on economic grounds, ought to be completed. This paper highlights the notion of premature termination, suggests why such errors are possible and discusses the implications for practice.
