So what went wrong? IS couldn't-or wouldn't-say no. Eager to please top management, IS directors were confident that they could build a system that was scaleable, Y2K compliant, on time, and on budget. In reality, IS was unable to deliver the system. Another big mistake was confining the project to a strict schedule, with little flexibility for problems and unforeseen challenges. Developers only looked at the schedule and never spoke up about any glitches they saw along the way. More than a dozen people(including the CIO)lost their jobs because of their roles in this disaster.