There is good complexity and bad complexity. Bad complexity includes infrastructure that has redundant components, that is, multiple types of components to provide the same service. This was addressed in the article. Good complexity includes:
1. business features that are useful and used, 2.infrastructure that is more complex to improve flexibility, scalability and agility
Both bad and good complexity need business case justification because both will cost money to implement. Bad complexity will need to show a realistic reduction in cost or risk to be funded. This is typically an IT department project or program. Good complexity will require a positive impact on a business function or process that will increase revenue or decrease cost or provide intangible benefits such as flexibility, scalability and agility which are future benefits.
So the drivers of bad complexity and ownership of the problem are often different. Be careful how you approach each of these very different issues.
BK