Keep it general and straightforward when using archetypes or classical stories in systems thought. If the community wants to know more about an archetype, then you can go into more specifics.
Do not attempt to “sell” archetypes; once people see the similarities between archetypes and their problems for themselves, they will understand more. Nevertheless, you should seek to demystify the archetypes by connecting them to shared interactions that we all share.
How Do We Know That We’ve “Got It”?
Here is how you can tell you that you have had a handle on systems thinking:
• You ask different types of questions, then you have previously asked.
• You hear “catchphrases” raising flags of caution. For example, if anyone says: “We need more (sales, revenue), the question is that we need more.”
• You start noticing archetypes and balancing and reinforcing processes in stories you hear or read.
• You’re looking at visual models (both your own and others’ versions).
• You know the leverage points for classic stories about structures.
When you have started using devices that are designed for investigations and diagnostic purposes, you may want to move towards more complicated models of system accumulator and flow diagrams, flight simulators, or simulation software. Alternatively, you can find that taking a system-thinking approach and using causal loop diagrams provide you with ample insights to tackle problems. Nevertheless, cognitive processes will also change the way you think about the environment and solve problems.
Your article helped me a lot, is there any more related content? Thanks!