# Design Principles All of the ideas and practices presented in this book have been tested against the following ideas. ## Beginners Mind The world which has shaped many of our assumptions about organising is rapidly disappearing. We need to consciously reconnect with first principles and design organising systems adapted for todays world. Forget about legal structures, finances, brands and departments. What naturally unfolds when we start with living systems, people and purpose? Forget the concept of an organisation and embrace dynamic and interconnected networks. We do not build organisations, we design organising systems. ## Simple and Intuitive Imagine sitting down with someone new to this work and explaining an organising system to them. We use language that they are familiar and comfortable with and new terms are only introduced when absolutely necessary. In less than 15 minutes a new user should have all the new concepts they need to naturally explore the organising system with ease. ## Fractal Unfolding Our organising systems should resemble fractals where a small number of simple patterns can be applied at different scales to create structures of complex beauty. Coplexity should be emergent and not inherrant. ## Systemic Health Our organising systems are not separate from the world but connected with it. They recognise this interconnection and naturally tend towards health and wellbeing at every level. ## Embedded in culture and software The technology we use deeply shapes the way we organise. Likewise software without culture is a lifeless system. To design organising systems we need to consider both the human and technical components. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://enspiral.gitbook.io/os-draft/en/design_principles.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.