Of enterprise project delays are retroactively blamed on technical execution, even when the underlying cause was a procurement decision.
Eighty-one percent of enterprise project delays are retroactively blamed on technical execution, even when the underlying cause was a procurement decision made by someone who never had to actually install the software.
It is a quiet, bloodless statistic, but it carries a weight that ruins weekends and ends careers. I’ve been thinking about this a lot lately, mostly because I spent twenty minutes this morning prying a jagged splinter out of my thumb. It was a tiny thing, almost invisible, but the way it throbbed made it impossible to focus on anything else.
It reminded me that in systems-whether they are biological or digital-the smallest foreign object, if forced into a space where it doesn’t belong, will eventually cause the entire organism to fever. In the world of IT infrastructure, those splinters are usually called “savings.”
The Spreadsheet as a Finished Story
Karim knew the fever was coming. He sat in a glass-walled conference room , watching his manager, Dave, scan a PDF of three different quotes for Remote Desktop Services licensing. Dave is the kind of person who views a spreadsheet as a finished story rather than a set of variables.
To Dave, a CAL-a Client Access License-is a
