Any leading staff, if not the most responsible individual, in an organization decides if it follows either policy, favorable inclination of end-users to a certain product or service or a direction from management which is different from the views of the others. Then there is the preference of a vendor, if not the only factor that's been considered.
Every proven policy is vague for every new project.
Such inclination to a product/service, even a best practice, is detrimental.
Such management direction is unhelpful.
On top of it all during the acquisition period, no matter the size of a certain, if not just one of the forms in a bigger, project plan, the responsibility within the acquiring organization must be muzzy. Or the responsible individual lacks the role and know-how about the project's practical application and business value, first for the end-users, and the entire organization's operational requirement. This must have been elucidated before bringing in any vendor.
Whatever the project's purpose, it's been broken from the start. Even if every option above had been used together in the decision making, it would still be a busted project.
With this only approach, employed throughout, everything is now on sensitive to erratic performance, the need to increase resources and staff, planned budget turned to be a stream of requital which extended beyond customer-vendor transaction, including but not limited to cyberattacks.
Comments