Design anti-pattern: Tightly coupling infrastructure to org structure

The Anti-Pattern

This came up recently for me following a rather large company-wide re-org under several new business units. One of the teams wanted to split their tools so that each business unit would have their own separate instance. At first this seemed like a good idea: the benefits would provide better accountability for how each business unit/cost center were managing their costs with that tool, and each would have the agency to re-configure their instance as they see fit without worrying about impacting the other business units. Unfortunately, this approach doesn’t quite pan out that way in reality.

A better design pattern

The problem that was meant to be solved in the first place is one of financial accountability in order to reduce costs and increase efficiency. Unfortunately, doing so by splitting infrastructure across business units can often lead to the opposite result.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store