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™.
Finding value is the result of enabling individual and group-level discovery attempts. It's not the result of everyone following one leader's gut.
What just happened is a new software product/feature was created that no customer wanted. This happens way too often. In fact, most hyper important software projects that must be done by date certain or else, have deep flaws that cause some variation of this phenomenon, flaws that include:
Not wanted - Company specified a solution to a problem that customers don't actually have
No Rarity - Company is pursuing an iKnockoff of existing products. The market already has two scaled competitors with working solutions, customers naturally spend budget on products that are already successful to avoid risk
Incorrect Packaging - Customers need a website, but the company created an iOS app instead
Incorrect Pricing - Customers need SaaS pricing, but the company created a shrink wrapped, on-premise solution with CapEx and maintenance agreements instead
I have appropriated from Brian Eno and others the distinction between architecture and gardening, and have described my blog as a kind of garden. But lately I’ve been revisiting the architecture/gardening distinction and I have come to think that there is something architectural about writing a blog, or can be – but not in the sense of a typical architectural project, which is designed in advanced and built to specifications. Rather, writing a blog over a period of years is something like building the Watts Towers.
Simon Rodi didn’t have a plan, didn’t even have a purpose: he just started building. His work was sustained and extended by bricolage, the acquisition and deployment of found objects – and not just any objects, but objects that the world had discarded as useless, as filth. You put something in here, then something else, you discover, fits there … over time you get something big and with a discernible shape. Not the regular shape envisioned in architectural drawings, but nevertheless something that can be pleasing or at least interesting to look at – an organic and irregular shape. A geometry of irregular forms.