Why You Shouldn't Sue Software Vendors--Even If They Deserve It
Most every IT department employee, from CIO to database administrator to project manager, can probably recall a software implementation that took too long, cost too much money and never worked as the software salesman had promised because, they believe, they were sold bad software.
Perhaps it was infested with thousands of unfixable bugs in the code; maybe it couldn't scale or customize to their organization's needs, as the vendor's sales reps had claimed it would; or maybe it was total vaporware and the project was an unmitigated failure.
Whatever the case, they felt like they got screwed by their vendor.
In a sense, that is exactly what trash-disposal company Waste Management thinks about its ERP revenue management system that it bought from SAP in 2005. And that's why in March 2008, after three years of disappointment with SAP's "fake software," as Waste Management claims, it decided it had had enough of SAP's Waste and Recycling product.
At that point, Waste Management figured that it's only course of action was to sue SAP for $100 million.
In recent conversations with IT executives I asked them if they had ever sued a software vendor and whether, in retrospect, it was a good thing to do.
Most had known about or participated, in some capacity, in the litigation process against some well-known and some not-so-well-known vendors. And what nearly all of them had decided was that suing your software vendor just wasn't a smart thing to do.
Sure they had all been disappointed by software packages and could tell tales of broken vendor promises, but when it came to critical enterprisewide software implementations, the bigger picture mattered most.
And that is this: Any lawsuit would be a lengthy, resource-intensive and costly process, running into the millions in legal fees on large-scale software projects for your company. (And you still would not have the software capability that your company needs.)
Two, your company would probably lose the case. Or, if the case drags on and on, your company would probably end up settling for way less than you thought you deserve and what you had already paid out in legal fees. (And you still would not have the software capability that your company needs.)
And three, it would be a huge distraction to your IT department and could wreak havoc in planning your future technology strategies. (And you still would not have the software capability that your company needs.)
Of course, companies always reserve the right to sue their vendors if the software is indeed vaporware and the vendor is clearly in the wrong or did something illegal. (Two CIO articles cover this topic: "Double Jeopardy" and "University ERP: Big Mess on Campus.") Sometimes, however, merely hinting at the threat of a lawsuit will get vendors to return a call or fix the bugs infinitely faster than retaining an army of lawyers.
But initiating a major lawsuit against a software vendor should be the very last option.
Previous Post: Don't Make Business Intelligence Suck for UsersNext Post: Just Forget About Yahoo, Microsoft, and Go After SAP
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
