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 &#x27;enterprise software&#x27;. This is why so much of it is so bad (sometimes in trivial, easy to change ways), why it&#x27;s typically so expensive, and why it sometimes so narrowly satisfies stated requirements that it creates whole new problems for the organization.<p>Silo-ing as an organizational principle almost always goes wrong and what you end up with is a stovepipe organization.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Stovepipe_(organisation)" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Stovepipe_(organisation)</a>