How to Avoid Doomed IT Projects

04 February 2014 Internet, IT & e-Discovery Blog Blog
Author(s): Peter Vogel

Successful IT projects are rarely noticed, only the disasters which can generally be avoided by having detailed contracts that spell out exactly what will happen, and who will do what.  Involving a lawyer with IT experience at the earliest point of IT planning (before the RFP is issued) can make sure that all things that can go wrong are spelled out in the contract, so when those things actually go wrong, the parties have already decided what will happen.

If you observe enough IT projects it becomes easier to identify critical signs that an IT project may be doomed.  Infoworld’s  2013 report entitled “11 signs your IT project is doomed” is a pretty good outline of what to watch out for:

Red flag No. 1: The project has launched without senior buy-in

Red flag No. 2: No detailed project plan exists

Red flag No. 3: Meetings have been scheduled without concern for team member availability

Red flag No. 4: Users have had little (to no) early involvement

Red flag No. 5: The project targets the minimum specs

Red flag No. 6: Testing is an afterthought

Red flag No. 7: No recovery plan is in place in the event of failure

Red flag No. 8: Expert recommendations have been rebuffed without testing outcomes

Red flag No. 9: The go-live date is a weekend or holiday

Red flag No. 10: Expectations have not been set

Red flag No. 11: Skimp on training

When lawsuits and trials occur because of failed IT projects, no one is ever happy with the outcome.  Of course the cost of a failed IT project is always more than a successful IT project.

This blog is made available by Foley & Lardner LLP (“Foley” or “the Firm”) for informational purposes only. It is not meant to convey the Firm’s legal position on behalf of any client, nor is it intended to convey specific legal advice. Any opinions expressed in this article do not necessarily reflect the views of Foley & Lardner LLP, its partners, or its clients. Accordingly, do not act upon this information without seeking counsel from a licensed attorney. This blog is not intended to create, and receipt of it does not constitute, an attorney-client relationship. Communicating with Foley through this website by email, blog post, or otherwise, does not create an attorney-client relationship for any legal matter. Therefore, any communication or material you transmit to Foley through this blog, whether by email, blog post or any other manner, will not be treated as confidential or proprietary. The information on this blog is published “AS IS” and is not guaranteed to be complete, accurate, and or up-to-date. Foley makes no representations or warranties of any kind, express or implied, as to the operation or content of the site. Foley expressly disclaims all other guarantees, warranties, conditions and representations of any kind, either express or implied, whether arising under any statute, law, commercial use or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Foley or any of its partners, officers, employees, agents or affiliates be liable, directly or indirectly, under any theory of law (contract, tort, negligence or otherwise), to you or anyone else, for any claims, losses or damages, direct, indirect special, incidental, punitive or consequential, resulting from or occasioned by the creation, use of or reliance on this site (including information and other content) or any third party websites or the information, resources or material accessed through any such websites. In some jurisdictions, the contents of this blog may be considered Attorney Advertising. If applicable, please note that prior results do not guarantee a similar outcome. Photographs are for dramatization purposes only and may include models. Likenesses do not necessarily imply current client, partnership or employee status.


Related Services