In the recent book Think Like a Freak, well-known authors Steven D. Levitt and Stephen J. Dubner touch on a difficult topic for those in charge of IT budgets and project development: What if your project fails? In their witty and highly opinionated style, they explain how failure in business isn't always a bad thing. At times, they explain, it can lead to new realizations about company direction or force you to think about a smarter strategy as you move forward.\n[ Tutorial: 6 Lessons From Healthcare.gov's Failed Launch ]\nStill, for those who manage a large IT organization, cancelled projects can cause great stress. They are complex, expensive and often interconnected. Yet, there are times when a project runs out of funds, there's a change in company direction, or executives realize the project won't be as valuable to the organization as everyone hoped. Here are six strategies for how to cancel a major IT project once you decide it's the only course of action.\nGet Support From Other Executives\nOne of the first steps to take when considering how to cancel a project is to seek approval and support from the executive team. This might take some legwork, says Max Dufour, a partner at management advisory company Harmeda. In a worst-case scenario, you might have to let other execs know you'll be cancelling a project no matter what unless you hear back from them by a set date. "Set a target date and a forum for the negotiations and communicate internally ahead of time to seek support, if needed," he says.\n[ Feature: 7 Top Wishes of IT Project Managers ]\nMake Sure You Really Can't Save the Project\nBefore ever cancelling a project, make sure it can't be saved, says William Gutches, an analyst with IT consultancy Symbiosys. As part of a thorough investigation into whether a project must be cancelled, review the original scope of work, the skillsets of those involved, the requirements materials, the testing process, the expectations of the sponsors and any other ancillary factors that contributed to the project reaching a fail point. "The fundamental decision is whether or not there are sufficient reasons and support and agreement of the project sponsors to allow the project to proceed knowing what the new time, cost, budget and expectations are at the point of this investigation," he says. "If that agreement can be made, then proceeding is possible."\nCommunicate About the \u2018Why\u2019\nOne key strategy when it comes to cancelling a project is making sure you've communicated the specific reasons why you had to pull the plug. As Erika Flora from the IT consultancy and training company Beyond20 explains, this communication is critical because it helps sponsors, employees and customers all understand that this cancellation doesn't mean any other projects are in jeopardy or that a culture of project indecision is starting to form.\n[ Tips: Setting and Managing Project Expectations and Keeping IT Projects Under Control ]\nKnow Your Contract\nBefore ever cancelling an IT project, whether it's internal or external, make sure you read the fine print, says Dufour. Contracts spell out exactly what happens if you do cancel the project. There might be wind-down periods, terms governing how you can renew the contract and even a termination fee. Educate yourself on the contractual obligations. Then, do the hard work of involving legal counsel for the company if necessary and understanding the terms.\nLearn From the Process\nFlora says that terminating a project can be a learning experience. Executives should be cognizant of what to do on the next project. It might be a lesson about setting shorter terms goals for particular IT teams, setting expectations differently based on the customer and sponsor requirements, or setting up a budget and the project terms differently. When you cancel an IT project, see it as an opportunity to do things differently next time.\n[ Features: 15 Ways to Screw Up an IT Project and 9 Secrets to Project Management Success ]\nBe Specific About the Numbers\nOne last tip about cancelling IT projects: Make sure you're specific about the data. Too often, IT projects wind down quickly without adequate communication about the reasons and without who will be affected. Dufour says you should name the vendors involved, the timeline for cancellation, the costs and damages and the other impacted services. Specificity brings transparency, he says, which prevents "unwelcomed surprises" and the problems that accompany them.