The system trap called "Shifting the burden to the intervenor", also called addiction or dependence, is a very  interesting anti-pattern, but one that can also be extremely challenging to identify and work with. However, leaving this anti-pattern unchecked can easily lead to unexpected, catastrophic failure. It's worth noting that a

One anti-pattern from systems thinking we have probably all seen in action is perverse incentives. But yet, we seem to fall for this one over and over again. Perverse incentives is what happens when you try to stimulate a system to achieve a certain goal by giving incentives towards that

One of the things I learnt from the "Thinking in Systems: A Primer" book by Donella Meadows is a thing called suboptimization. I choose to call this an anti-pattern as it's a behavior you can frequently observe in systems, and one I think more people should be aware of. So

Coming out of Dave Snowden's 2 day workshop on Complexity-Based Design Thinking [https://training.dddeurope.com/complexity-based-design-thinking/] at DDDEurope 2019 [https://dddeurope.com/2019/], it's easy to get many thoughts spinning in your head, and it definitely takes time to reflect on the dense knowlegde taken in over just 2

After learning about the Cynefin Framework [https://hbr.org/2007/11/a-leaders-framework-for-decision-making] at the DDDEurope [https://dddeurope.com/2018/] conference earlier this year, it's been interesting to utilize the framework to try and make sense of observations at work. I've long been very interested in the DevOps movement (like most

Disclaimer: This is actually not based on science, just personal observation and opinion. Having worked in a large organization for almost 4 years now, I've (naturally) observed a lot of office and organization politics, both from technical people (developers, architects, etc) and people with a more business-oriented background. A recurring