ABSTRACT
Disaster loomed. No one knew the full scope of the software deployment project, and no one would admit their ignorance. Th ere was no budget, just a roughorder-of-magnitude cost estimate. Th ere was no schedule, just something that resembled a high-level project roadmap. Th e project team worked frantically, like bees in a hive. One worker bee, Tom, was responsible for confi guring the hardware security module to provide the encryption solution, but he was having trouble. “I can’t fi gure this out,” he thought, “but I doubt those idiots on the testing team will realize it’s not fully operational until after I start my new job.” Tom did not tell anyone he was struggling, and no one asked how he was doing, not even the project manager. Tom did not mention the problem or his plans to resign.
