Satir workshops

The experiential patterns we have gathered so far for working with mandala architectures (for a more buddhistic perspective please read “Metaphor, Architecture and XP” by David West)

• A mandala is to enhance for the project helpful communication.Its purpose is to make applicable words, phrases, stories and images pop up in your mind while building the system and solving problems to make it happen.
• The mandala is to support creating feedback loops and trust between stakeholders – real change comes from within.
• To effectively encapsulate the Unknown and allow fast recovery from failures, a mandala must be simple to create, without special skills or extensive knowledge of modelling syntax, so all stakeholders can easily modify it.
• The mandala is to be visible and available as artefact with shared ownership by all stakeholders involved to make emotional attachment to the process possible.
• As a result, if the mandala is not a joy to make and maintain, you can perceive such as a sure sign you need to investigate what is actually happening.
• A mandala can capture state or time in order to provide the project and business management process with feedback in support of explicit and actual trade off of pressures working on the system.
• To enhance the carrying capacity of the system a mandala is to invoke feelings of courageousness for the stakeholders. Such feelings of courageousness are only likely to occur if icons and their placing on the mandala effectively facilitate problem solving.
• Mandalas must be perceived as a tool, not a means. An effective mandala can only be built and maintained within the context it serves, and by its involved stakeholders.