Yes; exactly. Silo-ing in large companies where software acquisition, software deployment, and software use are separate functions in the organization is probab

Yes; exactly. Silo-ing in large companies where software acquisition, software deployment, and software use are separate functions in the organization is probably the defining influence on 'enterprise software'. This is why so much of it is so bad (sometimes in trivial, easy to change ways), why it's typically so expensive, and why it sometimes so narrowly satisfies stated requirements that it creates whole new problems for the organization. Silo-ing as an organizational principle almost always goes wrong and what you end up with is a stovepipe organization. https://en.wikipedia.org/wiki/Stovepipe_(organisation) https://en.wikipedia.org/wiki/Stovepipe_(organisation)