View profile

🦉 10x curiosity - Using system archetypes to shortcut problem solving

Revue
 
 

🦉 10x curiosity

August 15 · Issue #221 · View online

🦉 A weekly sample of links that made me think 🤔


Thinking…
This is an abridged version of a post on my 10x Curiosity blog
Systems thinking is a powerful way of viewing the world that I have just begun to explore. It provides perspective that takes into account more of the complexity and interactions of real world issues when compared to other forms of problem solving tools, such as root cause analysis (RCA). That complexity involves reinforcing and balancing loops, input and delays, all of which can create counter intuitive outcomes, often at odds to the original desired result especially when looked at over different time scales.
Peter Senge writes in “The Fifth Discipline”
“From an early age we are taught to break apart problems, to fragment the world. This apparently makes complex tasks and subjects more manageable, but we pay a hidden, enormous price. We can no longer see the consequences of our actions: we lose our intrinsic sense of connection to a larger whole.”
System Archetypes are behavioral patterns that can occur in different setting but with common fundamental structures. Being able to spot these patterns allows you to apply pressure at high levels of influence, improving the chance of an effective outcome. As these patterns are similar, despite occurring across a wide range of process settings, understanding what works well in one setting, can be frequently be applied across other settings, both in time and context.
This is a classic example of building on mental models that are generic in nature to solve many seemingly unrelated problems, and provide a very powerful tool to have in your problem solving tool kit.
The theory behind system archetypes is that situations with unwanted results or side effects can be mapped to the common behavior models. Given the knowledge available about system archetypes, problem solvers, in general, can apply its principles and arrive at a rich diagnosis of a situation and plan a recovery. The knowledge base on system archetypes provides guidelines for determining what archetype is at play and, once identified, how to approach an intervention.
Kim explains in his excellent summary:
The archetypes consist of different combinations of reinforcing and balancing loops, and when applied to business problems, can yield insight into the struc- ture at work and reveal possible high-leverage interventions
Organizations can use the archetypes to become more effective at tackling complex issues in at least three different ways.
  • First, the archetypes can be used as diagnostic tools for developing an understanding of a current situation.
  • Second, as planning tools, they can help us anticipate future consequences and for them.
  • Third, the archetypes can be used as theory-building tools to help build a growing body of knowledge about our understanding of the world.
  1. Fixes that fail — A solution is rapidly implemented to address the symptoms of an urgent problem. This quick fix sets into motion unintended consequences that are not evident at first but end up adding to the symptoms.
  2. Shifting the burden — A problem symptom is addressed by a short-term and a fundamental solution. The short-term solution produces side effects affecting the fundamental solution. As this occurs, the system’s attention shifts to the short-term solution or to the side effects.
  3. Limits to growth — A given effort initially generates positive performance. However, over time the effort reaches a constraint that slows down the overall performance no matter how much energy is applied.
  4. Drifting goals — As a gap between goal and actual performance is realized, the conscious decision is to lower the goal. The effect of this decision is a gradual decline in the system performance.
  5. Growth and underinvestment — Growth approaches a limit potentially avoidable with investments in capacity. However, a decision is made to not invest resulting in performance degradation, which results in the decline in demand validating the decision not to invest.
  6. Success to the successful — Two or more efforts compete for the same finite resources. The more successful effort gets a disproportionately larger allocation of the resources to the detriment of the others.
  7. Escalation — Parties take mutually threatening actions, which escalate their retaliation attempting to “one-up” each other.
  8. Tragedy of the commons — Multiple parties enjoying the benefits of a common resource do not pay attention to the effects they are having on the common resource. Eventually, this resource is exhausted resulting in the shutdown of the activities of all parties in the system.
Goodman and Kleiner in an article posted on “The Systems Thinker” have produced a family tree of Archetypes to help work through which one is most useful for a given situation.

Archetype family Tree - (Goodman & Kleiner)
Archetype family Tree - (Goodman & Kleiner)
In a future post I plan to look into the places to intervene in a system.
Further reading and references
Let me know what you think? I’d love your feedback. If you haven’t already then sign up for a weekly dose just like this.
You might also like:
  • Boundaries of failure — Rasmussen’s model of how accidents happen.
  • Systems Archetypes- Places to intervene — An advantage with using systems archetypes as a problem solving methodology is that places to intervene in the system can be thought through and played with.
  • Swarm Intelligence — Can managers develop simple rules to shape the behaviour of their organizations and replace rigid command-and-control structures?
  • Kanban your work — The Kanban method is in the Agile suite of tools that can help you visualise and prioritise work.
Links that made me think...
A radically different approach to clarifying roles in a matrix setup
The Art and Science of Tripping Up the Stairs
How the Army plans to use Microsoft's high-tech HoloLens goggles on the battlefield
Why Cutting Costs is Expensive: How $9/Hour Software Engineers Cost Boeing Billions
this is why we fly.... Coming into land in Queenstown NZ through clouds
Did you enjoy this issue?
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue