Every programmer ever born thinks whatever idea just popped out of their head into their editor is the most generalized, most flexible, most one-size-fits all solution that has ever been conceived. We think we’ve built software that is a general purpose solution to some set of problems, but we are almost always wrong. It is three times as difficult to build reusable components as single use components, and a reusable component should be tried out in three different applications before it will be sufficiently general to accept into a reuse library.

Many things in this organization operate in siloes - business functions, business processes, IT applications, infrastructure teams etc - it’s the nature of organizations. However, this can add cost, complexity, and risk because different teams go in different directions, duplicating things or conflicting with each other - IT is not aligned with the business, or the business itself is not aligned. In addition, each team / silo is naturally incented to make decisions that are best for them, but not necessarily best for the org as a whole - who is looking at the overall big picture?