Biomimetics 12 Insights
Theory
Patterns and pattern language are seductively simple concepts on the surface. It is only through trying to write patterns that the richness, depth and detail required to develop useful patterns become clear. Practical guidance on developing pattern languages proved difficult to find. Examples of pattern languages often take quite different approaches from the original Alexandrian Pattern Language, and the rationale for these differences is not always obvious. Most pattern languages are are only presented in their final form. Significant time needs to be allocated so that all participants can fully understand the nuances of patterns and pattern language. 'Learning by doing' seems to have been the best approach in this context, along with frequent discussions to explore the finer details and to develop a consensus.
Good patterns are devilishly difficult to write. In hindsight, the scope of the project was far too broad and ambitious, given the information and resources available. Nevertheless, applying the rigor of the patterns process to deepen our understanding of ecosystem principles has already delivered worthwhile insights. One of the benefits of the patterns approach is that even preliminary results can be useful. For example, a team member has commented that the discussions on the ecosystem principles have helped her develop a more comprehensive and insightful model for a resource handbook she is developing.
Project Evolution
The team started looking at 'pattern language' as a tool or a method to solve a specific problem: how can we organize, communicate, and make biological information available to disciplines outside of biology? We recognized early in the project the importance of thinking in terms of systems, with natural and societal systems forming a continuum. We also questioned whether it was appropriate to talk about 'solutions to problems' - did it make more sense to talk about current and future states?
The complexity and uncertainty of working with self organizing systems suggests pattern languages could be a useful tool to capture the current 'state of knowledge' as well as the gaps in that knowledge. This would not only help practitioners apply the knowledge but also set realistic expectations through awareness of the limitations and boundaries of that knowledge. Such a framework would also encourage research to close the gaps and act as a 'working document' to collect and communicate additional knowledge, tools and methods as they become available.
A pattern language may also prove to be more amenable to the kind of dynamic design process that Kay describes. [35] Patterns encourage practitioners to think about the problem itself, rather than jumping immediately into finding a solution. The multi-scale aspect of pattern languages helps practitioners look at how their solutions 'fit' within the larger context, while the communication and collaboration aspects helps them work with multiple stakeholders.
Implications for Design
At an abstract level, the existing design process is compatible with the concepts of systems thinking: we will still identified goals, develop concepts, attempt to embody them and test prototypes, iterating the cycle as required. Applying principles from ecosystems will change and add to the list of goals that designers, developers and manufacturers set for their products and services. The bounds of systems analyzed in the design phase will likely expand and designers will take greater interest in hierarchical levels above and below the level occupied by the product or service.
In practice, the changes will likely be more wide reaching. Kay argues that "We can no longer treat our designs as mechanical clock work edifices designed to withstand the test of time." [35] Design is no longer seen as finding a 'right' solution to a problem, but rather a process for evolving the design to meet changing needs and conditions. Instead of static solutions, we need to develop dynamic processes. The implication is that designers will remain involved with their designs beyond what is normally considered the end of a traditional design engagement.
Kay believes that designs must be more adaptive, which implies both gathering of information and acting upon that information. In architecture, Post-Occupancy Reviews our discovering that the interaction between facilities management, occupants and buildings can be dramatically different from design predictions. Buildings are now being designed with extensive monitoring capabilities. This information can be used to tune the building, provide additional information to the users, and review building design models.
Kay argues that "Central to the design process is the activity of making trade-offs. Choosing between alternatives usually comes down to people's values. ... ethics and values must be incorporated into any discussion, if for no other reason than trade-offs between sustainable livelihoods and ecological integrity will have to be made." [35] Just as designs need to fit within the natural ecosystem, they also need to fit within the societal ecosystem, with all of its stakeholders. Kay recommends designers:
- identify the players and their issues
- build a systems description of the situation
- develop an ongoing adaptive management strategy
- implement a governance structure
The wider scope of the design process puts a greater emphasis on collaboration and communication. designers will need to tap into diverse perspectives that approach the design challenge from different temporal and spatial scales. Designers may rely more extensively on narratives and scenarios to capture a richer range of possibilities that existing design tools. By being simple and able to capture complex ideas, loosely structured yet providing a strong process, and capable of handing both 'hard' and 'soft' information, pattern languages can provide a powerful framework to help practitioners develop better and more sustainable designs.
