Over a million developers have joined DZone.

Complexity Everywhere

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

SpoonErnst & Young recently “discovered” that employees will resort to corruption and fraud when they are squeezed by management. Or, in other words, when you treat them unethically they will behave unethically.

Surprise, surprise!

It is hard to count the number of similar discoveries people have made over time. Patrick Hoverstadt, author of The Fractal Organization, wrote that Theory-X managers get constant feedback that their world-view is correct. They treat employees as people who cannot be trusted. Et voilà, the result is indeed that nobody can be trusted! You get what you measure! (Goodheart’s Law). Ralph Stacey, author of Complexity and Management, called it reflexivity. There is no objective observer.

The observer influences the system, and the system influences the observer.

This makes it all the more strange that some complexity thinkers aim to provide a framework for dealing with different kinds of systems. If the observer judges the system to be “complicated” then he should apply “Sense-Analyze-Respond”, and if the observer thinks the system is “complex” then she should use “Probe-Sense-Respond”.

Sorry, but that just doesn’t make much sense to me when I take into account reflexivity and the influence of observers. Because maybe, when I treat a complex system as simple, this is exactly how it will behave to me. Or when I judge the system to be chaotic, this could indeed be how it will respond, but only because that's how I treat it. The way I treat the system will influence how it behaves. The observer influences the system. For example, why bother deciding if the behavior of a system is chaotic? Simply the act of ignoring chaos could make it go away! Problem solved. (It could also blow up in your face. You just can’t predict the cascading effects of your actions.)

It’s much easier just to assume complexity everywhere.

You can always reduce the universe to a few domains or categories later. When you have time, over a cup of coffee. With a delicious slice of Welsh tea cake, as I just enjoyed.

(image by Jonathan Lidbeck)

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.


Published at DZone with permission of Jurgen Appelo. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}