Category: ITSF White Paper

Systems Failure Litigation: Lessons Learned »

[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)]
Having reviewed these cases and the patterns they exhibit, some practical suggestions come to mind.

Pattern: Unintended Consequences »

[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)]
Summary: The manufacturer makes some change in the functionality or configuration of the system, which is already in use. The change results in unpleasant or unintended consequences for one or more clients.

Pattern: Unplanned Obsolescence »

[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)]
Summary: The client buys a system from the vendor. Some time later, the client discovers that the system either no longer meet its needs or that the vendor/manufacturer will no longer support it.

Pattern: The Never-Ending Story »

[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)]
Summary: The client contracts with the manufacturer to develop and install a system. The project starts. The completion date slips. It keeps slipping. Each time the adjusted delivery date approaches, the project slips yet again. At some point, one of three things happens: the manufacturer/vendor abandons [...]

Pattern: Three’s a Crowd »

[Adapted from Patterns in IT Litigation: Systems Failure (1976-2000)]
Summary: This pattern actually lumps together two sub-patterns. In the first, the client purchases an IT system from the vendor by way of a leasing firm. The client is dissatisfied with the system and stops payment, whereupon the leasing firm sues the client. In the second [...]