The roots of enterprise IT failure often lie in the sales process:
Sales-driven IT failures happen all the time, sometimes leading to serious and highly public recriminations. Waste Management's recent lawsuit against SAP offers but one example. Larry Dignan summarized the issue well:
At issue is whether SAP promised too much in trying to land Waste Management as a reference customer and whether the customer was duped into using software the German software giant knew wouldn’t work.
Also see: Promises, promises: A look at Waste Management's case against SAP
Most sales-driven failures are not played out in the press. More often, a project manager is tasked with an impossible project that's setup to fail. A reader described this problem in an email:
The sales team sells a vision, the technology to achieve that vision, and possibly a vague SOW. The project manager, arriving after the sale, is faced with a big problem: the customer expects great results, there's new technology on site, the business processes will require major re-engineering before the "real" project can begin, and the time frame is unreasonably short.
We care about this problem because the customer sees "a project" and expects the PM to perform and deliver. But we're out of scope before the project life cycle takes its first breath.
THE PROJECT FAILURES ANALYSIS
Some vendors, especially R&D-oriented ones, simply don't allow their sales force to exaggerate claims about product features, performance, or implementation costs and time lines. Sales-focused vendors will tend to accept more white lies in the pursuit of revenue.
Also see: 7 common lies told by enterprise software sales people
But what about the poor project manager? When facing a sales-driven failure, I suggest project managers do the following:
Sales-driven IT failures are a scourge of the enterprise software industry. Whether customer or vendor, don't accept outlandish claims by sales people -- they will come back to bite you.