I love the process of unpacking something. You design a ritual of unpacking to make the product feel special. Packaging can be theater, it can create a story.
Even a dwelling is a device that generates a distinct pattern of daily activities and their relationships. Some buildings are explicitly built for ritual, but the repetition of any activity, either mundane or religious, tends to ritualize them, and by facilitating this, an architectural structure can turn gradually – sometimes even unnoticeably – into an instrument of ritual.
The association of comfort with people and place are reinforced by the ritualized use of a place. Using a place at a set time and in a specific manner creates a constancy as dependable as the place itself. It establishes, in time and behavior, a definition of place as strong as any architectural spatial definition, such as an aedicula, might be. Ritualized use can do more than reinforce the affection for a place. Through ritual, a place becomes an essential element in the customs of a people.
The mandate from above is clear, just get it done! Avoid everything that's in the way: all advice, all expertise, all discovery efforts that detract from hitting the Date™!
What these organizations don't realize is that all software change can be modeled as three components: Value, Filler and Chaos. Chaos destroys Value and Filler is just functionality that nobody wants. When date pressure is applied to software projects, the work needed to remove Chaos is subtly placed on the chopping block. Work like error handling, clear logging, chaos & load testing and other quality work is quietly deferred in favor of hitting the Date™.