System archetypesThis is a featured page

Archetypes consist of causal loop diagrams and are depicting typical and problematic system structures. In systems thinking literature, quite a number of such archetypes are described. Let us start by an example in order to understand better what archetypes are: Think about what happened during the cold war, when the USA increased its weapons stockpile in order to increase security. This actually led to a decrease in security for all, as an arms race in nuclear weapons developed. Such a problematic system structure is called escalation and it means that two balancing loops interact in a way that creates a single reinforcing loop.

The arms race - escalation archetype
Example taken from: Continuous Improvement Associates, Systems Thinking Archetypes, p. 7 <http://www.exponentialimprovement.com/cms/uploads/ArchetypesGeneric02.pdf> (accessed 13 August 2009)


Archetypes can be useful when you want to answer the question: “Why is the same problem occurring over and over again over time?” With using archetypes you can gain insight into the nature of the underlying problem. But archetypes are generic in nature and thereby do often not pay attention to all important variables. Archetypes therefore provide more of a starting point for a further development of a model.


For more information about archetypes and examples, please refer to:






chachabooth
chachabooth
Latest page update: made by chachabooth , Aug 14 2009, 9:17 AM EDT (about this update About This Update chachabooth Edited by chachabooth

242 words added
1 image added

view changes

- complete history)
Keyword tags: None (edit keyword tags)
More Info: links to this page

Anonymous  (Get credit for your thread)


There are no threads for this page.  Be the first to start a new thread.