In the previous post of this series I started to discuss drivers on the project level that lead to accidental complexity regarding unnecessary requirements that do not add any value to the solution.

In the previous post of this series I discussed some drivers on the company level that (among other things) cause a lot of accidental complexity in IT. The drivers were not understanding IT and its role today.

In the previous post of this series, we looked at post-industrial markets and digital transformation as external market-based drivers that create pressure on companies and their IT departments. We also have seen how not understanding these drivers usually leads to counter-productive responses that ultimately make things worse instead better.

In the previous post, we looked at the different types of accidental complexity that help us to identify the places where to look for unnecessary complexity.

In the previous post, I discussed the difference between essential and accidental complexity. While we cannot avoid the essential complexity of a given problem, accidental complexity makes things unnecessarily harder without adding any value to the solution.