Unintended Consequences in Complex Systems
In complex socio-technical systems, every interaction and intervention inevitably generates unintended consequences. To manage these, interventions must be small, safe-to-fail, and coupled with dampening strategies, while embracing serendipitous positive outcomes.
THE IDEA
On unintended consequences
We can also never forget that complex systems are open systems; whenever we interact with them, we become part of that system. The systems we deal with are typically complex socio-technical systems, and in these systems, there is no such thing as an independent or neutral observer or consultant. When we enter a system, we become part of it; its dynamics influence us, and in turn, it changes in response to our presence. A team is not the same once a coach arrives, even if all that person does is observe. When a consultant turns up, the system changes. New connections and meanings form that change prevailing systemic patterns in unpredictable ways. Because of this, every diagnostic is an intervention, and every intervention is a diagnostic (if we are situationally aware).
In complex systems as well, despite our best efforts, there will be unintended consequences flowing from our interactions with the system. We mitigate these by keeping our interventions small and safe-to-fail, and ensuring that we have dampening strategies in place should unintended negative consequences arise. Sometimes these may be ‘helpful accidents,’ and when these happen, we embrace serendipity and attempt to amplify them. The fundamental principle here is to understand that there will be consequences, because we know that they are our responsibility to manage.
People in a particular system generally have in-depth contextual knowledge, but they may have been part of the system for so long that they no longer see what’s right in front of them. Leaders often got to be in their influential positions because they were the best competitors in the old paradigm. It is hard for people to face the idea that the knowledge and skills that brought them this far in their careers may have become detrimental. When we enter these systems as change agents, it is best to cultivate a thick skin as we will encounter defensiveness when we challenge customers’ long-held beliefs and ‘best practices.’
I’ve learned to be wary of the subtle, and not-so-subtle, ways the system often attempts to seduce me into colluding with some of its dysfunctional dynamics. This is where it can be beneficial to have a thinking partner or coach, or even to be part of a professional reflection group that can help keep us honest and force us to look in the mirror ourselves. One of the critical things to remember here is that we cannot force another person or a system to change. Our role is to help people see and think differently, be a mirror, challenge, and sometimes teach, mentor, and introduce new tools and methods. But in the end, we can’t control what happens regarding their gains in the process. The famous Biblical parable of the sower applies here. We sow seeds, some fall on fertile ground, others on impenetrable soil, and yet others sprout but get overgrown by weeds. Our responsibility is to keep sowing the seeds, that is all we have control over.
When to use it
A manager implementing a new performance review system should anticipate unintended effects on team morale and collaboration. Small pilots and dampening strategies can reduce backlash.
A policy maker designing a new regulation should consider feedback loops and unintended consequences, such as black markets or reduced compliance, and use safe-to-fail experiments.
A coach entering a team should be aware that their presence changes dynamics; they must remain reflective and use their observations as diagnostic interventions.
A software developer introducing a new feature should monitor for unexpected usage patterns and be ready to amplify helpful accidents or dampen harmful ones.
FROM THEORY TO EVERYDAY LIFE
In practice
Consultant as observer
A consultant is hired to improve team performance. By merely observing, the team dynamics shift as members become self-conscious or form new alliances. The consultant’s presence becomes an intervention, and the diagnostic itself alters the system.
New software tool introduction
Introducing a new software tool in an organization creates unintended workflows and resistances. Employees may work around the tool, adopt it in unexpected ways, or experience decreased productivity before improvement. Small, safe-to-fail pilot tests help mitigate negative consequences.
A MOMENT TO REFLECT
Put it to work.
Recall a recent change you initiated in a group or organization. What unintended consequences emerged, and how did you respond?
How can you design your next intervention to be smaller and safer to fail, while still gathering useful feedback?
In what ways do you become part of the system when you attempt to diagnose or change it? How does that influence your objectivity?
CONTINUE THE CONVERSATION
Source texts
- Cynefin - Weaving Sense-Making into the Fabric of Our World ED02 (Dave Snowden Sonja Blignaut Zhen Goh)