



![]() | Choosing an archetype. You start by making guesses. You | |
| may have to trust your intuition at first. Some people worry that they will apply the “wrong” archetype, misdiagnose the problem and make things worse. In practice, this doesn’t happen, because by definition, people initially pick archetypes that hold interest for them. The fact that they are interested in one particular systems story is a clue that it probably applies, at least enough to start there. | ||
![]() | Keep alert for the archetype stories which seem to run | |
| analogously to your own story. Generalizing your story – omit details to simplify it and looking at it from a more distant perspective – can help you place it. |
![]() | One good clue is finding a pattern of performance that seems | |
| to sum up the behaviour of the archetype | ||
![]() | Add your elements to the story. Start with the core loop that | |
| seems to drive the behaviour of the system. This loop often closely matches the pattern of behaviour over time, and often depict what people in the system are paying the most attention to. | ||
![]() | Work around the structure. About each element, ask: What’ | |
| s causing changes in this element? What influences it to vary? Or if you get stuck, try working forward: What is the effect when this variable changes? What other elements must change? If you still get stuck, go back to the story. Are there key elements which you have left out? Where do they link to the archetypes? | ||
![]() | It’s particularly valuable to include any elements which are at | |
| least partly under your influence: if you can change the relationship of your organisation with the customers, seeing that element as part of a vicious cycle may lead to insights about how you can influence the whole system. | ||
![]() | When you have applied an archetype, check the patterns of | |
| behaviour you would expect to see. Does it match the patterns you have seen in your own history? |
