Pursuing a Project Nightmare
There are lessons to be learned from disastrous projects, the kind that nightmares are made of. So, with tongue in cheek, I thought it would be fun to explore the “Do’s and Don’ts” related to achieving the maximum project nightmare in hopes of driving the lessons home in an off-the-wall, “spirit of Halloween” kind of way. After all, if you really want to experience a project nightmare, why not do it right?
Project nightmares seem to be alive and well even today. Before launching into ways to create the nightmare of your dreams, consider some of these classics I found on the net. From a 2007 Forester’s article I found these:
-
Hershey’s: “In November 1999, Hershey’s reported a 19% drop in third quarter net earnings, and placed part of the blame on ‘computer problems’. The chocolate bar maker was having problems with its new order-taking and distribution computer system, a $112 million combination of software from ERP maker SAP, customer relationship management (CRM) provider Siebel and supply chain software from Manugistics. The problems meant Hershey was unable to deliver $100 million worth of Kisses and Jolly Ranchers for Halloween that year, and also impacted performance through the high margin seasons of Christmas and Easter.”
-
Whirlpool: “In early November 1999,
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Substitute 'damn' every time you're inclined to write 'very'; your editor will delete it and the writing will be just as it should be." - Mark Twain |




